Forum Discussion

ashishshelke's avatar
New Contributor
5 years ago

ReadyAPI is not closing jdbc connections

We are using JDBC request in ReadyAPI, but connection is not getting closed.

can anyone help, to close jdbc connections using ReadyAPI.

  • nmrao, richie, thank you for help!


    Hi ashishshelke , did you solve the issue? If it still persists, I suggest that you contact support and describe the situation as minutely as possible to them. Let us know when you get a solution from them.

5 Replies

  • richie's avatar
    Community Hero
    Hi ashishshelke,

    Can you provide a bit more info?

    What RDBMS are you connecting to? (Oracle? SQLServer? Postgres?, etc.)

    What makes you think the connection isn't being closed?

    What version of ReadyAPI! are you using?


    • ashishshelke's avatar
      New Contributor

      I am using Oracle database.

      Because further connections are failing because of limited number of sessions.

      we are checking the ACTIVE sessions using sql query on Oracle.

      • richie's avatar
        Community Hero
        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 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.


  • nmrao's avatar
    Champion Level 3
    Since the tool does the connection and closing, I believe, users don't have control over the connection.
    Do you still this issue if you close the tool?
    By the way, how are you monitoring the connections?

    Any ways, how do you use the tool? I mean the usage? If you have automated tests, then they can be executed from command line and as soon the execution is completed, there should not be any active sessions / connections to db.
    If the usage is just limited to UI (tool), then probably no connections at least after closing the tool.

    You may try the above to see if that is helpful. Otherwise, you may get in touch with support team.