Details
-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
Description
Due to issues with affinity processing, authentication stickiness, and user transaction stickiness, node topology information is effectively ignored, causing balancing and failover to not behave properly.
Attachments
Issue Links
- blocks
-
JBEAP-12285 Remote EJB clustered node discovery is ignored
-
- Verified
-
- clones
-
JBEAP-12285 Remote EJB clustered node discovery is ignored
-
- Verified
-
- is blocked by
-
WFLY-9349 Upgrade WildFly Naming Client to 1.0.2.Final
-
- Closed
-
-
WFLY-9350 Upgrade WildFly Transaction Client to 1.0.1.Final
-
- Closed
-
-
WFLY-9351 Upgrade JBoss EJB Client to 4.0.1.Final (Legacy to 3.0.1.Final)
-
- Closed
-
-
WFLY-9352 Upgrade WildFly HTTP client components to 1.0.3.Final
-
- Closed
-
- is caused by
-
WFLY-9357 User can not overridden with InitialContext properties as expected if wilfdfly-config-xml is used
-
- Closed
-
-
WFLY-6316 Deploying @Stateless EJB causes default ejb cache to start unnecessarily.
-
- Closed
-
-
WFLY-9282 UserTransaction should be lazy to allow node selection (loadbalancing) even if the invocations stick to one node
-
- Open
-