Hi
ashishshelke,
I've used sql to close active sessions on Oracle before. It sounds like you've found the table already but just in case it was a table in the system schema/user.
It was a loooooong time ago though.....i think i did it on Oracle v9i....unsure whether dropping the row in the table for the session would work on later versions, but that's how i did it before cos the sessions weren't being released back to the pool by the application.
You state that "further connections arent working because a limited number of sessions". Have you actually determined whats going on regarding the db connections? Are you saying that each test which has a JDBC step isnt releasing its db connection? Or is the nonrelease of the connection occurring each time you execute the whole soapui project? Understanding how the connections are being built up (once per test, etc.) without being released will help you identify how to get around it if the SQL option no longer works. Are you running in sequential or parallel mode? I would expect ReadyAPI! to release connections backs to the pool as soon as its not needed, so i'd double check there isn't something else going on on the oracle side that isnt the cause of the nonrelease of the connections
Oh...just as an aside...i ALWAYS add semi colons at the end of my SQL statements. I know its no longer mandatory, but still helps the RDBMS know that is the end of the executable SQL, it cant hurt and can only help so id make sure you are ending your statements with a semi colon.
As Rao said....contact support, but also there's a number or stackoverflow posts about killing a db connection using java....perhaps you could look at these to kill it if deleting the session row/truncating the table doesnt work (like it used to) using SQL.
Ta
Rich
