[jbosstools-issues] [JBoss JIRA] (JBIDE-22272) NPE when using LaunchBar to run an app on WildFly

Martin Malina (JIRA) issues at jboss.org
Tue Jun 14 04:03:00 EDT 2016


     [ https://issues.jboss.org/browse/JBIDE-22272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Malina closed JBIDE-22272.
---------------------------------


Hmm, the other issue talked about null target. I don't think the target was null in this case. But anyway, it seems to be fixed - I tried it now and there are no NPEs. Verified in 4.4.0. Closing.

> NPE when using LaunchBar to run an app on WildFly
> -------------------------------------------------
>
>                 Key: JBIDE-22272
>                 URL: https://issues.jboss.org/browse/JBIDE-22272
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.4.0.Alpha1
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.4.0.Final
>
>
> I tried to run jboss java ee web app from Central on WildFly 10 using launchbar. And it did work, but a NPE was thrown:
> {code}
> Plug-in: org.eclipse.debug.core
> An exception occurred during launch change notification.
> java.lang.NullPointerException
> 	at org.jboss.tools.wtp.server.launchbar.ModuleLaunchConfigurationProvider.getLaunchConfiguration(ModuleLaunchConfigurationProvider.java:84)
> 	at org.jboss.tools.wtp.server.launchbar.ModuleLaunchConfigurationProvider.launchDescriptorMatches(ModuleLaunchConfigurationProvider.java:128)
> 	at org.eclipse.launchbar.core.internal.LaunchBarManager.launchDescriptorMatches(LaunchBarManager.java:964)
> 	at org.eclipse.launchbar.core.internal.LaunchBarManager.getLaunchDescriptor(LaunchBarManager.java:942)
> 	at org.eclipse.launchbar.core.internal.LaunchBarManager.setActive(LaunchBarManager.java:424)
> 	at org.eclipse.launchbar.core.internal.LaunchBarManager.access$0(LaunchBarManager.java:423)
> 	at org.eclipse.launchbar.core.internal.LaunchBarManager$2.launchAdded(LaunchBarManager.java:169)
> 	at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:446)
> 	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> 	at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:433)
> 	at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1043)
> 	at org.eclipse.debug.internal.core.LaunchManager.addLaunch(LaunchManager.java:703)
> 	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:834)
> 	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> 	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> 	at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
> 	at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> 	at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jbosstools-issues mailing list