|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of
|[EMAIL PROTECTED]
|Sent: Tuesday, November 21, 2000 4:31 PM
|To: jBoss
|Subject: RE: [jBoss-User] NotSerializableException
|
|
|Thank you for the hint. I mixed up the attribute with the session context.
|What I also found appart from the fact that my code was wrong is, that in
|case this type of error arrises, i observed two things:
|
|1 - If I made a high number of calls, there came a situation when the
|server seemed to run in a loop writing the exceptions from my
|previous message.
|I only was able to stop him by CTRL-C.


mmmmm

one thing we should make sure is that a Passivation that "fails" still
removes the bean from memory...

it seems they are not removed and they keep on bugging you

flag this is bugzilla for me please

marc
|
|2 - Isn't it correct to for server to deaktivate any bean which doesn't
|conform to the specification?
|
|Regards
|Christian
|
|> you cannot keep references that are not serializable, if you do then
|> disable
|> the "passivation".
|>
|> If you want to keep the passivation use the "activate' method to
|> retrieve
|> your reference
|>
|> marc
|
|
|--
|Sent through GMX FreeMail - http://www.gmx.net
|
|
|--
|--------------------------------------------------------------
|To subscribe:        [EMAIL PROTECTED]
|To unsubscribe:      [EMAIL PROTECTED]
|Problems?:           [EMAIL PROTECTED]
|
|



--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to