Hey Marc,
> but that is normal,
>
> if the bean is not passivatable we remove it from cache.
> Maybe this is
> confusing since you recieve an exception?
>
> Simone
Call me Simon :)
> do you think it is a better policy to leave the beans,
> log a message
> and disable passivation if it happens that a bean deployed is
> not good ?
Well, the spec is unclear on this.
Personally I would leave the bean in the cache, and let the server complain
every time the bean is passivated, so that someone can know that this bean
is somehow wrong.
Giving to EnterpriseContext a set/isPassivatable and setting it to false
when the first passivation fails, will result in a stack trace only the
first time the bean is (tried to be) passivated and no stack traces from
there on (but beans of that kind continues to live and occupy resources); so
if you miss it, well nothing serious but...
The client is not affected by passivation exceptions, while it would be in
case of bean removal. In this case of course the bean developer must correct
the bean ASAP. To recap I see 3 policies:
1) Silence: we setPassivatable(false) on first passivation failure, then we
check for it when trying to passivate next time: if false to don't
passivate. Client is not affected.
2) Talk: we stack trace every time we try to passivate, client is not
affected.
3) Scream: we remove the bean, the client can't go on.
Now 3 is implemented, given your last suggestion; I would stay with 2 as it
was before.
Simon
>
> marc
>
>
> |-----Original Message-----
> |From: [EMAIL PROTECTED]
> |[mailto:[EMAIL PROTECTED]]On Behalf Of Rico Hendriks
> |Sent: Wednesday, November 29, 2000 6:27 AM
> |To: jBoss
> |Subject: RE: [jBoss-User] Exceptions after sitting idle
> |
> |
> |Simon,
> |
> |I used the Music app on the jboss website using jdk 1.3,
> j2sdkee1.2.2, on
> |windoze 2000 using cygwin, and Hypersonic DB. Run
> run_lookup.bat, then let
> |it sit for a while. It will then reduce the pool from 1000
> to 50, and then
> |it will passivate all remaining 50 beans with id null (an error).
> |After that
> |you can run run_lookup.bat again and you will get the exception.
> |
> |If you need more system specifics or xml files let me know.
> |
> |-----Original Message-----
> |From: [EMAIL PROTECTED]
> |[mailto:[EMAIL PROTECTED]]On Behalf Of Bordet, Simone
> |Sent: Wednesday, November 29, 2000 3:20 AM
> |To: jBoss User Mailing List (E-mail)
> |Subject: [jBoss-User] Exceptions after sitting idle
> |
> |
> |Hi all,
> |
> |can someone that is experiencing this problem send me the
> relevant bean and
> |the steps necessary to obtain the exception ?
> |I tried but cannot restore this problem, for me everything
> works fine...
> |
> |Simon
> |
> |
> |--
> |--------------------------------------------------------------
> |To subscribe: [EMAIL PROTECTED]
> |To unsubscribe: [EMAIL PROTECTED]
> |Problems?: [EMAIL PROTECTED]
> |
> |
> |
> |
> |
> |--
> |--------------------------------------------------------------
> |To subscribe: [EMAIL PROTECTED]
> |To unsubscribe: [EMAIL PROTECTED]
> |Problems?: [EMAIL PROTECTED]
> |
> |
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
