On 03/23/2016 08:56 AM, Aleks Balaban wrote:
Tim,
Thx, good to know that the failover works! Obviously I've been doing
something wrong. Well, as you requested here is my JMS/AMQP client
source (I have removed the SSL initialization part used for amqps
conncetion ):
Your code relies on
Tim,
Thx, good to know that the failover works! Obviously I've been doing
something wrong. Well, as you requested here is my JMS/AMQP client
source (I have removed the SSL initialization part used for amqps
conncetion ):
Connection URI:
connectionfactory.nm =
On 03/22/2016 12:51 PM, Aleks Balaban wrote:
Thank you for writing back. My client quite minimalistic JMS client
application with usual JMS stuff such as Connection, Session objects
and "onMessage" listeners, which does nothing but connect to an AMQP
server and waits to receive
Thank you for writing back. My client quite minimalistic JMS client
application with usual JMS stuff such as Connection, Session objects and
"onMessage" listeners, which does nothing but connect to an AMQP server
and waits to receive notifications/messages. It works just fine, only it
isn't
I'd recommend that you post some code to show what your client is
doing. The logs really don't provide enough information to diagnose
what might be going on.
On 03/22/2016 11:07 AM, Aleks Balaban wrote:
Hi,
Im using Qpid JMS 0.8.0 library in order to implement a standalone
Java AMQP
Hi,
Im using Qpid JMS 0.8.0 library in order to implement a standalone Java
AMQP client. Because the underlying transport connection tends to break
every couple of hours I was trying to configure the reconnection
attempts (like failover but to the same server) using following
configuration:
