9:38 a.m.
Radoslav Husar created AS7-3848:
-----------------------------------
Summary: @Clustered @Stateless SLSB should send topology information to the
client
Key: AS7-3848
URL: https://issues.jboss.org/browse/AS7-3848
Project: Application Server 7
Issue Type: Feature Request
Components: Clustering, EJB
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: jaikiran pai
Fix For: 7.1.1.Final
Having AS7-2887 fixed, we currently take no action on @Clustered @Stateless but we allow
deployment.
The remote ejb client then treats the node as standalone nodes, clustering subsystem is
not started. This however means that the topology is static -- compared to AS5 client
behavior.
There are cases where it's useful mainly because the server side is constrained by the
pool size of the SLSB (--Jaikiran).
--
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
9:38 a.m.
[
https://issues.jboss.org/browse/AS7-3848?page=com.atlassian.jira.plugin.s...
]
Radoslav Husar commented on AS7-3848:
-------------------------------------
I set Fix Version/s: 7.1.1.Final but this is item for triage and scheduling.
@Clustered @Stateless SLSB should send topology information to the
client
-------------------------------------------------------------------------
Key: AS7-3848
URL: https://issues.jboss.org/browse/AS7-3848
Project: Application Server 7
Issue Type: Feature Request
Components: Clustering, EJB
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: jaikiran pai
Fix For: 7.1.1.Final
Having AS7-2887 fixed, we currently take no action on @Clustered @Stateless but we allow
deployment.
The remote ejb client then treats the node as standalone nodes, clustering subsystem is
not started. This however means that the topology is static -- compared to AS5 client
behavior.
There are cases where it's useful mainly because the server side is constrained by
the pool size of the SLSB (--Jaikiran).
--
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
3:58 p.m.
[
https://issues.jboss.org/browse/AS7-3848?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-3848:
------------------------------
Fix Version/s: 7.1.2.Final
(was: 7.1.1.Final)
This issue is being relocated to 7.1.2 so that 7.1.1 only contains criticals, blockers,
and EAP LA issues (which are probably not yet at the right status, or need an extra triage
pass).
If these issues are completed in a 7.1.1 timeframe please change the fix version. Although
if you forget I will bulk correct.
@Clustered @Stateless SLSB should send topology information to the
client
-------------------------------------------------------------------------
Key: AS7-3848
URL: https://issues.jboss.org/browse/AS7-3848
Project: Application Server 7
Issue Type: Feature Request
Components: Clustering, EJB
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: jaikiran pai
Labels: failover_testing
Fix For: 7.1.2.Final
Having AS7-2887 fixed, we currently take no action on @Clustered @Stateless but we allow
deployment.
The remote ejb client then treats the node as standalone nodes, clustering subsystem is
not started. This however means that the topology is static -- compared to AS5 client
behavior.
There are cases where it's useful mainly because the server side is constrained by
the pool size of the SLSB (--Jaikiran).
--
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
3:01 p.m.
[
https://issues.jboss.org/browse/AS7-3848?page=com.atlassian.jira.plugin.s...
]
Paul Ferraro reassigned AS7-3848:
---------------------------------
Assignee: Paul Ferraro (was: jaikiran pai)
@Clustered @Stateless SLSB should send topology information to the
client
-------------------------------------------------------------------------
Key: AS7-3848
URL: https://issues.jboss.org/browse/AS7-3848
Project: Application Server 7
Issue Type: Feature Request
Components: Clustering, EJB
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Labels: failover_testing
Fix For: 7.1.2.Final
Having AS7-2887 fixed, we currently take no action on @Clustered @Stateless but we allow
deployment.
The remote ejb client then treats the node as standalone nodes, clustering subsystem is
not started. This however means that the topology is static -- compared to AS5 client
behavior.
There are cases where it's useful mainly because the server side is constrained by
the pool size of the SLSB (--Jaikiran).
--
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
7:05 a.m.
[
https://issues.jboss.org/browse/AS7-3848?page=com.atlassian.jira.plugin.s...
]
Radoslav Husar commented on AS7-3848:
-------------------------------------
Brian, this is a feature request for missing feature from previous AS versions. The filing
is based on discussion we had on @Clustered SLSB Jira.
Currently, the EJB client when accessing stateless beans only accesses nodes which are
defined in the client's properties files. Thus when new servers are added to the
cluster (and the client has not been updated) it will never use the added nodes to request
SLSB. The @Clustered annotation has no effect on SLSB ATM. In a sense, when all nodes
defined in the client properties are not accessible but the cluster is still up -- the
client is not HA.
@Clustered @Stateless SLSB should send topology information to the
client
-------------------------------------------------------------------------
Key: AS7-3848
URL: https://issues.jboss.org/browse/AS7-3848
Project: Application Server 7
Issue Type: Feature Request
Components: Clustering, EJB
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Labels: failover_testing
Fix For: 7.1.2.Final
Having AS7-2887 fixed, we currently take no action on @Clustered @Stateless but we allow
deployment.
The remote ejb client then treats the node as standalone nodes, clustering subsystem is
not started. This however means that the topology is static -- compared to AS5 client
behavior.
There are cases where it's useful mainly because the server side is constrained by
the pool size of the SLSB (--Jaikiran).
--
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
8:58 a.m.
[
https://issues.jboss.org/browse/AS7-3848?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-3848:
-----------------------------------
To add more to this - we currently consider @Clustered @Stateless just as any other
@Stateless. The EJB client API has the ability to route invocations (based on configurable
algorithm) to different nodes within a cluster if it knows the cluster topology of the
bean. If the topology isn't available then the invocations for the stateless bean
always end up on the same server, which is constrained by the size of the bean instance
pool used by the stateless bean.
From an implementation point of view, just like for stateful beans,
the server side would have to do the following for stateless beans:
1) Send back a cluster topology to clients, when a client connects to a server and the
server has @Clustered @Stateless beans deployed.
2) Send back cluster view change notifications
3) Send back weak affinity association for invocations even on stateless beans
@Clustered @Stateless SLSB should send topology information to the
client
-------------------------------------------------------------------------
Key: AS7-3848
URL: https://issues.jboss.org/browse/AS7-3848
Project: Application Server 7
Issue Type: Feature Request
Components: Clustering, EJB
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Labels: eap6_LA, failover_testing
Fix For: 7.1.2.Final
Having AS7-2887 fixed, we currently take no action on @Clustered @Stateless but we allow
deployment.
The remote ejb client then treats the node as standalone nodes, clustering subsystem is
not started. This however means that the topology is static -- compared to AS5 client
behavior.
There are cases where it's useful mainly because the server side is constrained by
the pool size of the SLSB (--Jaikiran).
--
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
5:24 a.m.
[
https://issues.jboss.org/browse/AS7-3848?page=com.atlassian.jira.plugin.s...
]
Radoslav Husar closed AS7-3848.
-------------------------------
Verified, closing.
@Clustered @Stateless SLSB should send topology information to the
client
-------------------------------------------------------------------------
Key: AS7-3848
URL: https://issues.jboss.org/browse/AS7-3848
Project: Application Server 7
Issue Type: Feature Request
Components: Clustering, EJB
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Labels: eap6_LA, failover_testing
Fix For: 7.1.1.Final
Having AS7-2887 fixed, we currently take no action on @Clustered @Stateless but we allow
deployment.
The remote ejb client then treats the node as standalone nodes, clustering subsystem is
not started. This however means that the topology is static -- compared to AS5 client
behavior.
There are cases where it's useful mainly because the server side is constrained by
the pool size of the SLSB (--Jaikiran).
--
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
5:27 a.m.
[
https://issues.jboss.org/browse/AS7-3848?page=com.atlassian.jira.plugin.s...
]
Vikky B commented on AS7-3848:
------------------------------
Could you please let us know how did you verify with some sample program..thanks
@Clustered @Stateless SLSB should send topology information to the
client
-------------------------------------------------------------------------
Key: AS7-3848
URL: https://issues.jboss.org/browse/AS7-3848
Project: Application Server 7
Issue Type: Feature Request
Components: Clustering, EJB
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Labels: eap6_LA, failover_testing
Fix For: 7.1.1.Final
Having AS7-2887 fixed, we currently take no action on @Clustered @Stateless but we allow
deployment.
The remote ejb client then treats the node as standalone nodes, clustering subsystem is
not started. This however means that the topology is static -- compared to AS5 client
behavior.
There are cases where it's useful mainly because the server side is constrained by
the pool size of the SLSB (--Jaikiran).
--
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
5:49 a.m.
[
https://issues.jboss.org/browse/AS7-3848?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-3848:
-----------------------------------
{quote}
Could you please let us know how did you verify with some sample program..thanks
{quote}
You don't have to do anything. Just deploy the @Clustered beans on the server side and
invoke them from a client. Here's one example of the client invoking on remote beans
https://docs.jboss.org/author/display/AS71/EJB+invocations+from+a+remote+....
That example isn't specific to @Clustered beans though.
@Clustered @Stateless SLSB should send topology information to the
client
-------------------------------------------------------------------------
Key: AS7-3848
URL: https://issues.jboss.org/browse/AS7-3848
Project: Application Server 7
Issue Type: Feature Request
Components: Clustering, EJB
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Labels: eap6_LA, failover_testing
Fix For: 7.1.1.Final
Having AS7-2887 fixed, we currently take no action on @Clustered @Stateless but we allow
deployment.
The remote ejb client then treats the node as standalone nodes, clustering subsystem is
not started. This however means that the topology is static -- compared to AS5 client
behavior.
There are cases where it's useful mainly because the server side is constrained by
the pool size of the SLSB (--Jaikiran).
--
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
6:21 a.m.
[
https://issues.jboss.org/browse/AS7-3848?page=com.atlassian.jira.plugin.s...
]
Vikky B commented on AS7-3848:
------------------------------
thanks jaikiran...I have started two JBOSS instance with standalone-ha.xml..and I see in
the log that they are part of cluster...As per the documentation..I can add one of the
server host / port to get the request processed..but when I bring down the server whose
address I added to jboss-client.properties...it does not connect to the another JBOSS
instance in the cluster..
@Clustered @Stateless SLSB should send topology information to the
client
-------------------------------------------------------------------------
Key: AS7-3848
URL: https://issues.jboss.org/browse/AS7-3848
Project: Application Server 7
Issue Type: Feature Request
Components: Clustering, EJB
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: Paul Ferraro
Labels: eap6_LA, failover_testing
Fix For: 7.1.1.Final
Having AS7-2887 fixed, we currently take no action on @Clustered @Stateless but we allow
deployment.
The remote ejb client then treats the node as standalone nodes, clustering subsystem is
not started. This however means that the topology is static -- compared to AS5 client
behavior.
There are cases where it's useful mainly because the server side is constrained by
the pool size of the SLSB (--Jaikiran).
--
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
5090
days inactive
5181
days old
9 comments
5 participants
participants (5)
-
jaikiran pai (JIRA) -
Jason Greene (JIRA)
-
Paul Ferraro (JIRA)
-
Radoslav Husar (JIRA)
-
Vikky B (JIRA)