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
anonymous wrote : Would it be possible for you to elaborate on the "In order to test..." part?
It literally is as it says. From the 'Run' menu, choose the 'Run as' submenu, and then the 'Eclipse Application' menu item.
The plugin is then run in a new wokbench, called 'runtime-Workbench' relative to your existing workspace.
If you haven't already, then I think you should read through the eclipse plugin development tutorials before attempting to work on the designer.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959452#3959452
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3959452