php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Request #59977 Better disconnect handling
Submitted: 2011-09-29 10:32 UTC Modified: 2011-10-08 02:55 UTC
From: henrik dot westphal at gmail dot com Assigned:
Status: Closed Package: amqp (PECL)
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
View Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem:
10 + 14 = ?
Subscribe to this entry?

 
 [2011-09-29 10:32 UTC] henrik dot westphal at gmail dot com 
Description:
------------
When calling AMQPConnection::disconnect() the socket seems to be closed directly instead of sending a "connection.close" command and waiting for "connection.close_ok".
This results in the "connection_closed_abruptly" warning in the RabbitMQ log.

Expected result:
----------------
=INFO REPORT==== 29-Sep-2011::16:25:09 ===
accepted TCP connection on [::]:5672 from 127.0.0.1:49481

=INFO REPORT==== 29-Sep-2011::16:25:09 ===
starting TCP connection <0.12642.0> from 127.0.0.1:49481

=INFO REPORT==== 29-Sep-2011::16:25:09 ===
closing TCP connection <0.12642.0> from 127.0.0.1:49481

Actual result:
--------------
=INFO REPORT==== 29-Sep-2011::16:24:04 ===
accepted TCP connection on [::]:5672 from 127.0.0.1:49480

=INFO REPORT==== 29-Sep-2011::16:24:04 ===
starting TCP connection <0.12544.0> from 127.0.0.1:49480

=WARNING REPORT==== 29-Sep-2011::16:24:04 ===
exception on TCP connection <0.12544.0> from 127.0.0.1:49480
connection_closed_abruptly

=INFO REPORT==== 29-Sep-2011::16:24:04 ===
closing TCP connection <0.12544.0> from 127.0.0.1:49480

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2011-10-08 02:55 UTC] pdezwart at gmail dot com 
This bug has been fixed in SVN.

In case this was a documentation problem, the fix will show up at the
end of next Sunday (CET) on pecl.php.net.

In case this was a pecl.php.net website problem, the change will show
up on the website in short time.
 
Thank you for the report, and for helping us make PECL better.

Fixed in trunk @ r317885
 
PHP Copyright © 2001-2026 The PHP Group
All rights reserved. 		Last updated: Mon Jan 05 03:00:01 2026 UTC