[jbosscache-issues] [JBoss JIRA] (JBCACHE-1639) org.jgroups.protocols.UDP failed sending message to null (191 bytes) java.lang.Exception: dest=/224.1.2.22:45222 (194 bytes)

Bagavathi S (JIRA) issues at jboss.org
Tue Jul 26 03:29:00 EDT 2016


    [ https://issues.jboss.org/browse/JBCACHE-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13270343#comment-13270343 ] 

Bagavathi S commented on JBCACHE-1639:
--------------------------------------

Before STABLE packet sent is judged as failure, another STABLE is supposed to be sent for several times?
or if only one STABLE fails, it is judged as failure immediately?

We'd like to know that, If the error cause were lost of UDP packet, several attempts were tried or only one attempt was tried.

> org.jgroups.protocols.UDP  failed sending message to null (191 bytes) java.lang.Exception: dest=/224.1.2.22:45222 (194 bytes)
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-1639
>                 URL: https://issues.jboss.org/browse/JBCACHE-1639
>             Project: JBoss Cache
>          Issue Type: Bug
>            Reporter: Bagavathi S
>            Assignee: Manik Surtani
>            Priority: Minor
>
> In our application we are using the below components of Jboss  
>  1.	JGroups Version:      2.6.13.GA  
> 2.	Jboss Cache Version:        3.2.2.GA  
>  We observed the ERROR as “failed sending message to null (191 bytes) java.lang.Exception: dest=/224.1.2.22:45222 (194 bytes)” [full stack Trace below] 
> ERROR] - 07/02/16 07:12:57 -  org.jgroups.protocols.UDP --> failed sending message to null (191 bytes) java.lang.Exception: dest=/224.1.2.22:45222 (194 bytes)                 at org.jgroups.protocols.UDP._send(UDP.java:361)                 at org.jgroups.protocols.UDP.sendToAllMembers(UDP.java:302)                 at org.jgroups.protocols.TP.doSend(TP.java:1474)                 at org.jgroups.protocols.TP.send(TP.java:1464)                 at org.jgroups.protocols.TP.down(TP.java:1185)                 at org.jgroups.protocols.Discovery.down(Discovery.java:374)                 at org.jgroups.protocols.MERGE2.down(MERGE2.java:175)                 at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:360)                 at org.jgroups.protocols.FD.down(FD.java:315)                 at org.jgroups.protocols.VERIFY_SUSPECT.down(VERIFY_SUSPECT.java:95)                 at org.jgroups.protocols.pbcast.NAKACK.send(NAKACK.java:803)                 at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:604)                 at org.jgroups.protocols.UNICAST.down(UNICAST.java:455)                 at org.jgroups.protocols.pbcast.STABLE$StabilitySendTask.run(STABLE.java:855)                 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)                 at java.util.concurrent.FutureTask.run(FutureTask.java:262)                 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)                 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)                 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)                 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)                 at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: Operation not permitted                 at java.net.PlainDatagramSocketImpl.send(Native Method)                 at java.net.DatagramSocket.send(DatagramSocket.java:676)                 at org.jgroups.protocols.UDP._send(UDP.java:352)                 ... 20 more  
> We would like to know the cause the Error and does it impact the replication of Jboss Cache across the nodes in the cluster.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)



More information about the jbosscache-issues mailing list