If an XMPP endpoint is connected to both an incoming route and an outgoing route, the connection shouldn't be closed when the producer finishes. Perhaps it can be an option, like the Mina connector?
Don On Mon, Nov 1, 2010 at 5:03 AM, Willem Jiang <[email protected]> wrote: > On 11/1/10 4:17 PM, Willem Jiang wrote: >> >> I just checked the code of XmppPrivateChatProducer, it doesn't close the >> connection even the Producer is stopped. >> >> It's a bug of XMPP, I just create a JIRA[1] for it. >> >> >> [1]http://camel.465427.n5.nabble.com/XMPP-communication-not-closed-and-new-message-rejected-td3236657.html#a3236657 > > The JIRA link should be > https://issues.apache.org/activemq/browse/CAMEL-3298 > > BTW, I didn't have a chance to test the patch on XMPP Server. > Maybe we need to close the connection when the producer finish to send the > message. > >> >> >> On 10/27/10 9:03 PM, Alesque wrote: >>> >>> I'm using the Recipient List pattern to route dynamically messages to >>> different XMPP accounts. >>> >>> I'm experienced the same issue. I noticed XMPP connections remain open in >>> ejabberd. >>> >>> So the first message is routed, and when others occured, I've got an >>> Exception because accounts are already connected with the default >>> resource >>> identifier Camel. >>> >>> If I set a resource identifier (UUID) randomly for each recipient that >>> works, but connections remain open in ejabberd. >>> >>> Why XMPP connections remain open? Is this a bug? Is this the expected >>> behaviour? >>> >>> Perhaps connections are pooled and the algorithm to get the connection >>> related to a specific URI endpoint is broken. >>> >>> Any help would be greatly appreciated, >>> >>> Regards, >>> Alexandre >> >> > > > -- > Willem > ---------------------------------- > FuseSource > Web: http://www.fusesource.com > Blog: http://willemjiang.blogspot.com (English) > http://jnn.javaeye.com (Chinese) > Twitter: willemjiang >
