This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
I am trying from many days to fix an issue. We are using glassfish + jms (amq).
As part of performance testing I tried to send too many requests to our application and then I received some corba exception like thisI also received some exceptions like
Unexpected end-of-file encountered
Then I came to know that the servlet thread pool is set to its default size 5. Then I increased the thread pool to 100 for now and later I dint observer the second exception.
Then I tried to send too many requests again. This time I received another exception apart from corba exception.Then I understood that I have to increase the connection pool size.
I increased the pool size in our glassfish-resources.xml and redeployed the application, restarted the server and have send 50 requests, from which few of them failed with the same exception again and other exceptions. The connection pool size is not taking effect. From the documentation I read that the default size is 32. But after increasing the size glassfish is only creating max 30 connections. If I leave it to default glassfish is creating all 32 as per need.Then later I thought something might be wrong in the transaction management and then I configured XATransaction and max-wait-timeout-in-millis to 0 on the pool in my glassfish-resources.xml. Then I redeployed the application, restarted the server and have sent 20 request. This time glassfish created almost 36 connections. This time, for few requests the time taken to receive the response from the server increased a lot. In the glassfish server logs again I could see corba exceptions.
Can anyone please help me fix this problem. This will really be a big help for me. Thank you all in advance.