Mailing-List: contact user-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@curator.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Curator in an appserver environment
From: Jordan Zimmerman <jordan@jordanzimmerman.com>
In-Reply-To: 
 <CANykduZyN79jEh029uX6RNBFkQ550iQh7DYs7=Ju_EXz21_8qw@mail.gmail.com>
Date: Wed, 18 Dec 2013 14:56:53 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5034C8AC-139A-4E16-9265-7DD478B01314@jordanzimmerman.com>
References: 
 <CANykduZyN79jEh029uX6RNBFkQ550iQh7DYs7=Ju_EXz21_8qw@mail.gmail.com>
To: user@curator.apache.org

I=92ve personally used Curator with Tomcat and had no problems. Allocate =
your own Executors and pass them to Curator or let Curator allocate =
them.

-Jordan

On Dec 17, 2013, at 4:21 PM, Cameron McKenzie <mckenzie.cam@gmail.com> =
wrote:

> I've been using Curator in a standard Java environment, and haven't =
had any issues with it, but have just started using the same code in an =
appserver environment and have come across an issue.
>=20
> While, it's probably considered 'bad' to use Curator in this =
environment because it uses its own thread management, it runs fine in =
the vast majority of cases. The only time I have experience issues with =
it is when trying to call close() on the CuratorFramework instance. =
Specifically, calling close() when the app server is shutting down.
>=20
> The problem occurs because Curator uses an Executor to send the =
'shutting down' events to listeners, and the appserver has shut down all =
its Executor services because it's shutting itself down.
>=20
> My work around is to catch any runtime execptions thrown by the =
CuratorFramework close() method, and in this case grab the ZooKeeper =
connection from Curator and closing this. It's a bit ugly though.
>=20
> Any suggestions (other than not using an appserver, or not using =
Curator in this environment)?=20
>=20
> One fix would be to not use the Executor during shutdown to send the =
events, and instead just do this in the thread doing the shutdown. I =
doubt this would have great performance implications, given that you're =
unlikely to have millions of listeners.
>=20
> Thoughts?
> cheers
> Cam