Project

General

Profile

Exception: Missing XMLNS

NW NE
Added over 3 years ago

Hi,

I use tigase 7.0.2.

Do you have any hint what can couse these two type (but similar) errors?

  1. error:
2015-10-16 07:40:00.508 [in_7-pubsub]      AbstractComponent$1.write()        WARNING:  sending packet with not XMLNS set, should not occur, packet = from=pubsub.mydomain.co, to=http@localhost/8b70bfc1-684c-4424-8bf4-95b4861f66d4, DATA=<iq type="result" to="http@localhost/8b70bfc1-684c-4424-8bf4-95b4861f66d4" id="31469bbb-dd3d-48a4-9915-da55ffb50c0e" from="pubsub.mydomain.co"><command xmlns="http://jabber.org/protocol/commands" status="completed" node="subscribe-node"><x type="result" xmlns="jabber:x:data"><field type="fixed" var="Note"><value>Script execution error.</value></field><field type="fixed" var="Error message"><value>java.lang.RuntimeException: INCORRECT</value></field><field type="text-multi" var="Debug info"><value>java.lang.RuntimeException: INCORRECT</value><value>javax.script.ScriptException: java.lang.RuntimeException: INCORRECT</value><value>org.codehaus.groovy.jsr223.GroovyScriptEngineImpl.eval(GroovyScriptEngineImpl.java:349)</value><value>org.codehaus.groovy.jsr223.GroovyCompiledScript.eval(GroovyCompiledScript.java:41)</value><value>tigase.server.script.Script.runCommand(Script.java:159)</value><value>tigase.server.BasicComponent.processScriptCommand(BasicComponent.java:912)</value><value>tigase.pubsub.PubSubCom ... , SIZE=1788, XMLNS=null, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=result
java.lang.Exception: Missing XMLNS
    at tigase.component2.AbstractComponent$1.write(AbstractComponent.java:80)
    at tigase.component2.AbstractComponent$1.write(AbstractComponent.java:65)
    at tigase.pubsub.modules.AdHocConfigCommandModule.process(AdHocConfigCommandModule.java:100)
    at tigase.component2.modules.ModulesManager.process(ModulesManager.java:87)
    at tigase.component2.AbstractComponent.processStanzaPacket(AbstractComponent.java:221)
    at tigase.component2.AbstractComponent.processPacket(AbstractComponent.java:209)
    at tigase.pubsub.PubSubComponent.processPacket(PubSubComponent.java:599)
    at tigase.server.AbstractMessageReceiver$QueueListener.run(AbstractMessageReceiver.java:1424)
  1. error:
2015-10-16 07:40:00.515 [in_5-pubsub]      AbstractComponent$1.write()        WARNING:  sending packet with not XMLNS set, should not occur, packet = from=pubsub.mydomain.co, to=http@localhost/0e93d7d7-f772-4fd9-88d2-634ec6183a72, DATA=<iq type="result" to="http@localhost/0e93d7d7-f772-4fd9-88d2-634ec6183a72" id="acb27fb8-bc52-47ca-b6e5-21cb39ad138c" from="pubsub.mydomain.co"><command xmlns="http://jabber.org/protocol/commands" status="completed" node="subscribe-node"><x type="result" xmlns="jabber:x:data"><field type="fixed" var="Note"><value>Operation successful</value></field></x></command></iq>, SIZE=376, XMLNS=null, PRIORITY=NORMAL, PERMISSION=NONE, TYPE=result
java.lang.Exception: Missing XMLNS
    at tigase.component2.AbstractComponent$1.write(AbstractComponent.java:80)
    at tigase.component2.AbstractComponent$1.write(AbstractComponent.java:65)
    at tigase.pubsub.modules.AdHocConfigCommandModule.process(AdHocConfigCommandModule.java:100)
    at tigase.component2.modules.ModulesManager.process(ModulesManager.java:87)
    at tigase.component2.AbstractComponent.processStanzaPacket(AbstractComponent.java:221)
    at tigase.component2.AbstractComponent.processPacket(AbstractComponent.java:209)
    at tigase.pubsub.PubSubComponent.processPacket(PubSubComponent.java:599)
    at tigase.server.AbstractMessageReceiver$QueueListener.run(AbstractMessageReceiver.java:1424)

OK, I see "missing XMLNS" state, but I'm a little bit confused now, because this worked fine before, and works fine right now at our dev server, but in production we see these errors and pubsub (simple chat too) doesn't work.

Regrads,

NWNE


Replies (2)

Added by Wojciech Kapcia TigaseTeam over 3 years ago

This was a know issue, is fixed already and will be included in next release. This is mostly informative and doesn't interfere with the processing.

Added by NW NE over 3 years ago

OK, thank you and you are right, not these things caused malfunction of our pubsub or chat service.

    (1-2/2)