Wednesday, September 09, 2015

JGroups 3.6.6.Final released

I don't like releasing a week after I released 3.6.5, but the Infinispan team found 2 critical bugs in TCP_NIO2:
  • Messages would get corrupted as they were sent asynchronously and yet the buffer was reused and modified while the send was in transit (JGRP-1961)
  • TCP_NIO2 could start dropping messages because selection key registration was not thread safe: JGRP-1963
But bugs affect TCP_NIO2 only, and no other protocols.

So, there it is: 3.6.6.Final ! :-)

Enjoy (and find more bugs in TCP_NIO2) !
Posted by at

15 comments:

  1. Unknown6:08 PM

    There's a problem with the Sourceforge download page for 3.6.6 (previous releases work fine). It redirects to the main JGroups folder when attempting to download.

    ReplyDelete
  2. Bela Ban11:26 AM

    Works for me: can you try http://sourceforge.net/projects/javagroups/files/JGroups/3.6.6.Final/jgroups-3.6.6.Final.jar/download directly ?

    ReplyDelete
  3. Unknown1:48 AM

    Same problem here.
    Before no files where shown.
    Now the files are there but when you click in either 3 it goes to https://sourceforge.net/projects/javagroups/files/

    ReplyDelete
  4. Unknown6:50 PM

    I tried the direct URL, still doesn't work. I get the following error in the top-right corner, in a red alert box: "The "/JGroups/3.6.6.Final..oups-3.6.6.Final.jar" file could not be found or is not available. Please select another file."

    ReplyDelete
  5. Bela Ban5:02 PM

    I see... Unfortunately, I don't have access to my SF account right now. Can you try to download JGroups from maven central ?

    ReplyDelete
  6. Bela Ban5:07 PM

    Actually, I just recovered my access and uploaded 3.6.6 again.
    Can you try now ?

    ReplyDelete
  7. Unknown5:45 AM

    It works!!!!

    ReplyDelete
  8. Bela Ban2:22 PM

    Super ! Glad to fix that...

    ReplyDelete
  9. Unknown4:04 AM

    Yes, it works fine now!

    ReplyDelete
  10. Unknown5:16 PM

    Hi Bela,
    We are using jGroups 2.2.9.4 and it's been 9 years! we were caught into a couple of issues when the server hung during start up due to an issue with 'joining' cluster. So.. we are thinking either to upgrade jGroups or to replace it with something like Zookeeper. Your thoughts?

    ReplyDelete
  11. Bela Ban5:51 PM

    I'm biased, but... upgrade to a more recent version, e.g. 3.6.6 :-)

    ReplyDelete
    Replies
    1. Unknown7:59 PM

      hahaha.. thank you.. So, if I upgrade from 2.2.9.4 to 3.6.6, do you see any problems in doing that? Do I need a code change for my Distributed maps?

      Delete
  12. Bela Ban11:06 AM

    There are some API changes. If you use ReplicatedHashmap, the changes should be minor though... It's a matter of trying it out, I guess.
    Questions -> mailing list

    ReplyDelete
  13. Unknown1:14 PM

    Hello! what can i do with it ?

    31, 2015 2:05:12 PM org.jgroups.protocols.UDP setTimeToLive
    SEVERE: failed setting ip_ttl
    java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    ReplyDelete
  14. Bela Ban5:47 PM

    Use IPv4 or switch to master (3.6.7)

    ReplyDelete

Subscribe to: Post Comments (Atom)