|
Problem(Abstract) |
What are the default settings for Local Transaction 2.0 in
WebSphere® Application Server V5 for Resolution Control, Boundary,
Resolver, and Unresolved Action. |
|
|
|
Resolving the
problem |
- Resolution control default setting is "Application"
For more information, see the article in the information center
titled Using
Local Transactions.
- Boundary default setting is "BeanMethod"
This setting (which at WebSphere Application Server Version 5 is relevant
only if you deploy to Enterprise Edition or WebSphere Business Integration
Server Foundation) specifies the containment boundary at which all
contained resource manager local transactions (RMLTs) must be completed.
- BeanMethod:
RMLTs must be resolved within the same bean method in which they were
started.
- ActivitySession (For EJB™ components only):
RMLTs must be resolved within the scope of any ActivitySession in which
they were started or, if no ActivitySession context is present, within the
same bean method in which they were started.
- Resolver default setting is "Application"
This setting (which at WebSphere Version 5 is relevant only if you deploy
to WebSphere Enterprise Edition or WebSphere Business Integration Server
Foundation) specifies the component responsible for initiating and ending
resource manager local transactions (RMLTs).
- Application:
The application is responsible for both starting RMLTs and for completing
them within the local transaction containment (LTC) boundary. Any RMLTs
that are not completed by the end of the LTC boundary are cleaned up by
the container according to the value of the Unresolved action attribute.
- ContainerAtBoundary (For EJB components only):
The container is responsible for both starting RMLTs and for completing
them within the LTC boundary. The container begins an RMLT when a
connection is first used within the LTC scope and completes it
automatically at the end of the LTC scope.
If Boundary is set to ActivitySession, then the RMLTs are enlisted as
ActivitySession resources and directed to complete by the activitySession.
If Boundary is set to BeanMethod, then the RMLTs are committed at method
end by the container.
- Unresolved-action default setting is "Rollback"
The direction that the container requests RMLTs to take if they are
unresolved at the end of the LTC boundary scope and the Resolver is set to
Application.
- Rollback:
At end of the LTC boundary scope, the container instructs all unresolved
RMLTs to roll back.
- Commit:
At end of the LTC boundary scope, the container instructs all unresolved
RMLTs to commit.
Note: To change these settings, you must do so in the deployment
descriptor. |
|
|
|