• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Jeanne Boyarsky
  • Tim Cooke
Sheriffs:
  • Bear Bibeault
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • salvin francis
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Frits Walraven
Bartenders:
  • Jj Roberts
  • Carey Brown
  • Scott Selikoff

Transaction question for attribute "Not Supported"

 
Nikhil Pendharkar
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi ,
I am having an entity bean method which has CMT attribute "NotSupported"
. Session bean wants to call that method via its business method .
Session bean's method has explicitly started the transaction using UserTransaction object .
When I run through this scenario , I see that the entity bean method is never getting called , I suppose because it has attribute "NotSupported" ,and after few mins I get an exception that transaction is timed out and rolledback .
Is this the correct behaviour of container when a call is made to the method having CMT attribute "NotSupported" ? And if this is correct one , how should I handle the rollback situation in session bean which is making the call to entity bean's method .
 
Janne Karhu
Ranch Hand
Posts: 33
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
No, the only thing the NotSupported does in your case is to suspend the transaction for the duration of the entity bean method call. So, the original transaction you started in your session bean continues normally after the entity bean method call has returned. The entity bean method in question runs without transaction.

Originally posted by Nikhil Pendharkar:
Hi ,
I am having an entity bean method which has CMT attribute "NotSupported"
. Session bean wants to call that method via its business method .
Session bean's method has explicitly started the transaction using UserTransaction object .
When I run through this scenario , I see that the entity bean method is never getting called , I suppose because it has attribute "NotSupported" ,and after few mins I get an exception that transaction is timed out and rolledback .
Is this the correct behaviour of container when a call is made to the method having CMT attribute "NotSupported" ? And if this is correct one , how should I handle the rollback situation in session bean which is making the call to entity bean's method .

 
What's that smell? Hey, sniff this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic