It seems that the new CVS version (01/10) works fine, eliminating the lock
problem.
What are the changes?
Perhaps the problem was that I did not edit the jboss.jcml before, indeed, I
only
edited the jboss.conf file adding the following lines:
<MLET CODE = "org.jboss.jdbc.DataSourceImpl"
ARCHIVE="jboss.jar,jdbc2_0-stdext.jar,classes111.jar" CODEBASE="../lib/ext/">
<ARG TYPE="java.lang.String" VALUE="jdbc:oracle:thin:@wagner:1521:mobistar">
<ARG TYPE="java.lang.String" VALUE="Oracle">
<ARG TYPE="java.lang.String" VALUE="oracle.jdbc.driver.OracleDriver">
<ARG TYPE="java.lang.String" VALUE="dsie">
<ARG TYPE="java.lang.String" VALUE="dsie">
</MLET>
whose syntax seems to be different now.
regards
marc fleury a �crit :
> There is a double lock in your BMP entity... I need to see what your
> ejbCreate method does, can you post that code?
>
> Do me a favor Frederic, we have been debugging the source quite heavily
> yesterday and the CVS is new.
> Sebastien Alborini claims he saw a similar bug and that the new fixes we put
> in clean it.
>
> However if that remains, do a stack trace in the lock of enterpriseContext
> (new Exception().printStackTrace();)
> and send me the same dump, we will get you going
>
> regards
>
> marc
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Fr�d�ric FANIEN
> > Sent: Friday, September 29, 2000 1:54 AM
> > To: jBoss
> > Subject: Re: [jBoss-User] BMP lock problem
> >
> >
> > Hello Marc,
> > I send here the console output,
> > I as already said, my BMP entity is as simple as possible and works
> > fine without any changes on the 2 weeks ago CVS version.
> >
> > I simply try to use it like this
> > Resource resource = ressourceHome.create("resource0","name","firsname");
> > System.out.println(resource.getResourceName());
> > and it blocks here.
> > (I tried all transaction types : Never, Required etc...)
> >
> > [Default] JRMPCI:invokeHome create
> > [Default] JRMPCI (local) :invokeHome create
> > [Default] Tx is null
> > [Default] invokeHome
> > [workflow/Resource] TX_REQUIRED for create
> > [workflow/Resource] begin tx
> > [workflow/Resource] EnterpriseContext.lock() 7261893 1
> > [workflow/Resource] CacheKeyHash:677441345
> > [workflow/Resource] EnterpriseContext.lock() 7261893 2
> > [workflow/Resource] EnterpriseContext.unlock() 7261893 1
> > [workflow/Resource] TxInterceptorCMT: In finally
> > [workflow/Resource] TxInterceptorCMT:before commit
> > [workflow/Resource] txManager commit tx 0
> > [workflow/Resource] Before completion is done status is STATUS_ACTIVE
> > [workflow/Resource] EnterpriseContext.setTransaction null
> > [workflow/Resource] TxInterceptorCMT:after commit
> > [Default] JRMPCI:invoke getResourceName
> > [Default] JRMPCI (local) :invoke getResourceName
> > [Default] Tx is null
> > [workflow/Resource] TX_REQUIRED for getResourceName
> > [workflow/Resource] begin tx
> > [workflow/Resource] Get org.jboss.ejb.CacheKey@2860ef41 from cache
> > [workflow/Resource] EnterpriseContext.isLocked() 7261893 at 1
> >
> > << after about 20 seconds >>
> >
> > [Default] Transaction org.jboss.tm.XidImpl@614a78 timed out.
> >
> >
> > marc fleury a �crit :
> >
> > > hello,
> > >
> > > we run the BMP tests from the latest cvs fine... hold on, and make sure
> > > there are no exceptions thrown on the server (do you see a XA
> > exception? we
> > > had that in the testbeans for "bad behaviour" (not closing the
> > connection
> > > upon returning from a method)...
> > >
> > > do look for an xa exception, the new code is much stronger on
> > tx management
> > > and some things that use to "pass by" are now seen as
> > exceptions, which is
> > > kosher. There is currently an extensive discussion on the
> > proper management
> > > of these resources in bean management that spans invocations and
> > > transactions.
> > >
> > > tell me if you see the xa stuff
> > >
> > > marc
> > >
> > > > -----Original Message-----
> > > > From: [EMAIL PROTECTED]
> > > > [mailto:[EMAIL PROTECTED]]On Behalf Of Fr�d�ric FANIEN
> > > > Sent: Thursday, September 28, 2000 8:37 AM
> > > > To: jBoss
> > > > Subject: [jBoss-User] BMP lock problem
> > > >
> > > >
> > > > Hello,
> > > > I have a little problem with BMP entity EJB which exists is the
> > > > current CVS version, and not
> > > > in previous ones.
> > > > I have created an BMP entity Resource and I use it :
> > > >
> > > > line1 Resource resource =
> > > > resourceHome.create("resource0","name","firsname");
> > > > line2 System.out.println(resource.getName());
> > > >
> > > > The problem is jboss is blocked on line2 and don't continue. It
> > > > writes on screen, that the transaction is
> > > > locked.
> > > >
> > > > This EJB worked well with previous versions.
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > --------------------------------------------------------------
> > > > To subscribe: [EMAIL PROTECTED]
> > > > To unsubscribe: [EMAIL PROTECTED]
> > > > Problems?: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > > --
> > > --------------------------------------------------------------
> > > To subscribe: [EMAIL PROTECTED]
> > > To unsubscribe: [EMAIL PROTECTED]
> > > Problems?: [EMAIL PROTECTED]
> >
> >
> >
> > --
> > --------------------------------------------------------------
> > To subscribe: [EMAIL PROTECTED]
> > To unsubscribe: [EMAIL PROTECTED]
> > Problems?: [EMAIL PROTECTED]
> >
> >
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
