quick suggestion that may be way off the mark but such behavior would occur as
a result of ejb instances not having their member values re-initialised when
retrieved from the instance pool.
eg>
1. retrieve instance of company bean from pool and populate with company A data.
2. passivate and
I am using JBOSS v3.2.4, Hibernate 2.1.3 and Oracle9i and when my databse query
returns an 'ORA-24777: use of non-migratable database link not allowed'.
Basically we have a postcode table that has been set up as a DBLink table to point to
a central database. When we try and execute a query agai
I'm trying to configure an Oracle XA Data source and I get the error
errorCode=XAER_NOTA when my session bean tries to persist to the Oracle database.
I have attached a section of the log. Has anyone seen this before?
18:45:13,603 WARN [TransactionImpl] XAException: tx=TransactionImpl:XidImpl
Help -
I have an ejb session bean (A), with a transaction attribute set to required. This
invokes ejb session bean (B) which also has a transaction attribute set to required.
Session bean (B) persists data to the database via Hibernate v2.1.3. Session bean (A)
then persist data to the database