Hi Andrew,
1. I apologize for my bewildering request for a clarification of each time it
fires. I read too quickly and missed a MDB from the beginning of your
question, and I thought JBoss Messaging was the antecedent of it.
2. With your help I was able to reproduce the WARNING message, and
Hi Andrew,
I'm the author of that warning, which I expected to appear only in the event of
some unexpected problem. Are you saying that that it's appearing in the normal
course of events, in the absence of any problematic conditions, when you start
and stop the server? Could you clarify the
Hi Ron,
Thanks for your response. I have spent a bit of time investigating the
circumstances that trigger the WARN message, and can advise that it only seems
to be triggered after a call to the connection close() method.
If you run the following code snippet in a session bean you ought to be
First observation - you are using the ConnectionFactory at /ConnectionFactory
in JNDI - this is the non JCA (plain) connection factory - so you will be
creating and closing a real JMS connection every time the MDB receives a
message!
This is going to be *slow*. I'm assuming this is not what
Tim, thanks for the feedback.
anonymous wrote :
| This is going to be *slow*. I'm assuming this is not what you intended to
do.
No, it was not intentional but an oversight on my part due to my limited
experience with messaging.
I have changed over to the JmsXA connection factory and this
Apologies, forgot to mention - I'm running jboss-messaging-1.2.0.SP1 on
jboss-4.0.5.GA
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4040193#4040193
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4040193
