Mike,
Yes, I couldn't agree more.
On the subject of EJB timeouts, can anyone clear up something for me ? The
following is documentation about the validity-timeout attribute of the
entity-deployment tag in orion-ejb.jar.xml ...
"The maximum amount of time (in millis) that an entity is valid in the cache
(before being reloaded). Useful for loosely coupled environments where rare
updates from legacy systems occur. This attribute is only valid when
exclusive-write-access="true" (the default)."
I take this to mean that EJBs will be refreshed every 'n' milliseconds.
However, this does not agree with the bit about 'rare updates'. Also, I've
heard on this list opinions of what the attribute does which disagree with
my understanding, as follows ...
"a bean is removed only from the pool, if its timeout is reached, see the
'validity-timeout'"
"The first is a 'validity-timeout' set to milliseconds. This will passivate
the EJB if not active."
Does anybody agree that this is confusing, or am I missing something obvious
?
Thanks,
Tony.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Mike
Cannon-Brookes
Sent: 21 February 2001 11:14
To: Orion-Interest
Subject: RE: Flushing EJB cache
I think the reason this method is undocumented is you're not meant to play
with it ;) AFAIK it's an internal API.
By all means hack at Orion (I know I do), but beware that any hacking will
be unsupported by any Orion folks (I think this is fair enough).
-mike
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Tony J Brooks
> Sent: Wednesday, February 21, 2001 7:32 PM
> To: Orion-Interest
> Subject: RE: Flushing EJB cache
>
>
> Hey Peter,
>
> It's difficult to describe with absolute certainty since the documentation
> is poor (in fact, I haven't found any), but my understanding is that this
> method will remove instances of a named EJB from the container cache.
>
> It would be interesting to hear from other people on how
> effective they have
> found this method to be. We have observed that the OrionConsole 'flush'
> does not work - presumably this is calling 'flushEJBCache'. Does
> this imply
> that 'flushEJBCache' does not work ? We'll be testing this ourselves
> shortly.
>
> Hope that helps Peter,
>
> Tony.
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Peter Kua
> Sent: 21 February 2001 00:33
> To: Orion-Interest
> Subject: Re: Flushing EJB cache
>
>
> hi tony,
>
> may i know what this method does??
>
> thanks, peter
>
>
> ----- Original Message -----
> From: "Tony J Brooks" <[EMAIL PROTECTED]>
> To: "Orion-Interest" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Tuesday, February 20, 2001 5:52 PM
> Subject: RE: Flushing EJB cache
>
>
> To answer my own question - it is the JNDI name.
>
> -----Original Message-----
> From: Tony J Brooks [mailto:[EMAIL PROTECTED]]
> Sent: 20 February 2001 09:48
> To: Orion Interest
> Cc: [EMAIL PROTECTED]
> Subject: Flushing EJB cache
>
>
> Hi everyone,
>
> I want to use the following to flush the EJB cache ...
>
> void
> com.evermind.server.administration.ApplicationAdministrator.flushEJBCache(
> String p0 )
>
> ... can anybody tell me what the argument 'p0' specifies ?
>
> I've had a look for API documentation, but I can't find any.
>
> Thanks,
> Tony.
>
> ---
> Dr Tony J Brooks
> Apama (UK) Ltd
> 17 Millers Yard
> Cambridge, UK
>
> Mobile : 07748 767 110
> eMail : [EMAIL PROTECTED]
>
>
>
>
