[jbpm-issues] [JBoss JIRA] Commented: (JBPM-2636) NPE in Configuration.getProcessEngine() when using jbpm.jbossremote.cfg.xml
[
https://jira.jboss.org/jira/browse/JBPM-2636?page=com.atlassian.jira.plug...
]
Orestes Garcia commented on JBPM-2636:
--------------------------------------
is there any work around to this problem?
I am getting same behavior using a different configuration file.
<?xml version="1.0" encoding="UTF-8"?>
<jbpm-configuration>
<import resource="jbpm.default.cfg.xml" />
<import resource="jbpm.businesscalendar.cfg.xml" />
<import resource="jbpm.jpdl.cfg.xml" />
<import resource="jbpm.identity.cfg.xml" />
<process-engine-context>
<command-service>
<retry-interceptor />
<environment-interceptor />
<spring-transaction-interceptor />
</command-service>
</process-engine-context>
<transaction-context>
<transaction />
<hibernate-session />
</transaction-context>
</jbpm-configuration>
NPE in Configuration.getProcessEngine() when using
jbpm.jbossremote.cfg.xml
---------------------------------------------------------------------------
Key: JBPM-2636
URL: https://jira.jboss.org/jira/browse/JBPM-2636
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 4.2
Environment: Windows XP, JDK 6, JBoss, Oracle 10g
Reporter: Mark Roy
In jBPM 4.1, using the following jbpm.cfg.xml in my simple test app worked:
Code:
<jbpm-configuration>
<import resource="jbpm.jbossremote.cfg.xml" />
</jbpm-configuration>
Since upgrading to 4.2, however, I now get a NPE:
Code:
java.lang.NullPointerException
at org.jbpm.pvm.internal.cfg.ProcessEngineImpl.checkDb(ProcessEngineImpl.java:177)
at
org.jbpm.pvm.internal.cfg.ProcessEngineImpl.buildProcessEngine(ProcessEngineImpl.java:170)
at org.jbpm.api.Configuration.getProcessEngine(Configuration.java:161)
at org.jbpm.test.JbpmTestCase.initialize(JbpmTestCase.java:81)
at org.jbpm.test.JbpmTestCase.setUp(JbpmTestCase.java:76)
at com.mydomain..ReviewProcess.setUp(ReviewProcess.java:24)
at junit.framework.TestCase.runBare(TestCase.java:132)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at
org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:13
0)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
I traced this to the fact the userCommandService is assigned null from the following:
Code:
userCommandService = (CommandService)
processEngineWireContext.get(CommandService.NAME_TX_REQUIR
ED_COMMAND_SERVICE);
This problem can be easily reproduced using the examples included in the distribution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira