14 Replies Latest reply on Oct 17, 2007 2:31 PM by Rob Stryker

    Failed to Start JBoss 4.2.0 Application Platform with JBoss

    flindet Newbie

      Can others confirm problems starting the JBoss 4.2.0 Application Platform (not to be confused with JBoss AS 4.2.0.GA) from JBoss Tools or am I just doing something silly?

      I created a server based on JBoss 4.2 in Eclipse with JBoss Tools installed from JBossTools-200707100855-nightly-ALL-linux-gtk.zip

      I can start JBoss 4.2.0 Application Platform from the command line just fine. I'm starting a server configuration based on "all".

      Trying to do the same thing in JBoss Tools results in:

      org.jgroups.ChannelException: failed to start protocol stack
       at org.jgroups.JChannel.connect(JChannel.java:389)
       at org.jboss.cache.TreeCache.startService(TreeCache.java:1536)
       at org.jboss.cache.aop.PojoCache.startService(PojoCache.java:94)
       at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
       at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
       at sun.reflect.GeneratedMethodAccessor12.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 $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 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 $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: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.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 $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: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:508)
       at java.lang.Thread.run(Thread.java:595)
      Caused by: java.lang.Exception: exception caused by UDP.start()
       at org.jgroups.stack.Protocol.handleSpecialDownEvent(Protocol.java:582)
       at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:496)
       at org.jgroups.stack.Protocol.passDown(Protocol.java:533)
       at org.jgroups.protocols.Discovery.down(Discovery.java:333)
       at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:499)
       at org.jgroups.stack.Protocol.passDown(Protocol.java:533)
       at org.jgroups.protocols.MERGE2.down(MERGE2.java:207)
       at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:499)
       at org.jgroups.stack.Protocol.passDown(Protocol.java:533)
       at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:408)
       at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:499)
       at org.jgroups.stack.Protocol.passDown(Protocol.java:533)
       at org.jgroups.protocols.FD.down(FD.java:339)
       at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:499)
       at org.jgroups.stack.Protocol.passDown(Protocol.java:533)
       at org.jgroups.stack.Protocol.down(Protocol.java:559)
       at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:499)
       at org.jgroups.stack.Protocol.passDown(Protocol.java:533)
       at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:480)
       at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:499)
       at org.jgroups.stack.Protocol.passDown(Protocol.java:533)
       at org.jgroups.protocols.UNICAST.down(UNICAST.java:391)
       at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:499)
       at org.jgroups.stack.Protocol.passDown(Protocol.java:533)
       at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:283)
       at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:499)
       at org.jgroups.stack.Protocol.passDown(Protocol.java:533)
       at org.jgroups.protocols.pbcast.GMS.down(GMS.java:837)
       at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:499)
       at org.jgroups.stack.Protocol.passDown(Protocol.java:533)
       at org.jgroups.protocols.FC.down(FC.java:377)
       at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:499)
       at org.jgroups.protocols.FC.receiveDownEvent(FC.java:368)
       at org.jgroups.stack.Protocol.passDown(Protocol.java:533)
       at org.jgroups.protocols.FRAG2.down(FRAG2.java:167)
       at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:499)
       at org.jgroups.stack.Protocol.passDown(Protocol.java:533)
       at org.jgroups.protocols.pbcast.STATE_TRANSFER.down(STATE_TRANSFER.java:294)
       at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:499)
       at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:390)
       at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:291)
       at org.jgroups.JChannel.connect(JChannel.java:386)
       ... 95 more
      Caused by: java.lang.Exception: problem creating sockets (bind_addr=/fe80:0:0:0:213:72ff:feb7:c71c%2, mcast_addr=null)
       at org.jgroups.protocols.UDP.start(UDP.java:372)
       at org.jgroups.stack.Protocol.handleSpecialDownEvent(Protocol.java:571)
       ... 136 more
      Caused by: java.net.BindException: Cannot assign requested address
       at java.net.PlainDatagramSocketImpl.bind0(Native Method)
       at java.net.PlainDatagramSocketImpl.bind(PlainDatagramSocketImpl.java:82)
       at java.net.DatagramSocket.bind(DatagramSocket.java:368)
       at java.net.DatagramSocket.<init>(DatagramSocket.java:210)
       at java.net.DatagramSocket.<init>(DatagramSocket.java:261)
       at org.jgroups.protocols.UDP.createEphemeralDatagramSocket(UDP.java:572)
       at org.jgroups.protocols.UDP.createSockets(UDP.java:436)
       at org.jgroups.protocols.UDP.start(UDP.java:367)
       ... 137 more


      Thanks.

        • 1. Re: Failed to Start JBoss 4.2.0 Application Platform with JB
          flindet Newbie

          Okay, I've found the wiki entry explaining issues with IPv6 on GNU/Linux.

          http://wiki.jboss.org/wiki/Wiki.jsp?page=IPv6

          I don't know why I'm not seeing this when starting from the command line and only when starting from Eclipse, but adding the following to my VM arguments in Eclipse did seem to help:

          -Djava.net.preferIPv4Stack=true


          However, I'm still not able to complete the start of the JBoss 4.2.0 Application Platform.

          I'm now using JBossTools-200707110856-nightly-ALL-linux-gtk
          I'm on openSUSE 10.2.

          09:02:42,493 INFO [ServerInfo] Java version: 1.5.0_10,Sun Microsystems Inc.
          09:02:42,518 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_10-b03,Sun Microsystems Inc.
          09:02:42,519 INFO [ServerInfo] OS-System: Linux 2.6.18.8-0.5-default,i386


          I receive the following Exception:

          2007-07-11 09:03:26,944 ERROR [org.jboss.deployment.MainDeployer] Could not start deployment: file:/usr/local/jboss-eap-4.2/jboss-as/server/production/conf/jboss-service.xml
          org.jboss.deployment.DeploymentException: start operation failed on package
          file:/usr/local/jboss-eap-4.2/jboss-as/server/production/conf/jboss-service.xml; - nested throwable: (java.util.ConcurrentModificationException)
           at org.jboss.deployment.SARDeployer.start(SARDeployer.java:311)
           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: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:508)
           at java.lang.Thread.run(Thread.java:595)
          Caused by: java.util.ConcurrentModificationException
           at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:449)
           at java.util.AbstractList$Itr.next(AbstractList.java:420)
           at org.jboss.deployment.SARDeployer.start(SARDeployer.java:299)
           ... 23 more


          • 2. Re: Failed to Start JBoss 4.2.0 Application Platform with JB
            Max Rydahl Andersen Master

            but that doesn't look like a ip6 issue ?

            its a different error.

            are you adding that vm argument to the command line when starting eclipse or in the launcher for jboss ?

            • 3. Re: Failed to Start JBoss 4.2.0 Application Platform with JB
              flindet Newbie

              Oh, well, the mystery is solved regarding why I only have to do the IPv4 trick in Eclipse. In run.sh there is:

              # Force IPv4 on Linux systems since IPv6 doesn't work correctly with jdk5 and lower
              if [ "$linux" = "true" ]; then
               JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true"
              fi


              Likely the answer to my other issues lies in this script then as well. Hmmm...

              • 4. Re: Failed to Start JBoss 4.2.0 Application Platform with JB
                Max Rydahl Andersen Master

                ooh - interesting.

                i've created jbide-576 for tracking this which we should see if we could handle more transparently.

                let us know if other issues pops up...

                • 5. Re: Failed to Start JBoss 4.2.0 Application Platform with JB
                  flindet Newbie

                  Max,

                  Thanks for creating the JIRA entry.

                  I'm adding the VM argument to the JBoss AS launcher. I've opened a JBoss Server View provided by JBoss Tools. I right-click on my server, edit launch configuration, then add the option to the VM arguments tab.

                  This got me past the IPv6 issue, but the issue mentioned above regarding jboss-service.xml still remains. Like the IPv6 issue, this issue occurs only when launching JBoss 4.2 Enterprise Application Platform from within Eclipse with JBoss Tools. Launching from command line with run.sh starts successfully with no errors.

                  I'm still looking for other interesting behavior in run.sh that might somehow be responsible for the difference.

                  It may also be important to note that starting JBoss AS 4.2.0.GA from within Eclipse with JBoss Tools works just fine. The problem happens only when starting JBoss 4.2 Enterprise Application Platform from within Eclipse with JBoss Tools.

                  One difference is I installed JBoss 4.2.0.GA from the zip, but I used enterprise-installer-4.2.0-1.ep1.1.jar to install the Enterprise Application Platform, including securing the web console and the like. ...in case that matters...

                  • 6. Re: Failed to Start JBoss 4.2.0 Application Platform with JB
                    Max Rydahl Andersen Master

                    weell securing the web console etc. would probably also prevent jboss as adapter to interact with it.

                    does it make any difference if you use the wtp provided jboss as provider or the red hat provided jboss as provider ?

                    It sounds like we need to raise this against JBoss EAP...

                    • 7. Re: Failed to Start JBoss 4.2.0 Application Platform with JB
                      Edward Pilipczuk Newbie

                      the exception listed in the second thread entry is caused by the fact that you are running JBoss not as root and the $JBOSS_HOME/server/xx/conf directory does not have 'x' (search permission flag) set, so if you are running as 'jboss' you simply do not have access to conf/* directory content.
                      I think that 'chmod +x' on conf would help

                      • 8. Re: Failed to Start JBoss 4.2.0 Application Platform with JB
                        flindet Newbie

                        Hmmm... appears to be something else in my case. Unless I'm misunderstanding you...

                        flindet@HQISB-7Y2GF61:/usr/local/jboss-eap-4.2/jboss-as/server/dojesb> ls -l
                        total 36
                        drwxrwxr-x 4 jboss dojesb 4096 2007-07-10 14:41 conf/
                        drwxrwxr-x 6 jboss dojesb 4096 2007-07-10 15:22 data/
                        drwxrwxr-x 16 jboss dojesb 4096 2007-07-12 11:27 deploy/
                        drwxrwxr-x 2 jboss dojesb 4096 2007-07-10 14:41 deploy-hasingleton/
                        drwxrwxr-x 2 jboss dojesb 4096 2007-07-10 14:41 farm/
                        drwxrwxr-x 2 jboss dojesb 4096 2007-07-10 14:42 lib/
                        drwxrwxr-x 2 jboss dojesb 4096 2007-07-11 09:31 log/
                        drwxrwxr-x 5 jboss dojesb 4096 2007-07-17 09:18 tmp/
                        drwxrwxr-x 3 jboss dojesb 4096 2007-07-10 15:02 work/


                        • 9. Re: Failed to Start JBoss 4.2.0 Application Platform with JB
                          flindet Newbie

                          No, I'm mistaken. I'm sorry. I must have noticed that permission problem earlier and corrected it. And didn't notice that my exception had changed. I apologize.

                          It looks like I'm currently troubleshooting the following:

                          2007-07-17 09:18:30,935 ERROR [org.apache.catalina.connector.Connector] Coyote connector has not been started

                          and:
                          2007-07-17 09:18:31,675 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Unable to obtain watchUrl from deployer. Use url: file:/usr/local/jboss-eap-4.2/jboss-as/server/dojesb/deploy/deploy.last/
                          java.lang.NullPointerException
                           at org.jboss.deployment.scanner.AbstractDeploymentScanner.getDeployer(AbstractDeploymentScanner.java:88)
                           at org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL.getLastModified(URLDeploymentScanner.java:762)
                           at org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL.deployed(URLDeploymentScanner.java:734)
                           at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:432)
                           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.GeneratedMethodAccessor3.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 $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: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:508)
                           at java.lang.Thread.run(Thread.java:595)
                          2007-07-17 09:18:31,723 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] java.lang.NullPointerException


                          It's still true that I can start the JBoss EAP 4.2 from command line with my regular user account without problem. I just can't do so from within Eclipse 3.3 using JBoss Tools (now upgraded to JBossTools-200707170856-nightly-ALL-linux-gtk).

                          flindet@HQISB-7Y2GF61:/usr/local/jboss-eap-4.2/jboss-as/server/dojesb/deploy> ls -ld
                          drwxrwxr-x 16 jboss dojesb 4096 2007-07-12 11:27 ./
                          flindet@HQISB-7Y2GF61:/usr/local/jboss-eap-4.2/jboss-as/server/dojesb/deploy> ls -ld deploy.last/
                          drwxrwxr-x 2 jboss dojesb 4096 2007-07-10 14:41 deploy.last/


                          • 10. Re: Failed to Start JBoss 4.2.0 Application Platform with JB
                            Rob Stryker Master

                            Has there been any update to this?
                            After viewing the run.sh script, the only linux-specific lines appear to be

                            if [ "$linux" = "true" ]; then
                            JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true"
                            fi

                            Did user ever figure out what else was causing the errors? I'm trying to fix this issue for the release now. If user is still around, it'd be great if I could get some more feedback here.

                            • 11. Re: Failed to Start JBoss 4.2.0 Application Platform with JB
                              Max Rydahl Andersen Master

                              I think that settings is exactly what is preventing him from starting it.

                              and since it is just a system property setting it is something we can add safely since if the vm doesn't support it then it will be ignored.

                              It would be good though if the user could control it - will these settings be editable in the launch configs startup arguments ?

                              • 12. Re: Failed to Start JBoss 4.2.0 Application Platform with JB
                                Max Rydahl Andersen Master

                                ...if not I guess the user could add it manually ?

                                • 13. Re: Failed to Start JBoss 4.2.0 Application Platform with JB
                                  flindet Newbie

                                  It's been a while, but yeah, setting that parameter solved the problem. It would be nice if this was done automatically until the issue with GNU/Linux and IPv6 was resolved, but documentation is better than nothing.

                                  • 14. Re: Failed to Start JBoss 4.2.0 Application Platform with JB
                                    Rob Stryker Master

                                    I will add it only as a default argument for linux. It will still be editable in the launch configuration, but it will just be there by default to start.