I don't know what is going on either, but the problem is occurring when the cmp2 engine is trying to create a table during deployment of a bean. IMO it should be doing that in its own tx. However it isn't normally coming from an ejb call, so normally there is no tx context on the call. Maybe the MEJB needs tx attributes not supported on all its methods.
david jencks On 2002.03.22 09:01:17 -0500 marc fleury wrote: > wait wait wait.... > > a persistence engine???? > > this is a SSB... where does CMP come in? > > I really can't make sense of your story. > > marcf > > |-----Original Message----- > |From: Vesco Claudio [mailto:[EMAIL PROTECTED]] > |Sent: Friday, March 22, 2002 5:36 AM > |To: Jboss Dev (Posta elettronica) > |Cc: 'marc fleury' > |Subject: RE: [JBoss-dev] MEJB transactions (invoke deploy) > | > | > |I remember you that my English is very bad :-) > | > |In org.jboss.ejb.plugins.cmp.jdbc.JDBCStartCommand at line 143 there is > | > |manager.getContainer().getTransactionManager().begin (); > | > |If the container is already in transaction there is an exception > |(javax.transaction.NotSupportedException) because there is another > |transaction. > | > |The container have a transaction active because, I think, I have > deployed > |the entity with MEJB SSB and the method "invoke" of this ejb have a > |transaction defined in the transaction assembly part of ejb-jar.xml, > more > |there is not definitions and so the defaults are applied. > | > |The CMP engine start a new transaction because it need it for > |creating a sql > |table or a sql fk. > |I think that the transaction is only started when the ejb need a new sql > |table (deploy time). > | > |With others JMX remote invokers, I think there are no problems because > the > |transaction context is not propagate from client (external jboss) > |and jboss. > | > |I have added transaction-type="Bean" to > |jboss/management/mejb/ManagementBean.java and I can now deploy the > entity > |ejb. > | > |This is the best solution that it has come to me in mind. > | > |The alternative was that to control if active transaction existed > already > |:-( but I think that there are many place in jboss where a "jmx > invocation" > |trigger a transaction begin/commit. I remember you that I don't mean a > user > |client "ejb invocation". > | > |I checked the jsr-77 and I don't see restriction to set the transaction > of > |MEJB to "Bean" managed. > | > | Claudio > | > |> -----Original Message----- > |> From: marc fleury [SMTP:[EMAIL PROTECTED]] > |> Sent: Friday, March 22, 2002 1:33 PM > |> To: Vesco Claudio; Jboss Dev (Posta elettronica) > |> Subject: RE: [JBoss-dev] MEJB transactions (invoke deploy) > |> > |> the container/bean story does not sound right.... > |> > |> why does the CMP engine START a new transaction? that is not it's > place > |> what > |> persistence engine are you using? > |> > |> > |> marcf > |> > |> |-----Original Message----- > |> |From: [EMAIL PROTECTED] > |> |[mailto:[EMAIL PROTECTED]]On Behalf Of > Vesco > |> |Claudio > |> |Sent: Friday, March 22, 2002 1:29 AM > |> |To: Jboss Dev (Posta elettronica) > |> |Subject: [JBoss-dev] MEJB transactions (invoke deploy) > |> | > |> | > |> |Hi alls! > |> | > |> |When I try to deploy an ear (better, an CMP entity) with MEJB I have > an > |> |exception in org.jboss.ejb.plugins.cmp.jdbc.JDBCStartCommand > |because this > |> |class try to start a new transaction. > |> | > |> |The problem is that MEJB have a transaction management setting > |to default > |> |("Container"). > |> | > |> |I think that is better to set the transaction to "Bean". > |> | > |> |In jsr-77 I don't have found reference to the transaction mode of the > |> |management EJB. > |> | > |> |When I modify the transaction definition, the deployment go well. > |> | > |> |Another problem... > |> | > |> |There is an discrepancy with the pdf jsr-77. The method > |queryNames in the > |> |interface javax.management.j2ee.Management have a query parameter in > |> jsr-77 > |> |pdf which is not present in the current implementation. > |> | > |> |If not there are controindications, I'll commit the patches. > |> | > |> | Claudio > |> | > |> |_______________________________________________ > |> |Jboss-development mailing list > |> |[EMAIL PROTECTED] > |> |https://lists.sourceforge.net/lists/listinfo/jboss-development > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
