Stephan,
Thanks for the info. After looking into it some more, we found another
solution that worked really well, we migrated to PostgreSQL yesterday
morning ;-)
Thanks for the help.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> Stephan Gruschke
> Sent: Monday, April 09, 2001 4:08 AM
> To: Rick Gibbs; [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] Mysql Transactions + BMP
>
>
> Hi Rick,
>
> I'm using MySQL and JBoss 2.x both on Linux and Windows.
>
> Most of the problems arises from the crappy transaction
> implementation of the
> mysql.
>
> For example I received the RollbackException from a bean some weeks
> ago. This was caused by submitting remote interfaces as parameters to
> a method. After changing the remote interfaces into primary keys (and
> calling the findByPrimaryMethod on the home interface) everything went
> ok.
>
> The main problem concerning the mysql and the jdbc driver is the lack
> of support for setting the transaction level. The jdbc driver hasn't
> implemented it yet, because the protocol is *officially* not capable
> of doing that.
>
> I read a e-mail from Michael Widenius some days ago stating that there is
> already an protocol command for setting the transaction level.
>
> So I see there three choices:
> a) change the parameter using an remote interface of the (entity) bean
> to primary key. At least in my case it solved the biggest problems.
> b) dig into the jdbc driver and the mysql protocol to send the transaction
> level command to mysql.
> c) create an XADataSource implementation for the jdbc-driver, which
> uses the same connection (every bean using the same connection = no
> transaction isolation...)
>
> Well, I can't tell you exactly which path the shortest to achieve
> the best results.
>
> On a long term point of view the only way to create a good JBoss/MySQL
> combination is to extend the jdbc-driver to create XADataSource
> imlementations.
>
> Stephan.
>
>
> RG> Hi there,
>
> RG> I was wondering if anyone was able to get MySql to
> work with BMP. We are
> RG> running the latest and greatest version of MySql with
> transaction support
> RG> and I have spent the last couple of days trying to get it to
> work. We are
> RG> getting an exception stating that jboss can't commit the
> transaction which
> RG> makes sense since mysql is autocommit by default. Has anyone
> been able to
> RG> turn this off? I figured I'd ask instead of beating my head
> against the
> RG> wall anymore ;-)
>
> RG> thanks,
>
> RG> -Rick
>
>
> RG> java.lang.reflect.UndeclaredThrowableException:
> RG> javax.transaction.RollbackException: Unable to commit, tx=XidI
> RG> mpl [FormatId=257, GlobalId=eiger//2, BranchQual=]
> status=STATUS_ROLLEDBACK
> RG> at
> RG> sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown
> RG> Source)
> RG> at
> sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
> RG> at sun.rmi.server.UnicastRef.invoke(Unknown Source)
> RG> at
> RG>
> org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker_Stub.invoke(Unknown
> RG> Source)
> RG> at
> RG>
> org.jboss.ejb.plugins.jrmp.interfaces.EntityProxy.invoke(EntityPro
> xy.java:18
> RG> 2)
> RG> at $Proxy1.getData(Unknown Source)
> RG> ..........
>
>
> RG> _______________________________________________
> RG> Jboss-development mailing list
> RG> [EMAIL PROTECTED]
> RG> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
>
>
> --
> Best regards,
> Stephan mailto:[EMAIL PROTECTED]
>
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
