wood burning stoves*
The moose likes EJB and other Java EE Technologies and the fly likes Container managed transaction Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Container managed transaction" Watch "Container managed transaction" New topic
Author

Container managed transaction

harsha av
Greenhorn

Joined: Sep 02, 2004
Posts: 17
Hi,

I am trying to call a bean (B2) in domain D2, from a bean B1, in Domain D1.
B2 accesses the database. When i try to use the container managed transaction , the records are inserted into the Database ( not comitted),
the transaction is timing out and the user id of D2 is getting locked.

The userId and password for D2 are correct as i am able to invoke B2 and also as said earlier the records are inserted (but not comitted).

Basically, the summay is that,
1) the transaction is rolling back,
2) The user id of domain D2 is getting locked (saying it has had 5 invalid attempts). I am not sure where this number 5 is popping up from.

Any help in this regard would be greatly appreciated.

Regards,
Harsha
Osita Agbo
Greenhorn

Joined: Mar 13, 2005
Posts: 6
Hi,

Try this in your deployment descriptor:

Set the transaction attribute to Required.
<trans-attribute>Required</trans-attribute>

I hope this will help.

-Osita.
[ March 13, 2005: Message edited by: Osita Agbo ]
Valentin Tanase
Ranch Hand

Joined: Feb 17, 2005
Posts: 704
Hi Harsha,

This looks to me like no easy puzzle to solve. By default containers don�t allow users from one domain to access resources to other domain, before authenticating to the second domain as well. However the administrator might set a trust relationship between the two domains and then the users don�t need to authenticate to both domains. Another common sign on solution is to use container specific techniques, like building Identity Assertion Providers, or configuring the container to use a signature proof, etc. You need to check with your administrator and understand the security architecture first. You need to understand where this 5 invalid login attempts is coming from; is it a container setting? Is a behavior introduced after deploying a specific component? You might provide more information later on, but again this could be more difficult than it looks at a glance.
Regards.


I think, therefore I exist -- Rene Descartes
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Container managed transaction
 
Similar Threads
Transaction handling in stateless session bean.
data visibility across weblogic pool connection and JDBC connection
Help - Data visibility in Weblogic and JDBC connection problem
Weblogic pool connection Vs JDBC Connection
Exception - com.ibm.ejs.cm.exception.Work Rolled back Exception