Hi guys I meet a strange error and this is maybe because I do not use Camel in the right way. Here is a quick description of my problem:
I have a hornetQ JMS server. There is a queue inside. In this queue, there are two kind of messages : userEvent and systemEvent. --> userEvents are events to send to a specific recipient --> systemEvents are events which are sent to all recipient belonging to a specific domain of a ldap directory So a first Camel route is used to read from this queue, catching events and adding a specific field in the JMS message header to add destination recipient name reading in ldap server. These messages are then written in a JMS topic before delivery to recipients. In a second time, the topic is read and messages are sent to final recipient using recipientList (I used recipient list as I did not know what is the best way to simply retrieve a JMS message header information to build XMPP recipient destination URI. Maybe there is a clever way to send a message to only one destination after having customized the destination URI using a field in the JMS message header ? The main issue I meet with it is that when I send a message to a XMPP recipient, if another message is sent to this recipient, the second one failed. If I use a different resource to the XMPP URI, this works fine but I think this is not clean. When I have a look to the ejabberd server, I can see that communications with xmpp users are not closed, this is why I think, the second message to the same recipient with the same resource cannot be sent. Can somebody help me to find a solution ? Many thanks Vince -- View this message in context: http://camel.465427.n5.nabble.com/XMPP-communication-not-closed-and-new-message-rejected-tp3236657p3236657.html Sent from the Camel - Users mailing list archive at Nabble.com.
