• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: ERJGroupsSynchronizer.framework on EC2
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ERJGroupsSynchronizer.framework on EC2


  • Subject: Re: ERJGroupsSynchronizer.framework on EC2
  • From: Theodore Petrosky <email@hidden>
  • Date: Fri, 01 May 2015 09:20:10 -0400

when I did the update, I worked with ‘bela’ 

this is from an email I sent in Jan 2015:

There are some internals that had to be adjusted, but when I updated ERJGroupsSynchronizer, I worked directly with Bela (jGroups author) to understand the changes needed.
In a nutshell, he eliminated his Exception checking and changed to use the Java Exceptions. remove the section:

if (ERXProperties.booleanForKeyWithDefault("er.extensions.jgroupsSynchronizer.autoReconnect", true)) {
     _channel.setOpt(Channel.AUTO_RECONNECT, Boolean.TRUE);
}
as (in his words) Shunning was removed a long time ago.

there are a couple of others and he said, <bela__> tedpet: I also suggest use a config file shipped with the version you download, e.g. udp.xml, and then make slight modifications to it, if needed"

I have this working on a production server.

Ted

On May 1, 2015, at 9:13 AM, Ken Anderson <email@hidden> wrote:

Paul,

These are the basic reasons I didn’t tackle this as well.  I can’t imagine anyone would want to use the very old JGroups jar, but who knows?  Maybe we need a way for someone to post feedback so that we can determine whether or not it’s OK to upgrade.

Ken

On May 1, 2015, at 9:10 AM, Paul Hoadley <email@hidden> wrote:

Hi Ted,

On 1 May 2015, at 10:05 pm, Theodore Petrosky <email@hidden> wrote:

don’t know if this is of interest but I created a pull request for this:

https://github.com/wocommunity/wonder/pull/626

Thanks for pointing this out.  I didn’t know this pull request was open.  It kind of helps to demonstrate, though, why I was reluctant to touch the framework directly myself—I simply don’t know enough about it.  What I got running on EC2, for example, uses the 3.4.0 JAR.  Does this matter?  I don’t know.  Does updating 2.6.8 to 3.4.0 (let alone 3.6.1) cause backward-compatibility issues?  I don’t know.  Mike Schrag wrote it, and he’s long gone—does anyone else understand it deeply?  I don’t know.

This also ties in nicely with the thread started by Jean Pierre Malrieu the other day.  A pull request like Ted’s doesn’t sit there for three months untouched because no one cares, it’s because no one _dares_.


-- 
Paul Hoadley
http://logicsquad.net/

Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: ERJGroupsSynchronizer.framework on EC2
      • From: David Avendasora <email@hidden>
References: 
 >Re: ERJGroupsSynchronizer.framework on EC2 (From: Theodore Petrosky <email@hidden>)
 >Re: ERJGroupsSynchronizer.framework on EC2 (From: Paul Hoadley <email@hidden>)
 >Re: ERJGroupsSynchronizer.framework on EC2 (From: Ken Anderson <email@hidden>)

  • Prev by Date: Re: ERJGroupsSynchronizer.framework on EC2
  • Next by Date: Re: Wonder 7 and 8
  • Previous by thread: Re: ERJGroupsSynchronizer.framework on EC2
  • Next by thread: Re: ERJGroupsSynchronizer.framework on EC2
  • Index(es):
    • Date
    • Thread