Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Client's Transaction Aborted

 
Justin Phillips
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic