Remy Maucherat <> changed:

           What    |Removed                     |Added
         Resolution|---                         |FIXED
             Status|REOPENED                    |RESOLVED

--- Comment #6 from Remy Maucherat <> ---
The issue should be fixed: it is about not stopping and cleaning up properly.
As I said before: The root cause was that the container state was not properly
set to FAILED on a JVM error exception class.

The "root cause" is of course not fixed, since it is a classloader problem most
likely caused by your application. It is logged and things will go on from
there. Feel free to investigate about it on the user mailing list, but please
do not reopen the report for now.

You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to