Skip Menu |

This queue is for tickets about the POE-Component-Jabber CPAN distribution.

Report information
The Basics
Id: 23627
Status: resolved
Priority: 0/
Queue: POE-Component-Jabber

People
Owner: Nobody in particular
Requestors: km [...] krot.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 1.21
Fixed in:
  • 2.0
  • 2.01



Subject: Client::XMPP reconnecting
Reconnect to the server when connection goes down works sometimes, but it seems to me that reconnecting from ErrorEvent goes bad if error is of type PCJ_SOCKFAIL. I think I've found out why 'reconnect_to_server' does not do what it was supposed to do in case of sudden disconnection from the server. When ReadWrite wheel in XMPP component is created, Client::TCP's 'got_server_error' event should be fired off on ReadWrite's errors. The problem with 'got_server_error' is that it will call 'shutdown' on the Client::TCP session, and there the session's alias will be removed and as the result the session itself will disappear. As a result, calling 'reconnect_to_server' in that session after it's shut down won't help as the session will be gone. Nick: You asked to submit a ticket - here is it. Thanks!
Subject: Re: [rt.cpan.org #23627] Client::XMPP reconnecting
Date: Tue, 5 Dec 2006 11:42:10 -0600
To: bug-POE-Component-Jabber [...] rt.cpan.org
From: "Nicholas Perez" <nicholasrperez [...] gmail.com>
Thanks for ticket. I've got my development box done at this point (ie, things disconnect and reconnect without problems). I still need to test some more and iron out some corner cases (eg. add in a simple check for an error state before trying to push something into a wheel, so it doesn't bring the whole application down), go through and complete documentation and fill out the changelog. It is a major revision. I am going to bump to 2.0. If it is going to kill you to tweak your code (very simple changes are needed, but there is much more information available if you wanted to expand your app a bit), I can rev the old code with a hack and push it out on CPAN. Anyhow, I'm going to try to and get things settled this week and out on to CPAN by the next weekend. I just started a new job that looks like it is going to have much less stress, therefore more brain cycles for post work programming. Thanks for using PCJ, Nick On 11/26/06, Kirill Miazine via RT <bug-POE-Component-Jabber@rt.cpan.org> wrote: Show quoted text
> > Sun Nov 26 12:31:36 2006: Request 23627 was acted upon. > Transaction: Ticket created by krot > Queue: POE-Component-Jabber > Subject: Client::XMPP reconnecting > Broken in: 1.21 > Severity: Important > Owner: Nobody > Requestors: km@krot.org > Status: new > Ticket <URL: http://rt.cpan.org/Ticket/Display.html?id=23627 > > > > Reconnect to the server when connection goes down works sometimes, but > it seems to me that reconnecting from ErrorEvent goes bad if error is of > type PCJ_SOCKFAIL. > > I think I've found out why 'reconnect_to_server' does not do what it was > supposed to do in case of sudden disconnection from the server. > > When ReadWrite wheel in XMPP component is created, Client::TCP's > 'got_server_error' event should be fired off on ReadWrite's errors. The > problem with 'got_server_error' is that it will call 'shutdown' on the > Client::TCP session, and there the session's alias will be removed and > as the result the session itself will disappear. As a result, calling > 'reconnect_to_server' in that session after it's shut down won't help as > the session will be gone. > > Nick: You asked to submit a ticket - here is it. Thanks! >
This should be fixed now, but if you find you are still having problems with it in the 2.x branch, let me know (and subsequently, write me a .t that tests it :)