[
https://issues.apache.org/activemq/browse/AMQ-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Strachan resolved AMQ-1187.
---------------------------------
Resolution: Won't Fix
Many thanks guys for helping resolve this. So its clear that using the same
session/producer to send concurrently has issues; but then via the JMS
specification you are not meant to do this. So the workaround is either
* synchronise on the send method
* use a separate session/producer per thread
* use Camel as a facade over JMS to avoid these kinds of issues
* use Spring's JmsTemplate with the PoolingConnectionFactory
> Messages sent in parallel threads may not be enqueued
> -----------------------------------------------------
>
> Key: AMQ-1187
> URL: https://issues.apache.org/activemq/browse/AMQ-1187
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 4.0.2, 4.1.0
> Environment: Linux
> Reporter: Philippe Göllnitz
> Attachments: console.txt, jconsole.png, TestMqBroker.java,
> TestMqBroker2.java, TestMqBroker3.java
>
>
> I sent 1000 messages in own threads but monitoring the queue with jconsole
> sometimes only 999 are in the queue.
> This happens more likely if you raise the number of sent messages 10.000 or
> 100.000 but can also happen if set to 100.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
