An attempt to stop the mail bombing. :-)
Didn't you see this Rajesh?
Regards,
Adrian
-Forwarded Message-
From: Adrian Brock <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] error while trying to open a new connection
Date: 24 Sep 2003 17:22:57 +0100
I jus
: Adrian Brock [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 24, 2003 6:30 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] error while trying to open a new connection
Again you'll have to give me some information.
Where is getConnection() invoked and where do you store the connection?
Wh
help as we are stuck up with this.
Regards
Rajesh
-Original Message-
From: Adrian Brock [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 24, 2003 6:30 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] error while trying to open a new connection
Again you'll have to give
.suntec.tbms3.ui.CUserValidateSB.storeSignInDetails(CUserValidateSB.java:318)
>
>
> Could you pls help as we are stuck up with this.
>
> Regards
> Rajesh
>
> -----Original Message-----
> From: Adrian Brock [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 24, 2003 6:30 PM
>
help as we are stuck up with this.
Regards
Rajesh
-Original Message-
From: Adrian Brock [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 24, 2003 6:30 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] error while trying to open a new connection
Again you'll have to give
10:45:37,859 ERROR [STDERR] at
> org.jboss.resource.adapter.jdbc.WrappedConnection.commit(WrappedConnection.java:465)
> 10:45:37,859 ERROR [STDERR] at
> com.suntec.tbms3.ui.CUserValidateSB.storeSignInDetails(CUserValidateSB.java:318)
>
> -Original Message-
>
ember 23, 2003 8:39 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] error while trying to open a new connection
You'll have to provide some more information.
It says you are closing a connection that it does not know about
were there previous errors?
There has been some cleanup of the
You'll have to provide some more information.
It says you are closing a connection that it does not know about
were there previous errors?
There has been some cleanup of the error checking in the 3.2.2RC
releases can you check if you still have the problem with 3.2.2RC4?
This actual error should
