I have had problems with this particular Web-App page before. It used to cause
'CompilerThread' errors in the JVM (causing the JVM to exit) before I
rearranged the EJB loading order. I cannot find my original bulletin board post
about the CompilerThread issue (do JBoss purge old posts?).
My
To keep the server.log set the append property to true in your Log4J
appender. See conf/log4.xml.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3990110#3990110
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3990110
On 32 bit architecture the JBoss process can allocate at max. 2GB of memory.
You gave it 1GB of heap. Plus some PermGen. The rest is available to stack
space. Every thread allocates its own stack. This may be 256kb to 1MB depending
on your platform (see you JVM documentation). It's a simple
OutOfMemoryError: unable to create new native thread
The default stack size for Java 1.4x 64-bit mode JVM- created threads is 1MB.
Try reducing this by using the -Xss switch you will be able to generate more
Threads , yes the application threads .
I think you are getting this error when there is
Thanks for the quick answer.
The server is not under heavy load, we have seen this problem just after
startup when no more than 2 or 3 users are active.
Admittedly 2 users are using a EJB3-heavy (i.e. lots of bean cross references,
fetch joins etc) page simultaenously.
We have had problems
Please follow up on this and let us know if you are still having issues. If so,
I need to find the cause. The OracleValidConnectionChecker could stand some
reworking as it is.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3989342#3989342
Reply to the post
I'm trying.
One thing that does not help is that server.log gets wiped out (i.e emptied or
overwritten) when this error happens and JBoss restarts. All I have to work on
is the console output.
Dave
View the original post :
