Hello,
I've written an app with one EJB.
From client I forgot to call @Remove, so EJB stuck. Then the container wants to passivate the ejb which fails because ejb has a Logger object and it cannot be serialized.
And few days later (while clients keep making a lot of EJBs) the whole thing throws an "OutOfMemory: java heap" exception.
Is it possible that OutOfMemory is caused by that EJBs can't be passivated? A "non-passivable" is stuck forever in container or is there a timeout that finally kills it?
Thanx
Sorry for my language:)
[Message sent by forum member 'mbazs123' (mbazs123)]
http://forums.java.net/jive/thread.jspa?messageID=255756