As this was a non-trivial change (even though it sounds like one) that come along with external transactions this fix can hardly be applied to 2.0. Thus the only thing I can recommend for now is to either stick to the JDBCStore or wait for 2.1...
Anyway, thanks for helping :)
Oliver
Mike Wynholds wrote:
Running with Slide 2.1b1 works (at least in my initial testing). ..mike..
-----Original Message-----
From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 21, 2004 7:54 AM
To: Slide Users Mailing List
Subject: Re: Using J2EEStore with MySqlRDBMSAdapter throws exception.
Would you do me another favor and try to run one of the more recent versions of Slide? Maybe the 2.1b1? Would be great!
Thanks in advance,
Oliver
Mike Wynholds wrote:
I am using Slide 2.0.
JDBCStore does in fact work fine, and I am trying to move over to the J2EEStore in an effort to consolidate usage of a single DataSource between Slide and Hibernate.
It's strange since the J2EEStore and JDBCStore both extend the same
base
class and just appear to create a connection.
..mike..
-----Original Message-----
From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 21, 2004 1:08 AM
To: Slide Users Mailing List
Subject: Re: Using J2EEStore with MySqlRDBMSAdapter throws exception.
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]
--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- 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]
