How to stop error propagation

[pparks]

I'm have an error that's occurring because in the log you'll see client1 isn't available. Then Client2 which is a SleekXMPP based client sends an error which client1's library can't deal with when it starts up. How do I disable the error in SleekXMPP so that this doesn't happen.

2013-04-18 16:07:23.738  MessageRouter.processPacket()   FINEST:   Processing packet: from=sess...@tigasetest.example.com, to=c...@tigasetest.example.com/XX.XX.XX.XX_5222_XX.XX.XX.XX_50209, data=<iq to="internal...@example.com/resource" type="error" id="5005" from="internal...@example.com"><open sid="5005" block-size="4096" xmlns="http://jabber.org/protocol/ibb"/><error type="cancel" code="503"><service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" xml:lang="en">CData size: 22</text></error></iq>, XMLNS=null, priority=NORMAL

2013-04-18 16:07:23.738  ClientConnectionManager.processPacket()  FINEST: Processing packet: from=sess...@tigasetest.example.com, to=c...@tigasetest.example.com/XX.XX.XX.XX_5222_XX.XX.XX.XX_50209, data=<iq to="internal...@example.com/resource" type="error" id="5005" from="internal...@example.com"><open sid="5005" block-size="4096" xmlns="http://jabber.org/protocol/ibb"/><error type="cancel" code="503"><service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" xml:lang="en">CData size: 22</text></error></iq>, XMLNS=null, priority=NORMAL

2013-04-18 16:07:23.738  XMPPIOService.processWaitingPackets()  FINEST: XX.XX.XX.XX_5222_XX.XX.XX.XX_50209, type: accept, Socket: TLS: Socket[addr=/XX.XX.XX.XX,port=50209,localport=5222], Sending packet: from=sess...@tigasetest.example.com, to=c...@tigasetest.example.com/XX.XX.XX.XX_5222_XX.XX.XX.XX_50209, data=<iq to="internal...@example.com/resource" type="error" id="5005" from="internal...@example.com"><open sid="5005" block-size="4096" xmlns="http://jabber.org/protocol/ibb"/><error type="cancel" code="503"><service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" xml:lang="en">Service not available.</text></error></iq>, XMLNS=null, priority=NORMAL

2013-04-18 16:07:23.738  XMPPIOService.processWaitingPackets()  FINEST: XX.XX.XX.XX_5222_XX.XX.XX.XX_50209, type: accept, Socket: TLS: Socket[addr=/XX.XX.XX.XX,port=50209,localport=5222], Sending packet: from=sess...@tigasetest.example.com, to=c...@tigasetest.example.com/XX.XX.XX.XX_5222_XX.XX.XX.XX_50209, data=<iq to="internal...@example.com/resource" type="error" id="5005" from="internal...@example.com"><open sid="5005" block-size="4096" xmlns="http://jabber.org/protocol/ibb"/><error type="cancel" code="503"><service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" xml:lang="en">Service not available.</text></error></iq>, XMLNS=null, priority=NORMAL

2013-04-18 16:07:23.739  XMPPIOService.processWaitingPackets()  FINEST: XX.XX.XX.XX_5222_XX.XX.XX.XX_50209, type: accept, Socket: TLS: Socket[addr=/XX.XX.XX.XX,port=50209,localport=5222], SENT: <iq to="internal...@example.com/resource" type="error" id="5005" from="internal...@example.com"><open sid="5005" block-size="4096" xmlns="http://jabber.org/protocol/ibb"/><error type="cancel" code="503"><service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" xml:lang="en">Service not available.</text></error></iq>

2013-04-18 16:07:23.739  XMPPIOService.processWaitingPackets()  FINEST: XX.XX.XX.XX_5222_XX.XX.XX.XX_50209, type: accept, Socket: TLS: Socket[addr=/XX.XX.XX.XX,port=50209,localport=5222], SENT: <iq to="internal...@example.com/resource" type="error" id="5005" from="internal...@example.com"><open sid="5005" block-size="4096" xmlns="http://jabber.org/protocol/ibb"/><error type="cancel" code="503"><service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/><text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" xml:lang="en">Service not available.</text></error></iq>

[Lance Stout]

Do you have any more logs showing the stanza that is causing the error? I'm not seeing where Sleek would generate that particular error, by default. It actually looks like one that is generated by the server itself, since the iq's 'from' attribute is only a bare JID.

[pparks]

I'll post some additional logs in a few minutes, but hadn't notice the bare JID before that's interesting. I'll also check to make sure that I'm not sending that, but am pretty sure that's something Tigase must be doing.

[pparks]

Here's a larger section of the log. The error is at the very bottom

[Lance Stout]

Yeah, client1 is sending Iq requests to client2's bare JID. Once for entity time, and then again for opening an IBB stream.

> 2013-04-19 10:51:44.526 XMPPIOService.processSocketData() FINEST: XX.XX.XX.XX_5222_XX.XX.XX.XX_11286, type: accept, Socket: TLS: Socket[addr=/XX.XX.XX.XX,port=11286,localport=5222], READ:
> <iq type="get" from="clie...@xmpp.example.com/resource" to="clie...@xmpp.example.com" id="3"><time xmlns="urn:xmpp:time"/></iq>

and

> 2013-04-19 10:51:49.850 XMPPIOService.processSocketData() FINEST: XX.XX.XX.XX_5222_XX.XX.XX.XX_11286, type: accept, Socket: TLS: Socket[addr=/XX.XX.XX.XX,port=11286,localport=5222], READ:
> <iq from="clie...@xmpp.example.com/resource" id="6391" to="clie...@xmpp.example.com" type="set"><open xmlns="http://jabber.org/protocol/ibb" block-size="4096" sid="6391" /></iq>

Those entries are from the raw socket data handlers, so client_2 should have a resource specified there.


Looks like Tigase has an entity time plugin which is answering the time request itself when it ought to be returning an error.

The IBB stream request is being returned with an error by the server because it's not finding a resource for client2 to route the request to.