In ActiveMQ and probably others, it's possible to run an embedded broker within the client process. The client connects to the embedded broker and the embedded broker connects to the standalone broker. This allows the client to continue operating even when a connection to the standalone broker isn't possible, but it requires a more complicated configuration and it can mean that messages may disappear from the broker network when the client disconnects, which might be unacceptable depending on your needs.
On Dec 30, 2016 3:51 AM, "Clebert Suconic" <clebert.suco...@gmail.com> wrote: > You won't be connected. You need to either set recinnectiin options on your > connection factory or retry yourself. > > > This is valid for any broker I know. (Hornetq artemis Apolo activemq and a > few competitors I don't want to mention) > > > > On Wed, Dec 28, 2016 at 7:30 PM alopez27 <alo...@fcci-group.com> wrote: > > > I understand the persistence on the broker side, my question is on the > > client > > > > side. If the broker is down how I can assure the producer will send the > > > > messages as soon as the broker is backup? > > > > > > > > > > > > > > > > -- > > > > View this message in context: > > http://activemq.2283324.n4.nabble.com/How-to-persist-the- > producer-message-before-it-reach-the-broker-tp4720763.html > > > > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > > > >
