You have been free to convert all your db access to the jca framework for
the last 6 months, it appears noone has. The XADataSourceLoader change
more or less converts it for you. If you don't want to run on rabbithole
you could just use it for the conversion and copy the
ConnectionFactoryLoader config back to your normal 2.4 jboss. Note that
the race condition bug fix I mention is only applied to rh, and is almost
certainly present in 2.4. So you'd want the BaseConnectionManager from rh.
;-)) new frontiers in earning money from jboss -- "will convert your
XADataSourceLoaders for $$$" ;-)))
Try it, its pretty easy. And I'd like to know if it works for anyone other
than me.
david jencks
On 2001.08.16 11:27:06 -0400 Jason Dillon wrote:
> Is there a more prefered way short of the loaders?
>
> --jason
>
>
> On Thu, 16 Aug 2001, David Jencks wrote:
>
> > Ok, I finally got the rewritten XADataSourceLoader into cvs. All you
> need
> > to do to try with jca should be to use latest cvs rabbithole. The
> > XADataSourceLoader should do the conversion for you.
> >
> > It worked great for me, I'm waiting for the storm of protest if it
> breaks
> > something I didn't test.
> >
> > david jencks
> >
> > On 2001.08.15 14:40:42 -0400 Jason Dillon wrote:
> > > Could you explain what I need to do?
> > >
> > > --jason
> > >
> > >
> > > On Wed, 15 Aug 2001, David Jencks wrote:
> > >
> > > > Hi Jason, could you try converting to the jca version of db access
> and
> > > see
> > > > if the problem persists? I recently found a race condition in (the
> jca
> > > > versions) of the code that releases connections back to the pool
> after
> > > > transactions complete that was allowing several transactions to
> access
> > > the
> > > > same connection. Maybe a similar bug is present in the non-jca
> code.
> > > I'm
> > > > hoping to check in my "auto-converting-to-jca" XADatasourceLoader
> later
> > > > today, in case you don't want to try the conversion by hand. (this
> race
> > > fix
> > > > is only in rabbit hole).
> > > >
> > > > Thanks
> > > > david jencks
> > > >
> > > > On 2001.08.14 19:07:43 -0400 Jason Dillon wrote:
> > > > > I was trying to track down a concurrency problem which would show
> up
> > > as
> > > > > an
> > > > > Oracle deadlock exception. It looks like that exception was
> > > happening
> > > > > due
> > > > > to some fk constraints causing parent tables to lock and such.
> Any
> > > ways,
> > > > > after I got that deadlock exception, I got a ton of these session
> > > bean
> > > > > context errors.
> > > > >
> > > > > I think that I have fixed the deadlock problem by removing some
> of
> > > the fk
> > > > > constraints (which I don't like too much, but it stopped the
> > > exception
> > > > > from
> > > > > being thrown), but I am still getting these errors.
> > > > >
> > > > > I thought they were caused by the oracle problem, but now I think
> > > there
> > > > > might be something else going on.
> > > > >
> > > > > Does anyone have any ideas on why this might happen, and or how I
> > > might
> > > > > go
> > > > > about fixing it? The TX stuff is still a bit of a mystery to me.
> > > Any
> > > > > help
> > > > > would be appreciated.
> > > > >
> > > > > Below is the log of the exception thrown.
> > > > >
> > > > > --jason
> > > > >
> > > > >
> > > > > 2001-08-14 15:59:52,726 org.jboss.ejb.plugins.LogInterceptor
> [Thread
> > > Pool
> > > > > Worker] ERROR - TRANSACTION ROLLBACK EXCEPTION: Application
> Error:
> > > tried
> > > > > to
> > > > > enter Stateful bean with different transaction context; nested
> > > exception
> > > > > is:
> > > > > java.rmi.RemoteException: Application Error: tried to
> enter
> > > > > Stateful
> > > > > bean with different transaction context
> > > > >
> > > > > ...
> > > > >
> > > > > 2001-08-14 15:59:52,842 org.jboss.ejb.plugins.LogInterceptor
> [Thread
> > > Pool
> > > > > Worker] ERROR - Detail
> > > > > java.rmi.RemoteException: Application Error: tried to enter
> Stateful
> > > bean
> > > > > with different transaction context
> > > > > at
> > > > >
>org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor.invoke(StatefulSessionInstanceInterceptor.java:207)
> > > > > at
> > > > >
>org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:97)
> > > > > at
> > > > >
>org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:154)
> > > > > at
> > > > > org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:63)
> > > > > at
> > > > > org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:168)
> > > > > at
> > > > >
>org.jboss.ejb.StatefulSessionContainer.invoke(StatefulSessionContainer.java:354)
> > > > > at
> > > > >
>org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPContainerInvoker.java:445)
> > > > > at
> > > > >
>org.jboss.ejb.plugins.jrmp.interfaces.GenericProxy.invokeContainer(GenericProxy.java:339)
> > > > > at
> > > > >
>org.jboss.ejb.plugins.jrmp.interfaces.StatefulSessionProxy.invoke(StatefulSessionProxy.java:136)
> > > > > at $Proxy28.handle(Unknown Source)
> > > > > at
> > > > >
>com.boldfish.does.job.service.internal.ResponseProcessorEJB.process(ResponseProcessorEJB.java:152)
> > > > > at
> > > > >
>com.boldfish.ejb.AbstractMessageDrivenBean.onMessage(AbstractMessageDrivenBean.java:132)
> > > > > at java.lang.reflect.Method.invoke(Native Method)
> > > > > at
> > > > >
>org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke(MessageDrivenContainer.java:410)
> > > > > at
> > > > >
>org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor.invoke(MessageDrivenInstanceInterceptor.java:79)
> > > > > at
> > > > >
>org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:97)
> > > > > at
> > > > >
>org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:154)
> > > > > at
> > > > > org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:63)
> > > > > at
> > > > >
>org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:128)
> > > > > at
> > > > > org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:168)
> > > > > at
> > > > > org.jboss.ejb.MessageDrivenContainer.invoke(MessageDrivenContainer.java:285)
> > > > > at
> > > > >
>org.jboss.ejb.plugins.jms.JMSContainerInvoker.invoke(JMSContainerInvoker.java:165)
> > > > > at
> > > > >
>org.jboss.ejb.plugins.jms.JMSContainerInvoker$MessageListenerImpl.onMessage(JMSContainerInvoker.java:644)
> > > > > at
> > > > >
>org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:290)
> > > > > at
> > > > > org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:257)
> > > > > at org.jboss.mq.SpySession.run(SpySession.java:176)
> > > > > at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:177)
> > > > > at
> > > > >
>EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:655)
> > > > > at java.lang.Thread.run(Thread.java:484)
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > 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
> > > >
> > >
> > >
> > > _______________________________________________
> > > 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
> >
>
>
> _______________________________________________
> 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
