we noticed that when the RabbitMQ-Server fails the river is giving this
errormessage in the log:
[2012-06-08 15:45:14,362][WARN ][river.rabbitmq ] [Lincoln,
Lonnie Thompson] [rabbitmq][my_river71] failed to ack [498547]
com.rabbitmq.client.AlreadyClosedException: clean connection shutdown;
reason: Attempt to use closed channel
at
com.rabbitmq.client.impl.AMQChannel.ensureIsOpen(AMQChannel.java:190)
at com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:291)
at com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:285)
at com.rabbitmq.client.impl.ChannelN.basicAck(ChannelN.java:872)
at
org.elasticsearch.river.rabbitmq.RabbitmqRiver$Consumer.run(RabbitmqRiver.java:274)
at java.lang.Thread.run(Thread.java:636)
and then the river is not trying to reconnect (we waited at least 10
minutes). Is there a longer timeout or is this a bug?
we noticed that when the RabbitMQ-Server fails the river is giving this
errormessage in the log:
[2012-06-08 15:45:14,362][WARN ][river.rabbitmq ] [Lincoln,
Lonnie Thompson] [rabbitmq][my_river71] failed to ack [498547]
com.rabbitmq.client.AlreadyClosedException: clean connection shutdown;
reason: Attempt to use closed channel
at
com.rabbitmq.client.impl.AMQChannel.ensureIsOpen(AMQChannel.java:190)
at
com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:291)
at
com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:285)
at com.rabbitmq.client.impl.ChannelN.basicAck(ChannelN.java:872)
at
org.elasticsearch.river.rabbitmq.RabbitmqRiver$Consumer.run(RabbitmqRiver.java:274)
at java.lang.Thread.run(Thread.java:636)
and then the river is not trying to reconnect (we waited at least 10
minutes). Is there a longer timeout or is this a bug?
It's look really like what I have already seen with the twitter river.
After a failure, the river doesn't restart itself. And nothing in logs (only the failure with twitter).
I don't know if you remember this thread (it was in April I think), you asked me to set the river log level to debug but we did not see anything strange.
Could these issues be relative (Elasticsearch rivers internal) or not (relative to each river plugin) ?
Thanks
David
Twitter : @dadoonet / @elasticsearchfr
we noticed that when the RabbitMQ-Server fails the river is giving this errormessage in the log:
[2012-06-08 15:45:14,362][WARN ][river.rabbitmq ] [Lincoln, Lonnie Thompson] [rabbitmq][my_river71] failed to ack [498547]
com.rabbitmq.client.AlreadyClosedException: clean connection shutdown; reason: Attempt to use closed channel
at com.rabbitmq.client.impl.AMQChannel.ensureIsOpen(AMQChannel.java:190)
at com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:291)
at com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:285)
at com.rabbitmq.client.impl.ChannelN.basicAck(ChannelN.java:872)
at org.elasticsearch.river.rabbitmq.RabbitmqRiver$Consumer.run(RabbitmqRiver.java:274)
at java.lang.Thread.run(Thread.java:636)
and then the river is not trying to reconnect (we waited at least 10 minutes). Is there a longer timeout or is this a bug?
A thread dump shows that the river is not stopped but waits in the
LinkingBlockingQueue.
Maybe using a nextDelivery with a timeout to force to client to reconnect,
but I'm not sure that's the good solution ...
Vladislav
Le mardi 12 juin 2012 22:58:53 UTC+2, David Pilato a écrit :
Hi Shay,
It's look really like what I have already seen with the twitter river.
After a failure, the river doesn't restart itself. And nothing in logs
(only the failure with twitter).
I don't know if you remember this thread (it was in April I think), you
asked me to set the river log level to debug but we did not see anything
strange.
Could these issues be relative (Elasticsearch rivers internal) or not
(relative to each river plugin) ?
Thanks
David
Twitter : @dadoonet / @elasticsearchfr
Le 12 juin 2012 à 11:25, Shay Banon <kim...@gmail.com <javascript:>> a
écrit :
Seems like the connection to rabbitmq is closed, wondering how it
happened... . Do you see any other messages?
On Fri, Jun 8, 2012 at 6:13 PM, Max Kossatz <max.k...@gmail.com<javascript:>
wrote:
Hi,
we noticed that when the RabbitMQ-Server fails the river is giving this
errormessage in the log:
[2012-06-08 15:45:14,362][WARN ][river.rabbitmq ] [Lincoln,
Lonnie Thompson] [rabbitmq][my_river71] failed to ack [498547]
com.rabbitmq.client.AlreadyClosedException: clean connection shutdown;
reason: Attempt to use closed channel
at
com.rabbitmq.client.impl.AMQChannel.ensureIsOpen(AMQChannel.java:190)
at
com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:291)
at
com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:285)
at com.rabbitmq.client.impl.ChannelN.basicAck(ChannelN.java:872)
at
org.elasticsearch.river.rabbitmq.RabbitmqRiver$Consumer.run(RabbitmqRiver.java:274)
at java.lang.Thread.run(Thread.java:636)
and then the river is not trying to reconnect (we waited at least 10
minutes). Is there a longer timeout or is this a bug?
After hours of debugging, I found
that consumer.nextDelivery(bulkTimeout.millis()) throws
a ShutdownSignalException.
This RuntimeException is not catched by the catch block which only catch
InterruptedException.
So the thread exit silently.
Le mercredi 6 mars 2013 16:08:15 UTC+1, Vladislav Pernin a écrit :
Hi,
Has any of you found the solution ?
A thread dump shows that the river is not stopped but waits in the
LinkingBlockingQueue.
Maybe using a nextDelivery with a timeout to force to client to reconnect,
but I'm not sure that's the good solution ...
Vladislav
Le mardi 12 juin 2012 22:58:53 UTC+2, David Pilato a écrit :
Hi Shay,
It's look really like what I have already seen with the twitter river.
After a failure, the river doesn't restart itself. And nothing in logs
(only the failure with twitter).
I don't know if you remember this thread (it was in April I think), you
asked me to set the river log level to debug but we did not see anything
strange.
Could these issues be relative (Elasticsearch rivers internal) or not
(relative to each river plugin) ?
Thanks
David
Twitter : @dadoonet / @elasticsearchfr
we noticed that when the RabbitMQ-Server fails the river is giving this
errormessage in the log:
[2012-06-08 15:45:14,362][WARN ][river.rabbitmq ] [Lincoln,
Lonnie Thompson] [rabbitmq][my_river71] failed to ack [498547]
com.rabbitmq.client.AlreadyClosedException: clean connection shutdown;
reason: Attempt to use closed channel
at
com.rabbitmq.client.impl.AMQChannel.ensureIsOpen(AMQChannel.java:190)
at
com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:291)
at
com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:285)
at com.rabbitmq.client.impl.ChannelN.basicAck(ChannelN.java:872)
at
org.elasticsearch.river.rabbitmq.RabbitmqRiver$Consumer.run(RabbitmqRiver.java:274)
at java.lang.Thread.run(Thread.java:636)
and then the river is not trying to reconnect (we waited at least 10
minutes). Is there a longer timeout or is this a bug?
After hours of debugging, I found that consumer.nextDelivery(bulkTimeout.millis()) throws a ShutdownSignalException.
This RuntimeException is not catched by the catch block which only catch InterruptedException.
So the thread exit silently.
Le mercredi 6 mars 2013 16:08:15 UTC+1, Vladislav Pernin a écrit :
Hi,
Has any of you found the solution ?
A thread dump shows that the river is not stopped but waits in the LinkingBlockingQueue.
Maybe using a nextDelivery with a timeout to force to client to reconnect, but I'm not sure that's the good solution ...
Vladislav
Le mardi 12 juin 2012 22:58:53 UTC+2, David Pilato a écrit :
Hi Shay,
It's look really like what I have already seen with the twitter river.
After a failure, the river doesn't restart itself. And nothing in logs (only the failure with twitter).
I don't know if you remember this thread (it was in April I think), you asked me to set the river log level to debug but we did not see anything strange.
Could these issues be relative (Elasticsearch rivers internal) or not (relative to each river plugin) ?
Thanks
David
Twitter : @dadoonet / @elasticsearchfr
Seems like the connection to rabbitmq is closed, wondering how it happened... . Do you see any other messages?
On Fri, Jun 8, 2012 at 6:13 PM, Max Kossatz max.k...@gmail.com wrote:
Hi,
we noticed that when the RabbitMQ-Server fails the river is giving this errormessage in the log:
[2012-06-08 15:45:14,362][WARN ][river.rabbitmq ] [Lincoln, Lonnie Thompson] [rabbitmq][my_river71] failed to ack [498547]
com.rabbitmq.client.AlreadyClosedException: clean connection shutdown; reason: Attempt to use closed channel
at com.rabbitmq.client.impl.AMQChannel.ensureIsOpen(AMQChannel.java:190)
at com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:291)
at com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:285)
at com.rabbitmq.client.impl.ChannelN.basicAck(ChannelN.java:872)
at org.elasticsearch.river.rabbitmq.RabbitmqRiver$Consumer.run(RabbitmqRiver.java:274)
at java.lang.Thread.run(Thread.java:636)
and then the river is not trying to reconnect (we waited at least 10 minutes). Is there a longer timeout or is this a bug?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.