activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arthur Naseef <...@amlinv.com>
Subject Re: Failover Transport hangs forever on connection.start() in Master/Slave
Date Mon, 29 Apr 2019 21:59:15 GMT
Can you upload the full stack dump from the client application when this
happens as a GIST on github.com and send the link?  It's OK to filter out
any proprietary bits as long as all of the threads that have ActiveMQ in
the call history are listed.

BTW, the "oneWay" method sends a message over the transport - one way - and
is not involved in reconnect logic itself.  So blocking on that
reconnectMutex is normal given that somehow the reconnect logic is failing
to connect.  BTW with these settings,
startupMaxReconnectAttempts=5&maxReconnectAttempts=5, the transport will
stop attempting to reconnect - is it possible the application has failed
that many times and therefore just given up on attempting to reconnect?

Art


On Thu, Apr 25, 2019 at 7:28 AM smantri <shraddha.mantri@infor.com> wrote:

> I am using activemq version 5.15.8. I see the  issue when client first time
> tries to connect to activemq broker and if the randomly picked broker url
> happens to be slave, the call is stuck forever in FailoverTransport class
> at
> the following point:
>
> ##############################
>  @Override
>     public void oneway(Object o) throws IOException {
>
>         Command command = (Command) o;
>         Exception error = null;
>         try {
>
>             synchronized (reconnectMutex) {         <<<<<< blocked
here
> >>>>>
>
> ##############################
>
> call is stuck at the above point till i make one of the instance(either
> master or slave) for activemq go down.
>
>
>
> mikmela wrote
> > You haven't mentioned a version of your activemq, there were some issues
> > with
> > that in older versions...
> > We're on 5.6.0 and above - no issues...
> > See
> > http://activemq.apache.org/failover-transport-reference
> > &lt;http://activemq.apache.org/failover-transport-reference&gt;
> >
> >
> >
> > --
> > Sent from:
> > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>
>
> mikmela wrote
> > You haven't mentioned a version of your activemq, there were some issues
> > with
> > that in older versions...
> > We're on 5.6.0 and above - no issues...
> > See
> > http://activemq.apache.org/failover-transport-reference
> > &lt;http://activemq.apache.org/failover-transport-reference&gt;
> >
> >
> >
> > --
> > Sent from:
> > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>
>
> mikmela wrote
> > You haven't mentioned a version of your activemq, there were some issues
> > with
> > that in older versions...
> > We're on 5.6.0 and above - no issues...
> > See
> > http://activemq.apache.org/failover-transport-reference
> > &lt;http://activemq.apache.org/failover-transport-reference&gt;
> >
> >
> >
> > --
> > Sent from:
> > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>
>
> mikmela wrote
> > You haven't mentioned a version of your activemq, there were some issues
> > with
> > that in older versions...
> > We're on 5.6.0 and above - no issues...
> > See
> > http://activemq.apache.org/failover-transport-reference
> > &lt;http://activemq.apache.org/failover-transport-reference&gt;
> >
> >
> >
> > --
> > Sent from:
> > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>
>
>
>
>
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message