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

[jhalmes]

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

(I cross posted this here because the problem only occurs with the JMS persistence, the normal persistence to the same, or different, datasource never has the problem.)

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

[genman]

Hmm, sounds like a bug that was fixed in 3.2.4. This was a JCA issue. Perhaps you could have found your answer through the forum Search or release notes?

[jhalmes]

I did search the forums for several hours. The release notes would only help if I knew what this problem was called. I'll take your advice and read through them.

In the future you may want to think about the image you give to the open source community with responses like this. I work for a multi-billion dollar company, if my managers saw your response it would give them all the ammo they need to support the perception that open source software has no support.

You actually took the time to sit down and type an answer, I suggest next time that you include a little more helpful information. I clearly was not asking a newbe question, I have purchased documentation and spent a great deal of my company time debugging and searching through all the online information I could find on this topic. There are people giving up their 3 day weekend to try to fix this right now so we don't have to pull out JBoss and use a commercial product instead.

But you don't care about that, you're too smart for the rest of us. My apologies for wasting your precious time. Hmmm, maybe all the stupid people like me should just pay for Weblogic. At least if I posted a problem in their forums I wouldn't get insulted.

[nielsc]

Jason,

I know its been a while since you posted your problem.
Did upgrading fix your Inuse -1 problem.

We are getting the same problem using JBoss 3.2.3 on Windows 2000.
We specifically see the problem on our connection pool for the persisted
JMS queues. We are using MSSQL as our database.

Cheers,
Niels