org.jgroups.ChannelException

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.

  • JGroups UDP Errors starting JBoss AS | JBoss Developer
    via by Unknown author,
  • The testsuite is failing: jboss-all-config-tests: [server:start] Starting server "all" with command: [server:start] /qa/tools/opt/hpux_ia/java1.5/bin/java -cp /home/hudson/hudson_workspace/workspace/eap-as-hp-ia64/jboss-eap-4.3/jboss-as/bin/run.jar:/qa/tools/opt/hpux_ia/java1.5/lib/tools.jar -Xmx128m -XX:MaxPermSize=128m -Djava.endorsed.dirs=/home/hudson/hudson_workspace/workspace/eap-as-hp-ia64/jboss-eap-4.3/jboss-as/lib/endorsed -Djgroups.udp.ip_ttl=0 -Djava.net.preferIPv4Stack=false org.jboss.Main -c all -b 10.16.94.190 -u 239.16.94.191 [server:start] Failed to start server "all" before timeout. Destroying the process. BUILD FAILED /qa/services/hudson/hudson_workspace/workspace/eap-as-hp-ia64/src/jboss-eap-4.3-src/jboss-as/testsuite/build.xml:855: The following error occurred while executing this line: /qa/services/hudson/hudson_workspace/workspace/eap-as-hp-ia64/src/jboss-eap-4.3-src/jboss-as/testsuite/build.xml:1227: Error starting server "all": Server failed to start; see logs. The new thing is that now we start the server with "-Djava.net.preferIPv4Stack=false" unlike in the past. That is preventing the AS from starting up correctly. 15:57:34,765 WARN [ServiceController] Problem starting service jboss.cache:service=TomcatClusteringCache org.jgroups.ChannelException: failed to start protocol stack at org.jgroups.JChannel.connect(JChannel.java:389) at org.jboss.cache.TreeCache.startService(TreeCache.java:1549) at org.jboss.cache.aop.PojoCache.startService(PojoCache.java:94) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) ... Caused by: java.lang.Exception: exception caused by UDP.start() at org.jgroups.stack.Protocol.handleSpecialDownEvent(Protocol.java:582) at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:496) at org.jgroups.stack.Protocol.passDown(Protocol.java:533) at org.jgroups.protocols.Discovery.down(Discovery.java:333) at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:499) at org.jgroups.stack.Protocol.passDown(Protocol.java:533) at org.jgroups.protocols.MERGE2.down(MERGE2.java:207) at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:499) at org.jgroups.stack.Protocol.passDown(Protocol.java:533) ... Caused by: java.lang.Exception: problem creating sockets (bind_addr=/10.16.94.190, mcast_addr=null) at org.jgroups.protocols.UDP.start(UDP.java:381) at org.jgroups.stack.Protocol.handleSpecialDownEvent(Protocol.java:571) ... 135 more Caused by: java.net.SocketException: Operation not supported (errno:223) at java.net.PlainDatagramSocketImpl.setTimeToLive(Native Method) at java.net.MulticastSocket.setTimeToLive(MulticastSocket.java:209) at org.jgroups.protocols.UDP.createSockets(UDP.java:479) at org.jgroups.protocols.UDP.start(UDP.java:376) ... 136 more When the parameter is removed, the server starts normally.
    via by Martin Malina,
  • jboss deployment (JBoss/WildFly forum at Coderanch)
    via by Unknown author,
  • JGroups - Dev - "Failed to start protocol stack"
    via by Unknown author,
    • org.jgroups.ChannelException: failed to start protocol stack at org.jgroups.JChannel.connect(JChannel.java:389) at org.jboss.cache.TreeCache.startService(TreeCache.java:1549) at org.jboss.cache.aop.PojoCache.startService(PojoCache.java:94) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585)
    No Bugmate found.