[JBoss JIRA] (WFLY-11833) Stateful Session Bean affinity URI instead of cluster
by Joerg Baesner (Jira)
[ https://issues.jboss.org/browse/WFLY-11833?page=com.atlassian.jira.plugin... ]
Joerg Baesner updated WFLY-11833:
---------------------------------
Labels: downstream_dependency regression (was: downstream_dependency)
> 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, regression
> Attachments: stateful-timeout-eap7.0.zip, stateful-timeout.zip, test-debug-log.txt
>
>
> 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)
6 years, 11 months
[JBoss JIRA] (WFLY-12384) ManagedExecutorService keeping references on undeploy/deploy
by Joerg Baesner (Jira)
[ https://issues.jboss.org/browse/WFLY-12384?page=com.atlassian.jira.plugin... ]
Joerg Baesner updated WFLY-12384:
---------------------------------
Description:
Usage of {{ManagedExecutorService}} leading to kept references after {{undeploy}}/{{deploy}}. This can be seen in the log as below:
{code}
SEVERE [a.b.c.MemberRepository] (EE-ManagedThreadFactory-default-Thread-1) exception when loading the members: Type specified for TypedQuery [a.b.c.Member] is incompatible with query return type [class a.b.c.Member]: java.lang.IllegalArgumentException: Type specified for TypedQuery [a.b.c.Member] is incompatible with query return type [class a.b.c.Member]
at org.hibernate.internal.AbstractSharedSessionContract.resultClassChecking(AbstractSharedSessionContract.java:792)
at org.hibernate.internal.AbstractSharedSessionContract.createQuery(AbstractSharedSessionContract.java:746)
at org.hibernate.internal.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:23)
at org.jboss.as.jpa.container.AbstractEntityManager.createQuery(AbstractEntityManager.java:133)
at a.b.c.MemberRepository.loadMembers(MemberRepository.java:77)
at a.b.c.MemberRepository$Proxy$_$$_WeldClientProxy.loadMembers(Unknown Source)
at a.b.c.PollMembersTask.call(PollMembersTask.java:45)
at a.b.c.PollMembersTask.call(PollMembersTask.java:25)
at org.jboss.as.ee.concurrent.ControlPointUtils$ControlledCallable.call(ControlPointUtils.java:129)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.glassfish.enterprise.concurrent.internal.ManagedFutureTask.run(ManagedFutureTask.java:141)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250)
{code}
was:
Usage of {{ManagedExecutorService}} leading to kept references after {{undeploy}}/{{deploy}}. This can be seen in the log as below:
{code}
SEVERE [de.hessen.hzd.data.MemberRepository] (EE-ManagedThreadFactory-default-Thread-1) exception when loading the members: Type specified for TypedQuery [de.hessen.hzd.model.Member] is incompatible with query return type [class de.hessen.hzd.model.Member]: java.lang.IllegalArgumentException: Type specified for TypedQuery [de.hessen.hzd.model.Member] is incompatible with query return type [class de.hessen.hzd.model.Member]
at org.hibernate.internal.AbstractSharedSessionContract.resultClassChecking(AbstractSharedSessionContract.java:792)
at org.hibernate.internal.AbstractSharedSessionContract.createQuery(AbstractSharedSessionContract.java:746)
at org.hibernate.internal.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:23)
at org.jboss.as.jpa.container.AbstractEntityManager.createQuery(AbstractEntityManager.java:133)
at de.hessen.hzd.data.MemberRepository.loadMembers(MemberRepository.java:77)
at de.hessen.hzd.data.MemberRepository$Proxy$_$$_WeldClientProxy.loadMembers(Unknown Source)
at de.hessen.hzd.concurrency.PollMembersTask.call(PollMembersTask.java:45)
at de.hessen.hzd.concurrency.PollMembersTask.call(PollMembersTask.java:25)
at org.jboss.as.ee.concurrent.ControlPointUtils$ControlledCallable.call(ControlPointUtils.java:129)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.glassfish.enterprise.concurrent.internal.ManagedFutureTask.run(ManagedFutureTask.java:141)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250)
{code}
> ManagedExecutorService keeping references on undeploy/deploy
> ------------------------------------------------------------
>
> Key: WFLY-12384
> URL: https://issues.jboss.org/browse/WFLY-12384
> Project: WildFly
> Issue Type: Bug
> Components: Concurrency Utilities
> Affects Versions: 19.0.0.Beta1
> Reporter: Joerg Baesner
> Assignee: Eduardo Martins
> Priority: Major
> Labels: downstream_dependency
>
> Usage of {{ManagedExecutorService}} leading to kept references after {{undeploy}}/{{deploy}}. This can be seen in the log as below:
> {code}
> SEVERE [a.b.c.MemberRepository] (EE-ManagedThreadFactory-default-Thread-1) exception when loading the members: Type specified for TypedQuery [a.b.c.Member] is incompatible with query return type [class a.b.c.Member]: java.lang.IllegalArgumentException: Type specified for TypedQuery [a.b.c.Member] is incompatible with query return type [class a.b.c.Member]
> at org.hibernate.internal.AbstractSharedSessionContract.resultClassChecking(AbstractSharedSessionContract.java:792)
> at org.hibernate.internal.AbstractSharedSessionContract.createQuery(AbstractSharedSessionContract.java:746)
> at org.hibernate.internal.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:23)
> at org.jboss.as.jpa.container.AbstractEntityManager.createQuery(AbstractEntityManager.java:133)
> at a.b.c.MemberRepository.loadMembers(MemberRepository.java:77)
> at a.b.c.MemberRepository$Proxy$_$$_WeldClientProxy.loadMembers(Unknown Source)
> at a.b.c.PollMembersTask.call(PollMembersTask.java:45)
> at a.b.c.PollMembersTask.call(PollMembersTask.java:25)
> at org.jboss.as.ee.concurrent.ControlPointUtils$ControlledCallable.call(ControlPointUtils.java:129)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.glassfish.enterprise.concurrent.internal.ManagedFutureTask.run(ManagedFutureTask.java:141)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12384) ManagedExecutorService keeping references on undeploy/deploy
by Joerg Baesner (Jira)
[ https://issues.jboss.org/browse/WFLY-12384?page=com.atlassian.jira.plugin... ]
Joerg Baesner updated WFLY-12384:
---------------------------------
Labels: downstream_dependency (was: )
> ManagedExecutorService keeping references on undeploy/deploy
> ------------------------------------------------------------
>
> Key: WFLY-12384
> URL: https://issues.jboss.org/browse/WFLY-12384
> Project: WildFly
> Issue Type: Bug
> Components: Concurrency Utilities
> Affects Versions: 19.0.0.Beta1
> Reporter: Joerg Baesner
> Assignee: Eduardo Martins
> Priority: Major
> Labels: downstream_dependency
>
> Usage of {{ManagedExecutorService}} leading to kept references after {{undeploy}}/{{deploy}}. This can be seen in the log as below:
> {code}
> SEVERE [de.hessen.hzd.data.MemberRepository] (EE-ManagedThreadFactory-default-Thread-1) exception when loading the members: Type specified for TypedQuery [de.hessen.hzd.model.Member] is incompatible with query return type [class de.hessen.hzd.model.Member]: java.lang.IllegalArgumentException: Type specified for TypedQuery [de.hessen.hzd.model.Member] is incompatible with query return type [class de.hessen.hzd.model.Member]
> at org.hibernate.internal.AbstractSharedSessionContract.resultClassChecking(AbstractSharedSessionContract.java:792)
> at org.hibernate.internal.AbstractSharedSessionContract.createQuery(AbstractSharedSessionContract.java:746)
> at org.hibernate.internal.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:23)
> at org.jboss.as.jpa.container.AbstractEntityManager.createQuery(AbstractEntityManager.java:133)
> at de.hessen.hzd.data.MemberRepository.loadMembers(MemberRepository.java:77)
> at de.hessen.hzd.data.MemberRepository$Proxy$_$$_WeldClientProxy.loadMembers(Unknown Source)
> at de.hessen.hzd.concurrency.PollMembersTask.call(PollMembersTask.java:45)
> at de.hessen.hzd.concurrency.PollMembersTask.call(PollMembersTask.java:25)
> at org.jboss.as.ee.concurrent.ControlPointUtils$ControlledCallable.call(ControlPointUtils.java:129)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.glassfish.enterprise.concurrent.internal.ManagedFutureTask.run(ManagedFutureTask.java:141)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12385) [GSS](7.2.z) ManagedExecutorService keeping references on undeploy/deploy
by Joerg Baesner (Jira)
Joerg Baesner created WFLY-12385:
------------------------------------
Summary: [GSS](7.2.z) ManagedExecutorService keeping references on undeploy/deploy
Key: WFLY-12385
URL: https://issues.jboss.org/browse/WFLY-12385
Project: WildFly
Issue Type: Bug
Components: Concurrency Utilities
Affects Versions: 19.0.0.Beta1
Reporter: Joerg Baesner
Assignee: Eduardo Martins
Usage of {{ManagedExecutorService}} leading to kept references after {{undeploy}}/{{deploy}}. This can be seen in the log as below:
{code}
SEVERE [de.hessen.hzd.data.MemberRepository] (EE-ManagedThreadFactory-default-Thread-1) exception when loading the members: Type specified for TypedQuery [de.hessen.hzd.model.Member] is incompatible with query return type [class de.hessen.hzd.model.Member]: java.lang.IllegalArgumentException: Type specified for TypedQuery [de.hessen.hzd.model.Member] is incompatible with query return type [class de.hessen.hzd.model.Member]
at org.hibernate.internal.AbstractSharedSessionContract.resultClassChecking(AbstractSharedSessionContract.java:792)
at org.hibernate.internal.AbstractSharedSessionContract.createQuery(AbstractSharedSessionContract.java:746)
at org.hibernate.internal.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:23)
at org.jboss.as.jpa.container.AbstractEntityManager.createQuery(AbstractEntityManager.java:133)
at de.hessen.hzd.data.MemberRepository.loadMembers(MemberRepository.java:77)
at de.hessen.hzd.data.MemberRepository$Proxy$_$$_WeldClientProxy.loadMembers(Unknown Source)
at de.hessen.hzd.concurrency.PollMembersTask.call(PollMembersTask.java:45)
at de.hessen.hzd.concurrency.PollMembersTask.call(PollMembersTask.java:25)
at org.jboss.as.ee.concurrent.ControlPointUtils$ControlledCallable.call(ControlPointUtils.java:129)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.glassfish.enterprise.concurrent.internal.ManagedFutureTask.run(ManagedFutureTask.java:141)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250)
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12384) ManagedExecutorService keeping references on undeploy/deploy
by Joerg Baesner (Jira)
Joerg Baesner created WFLY-12384:
------------------------------------
Summary: ManagedExecutorService keeping references on undeploy/deploy
Key: WFLY-12384
URL: https://issues.jboss.org/browse/WFLY-12384
Project: WildFly
Issue Type: Bug
Components: Concurrency Utilities
Affects Versions: 19.0.0.Beta1
Reporter: Joerg Baesner
Assignee: Eduardo Martins
Usage of {{ManagedExecutorService}} leading to kept references after {{undeploy}}/{{deploy}}. This can be seen in the log as below:
{code}
SEVERE [de.hessen.hzd.data.MemberRepository] (EE-ManagedThreadFactory-default-Thread-1) exception when loading the members: Type specified for TypedQuery [de.hessen.hzd.model.Member] is incompatible with query return type [class de.hessen.hzd.model.Member]: java.lang.IllegalArgumentException: Type specified for TypedQuery [de.hessen.hzd.model.Member] is incompatible with query return type [class de.hessen.hzd.model.Member]
at org.hibernate.internal.AbstractSharedSessionContract.resultClassChecking(AbstractSharedSessionContract.java:792)
at org.hibernate.internal.AbstractSharedSessionContract.createQuery(AbstractSharedSessionContract.java:746)
at org.hibernate.internal.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:23)
at org.jboss.as.jpa.container.AbstractEntityManager.createQuery(AbstractEntityManager.java:133)
at de.hessen.hzd.data.MemberRepository.loadMembers(MemberRepository.java:77)
at de.hessen.hzd.data.MemberRepository$Proxy$_$$_WeldClientProxy.loadMembers(Unknown Source)
at de.hessen.hzd.concurrency.PollMembersTask.call(PollMembersTask.java:45)
at de.hessen.hzd.concurrency.PollMembersTask.call(PollMembersTask.java:25)
at org.jboss.as.ee.concurrent.ControlPointUtils$ControlledCallable.call(ControlPointUtils.java:129)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.glassfish.enterprise.concurrent.internal.ManagedFutureTask.run(ManagedFutureTask.java:141)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250)
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (JBJCA-1392) Need to add checkTransaction handling for unwrap connection
by Ivo Studensky (Jira)
[ https://issues.jboss.org/browse/JBJCA-1392?page=com.atlassian.jira.plugin... ]
Ivo Studensky updated JBJCA-1392:
---------------------------------
Git Pull Request: https://github.com/ironjacamar/ironjacamar/pull/689
> Need to add checkTransaction handling for unwrap connection
> -----------------------------------------------------------
>
> Key: JBJCA-1392
> URL: https://issues.jboss.org/browse/JBJCA-1392
> Project: IronJacamar
> Issue Type: Bug
> Components: JDBC
> Reporter: Ivo Studensky
> Assignee: Ivo Studensky
> Priority: Major
> Labels: downstream_dependency
>
> _connection.setAutoCommit_ cannot affect _unwrap_ native connection. The following _mc.getAutoCommit_ result is true.
> {code}
> c = dataSource.getConnection();
> c.setAutoCommit(false);
> if (c.isWrapperFor(oracle.jdbc.OracleConnection.class)) {
> mc = c.unwrap(oracle.jdbc.OracleConnection.class);
> }
> System.out.println("[JDBC 4 Wrapper] autoCommit : " + mc.getAutoCommit());
> {code}
> However, the following _getUnderlyingConnection_ native connection result is false.
> {code}
> c = dataSource.getConnection();
> c.setAutoCommit(false);
> WrappedConnection wc = (WrappedConnection)c;
> oracle.jdbc.OracleConnection mc = (oracle.jdbc.OracleConnection)wc.getUnderlyingConnection();
> System.out.println("[org.jboss.ironjacamar.jdbcadapters WrappedConnection] autoCommit : " + mc.getAutoCommit());
> {code}
> The _getUnderlyingConnection_ method call _BaseWrapperManagedConnection.checkTransaction_ process, but there is no similar process in _unwrap_ method.
> {code:title=org/jboss/jca/adapters/jdbc/BaseWrapperManagedConnection.java|borderStyle=solid}
> void checkTransaction() throws SQLException
> {
> synchronized (stateLock)
> {
> if (inManagedTransaction)
> return;
> // Check autocommit
> if (jdbcAutoCommit != underlyingAutoCommit)
> {
> con.setAutoCommit(jdbcAutoCommit);
> underlyingAutoCommit = jdbcAutoCommit;
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (JBJCA-1392) Need to add checkTransaction handling for unwrap connection
by Ivo Studensky (Jira)
[ https://issues.jboss.org/browse/JBJCA-1392?page=com.atlassian.jira.plugin... ]
Ivo Studensky updated JBJCA-1392:
---------------------------------
Labels: downstream_dependency (was: )
> Need to add checkTransaction handling for unwrap connection
> -----------------------------------------------------------
>
> Key: JBJCA-1392
> URL: https://issues.jboss.org/browse/JBJCA-1392
> Project: IronJacamar
> Issue Type: Bug
> Components: JDBC
> Reporter: Ivo Studensky
> Assignee: Ivo Studensky
> Priority: Major
> Labels: downstream_dependency
>
> _connection.setAutoCommit_ cannot affect _unwrap_ native connection. The following _mc.getAutoCommit_ result is true.
> {code}
> c = dataSource.getConnection();
> c.setAutoCommit(false);
> if (c.isWrapperFor(oracle.jdbc.OracleConnection.class)) {
> mc = c.unwrap(oracle.jdbc.OracleConnection.class);
> }
> System.out.println("[JDBC 4 Wrapper] autoCommit : " + mc.getAutoCommit());
> {code}
> However, the following _getUnderlyingConnection_ native connection result is false.
> {code}
> c = dataSource.getConnection();
> c.setAutoCommit(false);
> WrappedConnection wc = (WrappedConnection)c;
> oracle.jdbc.OracleConnection mc = (oracle.jdbc.OracleConnection)wc.getUnderlyingConnection();
> System.out.println("[org.jboss.ironjacamar.jdbcadapters WrappedConnection] autoCommit : " + mc.getAutoCommit());
> {code}
> The _getUnderlyingConnection_ method call _BaseWrapperManagedConnection.checkTransaction_ process, but there is no similar process in _unwrap_ method.
> {code:title=org/jboss/jca/adapters/jdbc/BaseWrapperManagedConnection.java|borderStyle=solid}
> void checkTransaction() throws SQLException
> {
> synchronized (stateLock)
> {
> if (inManagedTransaction)
> return;
> // Check autocommit
> if (jdbcAutoCommit != underlyingAutoCommit)
> {
> con.setAutoCommit(jdbcAutoCommit);
> underlyingAutoCommit = jdbcAutoCommit;
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (JBJCA-1392) Need to add checkTransaction handling for unwrap connection
by Ivo Studensky (Jira)
[ https://issues.jboss.org/browse/JBJCA-1392?page=com.atlassian.jira.plugin... ]
Ivo Studensky moved JBEAP-17409 to JBJCA-1392:
----------------------------------------------
Project: IronJacamar (was: JBoss Enterprise Application Platform)
Key: JBJCA-1392 (was: JBEAP-17409)
Workflow: classic default workflow (was: CDW with loose statuses v1)
Component/s: JDBC
(was: JCA)
Affects Version/s: (was: 7.2.0.GA)
> Need to add checkTransaction handling for unwrap connection
> -----------------------------------------------------------
>
> Key: JBJCA-1392
> URL: https://issues.jboss.org/browse/JBJCA-1392
> Project: IronJacamar
> Issue Type: Bug
> Components: JDBC
> Reporter: Ivo Studensky
> Assignee: Ivo Studensky
> Priority: Major
> Labels: downstream_dependency
>
> _connection.setAutoCommit_ cannot affect _unwrap_ native connection. The following _mc.getAutoCommit_ result is true.
> {code}
> c = dataSource.getConnection();
> c.setAutoCommit(false);
> if (c.isWrapperFor(oracle.jdbc.OracleConnection.class)) {
> mc = c.unwrap(oracle.jdbc.OracleConnection.class);
> }
> System.out.println("[JDBC 4 Wrapper] autoCommit : " + mc.getAutoCommit());
> {code}
> However, the following _getUnderlyingConnection_ native connection result is false.
> {code}
> c = dataSource.getConnection();
> c.setAutoCommit(false);
> WrappedConnection wc = (WrappedConnection)c;
> oracle.jdbc.OracleConnection mc = (oracle.jdbc.OracleConnection)wc.getUnderlyingConnection();
> System.out.println("[org.jboss.ironjacamar.jdbcadapters WrappedConnection] autoCommit : " + mc.getAutoCommit());
> {code}
> The _getUnderlyingConnection_ method call _BaseWrapperManagedConnection.checkTransaction_ process, but there is no similar process in _unwrap_ method.
> {code:title=org/jboss/jca/adapters/jdbc/BaseWrapperManagedConnection.java|borderStyle=solid}
> void checkTransaction() throws SQLException
> {
> synchronized (stateLock)
> {
> if (inManagedTransaction)
> return;
> // Check autocommit
> if (jdbcAutoCommit != underlyingAutoCommit)
> {
> con.setAutoCommit(jdbcAutoCommit);
> underlyingAutoCommit = jdbcAutoCommit;
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-11833) Stateful Session Bean affinity URI instead of cluster
by Joerg Baesner (Jira)
[ https://issues.jboss.org/browse/WFLY-11833?page=com.atlassian.jira.plugin... ]
Joerg Baesner updated WFLY-11833:
---------------------------------
Attachment: stateful-timeout-eap7.0.zip
> 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-eap7.0.zip, stateful-timeout.zip, test-debug-log.txt
>
>
> 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)
6 years, 11 months