[jboss-dev-forums] [Design of EJB 3.0] - Transaction leak?

[epbernard]

If someone outside Bill has a clue on that...

Not that I know of.  Maybe Clebert or somebody was trying to fix a
memory leak somewhere.  Doesn't make sense to me.

Emmanuel Bernard wrote:
> Apparently, Hibernate tries to register a work on a transaction that is
> no longer active. But to me the latest code cannot fall into this case.
> Plus the user solve his issue by increasing the heap size.
>
> Could it be that JBoss keep track of the transaction or something
> related to the Tx in some kind of weak hashmap making it candidate for
> GC when memory is low. This could explain the behavior the user have.
>

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959462#3959462

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3959462