java.lang.Exception

Can not remove callback listener as remoting client is not connected to server.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web4500

  • Can not remove callback listener as remoting client is not connected to server.
  • Can not remove callback listener as remoting client is not connected to server.
  • Can not remove callback listener as remoting client is not connected to server.
  • Stack trace

    • java.lang.Exception: Can not remove callback listener as remoting client is not connected to server. at org.jboss.remoting.Client.removeListener(Client.java:1466) at mage.remote.SessionImpl.disconnect(SessionImpl.java:502) at mage.remote.SessionImpl.establishJBossRemotingConnection(SessionImpl.java:428) at mage.remote.SessionImpl.connect(SessionImpl.java:239) at mage.client.MageFrame.connect(MageFrame.java:822) at mage.client.MageFrame.performConnect(MageFrame.java:866) at mage.client.MageFrame.autoConnect(MageFrame.java:835) at mage.client.MageFrame$7.run(MageFrame.java:426) at java.awt.event.InvocationEvent.dispatch(Unknown Source) at java.awt.EventQueue.dispatchEventImpl(Unknown Source) at java.awt.EventQueue.access$300(Unknown Source) at java.awt.EventQueue$3.run(Unknown Source) at java.awt.EventQueue$3.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.