When do you see this? What's going on at the time?
I get to see those logs after the server is started ,just after the message "Started in ....".
I've an EJB 3.0 deployed in the server with the @Clustered annotation.
Also in the server/all/lib I've replaced the jbosscache-core.jar with the latest version(3.0.2 GA) .
If this happens just once and the nodes properly cluster, this should not be a big problem. That would mean this is caused by the periodic activity of the MERGE2 protocol where it sends a multicast discovery message as part of its work periodic work of checking if any other subgroups exist on the same channel and need to be merged (see http://www.jboss.org/community/docs/DOC-10896). If that periodic task fails one time, it's not a big deal, it will just run again 10-20 seconds later.
If it's repeatedly failing its a bigger issue. And if this is occuring in the middle of startup, that would mean it is affecting the normal cluster formation process at startup, which is a bigger issue. But since it is appearing after the "Started in ...." logging it doesn't look like that is the case.
What's happening here is a thread is in native code trying to send a datagram. Per the class javadoc, a java.io.InterruptedIOException "is thrown to indicate that an input or output transfer has been terminated because the thread performing it was interrupted." Question is why the thread would be interrupted. Probable cause is the timeout waiting for a response has expired, which could cause the thread to be interrupted. The timeout is 3 seconds in a default AS 5.0. Question is why it would take more than 3 seconds to get the message *sent*. Normally the message gets sent almost immediately; the timeout kicks in waiting for *responses*. I really don't have a good answer for that question; most likely something specific to your environment.
Still, even if it isn't causing serious harm, if it's reproducible I encourage you to post on firstname.lastname@example.org so the JGroups folks are aware of it.
This seems to be reproducible as it occurs everytime I start my server and if this would affect the cluster set up , then I would like this to be fixed.
I'll definitely post it on email@example.com
Any thoughts from your end to resolve this?
Thanks in advance.
OK, this has been fixed (trunk, will be 2.10) and on the 2.6 branch (will be 2.6.15).
I have same "MPING failed sending discovery request" exception on JBoss.5.1.0.GA on Sun Solaris (Started with -u specifying mulitcast address).
I have changed the JGroups version from 2.6.10.GA to 2.6.15.GA (becauseof https://jira.jboss.org/browse/JGRP-1006) but now descibed exception of MPING occur.
When i check the source via
then i didn't see a change that the caught exception isn't logged anymore like you described in correction for
So i would say it isn't fixed in 2.6.15 and also in trunk i can't see a change.
Can you tell me what's the state or do i looking on wrong places ?
2010-09-13 18:01:58,912 ERROR () Timer-1,22.214.171.124:7900 [org.jgroups.protocols.MPING] failed sending discovery request
java.io.InterruptedIOException: operation interrupted
at java.net.PlainDatagramSocketImpl.send(Native Method)
I have the exact same error in Solaris, to be specific i am using:
JBoss EAP 5.1
Sun JDK 1.6.0_24
Could you solve this?