0 Replies Latest reply on Jul 2, 2004 8:40 PM by Jasen Halmes

    ManagedConnection [InUse/Avaliable/Max]: [-1/9/40] bug?

    Jasen Halmes Newbie

      We have spent days trying to figure this out. We have JBoss 3.2.3 running on Linux, w/JMS persisting to Oracle 9.

      The ManagedConnection seems to work for random amounts of time until the InUse value decrements to a negative number. Why would it ever do that? Is that a bug in 3.2.3?

      After the negative number shows up everything goes to heck.

      After an hour or less the application starts crashing because of the JMS persistence calls with "java.sql.SQLException: Io exception: Broken pipe". I can't post the stack trace or config files unfortunately, but here is some hand typed stuff from the log that seems relevent:

      [JBossManagedConnectionPool] putting ManagedConnection back into pool
      [JBossManagedConnectionPool] ManagedConnection is being returned after it was destroyedorg.jboss.resource.adapter.jdbc.local.LocalManagedConnection@28f52a14
      [JBossManagedConnectionPool] Returning connection to pool [InUse/Available/Max]: [-1/9/40]
      WARN [JBossManagedConnectionPool] Exception destroying ManagedConnection
      org.jboss.resource.JBossResourceException: SQLException; - nested throwable: (java.sql.SQLException: Io exception: Broken pipe)
      at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkException(BaseWrapperManagedConnection.java:546)
      ...lines omitted...
      at org.jboss.resource.adapter.jdbc.WrappedConnection.checkException(WrappedConnection.java:793)
      at org.jboss.resource.adapter.jdbc.WrappedStatement.checkException(WrappedStatement.java:802)
      at org.jboss.resource.adapter.jdbc.WrappedStatement.close(WrappedStatement.java:61)
      at org.jboss.mq.pm.jdbc2.PersistenceManager.add(PersistenceManager.java:790)
      at org.jboss.mq.pm.jdbc2.PersistenceManager.saveToStorage(PersistenceManager.java:1210)
      ...many lines omitted...

      So is this a JMS bug or a ManagedConnection bug or something else? If it is a known bug, does upgrading fix it?

      thanks,
      jasen