wood burning stoves*
The moose likes EJB and other Java EE Technologies and the fly likes Client's Transaction Aborted Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Client Watch "Client New topic
Author

Client's Transaction Aborted

Justin Phillips
Greenhorn

Joined: Nov 09, 2012
Posts: 2
Hey guys and gals

I'm having a lot of trouble diagnosing what is wrong with my application / environment.

I'm running a RESTful Jersey app with ejb 3.1 beans on a Glassfish 3.1.2 server.

I have two databases that I use in the app. Both of the connection pools in Glassfish ping successfully.

I keep getting this error -



I am unable to reproduce it with any consistency. It always comes from different beans as well (so the last line of the stack trace will change but it always ends up going to BaseContainer.useClientTx.

I also see a bunch of these




I've googled like crazy to no avail. Mostly, it seems I need to dig into the real root cause and fix that.

I'm admittedly not an EJB, Glassfish, or Java expert. Does anyone have any advice for debugging this?

Thanks so much in advance.
Justin Phillips
Greenhorn

Joined: Nov 09, 2012
Posts: 2
As I'm working through this I started wondering about how glassfish's EJB container handles what I've written. I have beans that talk to two databases in separate methods. Should a bean only ever talk to one database? Should i separate out the beans so that they only ever talk to one database? Could the bean caching be causing my weird errors?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Client's Transaction Aborted
 
Similar Threads
EJB5017: Exception while running preinvoke
EJB local injection and transactions
Servlets3.0 & EJB3.1
Double insertion using entity lifecycle listener
MySql - XA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detected