Bug 855873 - Jgroups failed sending diag rsp: Message too long
Summary: Jgroups failed sending diag rsp: Message too long
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Library
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ER1
: 6.1.0
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks: 854662
TreeView+ depends on / blocked
 
Reported: 2012-09-10 13:22 UTC by Ondrej Nevelik
Modified: 2013-03-08 00:18 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-11-28 13:58:37 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Ondrej Nevelik 2012-09-10 13:22:56 UTC 
During multiplecaches test in Library mode (i.e. there are ~50 caches running at each node) this IOException appears: 
ERROR [org.jgroups.protocols.UDP] (DiagnosticsHandler,x,edg-perf01-39764) failed sending diag rsp to /10.16.88.165:51576
java.io.IOException: Message too long
	at java.net.PlainDatagramSocketImpl.send(Native Method)
	at java.net.DatagramSocket.send(DatagramSocket.java:625)
	at org.jgroups.stack.DiagnosticsHandler.sendResponse(DiagnosticsHandler.java:196)
	at org.jgroups.stack.DiagnosticsHandler.handleDiagnosticProbe(DiagnosticsHandler.java:157)
	at org.jgroups.stack.DiagnosticsHandler.run(DiagnosticsHandler.java:118)
	at java.lang.Thread.run(Thread.java:662)



The job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/JDG-RADARGUN/job/jdg-60-radargun-perf-multicache/26/artifact/report/

For the server log, either see the stdout.zip or have a look into the loganalasis/slave folder.
Comment 1 Radim Vansa 2012-09-10 13:47:53 UTC 
Encountered also in https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-60-radargun-perf-non-transactional/18
Comment 2 Tristan Tarrant 2012-09-12 12:28:32 UTC 
Nothing really to see here: JGroups diag is broken and it should never be enabled in the configuration (it is disabled in default server and library configs)
Note You need to log in before you can comment on or make changes to this bug.