3 Replies Latest reply on Feb 2, 2008 7:48 PM by ewinston

    Connection timed out

    sven.waibel
    sven.waibel Jan 31, 2008 5:40 AM

      Hi,

      i got an exception while deploying my ear.
      I saw that the same problem is a resolved bug, but i got it in jboss 4.2.2 again.


      11:36:19,057 INFO [NativeServerConfig] JBoss Web Services - Native
11:36:19,059 INFO [NativeServerConfig] jbossws-native-2.0.3.GA (build=200801251318)
11:36:20,125 INFO [Embedded] Catalina naming disabled
11:36:20,312 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /opt/ibm/java2-i386-50/jre/bin:/opt/ibm/java2-i386-50/jre/bin/j9vm:/opt/ibm/java2-i386-50/jre/bin:/usr/lib
11:36:20,393 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-9619
11:36:20,394 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-9409
11:36:20,395 INFO [Catalina] Initialization processed in 269 ms
11:36:20,395 INFO [StandardService] Starting service jboss.web
11:36:20,398 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA


      Here the exception: 

      javax.xml.ws.WebServiceException: org.dom4j.DocumentException: Connection timed out Nested exception: Connection timed out
 at org.jboss.wsf.container.jboss42.WebXMLRewriterImpl.rewriteWebXml(WebXMLRewriterImpl.java:95)
 at org.jboss.wsf.container.jboss42.ModifyWebMetaDataDeploymentAspect.create(ModifyWebMetaDataDeploymentAspect.java:53)
 at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
 at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
 at org.jboss.wsf.container.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:79)
 at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
 at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
 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 $Proxy45.create(Unknown Source)
 at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
 at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
 at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:615)
 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 $Proxy9.deploy(Unknown Source)
 at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
 at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
 at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
 at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:615)
 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.GeneratedMethodAccessor4.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:615)
 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:1025)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:615)
 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:508)
 at java.lang.Thread.run(Thread.java:797)
Caused by:
org.dom4j.DocumentException: Connection timed out Nested exception: Connection timed out
 at org.dom4j.io.SAXReader.read(SAXReader.java:484)
 at org.dom4j.io.SAXReader.read(SAXReader.java:343)
 at org.jboss.wsf.container.jboss42.WebXMLRewriterImpl.rewriteWebXml(WebXMLRewriterImpl.java:108)
 at org.jboss.wsf.container.jboss42.WebXMLRewriterImpl.rewriteWebXml(WebXMLRewriterImpl.java:87)
 ... 80 more


      Any suggestions?

      Thanks
      Sven

      • 3560 Views
      • Tags:
        • 1. Re: Connection timed out
          ewinston Jan 31, 2008 9:52 PM (in response to sven.waibel)

          I have seen this problem. It is happening because JBoss cannot get out to validate an xml file. If you are behnd a firewall this can cause it.

          I got past this by passing the following parameters to JBoss 5.

          -Dhttp.proxyHost=x.x.x.x -Dhttp.proxyPort=yyyy


          where x.x.x.x is the hostname of your proxy, and yyyy is the port.

          I am thinking it may still work with 4.2.2.

          Good luck,
          Edward

            • Actions
          • 2. Re: Connection timed out
            sven.waibel
            sven.waibel Feb 1, 2008 1:36 AM (in response to sven.waibel)

            That could be one solution, but the server has no access to the internet.

            Thanks
            Sven

              • Actions
            • 3. Re: Connection timed out
              ewinston Feb 2, 2008 7:48 PM (in response to sven.waibel)

              Ok, then that is a problem I am running into as well.

              You have an xml file somewhere that is getting read by JBoss that has the DTD or schema specification in it. JBoss is supposed to validate against local files but it doesn't appear to (again, this is with 5.0), instead it tries to pull the file from the net.

              Since there is no access it will never work. The only solution I have found is to comment out the DTD or schema specification in the xml file (one of the deployment descriptors) and then try again. JBoss should then just accept the file and not try to validate against anything.

              This solution works for me when deploying a datasource that has the dtd defined when I am not connected to the network.

              Edward

                • Actions