[
https://issues.jboss.org/browse/JBTM-1104?page=com.atlassian.jira.plugin....
]
Paul Robinson updated JBTM-1104:
--------------------------------
Summary: XTS support for load-balanced scenarios (was: Does XTS support
load-balanced scenarios?)
Original Estimate: (was: 1 day)
Remaining Estimate: (was: 1 day)
Issue Type: Enhancement (was: Task)
Fix Version/s: 6.0.0.Final
(was: 5.0.0.Final)
Description:
Enabling session affinity on the load balancer should ensure that all requests for a
particular application endpoint, within a particular session, go to the same instance of
the web service.
However, XTS advertises a number of endpoint addresses that will not make sense in a load
balanced cluster. This is because it would be the internal endpoint address of the
particular server that is advertised, rather than the load balancer's external
address.
Even if we configured XTS (not yet possible) to offer the address of the LB, we would
still have a problem as XTS will use a different session to the application to send
protocol messages and thus they will go to a different server that is not aware of this
transaction.
was:Enabling session affinity on the load balancer should ensure that all requests for a
particular endpoint, within a particular esion, go to the same instance of the web service
and thus use the same subordinate coordinator. However, will protocol messages be
guaranteed to go to the same coordinator? I would assume not as they are using a different
session.
Component/s: XTS
(was: TXFramework)
XTS support for load-balanced scenarios
---------------------------------------
Key: JBTM-1104
URL:
https://issues.jboss.org/browse/JBTM-1104
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: XTS
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 6.0.0.Final
Enabling session affinity on the load balancer should ensure that all requests for a
particular application endpoint, within a particular session, go to the same instance of
the web service.
However, XTS advertises a number of endpoint addresses that will not make sense in a load
balanced cluster. This is because it would be the internal endpoint address of the
particular server that is advertised, rather than the load balancer's external
address.
Even if we configured XTS (not yet possible) to offer the address of the LB, we would
still have a problem as XTS will use a different session to the application to send
protocol messages and thus they will go to a different server that is not aware of this
transaction.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira