This week's book giveaway is in the OCPJP forum. We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line! See this thread for details.
Hi, In my application MDB with container manage transaction,I am doing performence testing ,for this in my configuration connection pool size is 15 ,I am sending message in every 2 second from my clint program. but after two or three hour I am getting this error.Imn my application I am persisting the jms message in jms table.
Any body having idea why I am getting this error.
BEA-010065 Jul 2, 2007 8:16:39 PM IST myserver Warning EJBMessageDrivenBean threw an Exception in onMessage(). The exc eption was:
Looks like you are running out of memory, which is not too much of a suprise if you are doing performance testing. There are a plethora of reasons why it could be happening, from the very obvious (you haven't configured your JVM with enough memory) to the less obvious (your application has a memory leak).
One of the first things to note is its actually quite easy to write a performance test that breaks an application in an invalid way, by which I mean your test is actually using the application in an unrealistic way. For example a common one I see is people writing test scripts that try to log all N hundred users on simmultaneously, rather than ramping them up over time.
Without knowing a lot about your application and its architecture it is very difficult to offer much advice beyond general stuff. Check your test: is it valid? Check your JVM configuration: does it have enough memory? If its a long running JVM, are you using the server configuration (if it is HotSpot we are talking about)? Tweek your JVM with things like GC logging on to see what is going on (see here for useful ones). Doing this last one will begin to hint a memory leak if there is one.