Hi,
dferugson wrote:
> Does this exception mean anything to anybody out there?
Yep. Thrown by XA resources as specified by JTA.
> I have been debuggint this for a while and I can't seem to track it down
> to any specific piece of code. Rather than including my entire bean, I
> will see if this is enough to go on. If nobody has any ideas I will post
> the code for my bean.
In this case, it looks to me like Minerva throws
this exception due to the following conditions:
- It does not currently participate in a transaction.
- It used to.
Could it be that the database connection was used in
a transaction that was suspended, and then then an
attempt to resume (same or other) transaction was done?
I dont think that Minerva likes that, though it really
should, according to JTA.
Do you use Bean Managed Transactions?
Any other exceptions before this one?
Best Regards,
Ole Husgaard.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
