Erlang/OTP Forums

Author Message

<  RabbitMQ mailing list  ~  Channel.isopen returns false and {timeout, running} exceptio

Guest
Posted: Tue Sep 29, 2009 7:35 am Reply with quote
Guest
Hi,

I am using RabbitMQ java client with default heart beat (Server is running
on linux machine). I am having two issues which i am unable to figure out.

(1) Sometimes when i try to open a new channel then channel.isopen returns
false although connections is still alive.

(2) Sometimes i got error like:
=ERROR REPORT==== 23-Sep-2009::05:18:22 ===
exception on TCP connection <0.22590.2> from 10.10.99.21:58705
{timeout,running}
can any body tell what could be the possible cause of this?

--
View this message in context: http://www.nabble.com/Channel.isopen-returns-false-and-%7Btimeout%2Crunning%7D-exception-tp25531373p25531373.html
Sent from the RabbitMQ mailing list archive at Nabble.com.


_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist
Guest
Posted: Tue Sep 29, 2009 7:55 am Reply with quote
Guest
Hi Katrina,

Are you able to reproduce this problem with a simple application? If you could provide simple code that reproduces the problem, it may make the issue easier to diagnose.

In the meantime, if you're finding that channels are closed when you don't expect them to be, you should also be able to call getCloseReason to query for information about why the channel is marked as closed.

Paul.

On Tue, Sep 29, 2009 at 8:35 AM, Katrina <adityagupta.iiitm@gmail.com (adityagupta.iiitm@gmail.com)> wrote:
Quote:

Hi,

I am using RabbitMQ java client with default heart beat
Guest
Posted: Tue Sep 29, 2009 5:10 pm Reply with quote
Guest
Hi Paul,

Yes the problem ({timeout,running}) is repeating again and again .. and
there is one mysterious finding .. dat it is repeating around same time (in
my case it is 01:00:52-56PST)

=ERROR REPORT==== 26-Sep-2009::01:00:56 ===
exception on TCP connection <0.17542.7> from 10.10.50.68:59706
{timeout,running}

=ERROR REPORT==== 27-Sep-2009::01:00:52 ===
exception on TCP connection <0.7164.10> from 10.10.50.68:50018
{timeout,running}

=ERROR REPORT==== 28-Sep-2009::01:00:52 ===
exception on TCP connection <0.28520.12> from 10.10.50.68:46859
{timeout,running}

=ERROR REPORT==== 29-Sep-2009::01:00:54 ===
exception on TCP connection <0.17111.15> from 10.10.50.68:60536
{timeout,running}

can u tell me wat r the possible causes/reasons for this condition to
arise???

thanks !!



Paul Jones-6 wrote:
>
> Hi Katrina,
>
> Are you able to reproduce this problem with a simple application? If you
> could provide simple code that reproduces the problem, it may make the
> issue
> easier to diagnose.
>
> In the meantime, if you're finding that channels are closed when you don't
> expect them to be, you should also be able to call getCloseReason to query
> for information about why the channel is marked as closed.
>
> Paul.
>
> On Tue, Sep 29, 2009 at 8:35 AM, Katrina
> <adityagupta.iiitm@gmail.com>wrote:
>
>>
>> Hi,
>>
>> I am using RabbitMQ java client with default heart beat (Server is
>> running
>> on linux machine). I am having two issues which i am unable to figure
>> out.
>>
>> (1) Sometimes when i try to open a new channel then channel.isopen
>> returns
>> false although connections is still alive.
>>
>> (2) Sometimes i got error like:
>> =ERROR REPORT==== 23-Sep-2009::05:18:22 ===
>> exception on TCP connection <0.22590.2> from 10.10.99.21:58705
>> {timeout,running}
>> can any body tell what could be the possible cause of this?
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Channel.isopen-returns-false-and-%7Btimeout%2Crunning%7D-exception-tp25531373p25531373.html
>> Sent from the RabbitMQ mailing list archive at Nabble.com.
>>
>>
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss@lists.rabbitmq.com
>> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss@lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>

--
View this message in context: http://www.nabble.com/Channel.isopen-returns-false-and-%7Btimeout%2Crunning%7D-exception-tp25531373p25667088.html
Sent from the RabbitMQ mailing list archive at Nabble.com.


_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist
Guest
Posted: Tue Sep 29, 2009 5:53 pm Reply with quote
Guest
Would you have any kind of networking event that happens at this time? For example, would it be possible that your network link gets reset?

Maybe you could try leaving an SSH connection open to the server over that time period, and see if it too ends up broken?

On Tue, Sep 29, 2009 at 6:10 PM, Katrina <adityagupta.iiitm@gmail.com (adityagupta.iiitm@gmail.com)> wrote:
Quote:

Hi Paul,

Yes the problem ({timeout,running}) is repeating again and again .. and
there is one mysterious finding .. dat
Guest
Posted: Tue Sep 29, 2009 6:00 pm Reply with quote
Guest
Katrina,

Paul Jones wrote:
> Would you have any kind of networking event that happens at this time?
> For example, would it be possible that your network link gets reset?
>
> Maybe you could try leaving an SSH connection open to the server over
> that time period, and see if it too ends up broken?

Actually, my guess would be that the error is caused by a busy machine,
perhaps due to backups or some other heavy duty cron jobs running.

I have seen heartbeat timeouts (that's what the {timeout,running} error
is) getting triggered under those circumstance on a customer system.

If so then the solution is to either increase the heartbeat interval or
turn off heartbeats altogether (by setting the interval to 0 in the client).


Regards,

Matthias.

_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist
Guest
Posted: Mon Oct 12, 2009 7:09 am Reply with quote
Guest
Hi Matthias,

the problem is still occurring ... till now we had set heartbeat as "10" ..
so wat if we set it to '0'.

Actually.. wat we are doing is .. we create a rabbitMQ connection through
our ..java client .. thn all the channels created we save them in
threadlocal .. so . while getting the channel .. we only check for (
channel.isopen()) ... and if connection got terminated or disconnected ..
then we .. call .. the shutdown listener ..

so my .. question is .. if we set heartbeat as "0" .. then will
shutdownlistner get called ??



Matthias Radestock-2 wrote:
>
> Katrina,
>
> Paul Jones wrote:
>> Would you have any kind of networking event that happens at this time?
>> For example, would it be possible that your network link gets reset?
>>
>> Maybe you could try leaving an SSH connection open to the server over
>> that time period, and see if it too ends up broken?
>
> Actually, my guess would be that the error is caused by a busy machine,
> perhaps due to backups or some other heavy duty cron jobs running.
>
> I have seen heartbeat timeouts (that's what the {timeout,running} error
> is) getting triggered under those circumstance on a customer system.
>
> If so then the solution is to either increase the heartbeat interval or
> turn off heartbeats altogether (by setting the interval to 0 in the
> client).
>
>
> Regards,
>
> Matthias.
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss@lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>

--
View this message in context: http://www.nabble.com/Channel.isopen-returns-false-and-%7Btimeout%2Crunning%7D-exception-tp25531373p25851350.html
Sent from the RabbitMQ mailing list archive at Nabble.com.


_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist
Guest
Posted: Mon Oct 12, 2009 8:42 am Reply with quote
Guest
Katrina,

Katrina wrote:
> the problem is still occurring ... till now we had set heartbeat as "10" ..
> so wat if we set it to '0'.
> [...]
> so my .. question is .. if we set heartbeat as "0" .. then will
> shutdownlistner get called ??

The shutdown listeners should get called when the connection is
terminated, whatever the reason.

Note that in the RabbitMQ 1.7.0 clients the default heartbeat interval
is 0, i.e. disabled. So if you are using the 1.7.0 Java client, simply
removing your explicit "10" setting ought to disable heartbeats.


Regards,

Matthias.

_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist

Display posts from previous:  

All times are GMT
Page 1 of 1
This forum is locked: you cannot post, reply to, or edit topics.

Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum