Filed this issue about a week ago per this email thread.
https://issues.apache.org/activemq/browse/AMQ-1780
Can someone give an ETA on this? This is a production problem for us
currently
jaya_srini wrote:
>
> Ah..ok. Got it.
>
> I'll raise a new JIRA issue then.
>
> thanks
> jaya
>
>
Ah..ok. Got it.
I'll raise a new JIRA issue then.
thanks
jaya
Mario Siegenthaler-2 wrote:
>
> No, if you're not using master/slave, then the issues are not going to
> hurt you (the 1591 is fixed btw).
> If your prefered db driver does not support auto-reconnect and it your
> broker stops work
No, if you're not using master/slave, then the issues are not going to
hurt you (the 1591 is fixed btw).
If your prefered db driver does not support auto-reconnect and it your
broker stops working after a failed db statement then I'd raise a new
JIRA issue.
The master/slave thing is not really con
Hi Mario
We are using only one Broker and we are still seeing this issue i.e Broker
not automatically reconnecting to the database
Will I need fixes to both the issues below
http://issues.apache.org/activemq/browse/AMQ-1591
https://issues.apache.org/activemq/browse/AMQ-1350
in order for the
Hi
Depending on the JDBC driver you can have the driver to auto-reconnect
(I think jTDS supports that). However there's a catch in that: The
broker looses the lock on the master/slave table, so you'll end up
with both being the master (if you use jdbc-master/slave). I didn't
check that with the new
Hi Jaya,
this is definitely a bug - can you raise an jira issue for it ?
cheers,
Rob
On 5 Jun 2008, at 22:28, jaya_srini wrote:
Hi Hiram
We are noticing that after any SQL Server restart or network blip
between
ActiveMQ and the database, after the connection or the database
comes back
Hi Hiram
We are noticing that after any SQL Server restart or network blip between
ActiveMQ and the database, after the connection or the database comes back
online activeMQ broker needs to be restarted as well i.e it doesn't
automatically re-establish connection to the database as result any mes
you will have to ask your DB driver supplier to explain the
com.jnetdirect.jsql.x: DBComms.transmit
> exception:[java.net.SocketException error in more detail.
As far as having to restart the broker for that specific error, it
would be a no, because the the clean up task is periodic and can
handle
Forgot to ask this in my previous post...after the connection is restablished
will the broker be able to continue without a restart or will we need to
restart the broker every time there is a network issue like this?
thanks
jaya
jaya_srini wrote:
>
> Hello
>
> We are using ActiveMQ 5.0.0 and
