Well, I created a context file named for my app (Spc.xml) and placed it
in ${CATALINA_HOME}/conf/Catalina/localhost/.  I set the two entries:

    <antiJARLocking>true</antiJARLocking>
    <antiResourceLocking>true</antiResourceLocking>

The Tomcat logs show:

 2009-10-09 16:03:11,093 DEBUG main
org.apache.catalina.startup.ContextConfig - Successfully processed
context [/Spc] configuration file
D:\apache-tomcat-6.0.18\conf\Catalina\localhost\Spc.xml null 
[Almost a four minute delay]

 2009-10-09 16:07:04,984 DEBUG main
org.apache.catalina.core.StandardContext - Starting /Spc  

and the thread dumps still show a similar state, with the:
        at java.io.FileOutputStream.close0(Native Method)
at the top of the "main" thread.  

-----Original Message-----
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] 
Sent: Wednesday, October 07, 2009 5:46 PM
To: Tomcat Users List
Subject: RE: Tomcat hangs for minutes between ContextConfig and
StandardContext (Starting the app)

> From: Law, Christopher [mailto:chris....@snapon.com]
> Subject: RE: Tomcat hangs for minutes between ContextConfig and 
> StandardContext (Starting the app)
> 
> I'm afraid I don't know what a blocking entropy is.

/dev/random is the system-provided random byte stream for UNIX/Linux and
some other platforms.  In order to generate a reasonably random
sequence, it needs sources of randomness, such as keyboard interrupts,
mouse movements, radioactive decay; than randomness is termed entropy,
and until there's enough of it, the stream will block when requests are
made to it.

> "main" prio=6 tid=0x002a7000 nid=0xd5c runnable 
> [0x0090f000..0x0090fe54]
>    java.lang.Thread.State: RUNNABLE
>       at java.io.FileOutputStream.close0(Native Method)
>       at java.io.FileOutputStream.close(FileOutputStream.java:279)
>       at java.io.FilterOutputStream.close(FilterOutputStream.java:143)

The above is the interesting one: it's stuck in close(), waiting for
something in the underlying file system.  Since you're on Windows, you
may need to set the antiJARLocking and antiResourceLocking attributes in
the <Context> element for your webapp.
http://tomcat.apache.org/tomcat-6.0-doc/config/context.html

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to