Re: [jboss-dev] Re: org.jboss.test.timer.test.BasicTimerUnitTestCase.testMDBTimer
Test is a persistent reply coming in, while the bean sends a
non-persistent reply, so definitely the wrong message.
The test tries to clear the queue with receiveNoWait, but that only
clears the client side of the queue. (I think it was you who mentioned
that some time ago.) So while the receiving end is fully established
that wrong message is dropped in the client side queue.
Carlo
On Thu, 2008-09-04 at 13:15 +0200, Adrian Brock wrote:
Isn't it just messages leaking across tests?
java.lang.NumberFormatException: Message property 'UNIQUE_ID' not set.
at org.jboss.jms.message.JBossMessage.getIntProperty(JBossMessage.java:636)
I'll bet clearing the queue at the start of the test
(and end so it doesn't leak messages when it fails)
fixes the problem.
But we still need to locate the "dirty" test that is leaving messages
lying around.
On Thu, 2008-09-04 at 14:02 +0300, Dimitris Andreadis wrote:
> We have been stuck on this testcase that passes locally, but fails on hudson for a
long time
> now:
>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>
> I don't know if it's related to the fact that a different messaging provider
is used in AS5
> (JBoss Messaging vs JBossMQ), but if you have any idea how to fix it, please give a
hand.
>
> https://jira.jboss.org/jira/browse/JBAS-5866
>
> Thanks