You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running amqproxy/0.8.6 with a PHP AMQP consumer.
After a while I can observe that the consumer stops processing messages from the queue. The processing continues after the consumer is being restarted. At the same time I can see the following errors in the amqproxy log:
2023-03-23 10:07:26 UTC: Proxy upstream: 10.10.100.33:5672
2023-03-23 10:07:26 UTC: Proxy listening on 0.0.0.0:5673
2023-03-23 12:25:33 UTC: Error reading from upstream: End of file reached (IO::EOFError)
from usr/share/crystal/src/io.cr:523:27 in 'read_fully'
from tmp/lib/amq-protocol/src/amq/protocol/frames.cr:26:9 in 'read_loop'
from tmp/src/amqproxy/upstream.cr:33:7 in '->'
from usr/share/crystal/src/fiber.cr:146:11 in 'run'
from usr/share/crystal/src/fiber.cr:98:34 in '->'
from ???
2023-03-23 12:45:59 UTC: Upstream connection closed when returned
2023-03-23 15:57:40 UTC: Error reading from upstream: End of file reached (IO::EOFError)
from usr/share/crystal/src/io.cr:523:27 in 'read_fully'
from tmp/lib/amq-protocol/src/amq/protocol/frames.cr:26:9 in 'read_loop'
from tmp/src/amqproxy/upstream.cr:33:7 in '->'
from usr/share/crystal/src/fiber.cr:146:11 in 'run'
from usr/share/crystal/src/fiber.cr:98:34 in '->'
from ???
2023-03-23 16:05:15 UTC: Upstream connection closed when returned
2023-03-23 16:09:12 UTC: Error reading from upstream: End of file reached (IO::EOFError)
from usr/share/crystal/src/io.cr:523:27 in 'read_fully'
from tmp/lib/amq-protocol/src/amq/protocol/frames.cr:26:9 in 'read_loop'
from tmp/src/amqproxy/upstream.cr:33:7 in '->'
from usr/share/crystal/src/fiber.cr:146:11 in 'run'
from usr/share/crystal/src/fiber.cr:98:34 in '->'
from ???
2023-03-23 16:25:56 UTC: Upstream connection closed when returned
For reference, my consumer code is pretty basic and looks like this:
This change also removes the code added in #104
The motivation behind that is
* IO:_Error that happens in Upstream#connect is raised as Upstream::Error
* IO::Error that happens in Upstream#read_loop is rescued in that method
* IO::Error that happens in Client#read_loop is raised as Client::Error
Adds an integration test with the php-amqp client run via Docker Compose
and Toxiproxy.
Close#118Close#111Close#98
This change also removes the code added in #104
The motivation behind that is
* IO:_Error that happens in Upstream#connect is raised as Upstream::Error
* IO::Error that happens in Upstream#read_loop is rescued in that method
* IO::Error that happens in Client#read_loop is raised as Client::Error
Adds an integration test with the php-amqp client run via Docker Compose
and Toxiproxy.
Close#118Close#111Close#98
I'm running amqproxy/0.8.6 with a PHP AMQP consumer.
After a while I can observe that the consumer stops processing messages from the queue. The processing continues after the consumer is being restarted. At the same time I can see the following errors in the amqproxy log:
For reference, my consumer code is pretty basic and looks like this:
Any idea what might cause those issues?
The text was updated successfully, but these errors were encountered: