EasyBeans

blocking shutdown on Tomcat 6

Details

  • Description:
    Hide
    Deployed the freshly downloaded EasyBeans war file in a near-stock Tomcat distribution (only modified a few logging configuration).
    Start the Tomcat with the war inside... some deployment messages are logged, no error message, all seems fine.
    Try to shutdown the Tomcat: some shutdown messages are logged from easybeans and tomcat, without apparent error, but...
    the shutdown doesn't end, and I have to manually kill the java server process.
    I repeated the procedure several times to ensure it wasn't a first-launch problem, and it is not.
    I first saw this on version 1.0.0, then tried the new 1.0.1 and it shows the same behaviour.

    I am considering EasyBeans as a candidate container for development and production of J2EE 5 applications, but this is cleary a show-stopper for production systems. I only rank it "critical" because it could be used for development anyway, if this issue is eventually solved.
    Show
    Deployed the freshly downloaded EasyBeans war file in a near-stock Tomcat distribution (only modified a few logging configuration). Start the Tomcat with the war inside... some deployment messages are logged, no error message, all seems fine. Try to shutdown the Tomcat: some shutdown messages are logged from easybeans and tomcat, without apparent error, but... the shutdown doesn't end, and I have to manually kill the java server process. I repeated the procedure several times to ensure it wasn't a first-launch problem, and it is not. I first saw this on version 1.0.0, then tried the new 1.0.1 and it shows the same behaviour. I am considering EasyBeans as a candidate container for development and production of J2EE 5 applications, but this is cleary a show-stopper for production systems. I only rank it "critical" because it could be used for development anyway, if this issue is eventually solved.
  • Environment:
    Tomcat 6.0.16, Java SE 1.6.0.6
    System: Debian GNU/Linux "etch", kernel 2.6.24.6 on 32-bits x86 dual-core

Attachments

  1. Text File
    tomcat-ezb-shutdown-bug.log
    (3 kB)
    John. H. Smith
    19/Jul/08 2:03 PM
  2. Text File
    tomcat-ezb-shutdown-threaddump.log
    (16 kB)
    John. H. Smith
    19/Jul/08 4:52 PM

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Florent BENOIT added a comment - 18/Jul/08 2:03 PM
  Hi, Could you provide a dump of the threads that are still running in your configuration ?

Maybe this is linked to http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4457683
but you've a JDK 6
Show
Florent BENOIT added a comment - 18/Jul/08 2:03 PM   Hi, Could you provide a dump of the threads that are still running in your configuration ? Maybe this is linked to http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4457683 but you've a JDK 6
Hide
Permalink
John. H. Smith added a comment - 19/Jul/08 2:02 PM
I can't tell about the maybe-linked bug... however I've only got _JRE_ 6 not JDK, but I think I'm allowed to do this with tomcat 5 and later.

I don't know what the "thread dump" thing means... Can you tell how to get it ?

I've checked the OS process list and listening ports:
- some threads remain,
- and there's a listening TCP port (but a different one at each launch).
(Attaching the log file)
Show
John. H. Smith added a comment - 19/Jul/08 2:02 PM I can't tell about the maybe-linked bug... however I've only got _JRE_ 6 not JDK, but I think I'm allowed to do this with tomcat 5 and later. I don't know what the "thread dump" thing means... Can you tell how to get it ? I've checked the OS process list and listening ports: - some threads remain, - and there's a listening TCP port (but a different one at each launch). (Attaching the log file)
Hide
Permalink
John. H. Smith added a comment - 19/Jul/08 2:03 PM
This is what I get after a simple startup-shutdown cycle.
Show
John. H. Smith added a comment - 19/Jul/08 2:03 PM This is what I get after a simple startup-shutdown cycle.
Hide
Permalink
Florent BENOIT added a comment - 19/Jul/08 3:49 PM
   Hi,

In order to get a thread dump, send a "kill -3" command on the process id of the java process.
This will show you a full dump of the JVM

Florent
Show
Florent BENOIT added a comment - 19/Jul/08 3:49 PM    Hi, In order to get a thread dump, send a "kill -3" command on the process id of the java process. This will show you a full dump of the JVM Florent
Hide
Permalink
John. H. Smith added a comment - 19/Jul/08 4:52 PM
Ok here it is.
Show
John. H. Smith added a comment - 19/Jul/08 4:52 PM Ok here it is.
Hide
Permalink
Florent BENOIT added a comment - 23/Jul/08 9:28 AM
I'm now able to reproduce the problem. I will keep you informed
Show
Florent BENOIT added a comment - 23/Jul/08 9:28 AM I'm now able to reproduce the problem. I will keep you informed
Hide
Permalink
Florent BENOIT added a comment - 24/Jul/08 5:49 PM
Fixed, you can do a try on snapshot from the stable branch :
http://maven.objectweb.org/maven2-snapshot/org/ow2/easybeans/ow2-easybeans-tomcat/1.0.2-SNAPSHOT/
Show
Florent BENOIT added a comment - 24/Jul/08 5:49 PM Fixed, you can do a try on snapshot from the stable branch : http://maven.objectweb.org/maven2-snapshot/org/ow2/easybeans/ow2-easybeans-tomcat/1.0.2-SNAPSHOT/
Hide
Permalink
John. H. Smith added a comment - 24/Jul/08 6:53 PM
Yes, the snapshot works fine now. Super!
Now I've got to find configuration documentation...
Show
John. H. Smith added a comment - 24/Jul/08 6:53 PM Yes, the snapshot works fine now. Super! Now I've got to find configuration documentation...

People

Dates

  • Created:
    18/Jul/08 1:34 PM
    Updated:
    24/Jul/08 6:53 PM
    Resolved:
    24/Jul/08 5:49 PM
Atlassian JIRA (v4.1.1#522) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for EasyBeans. Try JIRA - bug tracking software for your team.