It could also indicate that you have the port wrong (which doesn't seem
likely since you say that this is after a broker restart) or that the
broker isn't currently listening on that port for some reason (though
that isn't expected and would likely be a bug if that's what's happening).
I think it's
On 12/22/2014 10:55 AM, khandelwalanuj wrote:
Hi,
We have seen this warning lot of time in client side logs.
"java.net.ConnectException: Connection refused"
As we can see in stacktrace that this is not generated from ActiveMQ code or
any JMSException. This is coming from lower layer.
Can someo
Hi,
We have seen this warning lot of time in client side logs.
"java.net.ConnectException: Connection refused"
As we can see in stacktrace that this is not generated from ActiveMQ code or
any JMSException. This is coming from lower layer.
Can someone help me to understand this exception? When ca
