com.sun.messaging.jms.JMSException

> [ADD_CONSUMER_REPLY(15)] [C4036]: A broker error occurred. :[412] > [B4135]: Cannot add durable consumer null. No ClientID was set on > connection. user=guest, broker=localhost:37676(36560) > > Got it: Same client ID for all cluster instances, different IDs needed > for durability. > Unfortunately, I have no idea how to either turn off durability or set > client IDs. > > > 2. RMI > > Let's try RMI then, I thought, and, using code fragments posted to > this list, came up with this code: > > RemoteCommandManager rcm = new > RemoteCommandManager((CommandProcessor)session); > rcm.getDiscoveryManager().setMulticastGroupAddress("226.1.2.3"); > rcm.getDiscoveryManager().setMulticastPort(3122); > rcm.setShouldPropagateAsynchronously(true); > rcm.getDiscoveryManager().setAnnouncementDelay(5); > rcm.getTransportManager().setNamingServiceType(TransportManager.REGISTRY_NAMING_SERVICE); > > rcm.setUrl("rmi://$HOST:33700"); > rcm.setServerPlatform(session.getServerPlatform()); > ((DatabaseSession)session).setCommandManager(rcm); > ((DatabaseSession)session).setShouldPropagateChanges(false); > rcm.initialize(); > > The session customizer terminates orderly, but after some time, I get > the following exception: > > Exception Description: Could not post connection in local naming > service under name rmi://192.168.23.12:33700/11657788 > Internal Exception: java.rmi.ConnectIOException: error during JRMP > connection establishment; nested exception is: > java.io.EOFException > at > org.eclipse.persistence.exceptions.RemoteCommandManagerException.errorBindingConnection(RemoteCommandManagerException.java:87) > > at > org.eclipse.persistence.sessions.coordination.rmi.RMITransportManager.createLocalConnectionInRegistry(RMITransportManager.java:160) > > at > org.eclipse.persistence.sessions.coordination.rmi.RMITransportManager.createLocalConnection(RMITransportManager.java:113) > > at > org.eclipse.persistence.sessions.coordination.DiscoveryManager.run(DiscoveryManager.java:197) > >

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 web116

  • via Oracle Community by 392 Guest, 11 months ago
    > [ADD_CONSUMER_REPLY(15)] [C4036]: A broker error occurred. :[412] > [B4135]: Cannot add durable consumer null. No ClientID was set on > connection. user=guest, broker=localhost:37676(36560) > > Got it: Same client ID for all cluster instances
  • [ADD_CONSUMER_REPLY(15)] [C4036]: A broker error occurred. :[412] [B4135]: Cannot add durable consumer null. No ClientID was set on connection. user=guest, broker=localhost:37676(53330)
  • [ACKNOWLEDGE_REPLY(25)] [C4036]: A broker error occurred. :[412] Unexpected Broker Exception: [Transaction 25142028128331776 has state [FAILED(2)], not in [STARTED(1)] state] user=guest, broker=192.168.168.131:7676(60835)
  • Stack trace

    • com.sun.messaging.jms.JMSException: > [ADD_CONSUMER_REPLY(15)] [C4036]: A broker error occurred. :[412] > [B4135]: Cannot add durable consumer null. No ClientID was set on > connection. user=guest, broker=localhost:37676(36560) > > Got it: Same client ID for all cluster instances, different IDs needed > for durability. > Unfortunately, I have no idea how to either turn off durability or set > client IDs. > > > 2. RMI > > Let's try RMI then, I thought, and, using code fragments posted to > this list, came up with this code: > > RemoteCommandManager rcm = new > RemoteCommandManager((CommandProcessor)session); > rcm.getDiscoveryManager().setMulticastGroupAddress("226.1.2.3"); > rcm.getDiscoveryManager().setMulticastPort(3122); > rcm.setShouldPropagateAsynchronously(true); > rcm.getDiscoveryManager().setAnnouncementDelay(5); > rcm.getTransportManager().setNamingServiceType(TransportManager.REGISTRY_NAMING_SERVICE); > > rcm.setUrl("rmi://$HOST:33700"); > rcm.setServerPlatform(session.getServerPlatform()); > ((DatabaseSession)session).setCommandManager(rcm); > ((DatabaseSession)session).setShouldPropagateChanges(false); > rcm.initialize(); > > The session customizer terminates orderly, but after some time, I get > the following exception: > > Exception Description: Could not post connection in local naming > service under name rmi://192.168.23.12:33700/11657788 > Internal Exception: java.rmi.ConnectIOException: error during JRMP > connection establishment; nested exception is: > java.io.EOFException > at > org.eclipse.persistence.exceptions.RemoteCommandManagerException.errorBindingConnection(RemoteCommandManagerException.java:87) > > at > org.eclipse.persistence.sessions.coordination.rmi.RMITransportManager.createLocalConnectionInRegistry(RMITransportManager.java:160) > > at > org.eclipse.persistence.sessions.coordination.rmi.RMITransportManager.createLocalConnection(RMITransportManager.java:113) > > at > org.eclipse.persistence.sessions.coordination.DiscoveryManager.run(DiscoveryManager.java:197) > > at java.lang.Thread.run(Thread.java:619)

    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.