Win a copy of Programmer's Guide to Java SE 8 Oracle Certified Associate (OCA) this week in the OCAJP forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

402 STATUS_NO_TRANSACTION Problem

 
graham king
Ranch Hand
Posts: 133
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a project deployed on JBOSS which makes use of EJB's.

Just today a user informed me of a problem during an update:


It's strange because the method is also called during an Insert and they don't seem to fail. I've checked the ejb.xml file and the methods trans-attribute's are set to the RequiresNew, just switched one to Required with no affect.

How is it possible that the call would fail due to no transaction? Am I doing something/everything wrong?

Also wondering if the calls to multiple methods might be the fault? The sesion bean handles the initial request and passes it off to another method which then invokes a call on a different bean. Do all these methods have to have the trans attibute set? The main session bean has * - Supports, so I thought that the rest would fall into place when using Required or RequiresNew.

That's what I get for thinking!

thanks for any HELP!
[ July 27, 2006: Message edited by: graham king ]
 
graham king
Ranch Hand
Posts: 133
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
A JBoss staging environment is also setup. One that runs on a separate machine and points to test data. The EJB submits the insert fine!!!

We are running against SQL Server 7.0...

Any Thoughts?
 
graham king
Ranch Hand
Posts: 133
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hate to beat this one down, but, i'm just looking for ideas for what might be causing this one? especially the NO_TRANSACTION?

i took another look at the code and found within the suspect DAO a check on the return value:


removing the check allows for an update. what do you thing the cause is for the STATUS_NO_TRANSACTION? if the jdbc driver doesn't support the method call then shouldn't it just fail gracefully?

is this a known problem with microsoft's jdbc driver or just a known problem with microsoft?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic