Re: Producer blocks when trying to send async JMS messages to failed broker

Or for this case (where messages with age > 2 secs can be discarded), couldn't you have a variant... ignore the network connector status, and allow messages to be expired after 2000 milliseconds via setTimetoLive on the producer. - Michael Hayes B.Sc. (NUI), M.Sc. (DCU), SCSA SCNA -- View

Re: Producer blocks when trying to send async JMS messages to failed broker

yes, if the failure to connect/reconnect bubbles up to the application, it will need to initiate a new connection. fire and forget in jms terms is still mediated by the broker, and finding a broker is currently a synchronous operation. A jms connection that ignores the fact that it does not have a

Re: Producer blocks when trying to send async JMS messages to failed broker

Thanks Gary. I am still not completely sure I get it. I am using failover because I *do* want my client to reconnect when the broker comes back up. However, when it's down I don't want to queue messages or block anything - they can be thrown away. My messages really are 'fire and forget'. These

Re: Producer blocks when trying to send async JMS messages to failed broker

configure the failover maxReconnectAttempts and the failure to connect will bubble up to the application where you can ignore it. The assumption of failover is that you want to 'transparently' maintain the connection and block pending reconnect failover:(...)? maxReconnectAttempts=1 http://active