On Wed, 4 Jul 2001, Jason Dillon wrote:
> > Hm, I have never run the complete tests, therefore I never stumbled on the
> > problem. Another way of solving the probem is ofcourse to let for example
> > jmsra use some of the other queues that are defined in a standard
> > jbossmw.xml file.
>
> There is a QueueBean from the MDB tests that is still attached to the
> queue/testQueue which is breaking the jmsra tests. I think I have this
> fixed ala undeploy. Need to make sure though =)
>
> If this works then it might be a good idea to deploy/test/undeploy for all
> tests to avoid any problems like this in the future. It would also be a
> good test for deploy/undeploy.
>
> --jason
>
> > > I tried running the full test (ala sh ./build.sh -f run_tests.xml) but
> > > started getting odd server hangs while the application was being undeployed.
> > > It looked like it was going to just stay wedged, but would eventually
> > > continue with some messages about lost connections and such (I don't have
> > > the exact output... anymore... it scrolled... damn all that Address
> > > passivation fluff).
> >
> > Hm, hard for me to say anyting about it. I have not tested JMS and MDB at
> > al since Hiram made the latest changes to the ServerSessionPool stuff.
>
> I think that this was caused by a bug that I introduced in the
> test.util.Deploy class... I think. I have not gotten to look into the
> EOFException proplem more... which is what I really need fixed (for work).
> Perhaps I will have some time to look at that tonight. I was hoping that
> the test failure was related, but I do not think there is a direct relation.
>
> By the way, what is up with the topic to queue adapter thingy? I was
> confused by this, as well as the test for a topic using queue stuff, so I
> split up the queue/topic tests, or rather I abstracted the jms resource
> access from the test... not in the best way either, but it will work for
> now.
>
Well, I am not shure about what you mean. If you mean how the jmsra test
is done, the logic is that the client send messages and the expect to get
messages with a certain number, and not to get messages of a different
number (where a rollback will occur) from a queue. This is the way I done
it so that the client can actually get some feeling for that the suff
really worked.
//Peter
> --jason > > >
_______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
Jobba hos oss: http://www.tim.se/weblab
------------------------------------------------------------
Peter Antman Technology in Media, Box 34105 100 26 Stockholm
Systems Architect WWW: http://www.tim.se
Email: [EMAIL PROTECTED] WWW: http://www.backsource.org
Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942
------------------------------------------------------------
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
