org.xmpp.component.ComponentException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • If two or more different threads detect that the socket is broken they will attempt to open a new connection. Only one will succeed and the rest will stay in the loop forever printing the following exception: [java] Error trying to reconnect with the server [java] org.xmpp.component.ComponentException: conflict [java] at org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:205) [java] at org.jivesoftware.whack.ExternalComponent.connectionLost(ExternalComponent.java:384) [java] at org.jivesoftware.whack.ExternalComponent.send(ExternalComponent.java:318) [java] at org.jivesoftware.whack.ExternalComponentManager.sendPacket(ExternalComponentManager.java:203) [java] at com.jivesoftware.community.xmpp.ClearspaceComponent.send(ClearspaceComponent.java:179) [java] at com.jivesoftware.community.xmpp.ClearspaceComponent.processIQ(ClearspaceComponent.java:161) [java] at com.jivesoftware.community.xmpp.ClearspaceComponent.processPacket(ClearspaceComponent.java:49) [java] at org.jivesoftware.whack.ExternalComponent$1.run(ExternalComponent.java:300) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) [java] at java.lang.Thread.run(Thread.java:619) Moreover, the thread that created the new connection could not be accessible from the component. Thus leaving the external component with no connectivity to the server
    via by Gaston Dombiak,
  • If two or more different threads detect that the socket is broken they will attempt to open a new connection. Only one will succeed and the rest will stay in the loop forever printing the following exception: [java] Error trying to reconnect with the server [java] org.xmpp.component.ComponentException: conflict [java] at org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:205) [java] at org.jivesoftware.whack.ExternalComponent.connectionLost(ExternalComponent.java:384) [java] at org.jivesoftware.whack.ExternalComponent.send(ExternalComponent.java:318) [java] at org.jivesoftware.whack.ExternalComponentManager.sendPacket(ExternalComponentManager.java:203) [java] at com.jivesoftware.community.xmpp.ClearspaceComponent.send(ClearspaceComponent.java:179) [java] at com.jivesoftware.community.xmpp.ClearspaceComponent.processIQ(ClearspaceComponent.java:161) [java] at com.jivesoftware.community.xmpp.ClearspaceComponent.processPacket(ClearspaceComponent.java:49) [java] at org.jivesoftware.whack.ExternalComponent$1.run(ExternalComponent.java:300) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) [java] at java.lang.Thread.run(Thread.java:619) Moreover, the thread that created the new connection could not be accessible from the component. Thus leaving the external component with no connectivity to the server
    via by Gaston Dombiak,
  • If two or more different threads detect that the socket is broken they will attempt to open a new connection. Only one will succeed and the rest will stay in the loop forever printing the following exception: [java] Error trying to reconnect with the server [java] org.xmpp.component.ComponentException: conflict [java] at org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:205) [java] at org.jivesoftware.whack.ExternalComponent.connectionLost(ExternalComponent.java:384) [java] at org.jivesoftware.whack.ExternalComponent.send(ExternalComponent.java:318) [java] at org.jivesoftware.whack.ExternalComponentManager.sendPacket(ExternalComponentManager.java:203) [java] at com.jivesoftware.community.xmpp.ClearspaceComponent.send(ClearspaceComponent.java:179) [java] at com.jivesoftware.community.xmpp.ClearspaceComponent.processIQ(ClearspaceComponent.java:161) [java] at com.jivesoftware.community.xmpp.ClearspaceComponent.processPacket(ClearspaceComponent.java:49) [java] at org.jivesoftware.whack.ExternalComponent$1.run(ExternalComponent.java:300) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) [java] at java.lang.Thread.run(Thread.java:619) Moreover, the thread that created the new connection could not be accessible from the component. Thus leaving the external component with no connectivity to the server
    via by Gaston Dombiak,
  • GitHub comment 41#84010296
    via GitHub by bayugmail
    ,
  • GitHub comment 15#122343782
    via GitHub by damencho
    ,
  • GitHub comment 529#261202772
    via GitHub by s1341
    ,
  • GitHub comment 529#261762691
    via GitHub by s1341
    ,
    • org.xmpp.component.ComponentException: conflict at org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:205) at org.jivesoftware.whack.ExternalComponent.connectionLost(ExternalComponent.java:384) at org.jivesoftware.whack.ExternalComponent.send(ExternalComponent.java:318) at org.jivesoftware.whack.ExternalComponentManager.sendPacket(ExternalComponentManager.java:203) at com.jivesoftware.community.xmpp.ClearspaceComponent.send(ClearspaceComponent.java:179) at com.jivesoftware.community.xmpp.ClearspaceComponent.processIQ(ClearspaceComponent.java:161) at com.jivesoftware.community.xmpp.ClearspaceComponent.processPacket(ClearspaceComponent.java:49) at org.jivesoftware.whack.ExternalComponent$1.run(ExternalComponent.java:300) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619)
    No Bugmate found.