Skip to main content

ManagedConnection has no connection handle - ORA-02396: exceeded maximum idle time

If there's not any endgame, we're in quicksand. We take one more step, and we're still there, and there's no way out. - Richard Shelby
We've had yet another outage this week. We were exceeding connection idle time limit in Oracle. with almost 270 connections blocked by the application just waiting idly. There was something that was holding up the connections, so we rebounded the server. We thought that was an off shoot. However this repeated on another instance. Around 90 minutes into this blocked state, we got this stack trace.

org.springframework.jdbc.UncategorizedSQLException: Hibernate operation: could not inspect JDBC autocommit mode; uncategorized SQLException for SQL [???]; SQL state [null]; error code [0]; Connection handle is not currently associated with a ManagedConnection; nested exception is java.sql.SQLException: Connection handle is not currently associated with a ManagedConnection

[org.hibernate.util.JDBCExceptionReporter] ORA-02396: exceeded maximum idle time, please connect again

The first thing that came to our *brilliant* minds was - In Jboss, there is an idle-timeout-minutes setting for local-tx-datasource configuration - Why is the max idle time out coming from oracle (which in our case is way larger than idle-timeout-minutes specified in oracle-ds.xml).

A little research showed that the idle-timeout-minutes, is for connections that have been used by the app and returned to the pool. So, there are connections held up in the application. We started looking at where we have long standing transactions. To help us, The admin took a thread dump. all of them were held in a Mainframe call. The call was improperly configured to 90 minutes of time out. Fixed the time out. So far, we are good :)
Labels:

Popular posts from this blog

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.
Read More >>

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.
Read More >>

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>
Read More >>