I meant to add a comment here-
I've only fixed StandardProviderProcessor, MultiplexingProviderProcessor,
and StandardConsumerProcessor. MultiplexingConsumerProcessor is a bit more
complicated and I unfortunately don't have time for it right now.
I tested with mySQL and the jdbcStore, which worked fine except that the
size of the id column that the Store created was too small for the exchange
ID.. I suppose it should just be bigger by default, and I haven't fixed that
yet.
-Sam
JIRA [EMAIL PROTECTED] wrote:
In-Out Exchanges in a JMS queue cannot be successfully processed after a
crash/shutdown
---
Key: SM-998
URL: https://issues.apache.org/activemq/browse/SM-998
Project: ServiceMix
Issue Type: Bug
Components: servicemix-jms
Affects Versions: 3.1.2
Environment: any
Reporter: Sam Gerstein
Fix For: 3.1.2
Attachments: servicemix-jms_patch.txt
Because a temporary queue is used for the reply-to destination and the
Exchange is stored in an in-memory Map, In-Out message exchanges in a JMS
queue cannot be returned to their sender after a crash or shutdown of
ServiceMix.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
--
View this message in context:
http://www.nabble.com/-jira--Created%3A-%28SM-998%29-In-Out-Exchanges-in-a-JMS-queue-cannot-be-successfully-processed-after-a-crash-shutdown-tf4058643s12049.html#a11530104
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
