We are having a problem with WebSphere. We are running out of cursors inspite of closing the statements and connections.
The same code base works absolutely fine with weblogic. Is there some configuration of something you could suggest?
We have the same proplem on weblogic. Who can help me?
It is something specific to the database u use. The default settings of the cursors in the database(eg., ORACLE) is just 50. Where in if u use a large amount of data to be transacted this may give u a problem of maximum cursors exceeded. Where as to avoid it u can better go to the database and just increase the number of the cursors set.
try it out and work it out.
Execute the following queries, when cursor size exceeds..,
select sql_text, sid from v$open_cursor where user_name='DEMO' order by sid
select sql_text, sid from v$open_cursor where user_name='DEMO' and sid in
('19', '20') order by sid, sql_text
Here sid are the ones where the the number of
cursor should not be above 50 (default).
Using this U can increase Ur DB's cursor size if needed
Is there some other configuration that needs to be done in websphere.
Right now in the beans,we are acquiring a connection from the pool,performing a database operation and releasing the connection to the pool.
Is there any other care we need to take in the code with respect to connections/cursors??
The connection cache was set to 0 in the websphere configuration and it worked.