sight into this problem?
Good luck!
Mike
- Original Message -
From: "Mike Finn" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 19, 2001 10:56 AM
Subject: Re: [JBoss-user] SB timeout -> passivation -> activation failure
> > Hmm, that does
> Hmm, that does seem strange that you can serialize the home & pk, but not
> the handle.
Yes, it does seem strange which is why I am assuming there is something more
fundamental that I just don't yet get.
> I'm afraid I have never used EJB handles, so I won't be much
> help there. Every time
f I'm addressing the right
question (or if I'm telling you things you already know.) Good luck anyway!
Mike
- Original Message -
From: "Mike Finn" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 18, 2001 11:20 AM
Subject: Re: [JBoss-user]
On Wed, Jul 18, 2001 at 11:20:37AM -0600, Mike Finn wrote:
> I read somewhere (can't recall just now) that I was to use the handle, so
> that was what I was doing. But after resolving the passivation/activation
> yesterday, I have changed all my wrapper classes to use home/pk.
If I remember co
> I have never tried serializing an object by explicitly calling readObject()
> and writeObject() on a serializable. Does that work?
Yes. During serialization these methods will get called to allow a class to
control its own serialization process (mostly for transient fields). I am
using th
--- Original Message -
From: "Bordet, Simone" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 17, 2001 10:15 AM
Subject: RE: [JBoss-user] SB timeout -> passivation -> activation failure
> Hi !
>
> > Q1
> >
> > When I c
Thanks,
> In JBoss 2.4 and greater there is a tag for this purpose.
Excellent, I will upgrade.
> So: try to put in a very simple stateful bean and see if everything works
> ok. If not then it's a reproducible bug and you can file in a bug in
> sourceforge; otherwise try to add complexity to th
Hi !
> Q1
>
> When I checked what was happening during passivation of the
> SFSB I was using
> readObject() and writeObject() to serialize the handles of of
> any referenced
> entity beans. A handle was obtained from an EB's remote
> interfaces via
> EJBObject.getHandle(). The fix wa
> Passivation should definitely not kill a stateful session bean.
> (Does JBoss do this?)
No.
It seems that it was (as you suggested) a problem with serialization of
references that my stateful SB was holding (albeit somewhat indiretly) to
entity beans.
The last comments Burkhard and you made
Burkhard Vogel wrote:
Hey,
thats what ejbPassivate ejbActivate are for ;-). Restore any reference
or
non serializable object there.
Yes I do it now :) But tought that if original poster had
similiar problem..
--
jK.MkIII
___
JBoss-user maili
Hey,
thats what ejbPassivate ejbActivate are for ;-). Restore any reference or
non serializable object there.
Burkhard
- Original Message -
From: "jK.MkIII" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 17, 2001 12:43 PM
Subject: Re: [
Michael Jara wrote:
Passivation should definitely not kill a stateful
session bean. (Does JBoss
do this? So far, I haven't deployed anything in JBoss that is
idle for that
long a period.) However, I wouldn't be surprised if JBoss periodically
aged-out unused stateful session beans. I think th
Hi !
> So after 10 minutes of inactivity (jboss's default of 600
> secs) it should be
> passivated --not destroyed.
Right.
> Shouldn't I be able to continue
> to use the bean
> at 12 minutes (upon which the server will de-passify the bean
> ie. activate
> it) without the client ever bei
Okay, maybe I'm being daft - but I just don't get it.
from the manual
specifies the max age a bean can have
before being passivated by the overager ... the
specifies the period of the resizer, that is a periodic task that
runs ... Purpose of this periodic task is to shrink / en
Hi !
> Passivation should definitely not kill a stateful session
> bean. (Does JBoss
> do this?
No. JBoss doesn't do this.
> So far, I haven't deployed anything in JBoss that
> is idle for that
> long a period.) However, I wouldn't be surprised if JBoss
> periodically
> aged-out unused s
ot what's happening, then maybe it's a bug?
Mike
- Original Message -
From: "Mike Finn" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, July 15, 2001 7:33 PM
Subject: Re: [JBoss-user] SB timeout -> passivation -> activation failure
> Than
Thanks Michael & Burkhard
> I haven't done much experimenting with performance settings, but you might
> be able fix this with some adjustments the container cache policy. See
> http://www.jboss.org/documentation/HTML/ch06s08.html, the section on
> "Advanced cache configuration". You might try
ways...
Burkhard
- Original Message -
From: "Michael Jara" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, July 13, 2001 10:52 PM
Subject: Re: [JBoss-user] SB timeout -> passivation -> activation failure
> I haven't done much experimenting with perf
ing. (I assume this can apply to stateful session bean timeouts.)
Mike
- Original Message -
From: "Mike Finn" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, July 13, 2001 11:40 AM
Subject: [JBoss-user] SB timeout -> passivation -> activation fa
If I let a 'connected' client sit around for more than apporx 20
minutes it blows on its next attempt to use a remote method
of the SessionBean (only the one session appears to be blown, since
I can start a new client session without restarting the server).
What I want is to be able to have the c
20 matches
Mail list logo
