(Migrated) amqp broken pipe

(This message has been automatically imported from the retired mailing list)

Here I’m again…

I’ve configured amqp definition and connection.

Immediately it works well, but after 10 minutes of idle, it gives me the
following error:

2014-04-23 16:53:38,804 - ERROR - 6097:Thread-3 - zato.server.base:22 -
Could not handle broker msg:[Bunch(action=u’10603’, args=[],
body=u’{“index”: “queue_management”, “_type”: “queues”, “time_ts”:
1398264818000, “producer”: “postfix”, “time_iso”: “2014-04-23T16:53:38.7990
35”, “queues”: {“active”: 0, “deferred”: 0}, “hostname”: “sysdev02”,
“type”: “queues”, “id”: “201404231653”}’, exchange=u’sentinel-out’,
headers={}, kwargs={}, msg_type=u’0003’, out_name=u’SentinelOUT’,
properties={u’delivery_mode’: 2L, u’user_id’: u’guest’, u’app_id’: u’sen
tinel-out’}, routing_key=u’sentinel-out’)], e:[Traceback (most recent call
last):
File “/usr/local/zato-1.1/zato-server/src/zato/server/base/init.py”,
line 48, in on_broker_msg
getattr(self, handler)(msg)
File
"/usr/local/zato-1.1/zato-server/src/zato/server/connection/amqp/outgoing.py",
line 221, in on_broker_msg_OUTGOING_AMQP_PUBLISH
producer.publish(msg.body, routing_key=msg.routing_key,
exchange=msg.exchange, headers=headers, **properties)
File
"/usr/local/zato-1.1/eggs/kombu-2.5.10-py2.7.egg/kombu/messaging.py", line
164, in publish
routing_key, mandatory, immediate, exchange, declare)
File
"/usr/local/zato-1.1/eggs/kombu-2.5.10-py2.7.egg/kombu/messaging.py", line
180, in _publish
mandatory=mandatory, immediate=immediate,
File “/usr/local/zato-1.1/eggs/amqp-1.0.11-py2.7.egg/amqp/channel.py”,
line 2099, in basic_publish
self._send_method((60, 40), args, msg)
File
"/usr/local/zato-1.1/eggs/amqp-1.0.11-py2.7.egg/amqp/abstract_channel.py",
line 58, in _send_method
self.channel_id, method_sig, args, content,
File
"/usr/local/zato-1.1/eggs/amqp-1.0.11-py2.7.egg/amqp/method_framing.py",
line 219, in write_method
write_frame(1, channel, payload)
File “/usr/local/zato-1.1/eggs/amqp-1.0.11-py2.7.egg/amqp/transport.py”,
line 157, in write_frame
pack(’>BHI%dsB’ % size, frame_type, channel, size, payload, 0xce),
File “/usr/lib/python2.7/socket.py”, line 224, in meth
return getattr(self._sock,name)(*args)
error: [Errno 104] Connection reset by peer

Thank you :slight_smile:

On 04/23/2014 05:02 PM, Giovanni Colapinto wrote:

File “/usr/lib/python2.7/socket.py”, line 224, in meth
return getattr(self._sock,name)(*args)
error: [Errno 104] Connection reset by peer

Hi Giovanni,

The only situation I saw it in was when the user credentials were
incorrect - on Python end this manifested as an Errno 104, for some reason.

How does it look like on your AMQP broker’s end? Can you turn some kind
of tracing on and learn what it thinks happens at that time?

thanks,

On 04/23/2014 05:02 PM, Giovanni Colapinto wrote:

File “/usr/lib/python2.7/socket.py”, line 224, in meth
return getattr(self._sock,name)(*args)
error: [Errno 104] Connection reset by peer

Hi Giovanni,

The only situation I saw it in was when the user credentials were
incorrect - on Python end this manifested as an Errno 104, for some reason.

How does it look like on your AMQP broker’s end? Can you turn some kind
of tracing on and learn what it thinks happens at that time?

thanks,

I notice strange beahaviours with my zato version, so I decided to create a
new zato installation, starting from ubuntu packages

Cheers

On Wed, Apr 23, 2014 at 5:08 PM, Dariusz Suchojad dsuch@zato.io wrote:

On 04/23/2014 05:02 PM, Giovanni Colapinto wrote:

File “/usr/lib/python2.7/socket.py”, line 224, in meth
return getattr(self._sock,name)(*args)
error: [Errno 104] Connection reset by peer

Hi Giovanni,

The only situation I saw it in was when the user credentials were
incorrect - on Python end this manifested as an Errno 104, for some reason.

How does it look like on your AMQP broker’s end? Can you turn some kind
of tracing on and learn what it thinks happens at that time?

thanks,


Dariusz Suchojad

https://zato.io
ESB, SOA, REST, APIs and cloud integrations in Python

On 04/24/2014 08:42 AM, Giovanni Colapinto wrote:

I notice strange beahaviours with my zato version, so I decided to create a
new zato installation, starting from ubuntu packages

Ok, this won’t hurt but should it happen again, please let me know how
it looks like from AMQP’s end.

thanks a lot,