Did you solve this problem? I have more or less the same exception in a
different problem space (executing Groovy script in a SLSB and providing an
invalid Script which causes a groovy exception)...
Any hint would be helpful, thanks!
View the original post :
Do you have found any solution?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4138675#4138675
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4138675
___
jboss-user mailing list
Hi,
so what did you actually do to solve that problem?
Thx!
Pete
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4106139#4106139
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4106139
My problem apparently has gone away too, yesterday, so far running fine on two
servers.
I happened to rearrange how two Seam components (both stateful with scope
application) were interacting. (For completeness of record: I moved storing
of some kind of unique id from the one executing on
I had this problem and fixed it.
Before and EJB gets passivated, everything is serialized. Make sure your
objects can be fully serialized - especially non-EJB beans that you create
within your EJB. Also be sure to close any 'connections to external resources'
you have open, if any.
While
Same kind of problem, using JBoss 4.0.5.GA. Started when I had a new
application scoped SFSB in Seam.
Very long and in a few minutes recurring stack trace begins with
00:04:03,187 ERROR [SimpleStatefulCache] problem passivation thread
| javax.ejb.EJBException: Could not passivate; failed to
Hi,
I am having the same issue. Did you ever solve it? If so, how?
thanks
Dustin
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4005069#4005069
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4005069
Hi,
I also have the same problem which ends with an OutOfMemoryException.
I started to get this problem when i started to use Stateful session bean.
Is this have something to do with ClassLoading issues?
Best regards,
Bustanil Arifin
View the original post :