[jbpm-issues] [JBoss JIRA] Commented: (JBPM-1811) JmsMessageTest fails intermitently on HSQLDB
[
https://jira.jboss.org/jira/browse/JBPM-1811?page=com.atlassian.jira.plug...
]
Alejandro Guizar commented on JBPM-1811:
----------------------------------------
Excluded JmsMessageTest.testAsyncFork from HSQL test suite; HSQL cannot reliably handle
concurrent joins.
Followed Thomas' tip with one caveat: system properties set on the client are not
available on the server :-/ I had to query the dialect in use from the Hibernate
configuration available from DbPersistenceServiceFactory.
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