0 Replies Latest reply on Oct 24, 2011 8:42 AM by ejb3workshop

    "[MPING] failed sending discovery request" on startup

    ejb3workshop

      When using JBoss 5.1.0-GA on Solaris we get the following exception when starting up in a cluster configuration of two nodes.

       

      10:39:26,600 ERROR [MPING] failed sending discovery request

      java.io.InterruptedIOException: operation interrupted

              at java.net.PlainDatagramSocketImpl.send(Native Method)

              at java.net.DatagramSocket.send(DatagramSocket.java:625)

              at org.jgroups.protocols.MPING.sendMcastDiscoveryRequest(MPING.java:341)

              at org.jgroups.protocols.PING.sendGetMembersRequest(PING.java:259)

              at org.jgroups.protocols.Discovery$PingSenderTask$1.run(Discovery.java:407)

              at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)

              at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)

              at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)

              at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)

              at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)

              at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)

              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

              at java.lang.Thread.run(Thread.java:662)

       

      It looks like the issue previously discussed here : https://issues.jboss.org/browse/JGRP-1161 however the suggested work around of upgrading jgroups did not work. We tried using jgroups jgroups-2.6.15.GA.jar and several other versions which caused the entire startup to fail. Using jgroups-2.6.15.GA.jar allowed us to startup however the exception still persisted.