Hello Adrian and thanks for the suggestion,
the point is the use case is 100% asynchronous, the JMS client is
supposed to do other things and get notified when a reply comes. The
processing that the MDB on the other side is doing is quite lengthy
also, so this and the nature of the use case
Why don't you get the responses sent to your test?
The test can then wait for all responses or timeout.
Regards,
Adrian
On Fri, 2003-09-26 at 13:30, Stefan Puiu wrote:
Hello Adrian and thanks for the suggestion,
the point is the use case is 100% asynchronous, the JMS client is
supposed to
Adrian,
you lost me here, as far as I know a JMS destination can be either a JMS
queue or topic, from where either a message listener or a thread calling
receive() on the respective destination picks it up. The problem with
waiting for replies was the transaction deadlock problem, I've set all
Hey, I've set the isIdentical and the method that was causing me
problems (getValueObject) to be read-only, changed the behaviour of the
test class to do a synchroneous receive() after sending the message and
it works! The great thing is that eases my work in testing, because
instead of having
Hello,
I'm using JBoss 3.2.1, the 1.4.2 Sun JDK on Mandrake Linux 9.1.
I have some test classes that need to send messages on a JMS queue and
expect an answer on another queue. I also read some information from a
database that I use to build the messages (namely, it's a getter
method). Now, I
The answer to your specific question is something like
the following in jboss.xml:
enterprise-beans
entity
ejb-nameCMRTreeBean/ejb-name
local-jndi-namejava:/cmrTransactionTest/TreeLocal/local-jndi-name
method-attributes
method
