[
https://jira.jboss.org/jira/browse/JBPM-1811?page=com.atlassian.jira.plug...
]
Thomas Diesler reopened JBPM-1811:
----------------------------------
Alejandro sais:
I did not want to exclude the entire test. JMS and HSQLDB can work
together, provided no two jobs result in concurrent updates to the same
token, as in JmsMessageTest.testAsyncFork(). That is why I asked how
could I exclude a single method.
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: Thomas Diesler
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