Re: [JBoss-dev] Tyrex transaction manager
>From what I heard at JavaOne from a couple of people (e.g., Macromedia use a cut of it in their app. server), it's dead. Mark. - Original Message - From: "Bill Burke" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, June 26, 2003 4:54 PM Subject: RE: [JBoss-dev] Tyrex transaction manager > Anatoly Akkerman was maintaining it a lnnng time ago. Nobody really > uses it or used it. I think the project is dead since their last release > was May 2002 and they only have one CVS committer. > > http://sourceforge.net/projects/tyrex/ > > Bill > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of Bruce > > Snyder > > Sent: Thursday, June 26, 2003 11:10 AM > > To: [EMAIL PROTECTED] > > Subject: RE: [JBoss-dev] Tyrex transaction manager > > > > > > This one time, at band camp, Bill Burke said: > > > > BB>We will not be supporting the Tyrex transaction manager > > anymore unless you > > BB>want to take over the integration. > > > > I'm just curious, why was this decision made? Who used to maintain > > this integration? > > > > Bruce > > -- > > perl -e 'print > > unpack("u30","<0G)[EMAIL PROTECTED]&5R\"F9E > > > > > > > --- > > This SF.Net email is sponsored by: INetU > > Attention Web Developers & Consultants: Become An INetU Hosting Partner. > > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! > > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > > ___ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > --- > This SF.Net email is sponsored by: INetU > Attention Web Developers & Consultants: Become An INetU Hosting Partner. > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Tyrex transaction manager
They are actually one of our partners. Bill > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Fred > Hartman > Sent: Thursday, June 26, 2003 4:42 PM > To: '[EMAIL PROTECTED]' > Subject: RE: [JBoss-dev] Tyrex transaction manager > > > Maybe this is a production DTM option > http://www.arjuna.com/products/jboss/index.html although I don't know the > cost. > > Cheers, > Fred > > -Original Message- > From: Scott M Stark [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 26, 2003 12:23 PM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] Tyrex transaction manager > > > The Tyrex integration was done by Anatoly Akkerman([EMAIL PROTECTED]) > and it never reached a production quality service. Arbitrary stuff is > allowed in the codebase for experimentation, we only support production > level efforts that are maintained. > > -- > > Scott Stark > Chief Technology Officer > JBoss Group, LLC > > > Bruce Snyder wrote: > > > This one time, at band camp, Bill Burke said: > > > > BB>We will not be supporting the Tyrex transaction manager > anymore unless > you > > BB>want to take over the integration. > > > > I'm just curious, why was this decision made? Who used to maintain > > this integration? > > > > Bruce > > > > > --- > This SF.Net email is sponsored by: INetU > Attention Web Developers & Consultants: Become An INetU Hosting Partner. > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > --- > This SF.Net email is sponsored by: INetU > Attention Web Developers & Consultants: Become An INetU Hosting Partner. > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Tyrex transaction manager
Maybe this is a production DTM option http://www.arjuna.com/products/jboss/index.html although I don't know the cost. Cheers, Fred -Original Message- From: Scott M Stark [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2003 12:23 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] Tyrex transaction manager The Tyrex integration was done by Anatoly Akkerman([EMAIL PROTECTED]) and it never reached a production quality service. Arbitrary stuff is allowed in the codebase for experimentation, we only support production level efforts that are maintained. -- Scott Stark Chief Technology Officer JBoss Group, LLC Bruce Snyder wrote: > This one time, at band camp, Bill Burke said: > > BB>We will not be supporting the Tyrex transaction manager anymore unless you > BB>want to take over the integration. > > I'm just curious, why was this decision made? Who used to maintain > this integration? > > Bruce --- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Tyrex transaction manager
The Tyrex integration was done by Anatoly Akkerman([EMAIL PROTECTED]) and it never reached a production quality service. Arbitrary stuff is allowed in the codebase for experimentation, we only support production level efforts that are maintained. -- Scott Stark Chief Technology Officer JBoss Group, LLC Bruce Snyder wrote: This one time, at band camp, Bill Burke said: BB>We will not be supporting the Tyrex transaction manager anymore unless you BB>want to take over the integration. I'm just curious, why was this decision made? Who used to maintain this integration? Bruce --- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Tyrex transaction manager
Anatoly Akkerman was maintaining it a lnnng time ago. Nobody really uses it or used it. I think the project is dead since their last release was May 2002 and they only have one CVS committer. http://sourceforge.net/projects/tyrex/ Bill > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Bruce > Snyder > Sent: Thursday, June 26, 2003 11:10 AM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-dev] Tyrex transaction manager > > > This one time, at band camp, Bill Burke said: > > BB>We will not be supporting the Tyrex transaction manager > anymore unless you > BB>want to take over the integration. > > I'm just curious, why was this decision made? Who used to maintain > this integration? > > Bruce > -- > perl -e 'print > unpack("u30","<0G)[EMAIL PROTECTED]&5R\"F9E > > > --- > This SF.Net email is sponsored by: INetU > Attention Web Developers & Consultants: Become An INetU Hosting Partner. > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Tyrex transaction manager
Hi David, I'm gradually working my way through the same patch for 3.2 now as we speak. Regards, Adrian Adrian Brock Director of Support Back Office JBoss Group, LLC > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of David Jencks > Sent: 26 June 2003 15:50 > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] Tyrex transaction manager > > > Most likely this is caused by bugs 731349 and/or 731363. > These should > be fixed in jb4. I've been offered a patch for 3.2 from a commercial > company whose product depends on these bugs being fixed but it is > unclear if JBossGroup will allow it to be applied. AFAIK no > one wants > to fix these in the 3.0 branch. > > david jencks > > On Thursday, June 26, 2003, at 07:11 AM, Oleg V. Safonov wrote: > > > After deploy tyrex-tm-plugin I get next exception > > java.lang.IllegalStateException: The transaction is not yet or no > > longer > > active > > > > 2003-06-26 18:34:08,733 ERROR > [org.jboss.ejb.EntityContainer] Starting > > failed > > java.lang.IllegalStateException: The transaction is not yet or no > > longer > > active > > at > > > tyrex.tm.impl.TransactionImpl.enlistResource(TransactionImpl.java:600) > > at > > > tyrex.tm.impl.TransactionImpl.enlistResource(TransactionImpl.java:565) > > at > > > org.jboss.resource.connectionmanager.TxConnectionManager$TxCon > nectionEv > > entLi > > stener.enlist(TxConnectionManager.java:460) > > at > > > org.jboss.resource.connectionmanager.TxConnectionManager.manag > edConnect > > ionRe > > connected(TxConnectionManager.java:358) > > at > > > org.jboss.resource.connectionmanager.BaseConnectionManager2.al > locateCon > > necti > > on(BaseConnectionManager2.java:490) > > at > > > org.jboss.resource.connectionmanager.BaseConnectionManager2$Co > nnectionM > > anage > > rProxy.allocateConnection(BaseConnectionManager2.java:798) > > at > > > org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnectio > n(Wrapper > > DataS > > ource.java:102) > > at > > org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(SQLUtil.java:39) > > at > > > org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.( > JDBCEntit > > yBrid > > ge.java:119) > > at > > > org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManag > er(JDBCSt > > oreMa > > nager.java:438) > > at > > > org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStor > eManager. > > java: > > 372) > > at > > > org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersisten > ceManager > > .java > > :170) > > at > > org.jboss.ejb.EntityContainer.startService(EntityContainer.java:339) > > at > > > org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport > .java:192 > > ) > > at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) > > at > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth > odAccesso > > rImpl > > .java:25) > > at java.lang.reflect.Method.invoke(Method.java:324) > > at > > > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec > tedMBeanD > > ispat > > cher.java:284) > > at > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) > > at > > > org.jboss.system.ServiceController$ServiceProxy.invoke(Service > Controlle > > r.jav > > a:966) > > at $Proxy11.start(Unknown Source) > > at > > org.jboss.system.ServiceController.start(ServiceController.java:392) > > at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) > > at > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth > odAccesso > > rImpl > > .java:25) > > at java.lang.reflect.Method.invoke(Method.java:324) > > at > > > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec > tedMBeanD > > ispat > > cher.java:284) > > at > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) > > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) > > at $Proxy37.start(Unknown Source) > > at org.jboss.ejb.EjbModule.startService(EjbModule.java:329) > > at > > > org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport > .java:192 > > ) > >
RE: [JBoss-dev] Tyrex transaction manager
Read this post. http://www.mail-archive.com/[EMAIL PROTECTED]/msg09106.ht ml Adrian Brock Director of Support Back Office JBoss Group, LLC > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Bruce Snyder > Sent: 26 June 2003 16:10 > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-dev] Tyrex transaction manager > > > This one time, at band camp, Bill Burke said: > > BB>We will not be supporting the Tyrex transaction manager > anymore unless you > BB>want to take over the integration. > > I'm just curious, why was this decision made? Who used to maintain > this integration? > > Bruce > -- > perl -e 'print > unpack("u30","<0G)[EMAIL PROTECTED]&5R\"F9E > > > --- > This SF.Net email is sponsored by: INetU > Attention Web Developers & Consultants: Become An INetU > Hosting Partner. > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly > Commission! > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Tyrex transaction manager
This one time, at band camp, Bill Burke said: BB>We will not be supporting the Tyrex transaction manager anymore unless you BB>want to take over the integration. I'm just curious, why was this decision made? Who used to maintain this integration? Bruce -- perl -e 'print unpack("u30","<0G)[EMAIL PROTECTED]&5R\"F9Ehttp://www.inetu.net/partner/index.php ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Tyrex transaction manager
Most likely this is caused by bugs 731349 and/or 731363. These should be fixed in jb4. I've been offered a patch for 3.2 from a commercial company whose product depends on these bugs being fixed but it is unclear if JBossGroup will allow it to be applied. AFAIK no one wants to fix these in the 3.0 branch. david jencks On Thursday, June 26, 2003, at 07:11 AM, Oleg V. Safonov wrote: After deploy tyrex-tm-plugin I get next exception java.lang.IllegalStateException: The transaction is not yet or no longer active 2003-06-26 18:34:08,733 ERROR [org.jboss.ejb.EntityContainer] Starting failed java.lang.IllegalStateException: The transaction is not yet or no longer active at tyrex.tm.impl.TransactionImpl.enlistResource(TransactionImpl.java:600) at tyrex.tm.impl.TransactionImpl.enlistResource(TransactionImpl.java:565) at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEv entLi stener.enlist(TxConnectionManager.java:460) at org.jboss.resource.connectionmanager.TxConnectionManager.managedConnect ionRe connected(TxConnectionManager.java:358) at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateCon necti on(BaseConnectionManager2.java:490) at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionM anage rProxy.allocateConnection(BaseConnectionManager2.java:798) at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(Wrapper DataS ource.java:102) at org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(SQLUtil.java:39) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.(JDBCEntit yBrid ge.java:119) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(JDBCSt oreMa nager.java:438) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager. java: 372) at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager .java :170) at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:339) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192 ) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso rImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanD ispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControlle r.jav a:966) at $Proxy11.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:392) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso rImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanD ispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy37.start(Unknown Source) at org.jboss.ejb.EjbModule.startService(EjbModule.java:329) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192 ) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso rImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanD ispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControlle r.jav a:966) at $Proxy11.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:392) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso rImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanD ispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy24.start(Unknown Source) at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:540) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:613) at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso rImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanD ispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.mx.util.M
RE: [JBoss-dev] Tyrex transaction manager
We will not be supporting the Tyrex transaction manager anymore unless you want to take over the integration. Bill Burke Chief Architect JBoss Group, LLC Cast your vote for JBoss as JDJ Best App Server http://www.sys-con.com/java/readerschoice2003/vote.cfm > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf > Of Oleg V. Safonov > Sent: Thursday, June 26, 2003 10:12 AM > To: [EMAIL PROTECTED] > Subject: [JBoss-dev] Tyrex transaction manager > > > After deploy tyrex-tm-plugin I get next exception > java.lang.IllegalStateException: The transaction is not yet or no longer > active > > 2003-06-26 18:34:08,733 ERROR [org.jboss.ejb.EntityContainer] Starting > failed > java.lang.IllegalStateException: The transaction is not yet or no longer > active > at tyrex.tm.impl.TransactionImpl.enlistResource(TransactionImpl.java:600) > at tyrex.tm.impl.TransactionImpl.enlistResource(TransactionImpl.java:565) > at > org.jboss.resource.connectionmanager.TxConnectionManager$TxConnect > ionEventLi > stener.enlist(TxConnectionManager.java:460) > at > org.jboss.resource.connectionmanager.TxConnectionManager.managedCo > nnectionRe > connected(TxConnectionManager.java:358) > at > org.jboss.resource.connectionmanager.BaseConnectionManager2.alloca > teConnecti > on(BaseConnectionManager2.java:490) > at > org.jboss.resource.connectionmanager.BaseConnectionManager2$Connec > tionManage > rProxy.allocateConnection(BaseConnectionManager2.java:798) > at > org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(Wr > apperDataS > ource.java:102) > at org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(SQLUtil.java:39) > at > org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.(JDBC > EntityBrid > ge.java:119) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(J > DBCStoreMa > nager.java:438) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreMan > ager.java: > 372) > at > org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceMa > nager.java > :170) > at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:339) > at > org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192) > at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc > cessorImpl > .java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedM > BeanDispat > cher.java:284) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) > at > org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceCont > roller.jav > a:966) > at $Proxy11.start(Unknown Source) > at org.jboss.system.ServiceController.start(ServiceController.java:392) > at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc > cessorImpl > .java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedM > BeanDispat > cher.java:284) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) > at $Proxy37.start(Unknown Source) > at org.jboss.ejb.EjbModule.startService(EjbModule.java:329) > at > org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192) > at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc > cessorImpl > .java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedM > BeanDispat > cher.java:284) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) > at > org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceCont > roller.jav > a:966) > at $Proxy11.start(Unknown Source) > at org.jboss.system.ServiceController.start(ServiceController.java:392) > at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc > cessorImpl > .java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedM > BeanDispat > cher.java:284) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) > at $Proxy
[JBoss-dev] Tyrex transaction manager
After deploy tyrex-tm-plugin I get next exception java.lang.IllegalStateException: The transaction is not yet or no longer active 2003-06-26 18:34:08,733 ERROR [org.jboss.ejb.EntityContainer] Starting failed java.lang.IllegalStateException: The transaction is not yet or no longer active at tyrex.tm.impl.TransactionImpl.enlistResource(TransactionImpl.java:600) at tyrex.tm.impl.TransactionImpl.enlistResource(TransactionImpl.java:565) at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventLi stener.enlist(TxConnectionManager.java:460) at org.jboss.resource.connectionmanager.TxConnectionManager.managedConnectionRe connected(TxConnectionManager.java:358) at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnecti on(BaseConnectionManager2.java:490) at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManage rProxy.allocateConnection(BaseConnectionManager2.java:798) at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataS ource.java:102) at org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(SQLUtil.java:39) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.(JDBCEntityBrid ge.java:119) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(JDBCStoreMa nager.java:438) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java: 372) at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java :170) at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:339) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.jav a:966) at $Proxy11.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:392) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy37.start(Unknown Source) at org.jboss.ejb.EjbModule.startService(EjbModule.java:329) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.jav a:966) at $Proxy11.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:392) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy24.start(Unknown Source) at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:540) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:613) at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy7.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanne r.java:302) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner. java:476) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan( AbstractDeploymentScanner.java:200) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(Abstract DeploymentSc