[JBoss JIRA] Created: (JBPM-1830) Fix AppServerConfigurationsTest for sybase on jboss500
by Thomas Diesler (JIRA)
Fix AppServerConfigurationsTest for sybase on jboss500
------------------------------------------------------
Key: JBPM-1830
URL: https://jira.jboss.org/jira/browse/JBPM-1830
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Productization
Reporter: Thomas Diesler
Fix For: jBPM 3.3.1 GA
org.jbpm.enterprise.AppServerConfigurationsTest
Running org.jbpm.enterprise.AppServerConfigurationsTest
java.rmi.UnmarshalException: Error unmarshaling return; nested exception is:
java.lang.ClassNotFoundException: org.jboss.deployers.client.spi.IncompleteDeploymentException (no security manager: RMI class loader disabled)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:227)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)
at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
at $Proxy2.invoke(Unknown Source)
at org.jbpm.api.test.JBossArchiveDeployer.invokeMainDeployer(JBossArchiveDeployer.java:58)
at org.jbpm.api.test.JBossArchiveDeployer.deploy(JBossArchiveDeployer.java:48)
at org.jbpm.api.test.IntegrationTestHelper.deploy(IntegrationTestHelper.java:56)
at org.jbpm.api.test.IntegrationTestSetup.setUp(IntegrationTestSetup.java:105)
at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:23)
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 org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
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 org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997)
Caused by: java.lang.ClassNotFoundException: org.jboss.deployers.client.spi.IncompleteDeploymentException (no security manager: RMI class loader disabled)
at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:375)
at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:165)
at java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:620)
at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:247)
at sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:197)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1732)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:225)
--
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
16 years, 1 month
[JBoss JIRA] Created: (JBPM-1778) Empty map variables on process creation is set as null
by Paco Avila (JIRA)
Empty map variables on process creation is set as null
------------------------------------------------------
Key: JBPM-1778
URL: https://jira.jboss.org/jira/browse/JBPM-1778
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jBPM 3.2.3
Environment: JBoss 4.2.2.GA, Database HSQL, Ubuntu Linux
Reporter: Paco Avila
If I create a ProcessInstances with an empty variables Map, it is set to null. But if I put any value, I works fine. This below code show this behavior. Uncomment the "vars.put("uno", "dos");" line to see it return a the right map when it is not empty.
JbpmContext jbpmContext = JbpmConfiguration.getInstance().createJbpmContext();
try {
HashMap<String, String> vars = new HashMap<String, String>();
//vars.put("uno", "dos");
ProcessDefinition pd = ProcessDefinition.parseXmlString(
"<process-definition>" +
" <start-state>" +
" <transition to='s' />" +
" </start-state>" +
" <state name='s'>" +
" <transition to='end' />" +
" </state>" +
" <end-state name='end' />" +
"</process-definition>"
);
ProcessInstance pi = pd.createProcessInstance(vars);
TaskMgmtInstance tmi = pi.getTaskMgmtInstance();
tmi.createStartTaskInstance();
System.out.println("Created ProcessInstance Variables: "+pi.getContextInstance().getVariables());
} catch (Exception e) {
e.printStackTrace();
} finally {
jbpmContext.close();
}
--
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
16 years, 1 month
[JBoss JIRA] Created: (JBPM-1716) NPE in Transition.fireSuperStateEnterEvents() when destination is null
by Karl Palsson (JIRA)
NPE in Transition.fireSuperStateEnterEvents() when destination is null
----------------------------------------------------------------------
Key: JBPM-1716
URL: https://jira.jboss.org/jira/browse/JBPM-1716
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Core Engine
Affects Versions: jBPM 3.2.3
Reporter: Karl Palsson
The current method body is shown below. Destination is null in my case (I should check my process definition, it came about from a bad database move) However, instead of getting the JbpmException shown, I get the NPE from the "destination.isSuperStateNode()" loop above.
I'm not entirely sure what that loop is for, which is why I've not included a patch here. I'm unsure whether it should be moved down just past the first null check, or to the very bottom. Sorry :(
Source in question...
Node fireSuperStateEnterEvents(ExecutionContext executionContext) {
// calculate the actual destinationNode node
Node destination = to;
while (destination.isSuperStateNode()) { ###KJP This explodes before it gets to the Null check 3 lines down.
destination = (Node) destination.getNodes().get(0);
}
if (destination==null) {
String transitionName = (name!=null ? "'"+name+"'" : "in node '"+from+"'");
throw new JbpmException("transition "+transitionName+" doesn't have destination. check your processdefinition.xml");
}
// performance optimisation: check if at least there is a candidate superstate to be entered.
if ( destination.getSuperState()!=null ) {
// collect all the superstates being left
List leavingSuperStates = collectAllSuperStates(destination, from);
// reverse the order so that events are fired from outer to inner superstates
Collections.reverse(leavingSuperStates);
// fire a superstate-enter event for all superstates being left
fireSuperStateEvents(leavingSuperStates, Event.EVENTTYPE_SUPERSTATE_ENTER, executionContext);
}
return destination;
}
--
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
16 years, 1 month
[JBoss JIRA] Created: (JBPM-1765) Unclosed InputStream in org.jbpm.util.ClassLoaderUtil.getProperties
by Tim Timson (JIRA)
Unclosed InputStream in org.jbpm.util.ClassLoaderUtil.getProperties
-------------------------------------------------------------------
Key: JBPM-1765
URL: https://jira.jboss.org/jira/browse/JBPM-1765
Project: JBoss jBPM
Issue Type: Quality Risk
Security Level: Public (Everyone can see)
Affects Versions: jBPM 3.2.2
Environment: Glassfish v2
Reporter: Tim Timson
Fix For: jBPM 3.3.0 GA
Our Glassfish server logs a stack trace every time we undeploy our app. It looks like this is because you are not closing an input stream in the "getProperties" method of the org.jbpm.util.ClassLoaderUtil class.
Note that the "Properties.load" method does not close the input stream (unlike the "Properties.loadFromXml" method which does close the input stream). It looks like there is one case where you use Properties.load, and in that case you are not closing the input stream.
--
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
16 years, 1 month