camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Kahn (JIRA)" <>
Subject [jira] Commented: (CAMEL-659) XMPP endpoint should should auto-reconnect if it loses connection to the xmpp server
Date Sat, 05 Jul 2008 11:50:00 GMT


Michael Kahn commented on CAMEL-659:

I probably should not be asking this here - however, is there a general architectural approach
in camel for reconnecting or attempting to reinitialize a route that is failing due to an
IO-type error or exception?  I mean not just with the XMPP component but with components in
general.  It seems to me if certain errors occur "downstream", such as the above failure to
connect to the XMPP server, the entire route (i.e.: consuming the inbound endpoint) should/could
be suspended until the route can be properly reestablished.   Is this a feature that is there
already that I am missing?

> XMPP endpoint should should auto-reconnect if it loses connection to the xmpp server
> ------------------------------------------------------------------------------------
>                 Key: CAMEL-659
>                 URL:
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-xmpp
>    Affects Versions: 1.3.0
>            Reporter: Michael Kahn
> In 1.3.0, and related classes use the smack 2.2.1 API, and have a getConnection()
method that sets up and caches the xmpp connection and chat once when the endpoint is initialized.
If the network connection to the xmpp server is subsequently lost, attempts to route throw
an exception.  This makes use of this component on remote and roaming/wireless devices difficult.
> Smack API 3.0.4+ (the only version available for "official" download right now) should
auto-reconnect the XMPPConnection once it is created, reusing the same credentials from the
current login() session, however the API is not a drop-in replacement, there are a few differences.
 It also isn't in the maven repository yet - that maxes out at 2.2.1.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message