This week's book giveaways are in the Java EE and JavaScript forums.
We're giving away four copies each of The Java EE 7 Tutorial Volume 1 or Volume 2(winners choice) and jQuery UI in Action and have the authors on-line!
See this thread and this one for details.
The moose likes Java in General and the fly likes how to solve this Exception Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Java » Java in General
Bookmark "how to solve this Exception" Watch "how to solve this Exception" New topic
Author

how to solve this Exception

srikanth pidikiti
Greenhorn

Joined: Apr 14, 2006
Posts: 12
type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: Servlet execution threw an exception


root cause

java.lang.OutOfMemoryError: Java heap space


note The full stack trace of the root cause is available in the Apache Tomcat/5.0.30 logs.


--------------------------------------------------------------------------------

Apache Tomcat/5.0.30
Jan Groth
Ranch Hand

Joined: Feb 03, 2004
Posts: 456
looks like you got a memory leak somewhere. i think it's you user controler, which is invoked from loginUser.jsp. Probably you are creating new DataTransactionProxies in an endless loop. just use TransactionAwareProxyFactory() instead, then everything should work fine, the factory will take responsibility of the creation process.

no, seriously - what are you expection people to answer here? your - not so advanced - question is of the type "my car makes strange sounds. how can i fix it?".

try to inspect your code, figure out who is calling whom and debug systematicaly. with eclipse IDE you can set breakpoints on jsps, see what objects are created and where your (most likely) endless loop is...

;-)

best regards,
jan
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: how to solve this Exception