[jboss-user] [JNDI/Naming/Network] - Re: Recent Windows update might have broke my jboss - JNDI

2006-11-30 Thread jsaletan
I'm running JBoss 3.2.5 and Tomcat 5.0 on Windows 2003 and after the latest round of MS updates my application (Adobe LiveCycle Policy Server) stopped working. After I uninstalled KB924191 which is the MSXML 4.0 security update it started working again. I'm pretty new to JBoss and am not

[jboss-user] [JNDI/Naming/Network] - Re: Recent Windows update might have broke my jboss - JNDI

2006-11-16 Thread PeterJ
Some other process is already using port 1098. Find out what it is and stop it. To find out, either use netstat or better yet, use TcpView from www.sysinternals.com (look under networking tools). [Whoa, it has been about a month since I visited sysinternals and it has now been moved to MSDN.

[jboss-user] [JNDI/Naming/Network] - Re: Recent Windows update might have broke my jboss - JNDI

2006-11-16 Thread bmcgovern
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