[jbpm-dev] Re: JmsMessageTest fails intermitently on HSQLDB
Thomas Diesler
thomas.diesler at jboss.com
Fri Dec 19 02:19:21 EST 2008
Ah ok, thanks for clarifying this.
This is a requirement that is generally available for target containers
but not for DBs. I'll take care of it.
-thomas
Alejandro Guizar wrote:
> Thomas,
>
> 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.
>
> What do you think?
>
> -Alejandro
>
> El jue, 18-12-2008 a las 13:23 +0100, Thomas Diesler escribió:
>> Alejandro,
>>
>> I resolved the issue as "Won't Fix" and updated the pom accordingly for you.
>>
>> <!-- Won't Fix [JBPM-1811] JmsMessageTest fails intermitently on HSQLDB
>> <exclude>org/jbpm/msg/jms/JmsMessageTest.java</exclude>
>>
>> cheers
>> -thomas
>>
>>
>> Alejandro Guizar (JIRA) wrote:
>>> [ https://jira.jboss.org/jira/browse/JBPM-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>>
>>> Alejandro Guizar reassigned JBPM-1811:
>>> --------------------------------------
>>>
>>> Assignee: Thomas Diesler (was: Alejandro Guizar)
>>>
>>>
>>> Thomas,
>>>
>>> Feel free to do anything you consider good enough about this issue. I've excluded the asynchronous fork test from the HSQLDB test suite, a limitation which has been discussed, investigated and made known way too many times. I'm not spending any more time here.
>>>
>>>> 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
>>>> 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
>
More information about the jbpm-dev
mailing list