You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Benson Margulies <bi...@gmail.com> on 2009/08/28 00:52:20 UTC
JMS test fallure
Can't someone do something about:
Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 28.232
sec <<< FAILURE!
testDurableSubscriber(org.apache.cxf.transport.jms.JMSDestinationTest)
Time elapsed: 10.495 sec <<< FAILURE!
java.lang.AssertionError: Can't receive the Destination message in 10 seconds
Re: JMS test fallure
Posted by Willem Jiang <wi...@gmail.com>.
Hi Dan,
I just realized switch the JMS broker's transport makes it possible to
run the JUnit test with the broker in the same JVM.
It may not work for our JMSDestinationTest.
I can't reproduce the JMSDestinationTest error on my box.
Can you try to increase the sleep time after the jms destination started
to see if it works?
Willem
Daniel Kulp wrote:
> On Fri August 28 2009 8:34:46 pm Willem Jiang wrote:
>> Hi Dan,
>>
>> Maybe we need to switch the JMS broker to use the VM transport instead
>> of the TCP transport for the Unit test.
>
> Sure. I have no idea how to do it. :-)
>
>> We hit some JMS unit test issues in Apache Camel few month ago after
>> upgrading the ActivemMQ version. And resolved them by switching the
>> broker's transport.
>
> Well, I know 5.2 doesn't work for us at all which is why I went with 5.1.
> The transaction issue is fixed in the latest 5.3 snapshots, but 5.2 really
> doesn't work.
>
> Dan
>
>
>
>> Willem
>>
>> Daniel Kulp wrote:
>>> On Thu August 27 2009 10:06:33 pm Willem Jiang wrote:
>>>> Hi Benson,
>>>>
>>>> I found after upgrading to ActiveMQ 5.1, the JMS broker need more time
>>>> to create a durable subscriber jms destination.
>>>> Added a sleep make the test passed again :)
>>> Willem, Thanks for tracking that down. I couldn't figure out why it
>>> seemed to work OK for me 80% of the time, but randomly fail.
>>>
>>> One thing it DID teach me is how to use the "-rf" flag to maven 2.2.1.
>>>
>>> mvn -Pnochecks -rf rt/transports/jms
>>>
>>> was a popular call. :-)
>>>
>>> Dan
>>>
>>>> Willem
>>>>
>>>> Benson Margulies wrote:
>>>>> Can't someone do something about:
>>>>>
>>>>> Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 28.232
>>>>> sec <<< FAILURE!
>>>>> testDurableSubscriber(org.apache.cxf.transport.jms.JMSDestinationTest)
>>>>> Time elapsed: 10.495 sec <<< FAILURE!
>>>>> java.lang.AssertionError: Can't receive the Destination message in 10
>>>>> seconds
>
Re: JMS test fallure
Posted by Daniel Kulp <dk...@apache.org>.
On Fri August 28 2009 8:34:46 pm Willem Jiang wrote:
> Hi Dan,
>
> Maybe we need to switch the JMS broker to use the VM transport instead
> of the TCP transport for the Unit test.
Sure. I have no idea how to do it. :-)
> We hit some JMS unit test issues in Apache Camel few month ago after
> upgrading the ActivemMQ version. And resolved them by switching the
> broker's transport.
Well, I know 5.2 doesn't work for us at all which is why I went with 5.1.
The transaction issue is fixed in the latest 5.3 snapshots, but 5.2 really
doesn't work.
Dan
> Willem
>
> Daniel Kulp wrote:
> > On Thu August 27 2009 10:06:33 pm Willem Jiang wrote:
> >> Hi Benson,
> >>
> >> I found after upgrading to ActiveMQ 5.1, the JMS broker need more time
> >> to create a durable subscriber jms destination.
> >> Added a sleep make the test passed again :)
> >
> > Willem, Thanks for tracking that down. I couldn't figure out why it
> > seemed to work OK for me 80% of the time, but randomly fail.
> >
> > One thing it DID teach me is how to use the "-rf" flag to maven 2.2.1.
> >
> > mvn -Pnochecks -rf rt/transports/jms
> >
> > was a popular call. :-)
> >
> > Dan
> >
> >> Willem
> >>
> >> Benson Margulies wrote:
> >>> Can't someone do something about:
> >>>
> >>> Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 28.232
> >>> sec <<< FAILURE!
> >>> testDurableSubscriber(org.apache.cxf.transport.jms.JMSDestinationTest)
> >>> Time elapsed: 10.495 sec <<< FAILURE!
> >>> java.lang.AssertionError: Can't receive the Destination message in 10
> >>> seconds
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: JMS test fallure
Posted by Willem Jiang <wi...@gmail.com>.
Hi Dan,
Maybe we need to switch the JMS broker to use the VM transport instead
of the TCP transport for the Unit test.
We hit some JMS unit test issues in Apache Camel few month ago after
upgrading the ActivemMQ version. And resolved them by switching the
broker's transport.
Willem
Daniel Kulp wrote:
> On Thu August 27 2009 10:06:33 pm Willem Jiang wrote:
>> Hi Benson,
>>
>> I found after upgrading to ActiveMQ 5.1, the JMS broker need more time
>> to create a durable subscriber jms destination.
>> Added a sleep make the test passed again :)
>
> Willem, Thanks for tracking that down. I couldn't figure out why it seemed
> to work OK for me 80% of the time, but randomly fail.
>
> One thing it DID teach me is how to use the "-rf" flag to maven 2.2.1.
>
> mvn -Pnochecks -rf rt/transports/jms
>
> was a popular call. :-)
>
> Dan
>
>
>> Willem
>>
>> Benson Margulies wrote:
>>> Can't someone do something about:
>>>
>>> Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 28.232
>>> sec <<< FAILURE!
>>> testDurableSubscriber(org.apache.cxf.transport.jms.JMSDestinationTest)
>>> Time elapsed: 10.495 sec <<< FAILURE!
>>> java.lang.AssertionError: Can't receive the Destination message in 10
>>> seconds
>
Re: JMS test fallure
Posted by Daniel Kulp <dk...@apache.org>.
On Thu August 27 2009 10:06:33 pm Willem Jiang wrote:
> Hi Benson,
>
> I found after upgrading to ActiveMQ 5.1, the JMS broker need more time
> to create a durable subscriber jms destination.
> Added a sleep make the test passed again :)
Willem, Thanks for tracking that down. I couldn't figure out why it seemed
to work OK for me 80% of the time, but randomly fail.
One thing it DID teach me is how to use the "-rf" flag to maven 2.2.1.
mvn -Pnochecks -rf rt/transports/jms
was a popular call. :-)
Dan
>
> Willem
>
> Benson Margulies wrote:
> > Can't someone do something about:
> >
> > Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 28.232
> > sec <<< FAILURE!
> > testDurableSubscriber(org.apache.cxf.transport.jms.JMSDestinationTest)
> > Time elapsed: 10.495 sec <<< FAILURE!
> > java.lang.AssertionError: Can't receive the Destination message in 10
> > seconds
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
Re: JMS test fallure
Posted by Willem Jiang <wi...@gmail.com>.
Hi Benson,
I found after upgrading to ActiveMQ 5.1, the JMS broker need more time
to create a durable subscriber jms destination.
Added a sleep make the test passed again :)
Willem
Benson Margulies wrote:
> Can't someone do something about:
>
> Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 28.232
> sec <<< FAILURE!
> testDurableSubscriber(org.apache.cxf.transport.jms.JMSDestinationTest)
> Time elapsed: 10.495 sec <<< FAILURE!
> java.lang.AssertionError: Can't receive the Destination message in 10 seconds
>