Thanks Aaron. As near as I can see the only shutDown() right now is on CompositeCache which thus in my code counts on it being a singleton so I can fetch it multiple times.
Should I, instead, be putting a reference to it away for use at the end? or will JCS actually get a shutDown(0 call that calls the right composite cache internally? On Mon, Aug 24, 2009 at 10:16 AM, Aaron Smuts <[email protected]> wrote: > You shouldn't need to call release. I'll double check. > > The release model should be dropped. Many of the singletons keep a get > instance count. The idea is that this would be decremented on release and > we'd only dispose when there were no more clients. > > This was never done right and it wasn't useful. I started ripping it out > some time ago. I'll continue. And I'm still trying to get multiple > instance JCS working. There are only a few more things that assume the > cache is a singleton. > > Aaron > > --- On Mon, 8/24/09, Jeffrey Kesselman <[email protected]> wrote: > > > From: Jeffrey Kesselman <[email protected]> > > Subject: Re: Little question > > To: "JCS Users List" <[email protected]> > > Date: Monday, August 24, 2009, 6:15 AM > > Thanks. > > > > i had figured out shutDown since i posted but i hadn't > > figured out release > > yet. > > > > Thanks for the tip :) > > > > JK > > > > On Mon, Aug 24, 2009 at 4:30 AM, Horton Simon < > [email protected] > > > wrote: > > > > > Hi, > > > > > > Are you calling this JCS code during your shutdown of > > the > > > application/app server? > > > > > > CompositeCacheManager compositeCacheManager = > > > CompositeCacheManager.getInstance(); > > > > > > compositeCacheManager.release(); > > > compositeCacheManager.shutDown(); > > > > > > Regards, > > > > > > -----Original Message----- > > > From: Jeffrey Kesselman [mailto:[email protected]] > > > Sent: 24 August 2009 02:36 > > > To: JCS Users List > > > Subject: Little question > > > > > > I'm getting this warnign at shut down: > > > "WARNING: Region [resourceCache] Disk cache not > > shutdown properly, > > > shutting > > > down now." > > > > > > What am I not doing that I should? > > > > > > > > > -- > > > ~~ Microsoft help desk says: reply hazy, ask again > > later. ~~ > > > > > > This message and any files transmitted with it are > > confidential and > > > intended solely for the use of the individual or > > entity to whom they are > > > addressed. If you have received this message in error > > please delete it and > > > any files transmitted with it, after notifying > [email protected] > > > Any opinions expressed in this message may be those of > > the author and not > > > necessarily those of the company. The company accepts > > no responsibility for > > > the accuracy or completeness of any information > > contained herein. This > > > message is not intended to create legal relations > > between the company and > > > the recipient. > > > Recipients should please note that messages sent via > > the Internet may be > > > intercepted and that caution should therefore be > > exercised before > > > dispatching to the company any confidential or > > sensitive information. > > > Mizuho International plc Bracken House, One Friday > > Street, London EC4M 9JA. > > > TEL. 020 72361090. Wholly owned subsidiary of Mizuho > > Securities Co., Ltd. > > > Member of Mizuho Financial Group. Authorised and > > regulated by the Financial > > > Services Authority. Member of the London Stock > > Exchange. > > > > > > Registered in England No. 1203696. Registered office > > as above. > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > -- > > ~~ Microsoft help desk says: reply hazy, ask again later. > > ~~ > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- ~~ Microsoft help desk says: reply hazy, ask again later. ~~
