JMS reliability : AUTO_ACKNOWLEDGE vs. CLIENT_ACKNOWLEDGE

[samg]

Hi folks,
in my ongoing effort to not lose messages I've made another change to
servicemix-jms : It seems to me that three of the four processors
(standard/multiplexing consumer/provider combinations) can be trivially
switched to CLIENT_ACKNOWLEDGE without any performance hit at all (they can
all do the receive() and acknowledge() in one synchronous flow), so I've
done so.  I'm not using the MultiplexingConsumerProcessor, and it is the one
complex case.
This Issue :
https://issues.apache.org/activemq/browse/SM-555
 requests that it be added as an option, but perhaps it makes sense in these
cases to just switch over to CLIENT_ACKNOWLEDGE?  Let me know what you
think.
-Sam
-- 
View this message in context: 
http://www.nabble.com/JMS-reliability-%3A-AUTO_ACKNOWLEDGE-vs.-CLIENT_ACKNOWLEDGE-tf4105152s12049.html#a11674691
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.

Re: [jira] Created: (SM-998) In-Out Exchanges in a JMS queue cannot be successfully processed after a crash/shutdown

[samg]

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.