[
https://jira.jboss.org/jira/browse/JBPM-1811?page=com.atlassian.jira.plug...
]
Alejandro Guizar commented on JBPM-1811:
----------------------------------------
JmsMessageTest.testAsyncFork executes a process which contains a fork and several async
nodes. We can configure our job executor to use only one thread, but preventing the JMS
implementation from processing messages concurrently requires changes in the app server
configuration, which compromise the out-of-the-box experience. Hence I believe this issue
can only be resolved by excluding the test from the suite.
Note: is there a way to exclude a single test method, as opposed to the entire test case?
JmsMessageTest fails intermitently on HSQLDB
--------------------------------------------
Key: JBPM-1811
URL:
https://jira.jboss.org/jira/browse/JBPM-1811
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Engine
Reporter: Thomas Diesler
Assignee: Alejandro Guizar
Fix For: jBPM 3.3.1 GA
junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertTrue(Assert.java:27)
at org.jbpm.msg.jms.JmsMessageTest.testAsyncFork(JmsMessageTest.java:193)
EventCallback.waitForEvent(Event.EVENTTYPE_PROCESS_END);
assertTrue("Process has ended", hasProcessEnded(processId));
It seems that hasProcessEnded() can return false although the exent had already been
sent.
This sould be a race condition
--
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