As Art said, the typical configuration is to have one standalone broker
that all clients (producers and consumers) connect to, that is available
even when the clients are not. This won't work if the clients frequently
are up but don't have network connectivity, or if no one is willing to host
and
Art, it's always been my understanding that static TCP transports would
reconnect when used as a networkConnector, and that the only reason to use
failover is if you have multiple brokers. Is that not accurate?
On Mar 12, 2016 11:17 PM, "artnaseef" wrote:
> Ahh, here it is from the original post
Thanks for you advice for tuning JDBC and configuration of network connector,
and we'll definitely try that. But it looks like the network connector is
closed from the source side due to local JDBC exception(the source side
means the source ActiveMQ server of forwarded message via network
connector
Other possibilities are a bug in ActiveMQ code where we fail to close() our
PreparedStatements in certain cases, and a bug in the connection pool.
On Mar 12, 2016 11:13 PM, "artnaseef" wrote:
> Any idea what is causing "Borrow prepareStatement from pool failed"?
>
> The only possible cause coming
