Up to Discussions in Openfire Support

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (5 pts)
5 Replies Last post: Sep 3, 2008 2:55 PM by rdonnell  
devmage Bronze
devmage
10 posts since
Oct 1, 2007
Currently Being Moderated

Nov 6, 2007 10:08 AM

Openfire 3.4.1 "Packet sent to unreachable address"

I've been seeing these errors in my info/warn/debug logs along with a strange behavior I'm assuming has something to do with it.  I did a search and saw some posts about older versions and this issue but not a solution.

 

<span class="date">2007.11.05 11:03:55 Packet sent to unreachable address

             &n bsp; &lt;iq id="0YnQ6-18" to="someone@server/spark" type="get" from="adifferentperson@server/spark"&gt;

             &n bsp; &lt;query xmlns="http://jabber.org/protocol/disco#info"/>

             &n bsp; &lt;/iq&gt;<span class="date">2007.11.05 13:08:37 Packet sent to unreachable address

             &n bsp; &lt;iq id="1oO1b-34" to="someoneelse@server/spark" type="get" from="anotherperson@server/spark"&gt;

             &n bsp; &lt;query xmlns="http://jabber.org/protocol/disco#info"/>

             &n bsp; &lt;/iq&gt;

 

There isn't any network reason these packets wouldn't be able to get to the respective machines.  I did read in another post something about compression which is turned on so I shut that off today to see how it goes.  Along with this error I have had the odd behavior of people being online but spark not seeing they are online.  Over time after I logged in people slowly started to show back up.  I was thinking this was related if the client and server are having issues chatting.

 

Any info is appreciated.

 

Edit:

 

 

 

After shutting off compression and leaving debugging on for a while I'm seeing slightly different messages but similiar theme.

 

<span class="date">007.11.06 07:27:23 Failed to route packet to JID: someone@server packet:

             &n bsp; &lt;message id="gAQ48-24" to="someone@utlive" from="someonelse@server/spark"&gt;

             &n bsp; &lt;x xmlns="jabber:x:event"/&gt;

             &n bsp; &lt;/message&gt;

 

 

Second Edit:

 

 

I've also noticed in the warning log some more similar messages related to undelivered packets.

 

<span class="date">2007.11.06 08:01:22 Error or result packet could not be delivered

             &n bsp; &lt;iq type="result" id="FONEC-471" to="someone@server/spark"&gt;

             &n bsp; &lt;query xmlns="jabber:iq:private"&gt;

             &n bsp; &lt;scratchpad xmlns="scratchpad:tasks"/&gt;

             &n bsp; &lt;/query&gt;

             &n bsp; &lt;/iq&gt;

 

Something else to note this is running on a virtual server, I don't think that would make any difference but something worth mentioning perhaps.  The OS is Windows 2003 and database is linked to Microsoft SQL.

Tags: bug_report, openfire, error, bug, server
tnt Bronze
tnt
12 posts since
Aug 24, 2006
Currently Being Moderated
Dec 22, 2007 7:48 AM in response to: devmage
Re: Openfire 3.4.1 "Packet sent to unreachable address"

same problem here

 

 

 

2007.12.22 14:26:25 Packet sent to unreachable address

&lt;iq type="get" to="pele@b44.bg.wi/Psi" id="ab12a" from="tnt@b44.bg.wi/Psi"&gt;

&lt;query xmlns="jabber:iq:version"/&gt;

&lt;/iq&gt;

2007.12.22 14:26:25 Packet sent to unreachable address

&lt;iq type="get" to="dooki@b44.bg.wi/Psi" id="ab19a" from="tnt@b44.bg.wi/Psi"&gt;

&lt;query xmlns="jabber:iq:version"/&gt;

&lt;/iq&gt;

 

 

 

 

 

 

2007.12.22 14:26:26 Error or result packet could not be delivered

&lt;iq from="bole@b61.bg.wi/Miranda" to="tnt@b44.bg.wi/Psi" type="error" id="ab17a"&gt;

&lt;query xmlns="jabber:iq:version"/&gt;

&lt;error code="404" type="wait"&gt;

&lt;recipient-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/&gt;

&lt;/error&gt;

&lt;/iq&gt;

2007.12.22 14:26:26 Error or result packet could not be delivered

&lt;iq from="miljenko@b61.bg.wi/Psi" to="tnt@b44.bg.wi/Psi" type="error" id="ab35a"&gt;

&lt;query xmlns="jabber:iq:version"/&gt;

&lt;error code="404" type="wait"&gt;

&lt;recipient-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/&gt;

&lt;/error&gt;

&lt;/iq&gt;

2007.12.22 14:26:26 Error or result packet could not be delivered

&lt;iq from="miljenko@b61.bg.wi/Psi" to="tnt@b44.bg.wi/Psi" type="error" id="ab1aa"&gt;

&lt;query xmlns="jabber:iq:version"/&gt;

&lt;error code="404" type="wait"&gt;

&lt;recipient-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/&gt;

&lt;/error&gt;

&lt;/iq&gt;

 

 

 

 

Report Abuse
devmage Bronze
devmage
10 posts since
Oct 1, 2007
Currently Being Moderated
Dec 31, 2007 9:09 AM in response to: tnt
Re: Openfire 3.4.1 "Packet sent to unreachable address"

 

I ended up guessing it was somethign to do with Java, since there was no network problem that I could find.  I decided to chalk it up to Java some times being quirky about cross-platform and installed openfire on a linux server (which I assumed it was being developed on) and I haven't seen the error since then.   I don't know if it is truely due to running on windows but I haven't seen it since then and I do not have the users with status update issues anymore.

 

 

Report Abuse
Travis Woolworth Bronze
Travis Woolworth
1 posts since
Jul 15, 2008
Currently Being Moderated
Jul 15, 2008 3:47 PM in response to: devmage
Re: Openfire 3.4.1 "Packet sent to unreachable address"

The problem could have something to do with Java however I know it's not a Windows specific thing because I have the same problem on a CentOS 5 server. I also have not found a solution to the problem itself however I have found the piece of code that outputs both of the errors that we constantly see within the info log. They are as follows within IQRouter.java.

 

 

 

 

if (XMPPServer.getInstance().isLocal(recipientJID)) {

ClientSession session = sessionManager.getSession(recipientJID);

if (session != null) {

if (session.canProcess(packet)) {

session.process(packet);

handlerFound = true;

}

}

else {

Log.info("Packet sent to unreachable address " + packet);

}

}

else {

ChannelHandler route = routingTable.getRoute(recipientJID);

if (route != null) {

route.process(packet);

handlerFound = true;

}

else {

Log.info("Packet sent to unreachable address " + packet);

}

}

 

 

 

 

I'm not a developer for openfire though so I can't really go beyond this other then pointing out it seems that the else statement seems to be getting hit quite often with session = null and route = null.

There also seems to be another post about a previous version having the same problems. http://www.igniterealtime.org/community/thread/28519

Report Abuse
yasin Bronze
yasin
8 posts since
Feb 1, 2008
Currently Being Moderated
Aug 14, 2008 3:18 PM in response to: Travis Woolworth
Re: Openfire 3.4.1 "Packet sent to unreachable address"

Hi,

 

 

I have the same problem and getting the folloiwng warnings

 

2008.08.14 16:11:03 Error or result packet could not be delivered
<iq type="result" id="19WfF-49" to="nlesser@im.test.com/spark">
  <query xmlns="jabber:iq:private">
    <scratchpad xmlns="scratchpad:tasks"/>
  </query>
</iq>

 

 

it is still a problem or any one comes with solution.

 

Thnaks,

Report Abuse
rdonnell Bronze
rdonnell
1 posts since
Sep 3, 2008
Currently Being Moderated
Sep 3, 2008 2:55 PM in response to: devmage
Re: Openfire 3.4.1 "Packet sent to unreachable address"

I'm having the same issue here as well.

 

2008.09.03 15:00:58 Packet sent to unreachable address                   
<iq type="get" id="purple46084ba4" to="someuserl@imserver/Home" from="someotheruser@imserver/Home">       &n bsp;         
<query xmlns="http://jabber.org/protocol/disco#info" node="http://pidgin.im/caps#2.5.1"/>        &n bsp;        
</iq>
Report Abuse

More Like This

  • Retrieving data ...