[
https://issues.jboss.org/browse/WFLY-11833?page=com.atlassian.jira.plugin...
]
Joerg Baesner commented on WFLY-11833:
--------------------------------------
[~rachmato] this is not a matter of having the reproducer running without indicating a
failure on the command line.
I did re-run the reproducer with the least recent commit on {{upstream/master}} as well.
The result on the command line is absolutely intermittently (sometimes _success_,
sometimes _failure_). Independent of the result of the command line execution we have to
look into the resulting log in:
{{ejb/build/reports/tests/test/classes/org.jboss.repro.stateful.timeout.StatefulTimeoutManagerTest.html}}
In there we have the two log lines:
{code}
2019.04.25 13:32:58 [Test worker] INFO o.j.r.s.t.StatefulTimeoutManagerTest - Manager
strong affinity: Cluster "ejb", weak affinity: None
...
2019.04.25 13:32:59 [Test worker] INFO o.j.r.s.t.StatefulTimeoutManagerTest - Stateful
strong affinity: URI<remote+http://127.0.0.1:9080>, weak affinity:
URI<remote+http://127.0.0.1:9080>
{code}
In the reproducers test class {{StatefulTimeoutManagerTest}} we can see that the affinity
of _Cluster "ejb"_ on *Manager strong affinity* is set hard coded in the test,
whereas the affinity of _URI<remote+http://127.0.0.1:9080>_ on *Stateful strong
affinity* is returned from the server and this is what is the actual issue here...
Stateful Session Bean affinity URI instead of cluster
-----------------------------------------------------
Key: WFLY-11833
URL:
https://issues.jboss.org/browse/WFLY-11833
Project: WildFly
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 16.0.0.Final
Environment: WildFly cluster having SFSB deployed.
Reporter: Joerg Baesner
Assignee: Richard Achmatowicz
Priority: Major
Labels: downstream_dependency
Attachments: stateful-timeout.zip
Deployed is an application with the following setup:
* Containing a SFSB (_with passivationCapable="true"_)
* A SLSB exposing a _remote_ method to a standalone client returning an instance of the
SFSB
Scenario:
A standalone client is invoking the _remote_ method on the Stateless Session Bean and a
new instance of the Stateful Session Bean is returned.
The issue is that the affinity of the returned Stateful Session Bean is URI instead of
Cluster.
See the attached Gradle reproducer application
--
This message was sent by Atlassian Jira
(v7.12.1#712002)