powered by Jive Software

Wildfire 3.2.4; "IQRouter.java:341 Could not route packet" error when login

Hi,

I noticed for users logging in with a gajim client that I am getting the following error message in my Wildfire 3.2.4 server:

2007.04.01 13:04:41 org.jivesoftware.wildfire.filetransfer.proxy.ProxyConnectionManager$1$1.run(Prox yConnectionManager.java:110) Error processing file transfer proxy connection

java.io.IOException: Error reading Socks5 version and command

at org.jivesoftware.wildfire.filetransfer.proxy.ProxyConnectionManager.processInco mingSocks5Message(ProxyConnectionManager.java:215)

at org.jivesoftware.wildfire.filetransfer.proxy.ProxyConnectionManager.processConn ection(ProxyConnectionManager.java:168)

at org.jivesoftware.wildfire.filetransfer.proxy.ProxyConnectionManager.access$100( ProxyConnectionManager.java:39)

at org.jivesoftware.wildfire.filetransfer.proxy.ProxyConnectionManager$1$1.run(Pro xyConnectionManager.java:107)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

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

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

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

2007.04.01 13:04:41 org.jivesoftware.wildfire.IQRouter.handle(IQRouter.java:341) Could not route packet

java.lang.IllegalArgumentException: Illegal JID:

at org.xmpp.packet.JID.init(JID.java:384)

at org.xmpp.packet.JID.(JID.java:219)

at org.jivesoftware.wildfire.filetransfer.proxy.FileTransferProxy.handleIQ(FileTra nsferProxy.java:126)

at org.jivesoftware.wildfire.filetransfer.proxy.FileTransferProxy.process(FileTran sferProxy.java:349)

at org.jivesoftware.wildfire.IQRouter.handle(IQRouter.java:250)

at org.jivesoftware.wildfire.IQRouter.route(IQRouter.java:104)

at org.jivesoftware.wildfire.spi.PacketRouterImpl.route(PacketRouterImpl.java:67)

at org.jivesoftware.wildfire.net.StanzaHandler.processIQ(StanzaHandler.java:289)

at org.jivesoftware.wildfire.net.ClientStanzaHandler.processIQ(ClientStanzaHandler .java:79)

at org.jivesoftware.wildfire.net.StanzaHandler.process(StanzaHandler.java:254)

at org.jivesoftware.wildfire.net.StanzaHandler.process(StanzaHandler.java:153)

at org.jivesoftware.wildfire.nio.ConnectionHandler.messageReceived(ConnectionHandl er.java:131)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Caused by: org.jivesoftware.stringprep.IDNAException: String too long.

at org.jivesoftware.stringprep.IDNA.toASCII(IDNA.java:153)

at org.jivesoftware.stringprep.IDNA.toASCII(IDNA.java:53)

at org.xmpp.packet.JID.init(JID.java:355)

… 25 more

What goes along with that login is that the user gets logged in, kicked out and only the second time logged in successful. Has anybody else recognized this behavior?

From the error message, does that mean the gajim client is sending a too long JID?

What is the limitation here?

Thanks for the help.

Cheers,

Guenter