it also manifests in our TTS results (PubSub 2 (c2s), PubSub 4 (c2s), PubSub 5 (c2s)).
Full stacktrace:
java.lang.RuntimeException: Wrong class
at tigase.pubsub.repository.cached.CachedPubSubRepository.update(CachedPubSubRepository.java:770)
at tigase.pubsub.repository.PubSubRepositoryWrapper.update(PubSubRepositoryWrapper.java:108)
at tigase.pubsub.modules.NodeCreateModule.process(NodeCreateModule.java:228)
at tigase.component2.modules.ModulesManager.process(ModulesManager.java:62)
at tigase.component2.AbstractComponent.processStanzaPacket(AbstractComponent.java:196)
at tigase.component2.AbstractComponent.processPacket(AbstractComponent.java:184)
at tigase.server.AbstractMessageReceiver$QueueListener.run(AbstractMessageReceiver.java:1475)
2013-10-07 10:55:53.098 [in_0-pubsub] AbstractMessageReceiver$QueueListener.run() SEVERE: [in_0-pubsub] Exception during packet processing: from=sess-man@wojtek-laptok, to=null, DATA=<iq xmlns="jabber:client" to="pubsub.firefly" type="set" from="admin@firefly/wojtek-laptok" id="create1">
<pubsub xmlns="http://jabber.org/protocol/pubsub">
<create node="create2"/>
</pubsub>
</iq>, SIZE=205, XMLNS=jabber:client, PRIORITY=NORMAL, PERMISSION=ADMIN, TYPE=set
java.lang.RuntimeException: java.lang.RuntimeException: Wrong class
at tigase.pubsub.modules.NodeCreateModule.process(NodeCreateModule.java:269)
at tigase.component2.modules.ModulesManager.process(ModulesManager.java:62)
at tigase.component2.AbstractComponent.processStanzaPacket(AbstractComponent.java:196)
at tigase.component2.AbstractComponent.processPacket(AbstractComponent.java:184)
at tigase.server.AbstractMessageReceiver$QueueListener.run(AbstractMessageReceiver.java:1475)
Caused by: java.lang.RuntimeException: Wrong class
at tigase.pubsub.repository.cached.CachedPubSubRepository.update(CachedPubSubRepository.java:770)
at tigase.pubsub.repository.PubSubRepositoryWrapper.update(PubSubRepositoryWrapper.java:108)
at tigase.pubsub.modules.NodeCreateModule.process(NodeCreateModule.java:228)
at tigase.component2.modules.ModulesManager.process(ModulesManager.java:62)
at tigase.component2.AbstractComponent.processStanzaPacket(AbstractComponent.java:196)
at tigase.component2.AbstractComponent.processPacket(AbstractComponent.java:184)
at tigase.server.AbstractMessageReceiver$QueueListener.run(AbstractMessageReceiver.java:1475)
After bisecting
tigase-pubsub ((4681648...)|BISECTING)
$ git bisect good
4e51d5e77f6f5222540d5fb352dd4445c1920dae is the first bad commit
commit 4e51d5e77f6f5222540d5fb352dd4445c1920dae
Author: Bartosz Malkowski <bmalkowski@tigase.pl>
Date: Wed Sep 25 11:23:46 2013 +0200
allow to get presences (PubSub Node Presence Extension) in subscriptions
list
I've tried Andrzej's suggestion to apply commit, which supposedly fixes the issue, Fixes after minor tests from devel branch but to no avail and the issue persists.
Recent builds throws
java.lang.RuntimeException: Wrong class
when trying to create new node, i.e.it also manifests in our TTS results (PubSub 2 (c2s), PubSub 4 (c2s), PubSub 5 (c2s)).
Full stacktrace:
After bisecting
it turns out that the responsible commit is allow to get presences (PubSub Node Presence Extension) in subscriptions list
This is related to all databases.
I've tried Andrzej's suggestion to apply commit, which supposedly fixes the issue, Fixes after minor tests from devel branch but to no avail and the issue persists.