[JBoss JIRA] (JBIDE-18591) "Error while JSDT ClassPath changed" exception occurs when creating thym project
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18591?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-18591:
--------------------------------------
OK.. I have fixed this on Thym...
> "Error while JSDT ClassPath changed" exception occurs when creating thym project
> --------------------------------------------------------------------------------
>
> Key: JBIDE-18591
> URL: https://issues.jboss.org/browse/JBIDE-18591
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Final
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: respin-a
> Fix For: 4.2.1.CR1
>
>
> Error message is "Error while JSDT ClassPath changed." and stacktrace is:
> {code}org.eclipse.core.internal.resources.ResourceException: The resource tree is locked for modifications.
> at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:116)
> at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2251)
> at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1322)
> at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1376)
> at tern.eclipse.ide.core.TernNature.configure(TernNature.java:59)
> at tern.eclipse.ide.internal.core.IDETernProject.ensureNatureIsConfigured(IDETernProject.java:817)
> at tern.eclipse.ide.internal.core.IDETernProject.<init>(IDETernProject.java:111)
> at tern.eclipse.ide.internal.core.IDETernProject.getTernProject(IDETernProject.java:134)
> at tern.eclipse.ide.core.TernCorePlugin.getTernProject(TernCorePlugin.java:99)
> at tern.eclipse.ide.jsdt.internal.JSDTClassPathManager.elementChanged(JSDTClassPathManager.java:67)
> at org.eclipse.wst.jsdt.internal.core.DeltaProcessor$3.run(DeltaProcessor.java:1591)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1581)
> at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.firePostChangeDelta(DeltaProcessor.java:1416)
> at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1392)
> at org.eclipse.wst.jsdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:1945)
> at org.eclipse.wst.jsdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:389)
> at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
> at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
> at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:378)
> at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1498)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322)
> at org.eclipse.wst.jsdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:807)
> at org.eclipse.wst.jsdt.internal.core.JavaProject.setRawIncludepath(JavaProject.java:2992)
> at org.eclipse.wst.jsdt.internal.core.JavaProject.setRawIncludepath(JavaProject.java:3023)
> at org.eclipse.thym.ui.wizard.project.HybridProjectCreator.setUpJavaScriptProject(HybridProjectCreator.java:135)
> at org.eclipse.thym.ui.wizard.project.HybridProjectCreator.createProject(HybridProjectCreator.java:104)
> at org.eclipse.thym.ui.wizard.project.HybridProjectCreator.createBasicTemplatedProject(HybridProjectCreator.java:78)
> at org.eclipse.thym.ui.wizard.project.NewHybridProjectWizard$1.run(NewHybridProjectWizard.java:91)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:466)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:374)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1059)
> at org.eclipse.thym.ui.wizard.project.NewHybridProjectWizard.performFinish(NewHybridProjectWizard.java:103)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:853)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:438)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
> at org.eclipse.jface.window.Window.open(Window.java:808)
> at org.jboss.tools.central.editors.GettingStartedPage.openWizard(GettingStartedPage.java:697)
> at org.jboss.tools.central.editors.GettingStartedPage.access$14(GettingStartedPage.java:682)
> at org.jboss.tools.central.editors.GettingStartedPage$7.linkActivated(GettingStartedPage.java:636)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
> at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:199)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438){code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18366) Sometimes, EAP6/WildFly8/AS7 fails to start - Failed initializing module org.jboss.as.logging
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18366?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18366:
-------------------------------------
We're not able to consistantly replicate this issue but we suspect that JBIDE-18267 will fix it, based on various stacks and internet posts.
> Sometimes, EAP6/WildFly8/AS7 fails to start - Failed initializing module org.jboss.as.logging
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-18366
> URL: https://issues.jboss.org/browse/JBIDE-18366
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.1.CR1, 4.3.0.Alpha1
>
>
> Sometimes, right after start of the IDE, a server fails to start. When this happens, it produces something like this in the server log:
> {code}
> INFO: JBoss MSC version 1.1.5.Final-redhat-1
> Sep 17, 2014 11:27:40 AM org.jboss.as.server.ApplicationServerService start
> INFO: JBAS015899: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) starting
> Sep 17, 2014 11:27:40 AM org.jboss.as.controller.AbstractOperationContext executeStep
> ERROR: JBAS014612: Operation ("parallel-extension-add") failed - address: ([])
> java.lang.RuntimeException: JBAS014670: Failed initializing module org.jboss.as.logging
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:111)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:611)
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:489)
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:290)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:285)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1132)
> at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:299)
> at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:292)
> at org.jboss.as.server.ServerService.boot(ServerService.java:346)
> at org.jboss.as.server.ServerService.boot(ServerService.java:321)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:254)
> at java.lang.Thread.run(Thread.java:695)
> Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
> at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
> at java.util.concurrent.FutureTask.get(FutureTask.java:83)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:103)
> ... 11 more
> Caused by: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
> at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:106)
> at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:97)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:139)
> at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:125)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:695)
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> Sep 17, 2014 11:27:40 AM org.jboss.as.server.ServerService boot
> FATAL: JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {code}
> Unfortunately I don't have a reliable way to reproduce this. It happened to me like 3 times over the last few days.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18267) Errors when starting EAP 5.2 - problem with jmx agent
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18267?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-18267:
--------------------------------
Component/s: jmx
> Errors when starting EAP 5.2 - problem with jmx agent
> -----------------------------------------------------
>
> Key: JBIDE-18267
> URL: https://issues.jboss.org/browse/JBIDE-18267
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: respin-b
> Fix For: 4.2.1.Final
>
>
> When I add EAP 5.2 using runtime detection and then start the server, I get errors in the console:
> {code}
> 15:07:25,729 INFO [JMXKernel] Legacy JMX core initialized
> javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class org.jboss.mx.server.MBeanServerBuilderImpl: java.lang.ClassNotFoundException: org.jboss.mx.server.MBeanServerBuilderImpl
> at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:481)
> at javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:512)
> at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:299)
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:214)
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:175)
> at sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:302)
> at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:504)
> at sun.management.jmxremote.ConnectorBootstrap.startLocalConnectorServer(ConnectorBootstrap.java:458)
> at sun.management.Agent.startAgent(Agent.java:135)
> at sun.management.Agent.agentmain(Agent.java:95)
> 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:597)
> at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:325)
> at sun.instrument.InstrumentationImpl.loadClassAndCallAgentmain(InstrumentationImpl.java:348)
> Caused by: java.lang.ClassNotFoundException: org.jboss.mx.server.MBeanServerBuilderImpl
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> at javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:424)
> at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:466)
> ... 15 more
> Exception thrown by the agent : javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class org.jboss.mx.server.MBeanServerBuilderImpl: java.lang.ClassNotFoundException: org.jboss.mx.server.MBeanServerBuilderImpl
> Exception in thread "Attach Listener" java.lang.reflect.InvocationTargetException
> 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:597)
> at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:325)
> at sun.instrument.InstrumentationImpl.loadClassAndCallAgentmain(InstrumentationImpl.java:348)
> Caused by: java.lang.RuntimeException: javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class org.jboss.mx.server.MBeanServerBuilderImpl: java.lang.ClassNotFoundException: org.jboss.mx.server.MBeanServerBuilderImpl
> at sun.management.Agent.error(Agent.java:309)
> at sun.management.Agent.startAgent(Agent.java:153)
> at sun.management.Agent.agentmain(Agent.java:95)
> ... 6 more
> Caused by: javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class org.jboss.mx.server.MBeanServerBuilderImpl: java.lang.ClassNotFoundException: org.jboss.mx.server.MBeanServerBuilderImpl
> at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:481)
> at javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:512)
> at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:299)
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:214)
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:175)
> at sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:302)
> at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:504)
> at sun.management.jmxremote.ConnectorBootstrap.startLocalConnectorServer(ConnectorBootstrap.java:458)
> at sun.management.Agent.startAgent(Agent.java:135)
> ... 7 more
> Caused by: java.lang.ClassNotFoundException: org.jboss.mx.server.MBeanServerBuilderImpl
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> at javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:424)
> at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:466)
> ... 15 more
> Agent failed to start!
> {code}
> It's kind of strange, but it didn't happen at first. When I changed the server to compressed deployment, it started happening. So I wanted to check again in a new workspace. In the new workspace, I just added the server and start (with default - exploded wars) and it happened again.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18867) NPE in CDI (probably) Validation
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18867?page=com.atlassian.jira.plugi... ]
Rastislav Wagner resolved JBIDE-18867.
--------------------------------------
Resolution: Done
> NPE in CDI (probably) Validation
> --------------------------------
>
> Key: JBIDE-18867
> URL: https://issues.jboss.org/browse/JBIDE-18867
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Final
> Reporter: Rastislav Wagner
> Assignee: Alexey Kazakov
> Fix For: 4.3.0.Alpha1
>
>
> In some cases, when you're editing HTML Validation Preferences and agree to perform a build on pressing 'Apply' and then immediately do the same on pressing 'OK' button, an NPE occurs in Validation:
> {code}
> !ENTRY org.jboss.tools.common 4 0 2014-11-13 02:17:31.326
> !MESSAGE
> !STACK 0
> org.jboss.tools.common.validation.JBTValidationException
> at org.jboss.tools.common.validation.ValidatorManager.validate(ValidatorManager.java:123)
> at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:81)
> at org.eclipse.wst.validation.internal.core.ValidatorLauncher.start(ValidatorLauncher.java:77)
> at org.eclipse.wst.validation.Validator$V1.validate(Validator.java:768)
> at org.eclipse.wst.validation.Validator.validate(Validator.java:405)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
> at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
> at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:783)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
> at org.eclipse.wst.validation.internal.ValidationRunner.execute(ValidationRunner.java:134)
> at org.eclipse.wst.validation.internal.ValidationRunner.run(ValidationRunner.java:148)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
> at org.eclipse.wst.validation.internal.ValidationRunner.validate(ValidationRunner.java:67)
> at org.eclipse.wst.validation.ValidationFramework.validate(ValidationFramework.java:661)
> at org.eclipse.wst.sse.ui.internal.preferences.ui.AbstractValidationSettingsPage$ValidateJob.run(AbstractValidationSettingsPage.java:411)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.common.validation.ValidatorManager.validate(ValidatorManager.java:116)
> ... 15 more
> {code}
> Some debugging shows that NPE happens when validator is CDICoreValidator object: the following expression:
> {code}validationHelper.getValidationContextManager().getValidatingProjectTree(validator){code}, and that value is used with no any checks for that.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18867) NPE in CDI (probably) Validation
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18867?page=com.atlassian.jira.plugi... ]
Rastislav Wagner updated JBIDE-18867:
-------------------------------------
Fix Version/s: (was: 4.2.1.CR1)
> NPE in CDI (probably) Validation
> --------------------------------
>
> Key: JBIDE-18867
> URL: https://issues.jboss.org/browse/JBIDE-18867
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Final
> Reporter: Rastislav Wagner
> Assignee: Alexey Kazakov
> Fix For: 4.3.0.Alpha1
>
>
> In some cases, when you're editing HTML Validation Preferences and agree to perform a build on pressing 'Apply' and then immediately do the same on pressing 'OK' button, an NPE occurs in Validation:
> {code}
> !ENTRY org.jboss.tools.common 4 0 2014-11-13 02:17:31.326
> !MESSAGE
> !STACK 0
> org.jboss.tools.common.validation.JBTValidationException
> at org.jboss.tools.common.validation.ValidatorManager.validate(ValidatorManager.java:123)
> at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:81)
> at org.eclipse.wst.validation.internal.core.ValidatorLauncher.start(ValidatorLauncher.java:77)
> at org.eclipse.wst.validation.Validator$V1.validate(Validator.java:768)
> at org.eclipse.wst.validation.Validator.validate(Validator.java:405)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
> at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
> at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:783)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
> at org.eclipse.wst.validation.internal.ValidationRunner.execute(ValidationRunner.java:134)
> at org.eclipse.wst.validation.internal.ValidationRunner.run(ValidationRunner.java:148)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
> at org.eclipse.wst.validation.internal.ValidationRunner.validate(ValidationRunner.java:67)
> at org.eclipse.wst.validation.ValidationFramework.validate(ValidationFramework.java:661)
> at org.eclipse.wst.sse.ui.internal.preferences.ui.AbstractValidationSettingsPage$ValidateJob.run(AbstractValidationSettingsPage.java:411)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.common.validation.ValidatorManager.validate(ValidatorManager.java:116)
> ... 15 more
> {code}
> Some debugging shows that NPE happens when validator is CDICoreValidator object: the following expression:
> {code}validationHelper.getValidationContextManager().getValidatingProjectTree(validator){code}, and that value is used with no any checks for that.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18747) NPE in CDI (probably) Validation
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18747?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-18747.
------------------------------------
I cant reproduce in 4.2.1.CR1. Closing
> NPE in CDI (probably) Validation
> --------------------------------
>
> Key: JBIDE-18747
> URL: https://issues.jboss.org/browse/JBIDE-18747
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Final
> Reporter: Victor Rubezhny
> Assignee: Alexey Kazakov
> Fix For: 4.2.1.CR1, 4.3.0.Alpha1
>
>
> In some cases, when you're editing HTML Validation Preferences and agree to perform a build on pressing 'Apply' and then immediately do the same on pressing 'OK' button, an NPE occurs in Validation:
> {code}
> !ENTRY org.jboss.tools.common 4 0 2014-11-13 02:17:31.326
> !MESSAGE
> !STACK 0
> org.jboss.tools.common.validation.JBTValidationException
> at org.jboss.tools.common.validation.ValidatorManager.validate(ValidatorManager.java:123)
> at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:81)
> at org.eclipse.wst.validation.internal.core.ValidatorLauncher.start(ValidatorLauncher.java:77)
> at org.eclipse.wst.validation.Validator$V1.validate(Validator.java:768)
> at org.eclipse.wst.validation.Validator.validate(Validator.java:405)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
> at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
> at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:783)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
> at org.eclipse.wst.validation.internal.ValidationRunner.execute(ValidationRunner.java:134)
> at org.eclipse.wst.validation.internal.ValidationRunner.run(ValidationRunner.java:148)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
> at org.eclipse.wst.validation.internal.ValidationRunner.validate(ValidationRunner.java:67)
> at org.eclipse.wst.validation.ValidationFramework.validate(ValidationFramework.java:661)
> at org.eclipse.wst.sse.ui.internal.preferences.ui.AbstractValidationSettingsPage$ValidateJob.run(AbstractValidationSettingsPage.java:411)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.common.validation.ValidatorManager.validate(ValidatorManager.java:116)
> ... 15 more
> {code}
> Some debugging shows that NPE happens when validator is CDICoreValidator object: the following expression:
> {code}validationHelper.getValidationContextManager().getValidatingProjectTree(validator){code}, and that value is used with no any checks for that.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months