I noticed some strange behavior with ActiveMQ 4.1.1 and the Stomp protocol.
When I connect, I set the ack mode to "client". I read a message, and exit.
Since I did not ack the message, I should expect to get the same message on
next execution, and I do, as long as I do an explicit disconne
How about creating a consumer to receive the message and asserting the
message? There are examples of this throughout the ActiveMQ tests.
There's a really simple one in the
JMSConsumerTest.testReceiveMessageWithConsumer() test:
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/ja
On 5/26/07, Carfield Yim <[EMAIL PROTECTED]> wrote:
I've create a testcase according to
http://activemq.apache.org/how-to-unit-test-jms-code.html . However,
after I send the message, how can I assert my message really sent?
How about creating a consumer to receive the message and asserting the
On 5/25/07, Vinod_mit <[EMAIL PROTECTED]> wrote:
Hi friends
iam trying to connect mysql with acitvemq here is my code
and here is the description, i have copied
mysql-connector-java-5.0.5-bin.jar in activemq lib directory
here is my mysql
w
I've create a testcase according to
http://activemq.apache.org/how-to-unit-test-jms-code.html . However,
after I send the message, how can I assert my message really sent?
Hi,
I wonder if it's an issue with mysql driver/server compatibility.
Have you tried using other versions of the mysql connector?
Regards,
Jonas
Regards,
Jonas
Vinod_mit wrote:
Hi friends
iam trying to connect mysql with acitvemq here is my code
and here