It seems to do that due to participant bug, but need to be investigated further. Excerpt from log of one of those cases (may we fix that with only matching NoneAffiliation somewhere?)
23:21:29.149 [CodingteamSystem-akka.actor.default-dispatcher-14186] ERROR akka.actor.OneForOneStrategy - NoneAffiliation (of class ru.org.codingteam.horta.protocol.jabber.NoneAffiliation$)
scala.MatchError: NoneAffiliation (of class ru.org.codingteam.horta.protocol.jabber.NoneAffiliation$)
at ru.org.codingteam.horta.protocol.jabber.MucMessageHandler.getCredential(MucMessageHandler.scala:104) ~[horta-hell.jar:0.12]
at ru.org.codingteam.horta.protocol.jabber.MucMessageHandler$$anonfun$receive$1.applyOrElse(MucMessageHandler.scala:79) ~[horta-hell.jar:0.12]
at akka.actor.Actor$class.aroundReceive(Actor.scala:465) ~[horta-hell.jar:0.12]
at ru.org.codingteam.horta.protocol.LocationActor.aroundReceive(LocationActor.scala:10) ~[horta-hell.jar:0.12]
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516) [horta-hell.jar:0.12]
at akka.actor.ActorCell.invoke(ActorCell.scala:487) [horta-hell.jar:0.12]
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:238) [horta-hell.jar:0.12]
at akka.dispatch.Mailbox.run(Mailbox.scala:220) [horta-hell.jar:0.12]
at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:393) [horta-hell.jar:0.12]
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) [horta-hell.jar:0.12]
at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) [horta-hell.jar:0.12]
at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) [horta-hell.jar:0.12]
at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107) [horta-hell.jar:0.12]
23:21:33.696 [CodingteamSystem-akka.actor.default-dispatcher-14187] WARN r.o.c.h.p.jabber.MucMessageHandler - Cannot find participant javascript@conference.jabber.ru/j123123 in the participant list
@j123123 posted $pet resurrect exactly at that time, and it was not even logged.
It seems to do that due to participant bug, but need to be investigated further. Excerpt from log of one of those cases (may we fix that with only matching
NoneAffiliation
somewhere?)@j123123 posted
$pet resurrect
exactly at that time, and it was not even logged.