Re: [JBoss-user] Transaction Exceptions with OPTA2000

2001-05-17 Thread Rafael Alves Chaves 


Hi, all...

On Thu, 17 May 2001, Leonard Kierstead wrote:

> 
> 
> |The workaround I found was to ignore i-net data sources and use
> |OPTA 2000 as a JDBC 2.0 Optional Package non-compliant driver:
> 
> I'm not exactly sure what you mean by this.  I'm guessing that by changing :
>com.inet.tds.XDataSource
> to
> name="DataSourceClass">org.opentools.minerva.jdbc.xa.wrapper.XADataSourceImp
> l
> 
> I'm guessing that tells JBoss/JAWS that my driver doesn't support JDBC 2.0
> Optional Packages?  When you 
> do this what JDBC driver is used.

The URL attribute will tell what driver to use. For example, for i-net
for SQLServer 7/2000:


...
jdbc:inetdae7:127.0.0.1?database=sqlDB
...


Below follows the whole  tag:

  
sqlPool
org.opentools.minerva.jdbc.xa.wrapper.XADataSourceImpl

120
jdbc:inetdae7:127.0.0.1?database=sqlDB
myUser
10
myPassword
false
false
false
true
12
180
false
true
1.0
0
  


Hope this helps,

Rafael


___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user

Re: [JBoss-user] Transaction Exceptions with OPTA2000

2001-05-17 Thread Leonard Kierstead 



|The workaround I found was to ignore i-net data sources and use
|OPTA 2000 as a JDBC 2.0 Optional Package non-compliant driver:

I'm not exactly sure what you mean by this.  I'm guessing that by changing :
   com.inet.tds.XDataSource
to
   org.opentools.minerva.jdbc.xa.wrapper.XADataSourceImp
l

I'm guessing that tells JBoss/JAWS that my driver doesn't support JDBC 2.0
Optional Packages?  When you 
do this what JDBC driver is used.

I started with loadign the INet OPTA 2000 driver:

  
 com.inet.tds.TdsDriver

and Connection Pool:

  
   Amstel1DB
   com.inet.tds.XDataSource
   host=localhost;
database=Amstel1DB
   sa
   sa
  ...
  
 I tried changing the DataSourceClass to:

   org.opentools.minerva.jdbc.xa.wrapper.XADataSourceImp
l
   
I then got an error indicating a URL must be specified, so I added:

   jdbc:sqlserver://localhost:1433
   
I then got an error indicating No suitalbe driver. 

I then had to add the Merant driver back in:

  
 com.merant.datadirect.jdbc.sqlserver.SQLServerDriver
  

I then was back to the original error:

 Exists command executing: SELECT COUNT(*) FROM UnitInfo WHERE id=?
[JAWS] Set parameter: idx=1, jdbcType=INTEGER, value=1001
[JAWS] Create command executing: INSERT INTO UnitInfo
(address,groupname,displayname,unitname,propstring,district,id) VALUES
(?,?,?,?,?,?,?)
[JAWS] java.sql.SQLException: Unable to create PreparedStatement!
[JAWS]  at
org.opentools.minerva.jdbc.xa.wrapper.XAClientConnection.prepareStatement(XA
ClientConnection.java:169)
[JAWS]  at
org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand.jdbcExecute(JDBCCommand.java:158
)
[JAWS]  at
org.jboss.ejb.plugins.jaws.jdbc.JDBCCreateEntityCommand.execute(JDBCCreateEn
tityCommand.java:135)
[JAWS]  at
org.jboss.ejb.plugins.jaws.JAWSPersistenceManager.createEntity(JAWSPersisten
ceManager.java:122)
[JAWS]  at
org.jboss.ejb.plugins.CMPPersistenceManager.createEntity(CMPPersistenceManag
er.java:207)
[JAWS]  at
org.jboss.ejb.EntityContainer.createHome(EntityContainer.java:441)
[JAWS]  at java.lang.reflect.Method.invoke(Native Method)
[JAWS]  at
org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityContaine
r.java:639)
[JAWS]  at
org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntitySync
hronizationInterceptor.java:160)
[JAWS]  at
org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(EntityInstanceInt
erceptor.java:87)
[JAWS]  at
org.jboss.ejb.plugins.TxInterceptorCMT.invokeNext(TxInterceptorCMT.java:135)
[JAWS]  at
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.
java:263)
[JAWS]  at
org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:86)
[JAWS]  at
org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.jav
a:164)
[JAWS]  at
org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:106)
[JAWS]  at
org.jboss.ejb.EntityContainer.invokeHome(EntityContainer.java:316)
[JAWS]  at
org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invokeHome(JRMPContai
nerInvoker.java:436)
[JAWS]  at
org.jboss.ejb.plugins.jrmp.interfaces.HomeProxy.invoke(HomeProxy.java:212)
[JAWS]  at $Proxy10.create(Unknown Source)

|
|
|  oto25

What is oto25 for?

|  org.opentools.minerva.jdbc.xa.wrapper.XADataSourceIm
pl

What JDBC drvier is used when this class is specifed as the data source?

|  ...  
|
|From the Minerva docs:
|
|"You must determine whether your driver supports the JDBC 2.0 Optional
|Package in order to configure JBoss appropriately. 

How?  

|If it does not, JBoss
|will simulate it so that your EJBs will operate appropriately, but there
|are two important restrictions: 
|
|If you request more than one connection from a DataSource in the context
|of the same transaction, JBoss will return the same connection every time.
|This is so changes made by one bean will be visible to other beans
|operating in the same transaction.
|
|The connections cannot determine ahead of time whether it is possible for
|them to commit, so they cannot participate fully in the two-phase commit
|protocol used to commit multiple data sources. This means that if there's
|a problem with one of the data sources, some may commit and others may
|rollback. This is why we want all DB vendors to fully support the JDBC 2.0
|Optional Package"
|
|Are these restrictions too strong for you?
|
|Rafael


___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user

Re: [JBoss-user] Transaction Exceptions with OPTA2000

2001-05-16 Thread Leonard Kierstead 


I've now got a very simple example that shows the Transaction Exception when
trying to use SQLServer.  I deployed the Cabin example from chapter four in
the book:

Enterprise JavaBeans
Richard Monson-Haefel
O'reilly

I've attached the ear file, the code, the log, and the jboss.jcml file.  

Run the client and you get the error shown in the log.

Thanks for any help,

Leonard

>Hi, I'm trying to use the i-net OPTA 2000 4.0 for MS-SQL Server 2000
evaluation version (limited on two concurrent connections) with JBoss,
without success. Every time my BMP beans try to close the database
connection, the following exception occurs:
javax.transaction.xa.XAException: The XID is not valid. Can anyone explain
what I'm doing wrong? Thanks, Rafael 

 <>  <>  <>  <> 

 cabin.ear
 jboss.jcml
 cabin code.zip
 server.log

Re: [JBoss-user] Transaction Exceptions with OPTA2000

2001-05-14 Thread Rafael Alves Chaves 


The workaround I found was to ignore i-net data sources and use
OPTA 2000 as a JDBC 2.0 Optional Package non-compliant driver:


  oto25
  org.opentools.minerva.jdbc.xa.wrapper.XADataSourceImpl
  ...  

From the Minerva docs:

"You must determine whether your driver supports the JDBC 2.0 Optional
Package in order to configure JBoss appropriately. If it does not, JBoss
will simulate it so that your EJBs will operate appropriately, but there
are two important restrictions: 

If you request more than one connection from a DataSource in the context
of the same transaction, JBoss will return the same connection every time.
This is so changes made by one bean will be visible to other beans
operating in the same transaction.

The connections cannot determine ahead of time whether it is possible for
them to commit, so they cannot participate fully in the two-phase commit
protocol used to commit multiple data sources. This means that if there's
a problem with one of the data sources, some may commit and others may
rollback. This is why we want all DB vendors to fully support the JDBC 2.0
Optional Package"

Are these restrictions too strong for you?

Rafael


On Fri, 11 May 2001, Leonard Kierstead wrote:

> 
> 
> I too am getting the Transaction Exceptions described in note:
> 
> Re: [JBoss-user] Transaction Exceptions with OPTA2000
> http://www.mail-archive.com/jboss-user%40lists.sourceforge.net/msg03820.html
> 
> I've also tried the Merant driver and get an exception in the
> same place.  The Merant exception is: Unable to create PreparedStatement.
> 
> I've switched to InstandDB and everything works fine.
> 
> I've included the exceptions from both the Merant and INet drivers, on
> both a create and a find.
> 
> I assume others are using JBoss with SQLServer?  Any suggestions on how
> I can resolve this?
> 
> Thanks,
> 
> Leonard Kierstead
> 
> 
> Using the Merant Driver (create unitinfo):
> 
> [JAWS] Create, id is com.cerulean.amstel1.UnitInfoPK@3e9
> [Amstel1DB] Resource
> 'org.opentools.minerva.jdbc.xa.wrapper.XAResourceImpl@6d1dbe' enlisted for
> 'org.opentools.minerva.jdbc.xa.wrapper.XAConnectionImpl@ab323'.
> [Amstel1DB] Pool Amstel1DB [1/1/10] gave out pooled object:
> org.opentools.minerva.jdbc.xa.wrapper.XAConnectionImpl@ab323
> [JAWS] Exists command executing: SELECT COUNT(*) FROM UnitInfo WHERE id=?
> [JAWS] Set parameter: idx=1, jdbcType=INTEGER, value=1001
> [JAWS] Create command executing: INSERT INTO UnitInfo
> (address,groupname,displayname,unitname,propstring,district,id) VALUES
> (?,?,?,?,?,?,?)
> [JAWS] java.sql.SQLException: Unable to create PreparedStatement!
> [JAWS]  at
> org.opentools.minerva.jdbc.xa.wrapper.XAClientConnection.prepareStatement(XA
> ClientConnection.java:169)
> [JAWS]  at
> org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand.jdbcExecute(JDBCCommand.java:158
> )
> [JAWS]  at
> org.jboss.ejb.plugins.jaws.jdbc.JDBCCreateEntityCommand.execute(JDBCCreateEn
> tityCommand.java:135)
> [JAWS]  at
> org.jboss.ejb.plugins.jaws.JAWSPersistenceManager.createEntity(JAWSPersisten
> ceManager.java:122)
> ...
> 
> Using the IDC driver (create unitinfo):
> 
> [JAWS] Create, id is com.cerulean.amstel1.UnitInfoPK@3e9
> [Amstel1DB] Resource 'com.inet.tds.k@6e7a14' enlisted for
> 'com.inet.tds.k@6e7a14'.
> [Amstel1DB] Pool Amstel1DB [1/1/10] gave out pooled object:
> com.inet.tds.k@6e7a14
> [Amstel1DB] [TDS Driver]XA_CONNECTION_GET
> [Amstel1DB] SQL Server 7 unicode mode
> [Amstel1DB] This test License expires on 31-May-2001. You can purchase the
> driver at www.inetsoftware.de
> [Amstel1DB] Driver: i-net OPTA 2000 4.00
> [JAWS] Exists command executing: SELECT COUNT(*) FROM UnitInfo WHERE id=?
> [JAWS] Set parameter: idx=1, jdbcType=INTEGER, value=1001
> [Amstel1DB] setObject:1,java.lang.Integer,4
> [Amstel1DB] Statement.close
> [Amstel1DB] SELECT COUNT(*) FROM UnitInfo WHERE id=?
> [Amstel1DB] Statement.close
> [Amstel1DB] [TDS Driver]XA_CONNECTION_FREE
> [Amstel1DB] javax.transaction.xa.XAException: The XID is not valid.
> [UnitInfo] XAException: tx=XidImpl [FormatId=257, GlobalId=Timmy2//0,
> BranchQual=] errorCode=XAER_NOTA
> [UnitInfo] javax.transaction.xa.XAException: The XID is not valid.
> [UnitInfo]  at com.inet.tds.k.if(Unknown Source)
> [UnitInfo]  at com.inet.tds.k.for(Unknown Source)
> [UnitInfo]  at com.inet.tds.k.end(Unknown Source)
> [UnitInfo]  at org.jboss.tm.TxCapsule.endResource(TxCapsule.java:1147)
> [UnitInfo]  at org.jboss.tm.TxCapsule.delistResource(TxCapsule.java:541)
> [UnitInfo]  at
> org.jboss.tm.TransactionImpl.delistResource(TransactionImpl.java:99)
> [UnitInfo]  at
> org.opentools.minerva.jdbc.xa

Re: [JBoss-user] Transaction Exceptions with OPTA2000

2001-05-11 Thread Leonard Kierstead 



I too am getting the Transaction Exceptions described in note:

Re: [JBoss-user] Transaction Exceptions with OPTA2000
http://www.mail-archive.com/jboss-user%40lists.sourceforge.net/msg03820.html

I've also tried the Merant driver and get an exception in the
same place.  The Merant exception is: Unable to create PreparedStatement.

I've switched to InstandDB and everything works fine.

I've included the exceptions from both the Merant and INet drivers, on
both a create and a find.

I assume others are using JBoss with SQLServer?  Any suggestions on how
I can resolve this?

Thanks,

Leonard Kierstead


Using the Merant Driver (create unitinfo):

[JAWS] Create, id is com.cerulean.amstel1.UnitInfoPK@3e9
[Amstel1DB] Resource
'org.opentools.minerva.jdbc.xa.wrapper.XAResourceImpl@6d1dbe' enlisted for
'org.opentools.minerva.jdbc.xa.wrapper.XAConnectionImpl@ab323'.
[Amstel1DB] Pool Amstel1DB [1/1/10] gave out pooled object:
org.opentools.minerva.jdbc.xa.wrapper.XAConnectionImpl@ab323
[JAWS] Exists command executing: SELECT COUNT(*) FROM UnitInfo WHERE id=?
[JAWS] Set parameter: idx=1, jdbcType=INTEGER, value=1001
[JAWS] Create command executing: INSERT INTO UnitInfo
(address,groupname,displayname,unitname,propstring,district,id) VALUES
(?,?,?,?,?,?,?)
[JAWS] java.sql.SQLException: Unable to create PreparedStatement!
[JAWS]  at
org.opentools.minerva.jdbc.xa.wrapper.XAClientConnection.prepareStatement(XA
ClientConnection.java:169)
[JAWS]  at
org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand.jdbcExecute(JDBCCommand.java:158
)
[JAWS]  at
org.jboss.ejb.plugins.jaws.jdbc.JDBCCreateEntityCommand.execute(JDBCCreateEn
tityCommand.java:135)
[JAWS]  at
org.jboss.ejb.plugins.jaws.JAWSPersistenceManager.createEntity(JAWSPersisten
ceManager.java:122)
...

Using the IDC driver (create unitinfo):

[JAWS] Create, id is com.cerulean.amstel1.UnitInfoPK@3e9
[Amstel1DB] Resource 'com.inet.tds.k@6e7a14' enlisted for
'com.inet.tds.k@6e7a14'.
[Amstel1DB] Pool Amstel1DB [1/1/10] gave out pooled object:
com.inet.tds.k@6e7a14
[Amstel1DB] [TDS Driver]XA_CONNECTION_GET
[Amstel1DB] SQL Server 7 unicode mode
[Amstel1DB] This test License expires on 31-May-2001. You can purchase the
driver at www.inetsoftware.de
[Amstel1DB] Driver: i-net OPTA 2000 4.00
[JAWS] Exists command executing: SELECT COUNT(*) FROM UnitInfo WHERE id=?
[JAWS] Set parameter: idx=1, jdbcType=INTEGER, value=1001
[Amstel1DB] setObject:1,java.lang.Integer,4
[Amstel1DB] Statement.close
[Amstel1DB] SELECT COUNT(*) FROM UnitInfo WHERE id=?
[Amstel1DB] Statement.close
[Amstel1DB] [TDS Driver]XA_CONNECTION_FREE
[Amstel1DB] javax.transaction.xa.XAException: The XID is not valid.
[UnitInfo] XAException: tx=XidImpl [FormatId=257, GlobalId=Timmy2//0,
BranchQual=] errorCode=XAER_NOTA
[UnitInfo] javax.transaction.xa.XAException: The XID is not valid.
[UnitInfo]  at com.inet.tds.k.if(Unknown Source)
[UnitInfo]  at com.inet.tds.k.for(Unknown Source)
[UnitInfo]  at com.inet.tds.k.end(Unknown Source)
[UnitInfo]  at org.jboss.tm.TxCapsule.endResource(TxCapsule.java:1147)
[UnitInfo]  at org.jboss.tm.TxCapsule.delistResource(TxCapsule.java:541)
[UnitInfo]  at
org.jboss.tm.TransactionImpl.delistResource(TransactionImpl.java:99)
[UnitInfo]  at
org.opentools.minerva.jdbc.xa.XAConnectionFactory$2.closeConnection(XAConnec
tionFactory.java:97)
[UnitInfo]  at
org.opentools.minerva.jdbc.xa.XAConnectionFactory$2.connectionClosed(XAConne
ctionFactory.java:82)
[UnitInfo]  at com.inet.pool.c.a(Unknown Source)
...

Using the Merant driver (find unitinfo):

[Amstel1DB] Resource
'org.opentools.minerva.jdbc.xa.wrapper.XAResourceImpl@45fe3b' enlisted for
'org.opentools.minerva.jdbc.xa.wrapper.XAConnectionImpl@ab323'.
[Amstel1DB] Pool Amstel1DB [1/1/10] gave out pooled object:
org.opentools.minerva.jdbc.xa.wrapper.XAConnectionImpl@ab323
[JAWS] findAllUnits command executing: SELECT id FROM UnitInfo
[Amstel1DB] Pool Amstel1DB [0/1/10] returned object
org.opentools.minerva.jdbc.xa.wrapper.XAConnectionImpl@ab323 to the pool.
[UnitInfo] Activated bean UnitInfo with id =
com.cerulean.amstel1.UnitInfoPK@64
[Amstel1DB] Resource
'org.opentools.minerva.jdbc.xa.wrapper.XAResourceImpl@45fe3b' enlisted for
'org.opentools.minerva.jdbc.xa.wrapper.XAConnectionImpl@ab323'.
[Amstel1DB] Pool Amstel1DB [1/1/10] gave out pooled object:
org.opentools.minerva.jdbc.xa.wrapper.XAConnectionImpl@ab323
[JAWS] Load command executing: SELECT
address,groupname,displayname,unitname,propstring,district,id FROM UnitInfo
WHERE id=?
[JAWS] java.sql.SQLException: Unable to create PreparedStatement!
[JAWS]  at
org.opentools.minerva.jdbc.xa.wrapper.XAClientConnection.prepareStatement(XA
ClientConnection.java:169)
[JAWS]  at
org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand.jdbcExecute(JDBCCommand.java:158
)
[JAWS]  at
org.jboss.ejb.plugins.jaws.jdbc.JDBCLoadEntityCommand.execute(JDBCLoadEntity
Command.java:82)
[JAWS]  at
org.jboss.

Re: [JBoss-user] Transaction Exceptions with OPTA2000

2001-05-08 Thread Toby Allsopp 

On Tue, May 08, 2001 at 05:24:07PM -0300, Rafael Chaves wrote:
> >Can you include the complete stacktrace please?  
> 
> Of course, it's attached (trace.txt file). My bean class is the one which 
> name starts with br.com
> 
> For each close () call, two exceptions are generated (the second is from 
> rollback, right?)
> 
> I also have attached my jboss.jcml and ejb-jar.xml files.

Thanks.  To be honest, I'm a little out of my depth on this.
Hopefully Ole will respond.  You might like to try turning on tracing
in TxCapsule (it's a boolean field), recompiling and trying your test
again.  This should show what Xids are being used for enlistment.

> >Do you have the
> >jboss.xa.xidclass property set in jboss.properties (or elsewhere)?
>  
> No. Should I?

I'm not sure.  Probably not, but it is necessary for some Oracle
drivers I think.

Ole?

Toby.

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user

Re: [JBoss-user] Transaction Exceptions with OPTA2000

2001-05-08 Thread Rafael Chaves 

>Can you include the complete stacktrace please?  

Of course, it's attached (trace.txt file). My bean class is the one which 
name starts with br.com

For each close () call, two exceptions are generated (the second is from 
rollback, right?)

I also have attached my jboss.jcml and ejb-jar.xml files.

>Do you have the
>jboss.xa.xidclass property set in jboss.properties (or elsewhere)?
 
No. Should I?

Thanks

   Rafael



[TipoObjetoSistema] XAException: tx=XidImpl [FormatId=257, GlobalId=fabrica05//0, BranchQual=] errorCode=XAER_NOTA
[TipoObjetoSistema] javax.transaction.xa.XAException: The XID is not valid.
[TipoObjetoSistema] at com.inet.tds.k.if(Unknown Source)
[TipoObjetoSistema] at com.inet.tds.k.for(Unknown Source)
[TipoObjetoSistema] at com.inet.tds.k.end(Unknown Source)
[TipoObjetoSistema] at org.jboss.tm.TxCapsule.endResource(TxCapsule.java:1147)
[TipoObjetoSistema] at org.jboss.tm.TxCapsule.delistResource(TxCapsule.java:541)
[TipoObjetoSistema] at org.jboss.tm.TransactionImpl.delistResource(TransactionImpl.java:99)
[TipoObjetoSistema] at org.opentools.minerva.jdbc.xa.XAConnectionFactory$2.closeConnection(XAConnectionFactory.java:97)
[TipoObjetoSistema] at org.opentools.minerva.jdbc.xa.XAConnectionFactory$2.connectionClosed(XAConnectionFactory.java:82)
[TipoObjetoSistema] at com.inet.pool.c.a(Unknown Source)
[TipoObjetoSistema] at com.inet.tds.k.a(Unknown Source)
[TipoObjetoSistema] at com.inet.pool.a.close(Unknown Source)
[TipoObjetoSistema] at br.com.perfiltecnologia.infraestrutura.gerenciamentodocumento.tipoobjetosistema.TipoObjetoSistemaBean.ejbCreate(TipoObjetoSistemaBean.java:40)
[TipoObjetoSistema] at java.lang.reflect.Method.invoke(Native Method)
[TipoObjetoSistema] at org.jboss.ejb.plugins.BMPPersistenceManager.createEntity(BMPPersistenceManager.java:121)
[TipoObjetoSistema] at org.jboss.ejb.EntityContainer.createHome(EntityContainer.java:441)
[TipoObjetoSistema] at java.lang.reflect.Method.invoke(Native Method)
[TipoObjetoSistema] at org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityContainer.java:639)
[TipoObjetoSistema] at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntitySynchronizationInterceptor.java:160)
[TipoObjetoSistema] at org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(EntityInstanceInterceptor.java:87)
[TipoObjetoSistema] at org.jboss.ejb.plugins.TxInterceptorCMT.invokeNext(TxInterceptorCMT.java:135)
[TipoObjetoSistema] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:263)[TipoObjetoSistema] at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:86)
[TipoObjetoSistema] at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:164)
[TipoObjetoSistema] at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:106)
[TipoObjetoSistema] at org.jboss.ejb.EntityContainer.invokeHome(EntityContainer.java:316)
[TipoObjetoSistema] at org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invokeHome(JRMPContainerInvoker.java:369)
[TipoObjetoSistema] at java.lang.reflect.Method.invoke(Native Method)
[TipoObjetoSistema] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:241)
[TipoObjetoSistema] at sun.rmi.transport.Transport$1.run(Transport.java:142)
[TipoObjetoSistema] at java.security.AccessController.doPrivileged(Native Method)
[TipoObjetoSistema] at sun.rmi.transport.Transport.serviceCall(Transport.java:139)
[TipoObjetoSistema] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:443)
[TipoObjetoSistema] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:643)
[TipoObjetoSistema] at java.lang.Thread.run(Thread.java:484)
[TipoObjetoSistema] XAException: tx=XidImpl [FormatId=257, GlobalId=fabrica05//0, BranchQual=] errorCode=XAER_NOTA
[TipoObjetoSistema] javax.transaction.xa.XAException: The XID is not valid.
[TipoObjetoSistema] at com.inet.tds.k.if(Unknown Source)
[TipoObjetoSistema] at com.inet.tds.k.for(Unknown Source)
[TipoObjetoSistema] at com.inet.tds.k.rollback(Unknown Source)
[TipoObjetoSistema] at org.jboss.tm.TxCapsule.rollbackResources(TxCapsule.java:1557)
[TipoObjetoSistema] at org.jboss.tm.TxCapsule.rollback(TxCapsule.java:412)
[TipoObjetoSistema] at org.jboss.tm.TransactionImpl.rollback(TransactionImpl.java:88)
[TipoObjetoSistema] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:307)[TipoObjetoSistema] at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:86)
[TipoObjetoSistema] at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:164)
[TipoObjetoSistema] at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:106)
[TipoObjetoSistema] at org.jboss.ejb.EntityContainer.invokeHome(EntityContainer.ja

Re: [JBoss-user] Transaction Exceptions with OPTA2000

2001-05-08 Thread Toby Allsopp 

On Tue, May 08, 2001 at 10:52:27AM -0300, Rafael Alves Chaves wrote:
> 
> Hi,
> 
> I'm trying to use the i-net OPTA 2000 4.0 for MS-SQL Server 2000
> evaluation version (limited on two concurrent connections) with JBoss,
> without success.
> 
> Every time my BMP beans try to close the database connection, the
> following exception occurs:
>  
> javax.transaction.xa.XAException: The XID is not valid.
> 
> Can anyone explain what I'm doing wrong?

Can you include the complete stacktrace please?  Do you have the
jboss.xa.xidclass property set in jboss.properties (or elsewhere)?

Toby.

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user

[JBoss-user] Transaction Exceptions with OPTA2000

2001-05-08 Thread Rafael Alves Chaves 


Hi,

I'm trying to use the i-net OPTA 2000 4.0 for MS-SQL Server 2000
evaluation version (limited on two concurrent connections) with JBoss,
without success.

Every time my BMP beans try to close the database connection, the
following exception occurs:
 
javax.transaction.xa.XAException: The XID is not valid.

Can anyone explain what I'm doing wrong?

Thanks,

Rafael



___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user