I think I have found the cause of this error. The Continuum web
application and Tomcat are consuming 44 threads when all is idle. The
default max thread count on HP-UX is 64 per process. When Archiva is
added to the Tomcat instance the thread count hits 64.
Below is the database configuration in context.xml.
<Resource name="jdbc/continuum"
auth="Container"
type="javax.sql.DataSource"
username="sa"
password=""
driverClassName="org.apache.derby.jdbc.EmbeddedDriver"
url="jdbc:derby:/internal/continuum/db/continuum;create=true"
/>
So my questions are:
1) Why are so many threads being used?
2) How can be minimize the thread count?
Paul Spencer
Paul Spencer wrote:
Wendy Smoak wrote:
On Mon, Jun 9, 2008 at 8:52 AM, Paul Spencer <[EMAIL PROTECTED]> wrote:
Now that I have Archiva and Continuum running in the same Tomcat
6.0.16, I
am seeing the exception "java.lang.OutOfMemoryError: unable to create
new
native thread" in catalina.out.
JVM = build 1.5.0.01
OS = HP-UX 11.11
That looks familiar. :) Who is the JDK vendor? (ISTR that something
in Redback requires a Sun JDK...)
$ $JAVA_HOME/bin/java -version
java version "1.5.0.01" Java(TM) 2 Runtime Environment, Standard Edition
(build 1.5.0.01-_06_jun_2005_05_20)
Java HotSpot(TM) Server VM (build 1.5.0.01 jinteg:06.06.05-04:39 PA2.0
(aCC_AP), mixed mode)
java.lang.OutOfMemoryError: unable to create new native thread
I suspect the memory and/or stack configuration need to be altered,
but I am
not sure which ones to alter. Currently CATALINA_OPT =
'-Dapplication.base=$ARCHIVA_BASE -Dapplication.home=$ARCHIVA_BASE"
If the message is in the Catalina log, you probably need to give
Tomcat itself more memory. This might help:
http://wiki.apache.org/tomcat/FAQ/Memory
Paul Spencer
