The code you sent me looks ok.
There is a counter of committed and rollbacked transactions
on the transaction manager MBean in the most recent versions of jboss.
Regards,
Adrian
On Thu, 2003-08-07 at 13:31, Rafal Kedziorski wrote:
> hi,
>
> At 12:33 07.08.2003 +0100, you wrote:
> >On Thu, 2003-
The most likely cause of this error is trying to use the same
connection in two different threads/transactions concurrently.
The first error says it could not enlist the resource in the
transaction, probably because it is already enlisted in a different
transaction.
Regards,
Adrian
On Thu, 2003-
hi,
At 12:33 07.08.2003 +0100, you wrote:
On Thu, 2003-08-07 at 11:16, Rafal Kedziorski wrote:
> hi,
>
> At 10:09 07.08.2003 +0100, Adrian Brock wrote:
> >The most likely cause of this error is trying to use the same
> >connection in two different threads/transactions concurrently.
> >
> >The firs
hi,
At 10:09 07.08.2003 +0100, Adrian Brock wrote:
The most likely cause of this error is trying to use the same
connection in two different threads/transactions concurrently.
The first error says it could not enlist the resource in the
transaction, probably because it is already enlisted in a dif
hi,
I posted last week our connection problem with JBoss 3.2.1 and MySQL
4.0.14. This is our mysql-ds.xml:
MmcmsDS
jdbc:mysql://xx.xx.xx.xx:3306/mmcms
com.mysql.jdbc.Driver
...
...
true
5
50
5000
15
but we get now this exceptions:
2003-08-07
On Thu, 2003-08-07 at 11:16, Rafal Kedziorski wrote:
> hi,
>
> At 10:09 07.08.2003 +0100, Adrian Brock wrote:
> >The most likely cause of this error is trying to use the same
> >connection in two different threads/transactions concurrently.
> >
> >The first error says it could not enlist the resou
