Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

need help to setup trace for connection pooling in WAS

 
Prakash Chicka
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I need a help on how to set up trace for IBM WAS. We have a application, which is running on WAS and Oracle is the DB server. We are coming across "com.ibm.ejs.cm.portability.ResourceAllocationException: ORA-01000: maximum open cursors exceeded" error even though we are explicitly closing connections/resultsets/statements in the code.

Is there any possibility that WAS not releasing the connections back to the pool and causing this problem. If so, please let me know if there are any settings in the WAS.

The connection values in the WAS are set to min=1 and max=10, the open_cursor value is set to 600 and there are more than 100 apps using the same instance.

It would be great if anybody can help me as earliest.
 
Pat Flickner
Ranch Hand
Posts: 173
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What do you have your connection, idle, and orphan timeouts set to? We keep ours pretty low, no more than 30 so that they don't have any of these problems. Also, do you have a "SELECT_OPEN_CURSOR=true" for your connectionProperties? Oh, I just thought... what version of WAS are you running? I'm on 5.1.2, but for the database connections, I'm using the version 4.0 datasource when I set up the connections. I can't remember why we did this, but it works.

Pat
 
Prakash Chicka
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Pat,
Thanks lot for your reply, I have, Connection Timeout=180, idle timeout=1800, and orpahn timeout=1800. I really dont know where we set this "SELECT_OPEN_CURSOR=true".
The client is using WAS 4.0.4 and its in the production.

Regards,
Prakash
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic