That wasnt the problem. But good tip. Some process was holding that port but it had been for weeks, and Jboss still ran fine. The JNDI problem was because for some reason windows update of MSXML 4.0 Security Update released on November 14th, hijacked the jboss's ability to read any service xml files. Uninstalling the update corrected the problem immediately. Lets all have a nice big hand for microsoft -- for the win. - View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986649#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...