3 Replies Latest reply on Nov 30, 2006 12:06 PM by Jesse Saletan

    Recent Windows update might have broke my jboss  - JNDI erro

    Brian McGovern Newbie

      Lastnight windoz updated my machine. Jboss was workign perfectly last night.. now.. many many errors related to JNDI .. snippet pasted below. Im at a stand still can anyone help?

      =========================================================================
      
       JBoss Bootstrap Environment
      
       JBOSS_HOME: c:\Program Files\jboss-portal-2.4.0
      
       JAVA: /cygdrive/c/Program Files/Java/jdk1.5.0_06/bin/java
      
       JAVA_OPTS: -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dprogram.name=run.sh
      
       CLASSPATH: c:\Program Files\jboss-portal-2.4.0\bin\run.jar;c:\Program Files\Java\jdk1.5.0_06\lib\tools.jar
      
      =========================================================================
      
      11:18:19,500 INFO [Server] Starting JBoss (MX MicroKernel)...
      11:18:19,515 INFO [Server] Release ID: JBoss [Zion] 4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)
      11:18:19,515 INFO [Server] Home Dir: C:\Program Files\jboss-portal-2.4.0
      11:18:19,515 INFO [Server] Home URL: file:/C:/Program Files/jboss-portal-2.4.0/
      11:18:19,515 INFO [Server] Patch URL: null
      11:18:19,515 INFO [Server] Server Name: default
      11:18:19,515 INFO [Server] Server Home Dir: C:\Program Files\jboss-portal-2.4.0\server\default
      11:18:19,515 INFO [Server] Server Home URL: file:/C:/Program Files/jboss-portal-2.4.0/server/default/
      11:18:19,515 INFO [Server] Server Log Dir: C:\Program Files\jboss-portal-2.4.0\server\default\log
      11:18:19,515 INFO [Server] Server Temp Dir: C:\Program Files\jboss-portal-2.4.0\server\default\tmp
      11:18:19,515 INFO [Server] Root Deployment Filename: jboss-service.xml
      11:18:20,375 INFO [ServerInfo] Java version: 1.5.0_06,Sun Microsystems Inc.
      11:18:20,375 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_06-b05,Sun Microsystems Inc.
      11:18:20,375 INFO [ServerInfo] OS-System: Windows 2000 5.0,x86
      11:18:21,484 INFO [Server] Core system initialized
      11:18:27,140 INFO [WebService] Using RMI server codebase: http://BERYLLIUM2:8083/
      11:18:27,171 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
      11:18:28,015 WARN [ServiceController] Problem starting service jboss:service=Naming
      java.rmi.server.ExportException: Port already in use: 1098; nested exception is:
       java.net.BindException: Address already in use: JVM_Bind
       at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:243)
       at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:178)
       at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
       at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
       at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:180)
       at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:293)
       at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:256)
       at org.jnp.server.Main.initJnpInvoker(Main.java:314)
       at org.jnp.server.Main.start(Main.java:277)
       at org.jboss.naming.NamingService.startService(NamingService.java:236)
       at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
       at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
       at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
       at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
       at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
       at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
       at $Proxy0.start(Unknown Source)
       at org.jboss.system.ServiceController.start(ServiceController.java:417)
       at org.jboss.system.ServiceController.start(ServiceController.java:435)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
       at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
       at $Proxy4.start(Unknown Source)
       at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
       at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
       at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
       at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
       at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
       at $Proxy5.deploy(Unknown Source)
       at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
       at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
       at org.jboss.Main.boot(Main.java:200)
       at org.jboss.Main$1.run(Main.java:464)
       at java.lang.Thread.run(Thread.java:595)
      Caused by: java.net.BindException: Address already in use: JVM_Bind
       at java.net.PlainSocketImpl.socketBind(Native Method)
       at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
       at java.net.ServerSocket.bind(ServerSocket.java:319)
       at java.net.ServerSocket.<init>(ServerSocket.java:185)
       at org.jboss.net.sockets.DefaultSocketFactory.createServerSocket(DefaultSocketFactory.java:120)
       at org.jboss.net.sockets.DefaultSocketFactory.createServerSocket(DefaultSocketFactory.java:95)
       at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:622)
       at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:231)
       ... 61 more
      11:18:36,984 INFO [AspectDeployer] Deployed AOP: file:/C:/Program Files/jboss-portal-2.4.0/server/default/deploy/jboss-portal.sar/portal-aop.xml
      11:18:46,296 INFO [Embedded] Catalina naming disabled
      11:18:46,390 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rule set.
      11:18:46,406 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rule set.
      11:18:47,515 INFO [Http11BaseProtocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
      11:18:47,531 INFO [Catalina] Initialization processed in 1125 ms
      11:18:47,531 INFO [StandardService] Starting service jboss.web
      11:18:47,531 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.17
      11:18:47,609 INFO [StandardHost] XML validation disabled
      11:18:47,687 INFO [Catalina] Server startup in 156 ms
      11:18:47,953 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
      11:18:48,171 WARN [ServiceController] Problem starting service jboss.web.deployment:war=invoker.war,id=1948721705
      org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.naming.NameNotFoundException: comp not bound)
       at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:380)
       at org.jboss.web.WebModule.startModule(WebModule.java:83)
       at org.jboss.web.WebModule.startService(WebModule.java:61)
       at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
       at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
       at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
       at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
       at $Proxy0.start(Unknown Source)
       at org.jboss.system.ServiceController.start(ServiceController.java:417)
       at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
       at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
       at $Proxy92.start(Unknown Source)
       at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
       at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
       at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
       at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
       at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
       at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
       at $Proxy93.start(Unknown Source)
       at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
       at org.jboss.deployment.MainDeployer.addDeployer(MainDeployer.java:368)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
      


        • 1. Re: Recent Windows update might have broke my jboss  - JNDI
          Peter Johnson Master

          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. Socking at first but expected since MS bought Winternals.]

          • 2. Re: Recent Windows update might have broke my jboss  - JNDI
            Brian McGovern Newbie

            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.

            -

            • 3. Re: Recent Windows update might have broke my jboss  - JNDI
              Jesse Saletan Newbie

              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 adept at interpreting the logs so it's hard for me to say exactly what the problem was. I'm curious if anyone else has had this problem and if there's a better solution than not patching.

              Thanks,
              Jesse