David Jencks schrieb:
On 2003.06.04 18:23 Marek Lange wrote:
David Jencks schrieb:
I don't know what the Oracle error means, but you do not need an xa
datasource for jbossmq xa. In fact the jbossmq xa jdbc connections are
set
to autocommit while in use by jbossmq, as it handles transactions
ind
On 2003.06.04 18:23 Marek Lange wrote:
> David Jencks schrieb:
> > I don't know what the Oracle error means, but you do not need an xa
> > datasource for jbossmq xa. In fact the jbossmq xa jdbc connections are
> set
> > to autocommit while in use by jbossmq, as it handles transactions
> > independ
David Jencks schrieb:
I don't know what the Oracle error means, but you do not need an xa
datasource for jbossmq xa. In fact the jbossmq xa jdbc connections are set
to autocommit while in use by jbossmq, as it handles transactions
independently of the database.
David,
thanks for the information!
I don't know what the Oracle error means, but you do not need an xa
datasource for jbossmq xa. In fact the jbossmq xa jdbc connections are set
to autocommit while in use by jbossmq, as it handles transactions
independently of the database.
david jencks
On 2003.06.04 09:18 Marek Lange wrote:
> Hi
<[EMAIL PROTECTED]>
Kopie:
Thema: [JBoss-user] JMS and Oracle XA
Hi,
following problem: we use a XA data source with Oracle 8.1.7. The data
source deploys correctly. When the application tries to write into the
database, we get the following er
Hi,
following problem: we use a XA data source with Oracle 8.1.7. The data
source deploys correctly. When the application tries to write into the
database, we get the following error:
PLS-00201: identifier 'JAVA_XA.XA_START_NEW' must be declared
The error comes from a stored procedure. Does this
