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

Reply via email to