File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
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
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Container managed transaction" Watch "Container managed transaction" New topic

Container managed transaction

harsha av

Joined: Sep 02, 2004
Posts: 17

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.

Osita Agbo

Joined: Mar 13, 2005
Posts: 6

Try this in your deployment descriptor:

Set the transaction attribute to Required.

I hope this will help.

[ 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.

I think, therefore I exist -- Rene Descartes
I agree. Here's the link:
subject: Container managed transaction
It's not a secret anymore!