I am just having the same problem. Checked the logs of one of the cluster nodes
(where we have some active HA services) and it is full of the message:
15:06:05,687 ERROR [UDP] exception=java.net.SocketException: The message is
larger than the maximum supported by the underlying transport: Datagr
2.2.7.
2.2.8 is binry-incompatible with 2.2.7, so we want to upgrade JBoss in 4.1.x
and 3.3.x (if the latter ever occurs).
However, I have tested 2.2.8 with both 3.2.7 and 4.0.2/4.0.3, and it works.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3890634#3890
I have not seen a repeat of the problem so I am going to leave thing alone;)
What version of jgroups will be incorporated into jboss 4.03?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3890592#3890592
Reply to the post :
http://www.jboss.org/index.html?modul
Another thing to try out is JGroups 2.2.8: this is API-compatible with 2.2.7,
but you'll need to upgrade all of the node in the *same* cluster; I don't
support mixed 2.2.7 and 2.2.8 clusters. I tested that 2.2.8 works ith JBoss
4.0.x and 3.2.x though.
View the original post :
http://www.jboss.
Hmm, this is strange. This is emitted by te datagramsocket's send() method,
when a datagram packet is too big (usually bigger than 65K).
But your message is small, the payload is *zero* bytes !
Can you do the following ? Go into org.jgroups.protocols.UDP and modify send()
(I'm assuming JGroups 2.
