Burkhard,
Well, I'll apolagise... you were right - thankyou (o: I was at home when
I sent this reply, and changing the datasourceclass does help. Am I
correct in thinking that the jboss pool isjust a wrapper for minerva? I
would like to ask what it does, but I'll read the code instead (o:
cheesr, and thanks again,
dim
On Wed, 18 Jul 2001, Dmitri Colebatch wrote:
> Burkhard,
>
> Thanks for the response - had already ticked that box though, assuming
> you're referring to the datasourceclass attribute. I did notice some more
> though - I've come to the conclusion the two are related. I haven't ever
> had an XAException and not seen a EOFException. I will say though, that
> I was being stupid and not closing my JMS connection from the client,
> which is I assume what most of the EOFs were coming from.
>
> However, when I have a client that does a simple test, I can run it ok
> once, twice, no problems. I put a loop in with a 2 second sleep and it
> went ok for 20 runs... I ran it again and then I get the exception. A
> collegue found some questions about JBossMQ not releasing its
> filedescriptors quickly enough - my understanding is that it using the
> db/jbossmq/[queue-name] for the queue's persistance. This then makes
> sense, when I rapid fire a lot of messages, I get the XAExceptions -
> unable to start transaction (I think - not at work atm), which makes
> sense, because it cant be sure of the file contents? Am I on the right
> track here or miles off?
>
> I suppose my closing question is how ready is JBossMQ? Should we be using
> openJMS?
>
> cheers, and thanks again.
> dim
>
> On Wed, 18 Jul 2001, Burkhard Vogel wrote:
>
> > Hi,
> > concering the XAExceptions: they will usually go away if you use
> > org.jboss.pool pooling implementation:
> > <mbean code="org.jboss.jdbc.XADataSourceLoader"
> > name="DefaultDomain:service=XADataSource,name=DefaultDS">
> > <attribute name="PoolName">DefaultDS</attribute>
> > <attribute
> > name="DataSourceClass">org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl</attr
> > ibute>
> > Burkhard
> >
> > ----- Original Message -----
> > From: "Dmitri Colebatch" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Wednesday, July 18, 2001 7:22 AM
> > Subject: [JBoss-user] EOFException using MDB with standalone JMS client and
> > XAException - XAER_NOTA
> >
> >
> > > Hi list,
> > >
> > > Using JBoss 2.4.0 on linux with postgres backend - I have a couple of
> > > questions:
> > >
> > > I'm trying to use MDBs to enable async operations between different
> > > EJBs. The situation I have atm is an entity, a session, a MDB and a stand
> > > alone client. In short, I get the following exception on the server:
> > >
> > > java.io.EOFException
> > > at java.io.ObjectInputStream.readByte(ObjectInputStream.java:1907)
> > > at
> > >
> > org.jbossmq.distributed.server.DistributedJMSServerOIL.run(DistributedJMSSer
> > verOIL.java:79)
> > > at java.lang.Thread.run(Thread.java:484)
> > >
> > > It doesn't seem to affect my test, but is quite disconcerting. Can anyone
> > > shed any light on this?
> > >
> > > My second question is about XAExceptions. I get a few of these, quite a
> > > few - they're all XAER_NOTA, and I was wondering if Postgres caused any
> > > dramas here. I'm getting this as part of the above situation on the
> > > second time I run the test, but it seems to work ok first time... I'm a
> > > bit vauge on it all, sorry - could someone point me in the right direction
> > > as far as analying XAExceptions goes...
> > >
> > > thanks in advance (o:
> > >
> > > cheers
> > > dim
> > >
> > >
> > > _______________________________________________
> > > JBoss-user mailing list
> > > [EMAIL PROTECTED]
> > > http://lists.sourceforge.net/lists/listinfo/jboss-user
> >
> >
> > _______________________________________________
> > JBoss-user mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-user
> >
>
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
