Quantcast
Channel: Ignite Realtime : All Content - Openfire Support
Viewing all articles
Browse latest Browse all 4778

OF 3.7 vs 3.10: now getting "Failed to route packet to JID" on Jabber.NET clients

$
0
0

I have upgraded our OpenFire from 3.7 to 3.10.  Most of our clients work just fine.  But we have a Jabber.NET client that can receive okay from other client types (like Spark), but can not send messages.  When the client based on Jabber.NET sends a message through the 3.10 OF server, I see the following in the debug logs:

 

2015.08.14 16:19:31 org.apache.mina.filter.codec.ProtocolCodecFilter - Processing a MESSAGE_RECEIVED for session 11  
2015.08.14 16:19:31 org.jivesoftware.openfire.spi.RoutingTableImpl - Failed to route packet to JID: atlwave12297122971@172.22.1.81/IM packet: <message id="JN_16" to="atlwave12297122971@172.22.1.81/IM" from="atlwave12297422974@172.22.1.81/ViewPoint-d27b488e-c33b-43b9-a044-0975cbdfa266"><body>Message</body></message>  
2015.08.14 16:19:32 org.jivesoftware.util.log.util.CommonsLogFactory - Closing statement 1232583 (belonging to connection 3) automatically  
2015.08.14 16:19:32 org.jivesoftware.util.log.util.CommonsLogFactory - Closing statement eb3a80 (belonging to connection 3) automatically  
2015.08.14 16:19:33 org.apache.mina.filter.executor.OrderedThreadPoolExecutor - Adding event MESSAGE_RECEIVED to session 9 

 

Any thoughts on why this happens? If I flip back to using 3.7 - it works fine.

Thanks, Scott


Viewing all articles
Browse latest Browse all 4778

Trending Articles