Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: 3.3.0.M4
    • Fix Version/s: 3.3.0.M4
    • Component/s: server
    • Labels:
      None
    • Environment:
      Windows, AS 7.0.1

      Description

      Attempt to start AS7 results to following error

       
      !ENTRY org.eclipse.debug.ui 4 0 2011-10-07 18:44:30.796
      !MESSAGE Tab group extension: org.eclipse.jdt.debug.ui.launchConfigurationTabGroup.remoteJavaApplication for type org.eclipse.jdt.launching.remoteJavaApplication for the * mode has been replaced by extension: org.jboss.tools.common.jdt.debug.ui.launching.launchConfigurationTabGroup.JBossRemoteJavaApplication2
       
      !ENTRY org.eclipse.core.jobs 4 2 2011-10-07 18:44:30.828
      !MESSAGE An internal error occurred during: "Starting JBoss 7.0 Runtime Server".
      !STACK 0
      java.lang.IllegalArgumentException: classToLaunch cannot be null
      	at org.eclipse.jdt.launching.VMRunnerConfiguration.<init>(VMRunnerConfiguration.java:49)
      	at org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossStartLaunchConfiguration.actualLaunch(AbstractJBossStartLaunchConfiguration.java:177)
      	at org.jboss.ide.eclipse.as.core.server.internal.launch.LocalJBossStartLaunchDelegate.actualLaunch(LocalJBossStartLaunchDelegate.java:53)
      	at org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.actualLaunch(DelegatingStartLaunchConfiguration.java:56)
      	at org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossStartLaunchConfiguration.launch(AbstractJBossStartLaunchConfiguration.java:138)
      	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854)
      	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
      	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:696)
      	at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3402)
      	at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3340)
      	at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:363)
      	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
      

      JBossAS Tools 2.3.0.v20111007-0916-H768-M4

        Gliffy Diagrams

          Activity

          Hide
          mcaspers Matthew Casperson added a comment -

          Just did an update of JBoss Tools (10 Oct 2011) from the nightly repos and I can confirm that I am getting the same issue.

          Show
          mcaspers Matthew Casperson added a comment - Just did an update of JBoss Tools (10 Oct 2011) from the nightly repos and I can confirm that I am getting the same issue.
          Hide
          sandyperez Sandy Pérez added a comment -

          Hello, I have came across with the same issue. In my case, my environment is Windows 7 Professional SP1 (64bit), JDK 1.6.0_27 (32bits), JBoss AS 5.1, Eclipse 3.7 (32bits) and JBoss Tools 3.3 (nightly build 2011-10-12).

          !ENTRY org.eclipse.core.jobs 4 2 2011-10-12 13:44:50.037
          !MESSAGE An internal error occurred during: "Starting JBoss 5.1 Runtime Server".
          !STACK 0
          java.lang.IllegalArgumentException: classToLaunch cannot be null
          at org.eclipse.jdt.launching.VMRunnerConfiguration.<init>(VMRunnerConfiguration.java:49)
          at org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossStartLaunchConfiguration.actualLaunch(AbstractJBossStartLaunchConfiguration.java:177)
          at org.jboss.ide.eclipse.as.core.server.internal.launch.LocalJBossStartLaunchDelegate.actualLaunch(LocalJBossStartLaunchDelegate.java:53)
          at org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.actualLaunch(DelegatingStartLaunchConfiguration.java:56)
          at org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossStartLaunchConfiguration.launch(AbstractJBossStartLaunchConfiguration.java:138)
          at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854)
          at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
          at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:696)
          at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3402)
          at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3340)
          at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:363)
          at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

          Show
          sandyperez Sandy Pérez added a comment - Hello, I have came across with the same issue. In my case, my environment is Windows 7 Professional SP1 (64bit), JDK 1.6.0_27 (32bits), JBoss AS 5.1, Eclipse 3.7 (32bits) and JBoss Tools 3.3 (nightly build 2011-10-12). !ENTRY org.eclipse.core.jobs 4 2 2011-10-12 13:44:50.037 !MESSAGE An internal error occurred during: "Starting JBoss 5.1 Runtime Server". !STACK 0 java.lang.IllegalArgumentException: classToLaunch cannot be null at org.eclipse.jdt.launching.VMRunnerConfiguration.<init>(VMRunnerConfiguration.java:49) at org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossStartLaunchConfiguration.actualLaunch(AbstractJBossStartLaunchConfiguration.java:177) at org.jboss.ide.eclipse.as.core.server.internal.launch.LocalJBossStartLaunchDelegate.actualLaunch(LocalJBossStartLaunchDelegate.java:53) at org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.actualLaunch(DelegatingStartLaunchConfiguration.java:56) at org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossStartLaunchConfiguration.launch(AbstractJBossStartLaunchConfiguration.java:138) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:696) at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3402) at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3340) at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:363) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
          Hide
          mmalina Martin Malina added a comment - - edited

          I just tried it on Mac and got a NPE:

          !ENTRY org.eclipse.core.jobs 4 2 2011-10-12 16:26:27.459
          !MESSAGE An internal error occurred during: "Starting jboss-as-7.0.1.Final".
          !STACK 0
          java.lang.NullPointerException
          at org.jboss.ide.eclipse.as.core.server.internal.BehaviourModel.getLaunchDelegate(BehaviourModel.java:61)
          at org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.getDelegate(DelegatingStartLaunchConfiguration.java:47)
          at org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.preLaunchCheck(DelegatingStartLaunchConfiguration.java:61)
          at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:809)
          at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
          at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:696)
          at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3402)
          at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3340)
          at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:363)
          at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

          I used Eclipse Indigo SR1 Cocoa with JBoss Tools 3.3.0.v20111012-0912-H4012-M4 from http://download.jboss.org/jbosstools/updates/nightly/trunk/ and JBoss AS 7.0.1.

          Show
          mmalina Martin Malina added a comment - - edited I just tried it on Mac and got a NPE: !ENTRY org.eclipse.core.jobs 4 2 2011-10-12 16:26:27.459 !MESSAGE An internal error occurred during: "Starting jboss-as-7.0.1.Final". !STACK 0 java.lang.NullPointerException at org.jboss.ide.eclipse.as.core.server.internal.BehaviourModel.getLaunchDelegate(BehaviourModel.java:61) at org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.getDelegate(DelegatingStartLaunchConfiguration.java:47) at org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.preLaunchCheck(DelegatingStartLaunchConfiguration.java:61) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:809) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:696) at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3402) at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3340) at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:363) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) I used Eclipse Indigo SR1 Cocoa with JBoss Tools 3.3.0.v20111012-0912-H4012-M4 from http://download.jboss.org/jbosstools/updates/nightly/trunk/ and JBoss AS 7.0.1.
          Hide
          rob.stryker Rob Stryker added a comment -

          should be fixed in trunk

          Show
          rob.stryker Rob Stryker added a comment - should be fixed in trunk
          Hide
          jjankovi Jaroslav Jankovič added a comment -

          Verified in JBDS 5.0.0.v201110271830R-H42-M4. Closing Jira.

          Show
          jjankovi Jaroslav Jankovič added a comment - Verified in JBDS 5.0.0.v201110271830R-H42-M4. Closing Jira.

            People

            • Assignee:
              rob.stryker Rob Stryker
              Reporter:
              lzoubek Libor Zoubek
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development