Hi Mike, hi Ricardo,
which version of Slide are you using? I haven't used the J2EEStore for a long time and can only tell it used to work. Maybe something has gotten wrong there is the meantime. Anyway, could you do me a favor and try if it to use the JDBCStore for testing? Does it work there?
There also was another thread that reported unclosed connections when J2EE with MySqlRDBMSAdapter runs in JBoss, but I can not find the thread. Same question to those guys, which version of Slide are you using? Does it work with the JDBCStore?
Coming back to the problem. When I inspect the stack trace, I see the first and real error appears as soon as the jexus namespace is to be loaded. The subsequent ones are errors that pop up, because the connection has been closed before because of errors.
There used to be problems with namespaces in earlier versions of Slide, but I guess they have been fixed, haven't they? Could someone comment on that?
Oliver
Mike Wynholds wrote:
I am seeing this exact same issue. It seems that when Slide is attempting to start a transaction, it is first looking up the ThreadLocal transaction ID. The second (and thereafter) time it does this, the transaction ID is not null, which is throwing an XAException which then causes these lines to print out, and eventually to fail.
are these nested transactions and not supported?
..mike..
-----Original Message-----
From: Ricardo Gladwell [mailto:[EMAIL PROTECTED] Sent: Friday, September 17, 2004 1:25 AM
To: Slide Users Mailing List
Subject: Using J2EEStore with MySqlRDBMSAdapter throws exception.
Hi All,
Despite a seemingly valid configuration, Slide repeatedly throws exceptions with "cause is empty" message on initialisation, closing all connections to the data source (see log stack trace attached). I have verified that the datasource is up and running and that the correct login information has been provided (see sample.context.xml).
Does anyone have any idea what is causing this?
Kind regards, -- Ricardo Gladwell
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
