I did find the problem.
Thanks,
J.D.
-Original Message-
From: David Jencks [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 18, 2003 7:22 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] JBOSS 3.2RC2 - Connection Manager Info
You should be able to determine where the connection
Hello,
After moving from 3.2RC1 to 3.2RC2 I started receiving this
information message in my server log. I verified I was closing the
connection in my finally clauses, so I'm not sure why the CachedConnectionManager
is complaining.
Any suggestions?
J.D.
13:21:50,683 INFO
I, too, was getting this error after following the advice in a previous
posting regarding the TransactionManager attribute of the datasources' service.xml
file. The advice was to ignore the log messages asking you to change it
to jboss.tm:service=TransactionManagerService.
By turning the
PM
To:
[EMAIL PROTECTED]
Subject: Re: [JBoss-user] JBOSS
3.2RC2 - Connection Manager Info
I, too, was getting this error after following
the advice in a previous posting regarding the TransactionManager attribute of
the datasources' service.xml file. The advice was to ignore the log
messages
[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 18, 2003 3:41 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] JBOSS 3.2RC2 - Connection Manager Info
I, too, was getting this error after following the advice in a previous
posting regarding the TransactionManager attribute
Corbin, James wrote:
Ben,
I have verified
wherever there is a getConnection that it is subsequently followed by a closeConnection().
Alas, I may have missed one and will keep looking.
I don't know if it makes a difference, but I used
