Problem when 3 or more resource names are used by one user

Has anyone experienced a problem in Openfire when a single user attempts to connect with 3 different clients? In my case, the user is using 3 custom resource named which don’t conflict. He gets disconnected as soon as he begins to type a message when connected 3 times. We are running 3.9.3.

I have seen this exception produced at the exact moment this happens:

2014.12.17 17:01:02 org.jivesoftware.openfire.nio.ConnectionHandler - Closing connection due to error while processing message: wQ2Az0

org.dom4j.IllegalAddException: The node “org.dom4j.tree.DefaultElement@e947a5 [Element: <message uri: jabber:client attributes: [org.dom4j.tree.DefaultAttribute@15ec1e7 [Attribute: name id value “56el8-137”], org.dom4j.tree.DefaultAttribute@c4845 [Attribute: name to value "blah@xmpp.blah.com/jitsi-uafmgn”], org.dom4j.tree.DefaultAttribute@5cd311 [Attribute: name from value "blah2@xmpp.blah.com/jitsi-desktop"], org.dom4j.tree.DefaultAttribute@252d62 [Attribute: name type value “chat”]]/>]" could not be added to the element “forwarded” because: The Node already has an existing parent of “forwarded”

at org.dom4j.tree.AbstractElement.addNode(AbstractElement.java:1521)

at org.dom4j.tree.AbstractElement.add(AbstractElement.java:1002)

at org.jivesoftware.openfire.forward.Forwarded.(Forwarded.java:24)

at org.jivesoftware.openfire.MessageRouter.route(MessageRouter.java:161)

at org.jivesoftware.openfire.spi.PacketRouterImpl.route(PacketRouterImpl.java:80)

at org.jivesoftware.openfire.net.StanzaHandler.processMessage(StanzaHandler.java:3 66)

at org.jivesoftware.openfire.net.ClientStanzaHandler.processMessage(ClientStanzaHa ndler.java:107)

at org.jivesoftware.openfire.net.StanzaHandler.process(StanzaHandler.java:220)

at org.jivesoftware.openfire.net.StanzaHandler.process(StanzaHandler.java:187)

at org.jivesoftware.openfire.nio.ConnectionHandler.messageReceived(ConnectionHandl er.java:181)

at org.apache.mina.common.support.AbstractIoFilterChain$TailFilter.messageReceived (AbstractIoFilterChain.java:570)

at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(Ab stractIoFilterChain.java:299)

at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilt erChain.java:53)

at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceive d(AbstractIoFilterChain.java:648)

at org.apache.mina.common.IoFilterAdapter.messageReceived(IoFilterAdapter.java:80)

at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(Ab stractIoFilterChain.java:299)

at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilt erChain.java:53)

at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceive d(AbstractIoFilterChain.java:648)

at org.apache.mina.filter.codec.support.SimpleProtocolDecoderOutput.flush(SimplePr otocolDecoderOutput.java:58)

at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecF ilter.java:185)

at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(Ab stractIoFilterChain.java:299)

at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilt erChain.java:53)

at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceive d(AbstractIoFilterChain.java:648)

at org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java :239)

at org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(Execut orFilter.java:283)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:51)

at java.lang.Thread.run(Unknown Source)

This is a known issue, which already has been fixed (for 3.10.0)

https://igniterealtime.org/issues/browse/OF-803

But it seems that at least one of your resources has Message Carbons enabled. Can you confirm?

Thanks anyway.

It looks like the affected user does have Message Carbons enabled for two of his clients.

Is there an ETA on 3.10 or developer builds?

This is the latest build Project-Windows-distribution-files (it haas more fixes that just this one). No ETA on final release.

Thanks. I’ll look into using that.