Ok I have had a look at the mq tests and they run fine for me, I didn't have
any trouble.
The only thing I changed was to use the rollinglogged persistence manager
instead of the file persistence manager for JBossMQ. This shouldn't change
anything except the performance (rolling logged is many times faster), I
only did it so the tests would finish in a reasonable time, as it was the
JBossMQPerfStressTestCase took nearly 5 minutes to finish. I would imagine
that with file persistence and running 1000 iterations the total time could
take something like an 30 minutes to an hour (this is only a rough estimate
based on my previous experience).
During the test several errors are thrown out by the engine, looking at the
code these errors are all created by the test code closing the session the
message listener is registered with too soon. In other words these errors
are difficult to avoid but harmless.
The errors in particular I am talking about are
[SpyMessageConsumer,WARN] Message consumer closing due to error in listening
thread.
javax.jms.JMSException: Invalid transaction id.
at
org.jboss.mq.SpyXAResourceManager.ackMessage(SpyXAResourceManager.java:62)
at org.jboss.mq.SpyMessageConsumer.run(SpyMessageConsumer.java:365)
at java.lang.Thread.run(Thread.java:484)
or
[SpyMessageConsumer,WARN] Message consumer closing due to error in listening
thread.
org.jboss.mq.SpyJMSException: Cannot create a ConnectionReceiver
at org.jboss.mq.Connection.receive(Connection.java:595)
at org.jboss.mq.SpyMessageConsumer.run(SpyMessageConsumer.java:319)
at java.lang.Thread.run(Thread.java:484)
linked exception is:
javax.jms.JMSException: The provided subscription does not exist
<<no stack trace available>>
These should happen at most once per run, and sometimes you get neither, if
the timing of the threads closing down happens in the right order.
Other than that everything seems fine to me. If you continue to have
trouble let me know.
Cheers
David
> -----Original Message-----
> From: David Maplesden [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 20, 2001 8:21 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: [JBoss-dev] Help wanted on jbossmq tests (rh/3.0)
>
>
> I'll have a look, I've been through the MQ test stuff before
> and it did all
> work originally. I haven't looked at it since all the
> changes to the build
> system and new test stuff so its not too surprising if its
> having trouble.
>
> I'll let you know how I get on.
>
> David
>
> > -----Original Message-----
> > From: David Jencks [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, September 20, 2001 7:35 AM
> > To: jboss-dev
> > Subject: [JBoss-dev] Help wanted on jbossmq tests (rh/3.0)
> >
> >
> > Hi,
> >
> > It appears that most of the jbossmq tests are not working
> > currently with
> > rh. Much of this appears to me to be configuration problems. On my
> > machine, running JBossMQPerfStressTestCase usually freezes
> > something so
> > that subsequent tests don't run and jboss will not shut
> down: for this
> > reason I commented it out of the testsuite/build.xml.
> >
> > Could the jbossmq experts take a look?
> >
> > You may find the ability to set counts via a local.properties
> > file useful:
> >
> > ### Test properties
> >
> > junit.timeout=120000
> > jbosstest.threadcount=2
> > jbosstest.iterationcount=2
> > jbosstest.beancount=2
> >
> >
> > You may find the one-test target useful:
> >
> > ./build.sh -DJBossMQPerfStressTestCase one-test
> >
> > runs only the named test.
> >
> > Thanks
> > david jencks
> >
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
> >
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
