Some additional information...
The error above only occurs on the third and subsequent send "in a row".
That is, the first and second time my MDB sends its JMS message without
errors, but the third time fails. "in a row", because if I leave a good
minute between attempts, it always works.
I have tried setting 'async' to false in the following ways, in ra.xml:
<config-property-name>ServerUrl</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>vm://jboss-activemq-broker?create=false&async=false</config-property-value>
...and in my *-ds.ml in deply directory:
<connection-definition>javax.jms.QueueConnectionFactory</connection-definition>
<ServerUrl>vm://jboss-activemq-broker?create=false&async=false</ServerUrl>
...but this hasen't made any difference.
(Also... apologies for the uninformative subject. I clicked too soon.)
--
View this message in context:
http://activemq.2283324.n4.nabble.com/javax-jms-InvalidClientIDException-tp4421798p4422074.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
