Tomcat Internal Error

Unanswered Question
Aug 28th, 2007

Hi all,

Every time i select RME -> Report Generator -> Inventory - Hardware Report,

then I export this report in pdf format the following error is generated:

HTTP Status 500 - Internal Server Error

type Exception report

message Internal Server Error

description: The server encountered an internal error (Internal Server Error)

that prevented it from fulfilling this request.


javax.servlet.ServletException: Servlet execution threw an exception

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(

at org.apache.catalina.core.ApplicationFilterChain.doFilter(

at org.apache.catalina.core.StandardWrapperValve.invoke(




root cause


Thanks in advance.


a co-worker of Leonardo

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 2 (1 ratings)
Joe Clarke Tue, 08/28/2007 - 09:18

Looks like Tomcat ran out of memory. Restart dmgtd, and see if this problem is reliably reproducible.

marshajr Tue, 08/28/2007 - 19:34

We are also seeing this error at random intervals, running RME4.0.5 under Windows with 6Gig of memory. Restarting dmgtd only provides a temporary fix.

Joe Clarke Tue, 08/28/2007 - 20:09

If you can more or less reliably reproduce the problem, you should open a TAC service request so additional debugging can be performed.

Leonardo Roberto Wed, 08/29/2007 - 03:35

I executed following command lines:

dmgtd stop


I changed parameters into

from #JAVA_OPTS="$JAVA_OPTS -Xmx1024m -Xminf0.1 -Xmaxf0.1 -XX:MaxPermSize=256m -XX:PermSize=256m"

to JAVA_OPTS="$JAVA_OPTS -Xms1024m -Xmx2048m -Xminf0.1 -Xmaxf0.1 -XX:MaxPermSize=256m -XX:PermSize=256m"


dmgtd start

but the problem already exists;

then, I changed parameters into

from #JAVA_OPTS="$JAVA_OPTS -Xms1024m -Xmx2048m -Xminf0.1 -Xmaxf0.1 -XX:MaxPermSize=256m -XX:PermSize=256m"

to JAVA_OPTS="$JAVA_OPTS -Xms1024m -Xmx4098m -Xminf0.1 -Xmaxf0.1 -XX:MaxPermSize=256m -XX:PermSize=256m"

but now tomcat doesn't work!



Joe Clarke Wed, 08/29/2007 - 08:15

Why did you do that at all? Modifying the Tomcat start up parameters was not recommended to you.

You cannot set the maximum memory for a 32-bit Java process to 2048 or above. The highest you can make it is usually around 1900. In this case, I wouldn't go above 1800.

As I said in a previous post, if this can be reliably reproduced, I would open a TAC service request so additional troubleshooting and profiling can be performed.


This Discussion