5:05 p.m.
Extend connection identity to server side
-----------------------------------------
Key: JBREM-1144
URL: https://jira.jboss.org/jira/browse/JBREM-1144
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 2.2.3, 2.5.1 (Flounder)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.2 (Flounder), 2.2.3.SP1
In JBREM-1128 "Introduce connection identity concept" and JBREM-1132 "CLONE
[JBREM-1128] - Introduce connection identity concept", the server was equipped to
recognized when a client had been replaced by another client. In other words, clients
were assigned an identity. This concept should be extended to the server side, so that
ConnectionValidator can detect that a server has been replaced.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:33 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-1144) Extend connection identity to server side
[
https://jira.jboss.org/jira/browse/JBREM-1144?page=com.atlassian.jira.plu...
]
Ron Sigal updated JBREM-1144:
-----------------------------
Fix Version/s: (was: 2.5.2 (Flounder))
(was: 2.2.3.SP1)
Will not implement this issue unless it becomes necessary.
Extend connection identity to server side
-----------------------------------------
Key: JBREM-1144
URL: https://jira.jboss.org/jira/browse/JBREM-1144
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.5.1 (Flounder), 2.2.3
Reporter: Ron Sigal
Assignee: Ron Sigal
In JBREM-1128 "Introduce connection identity concept" and JBREM-1132
"CLONE [JBREM-1128] - Introduce connection identity concept", the server was
equipped to recognized when a client had been replaced by another client. In other words,
clients were assigned an identity. This concept should be extended to the server side, so
that ConnectionValidator can detect that a server has been replaced.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:03 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-1144) Extend connection identity to server side
[
https://issues.jboss.org/browse/JBREM-1144?page=com.atlassian.jira.plugin...
]
Ron Sigal updated JBREM-1144:
-----------------------------
Fix Version/s: 2.5.3.SP2
2.2.3.SP4
Affects Version/s: 2.2.3.SP3
2.5.3.SP1
(was: 2.2.3)
(was: 2.5.1 (Flounder))
Extend connection identity to server side
-----------------------------------------
Key: JBREM-1144
URL: https://issues.jboss.org/browse/JBREM-1144
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.5.3.SP1, 2.2.3.SP3
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.3.SP2, 2.2.3.SP4
In JBREM-1128 "Introduce connection identity concept" and JBREM-1132
"CLONE [JBREM-1128] - Introduce connection identity concept", the server was
equipped to recognized when a client had been replaced by another client. In other words,
clients were assigned an identity. This concept should be extended to the server side, so
that ConnectionValidator can detect that a server has been replaced.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:23 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-1144) Extend connection identity to server side
[
https://issues.jboss.org/browse/JBREM-1144?page=com.atlassian.jira.plugin...
]
Ron Sigal updated JBREM-1144:
-----------------------------
Extend connection identity to server side
-----------------------------------------
Key: JBREM-1144
URL: https://issues.jboss.org/browse/JBREM-1144
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.5.3.SP1, 2.2.3.SP3
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.3.SP2, 2.2.3.SP4
In JBREM-1128 "Introduce connection identity concept" and JBREM-1132
"CLONE [JBREM-1128] - Introduce connection identity concept", the server was
equipped to recognized when a client had been replaced by another client. In other words,
clients were assigned an identity. This concept should be extended to the server side, so
that ConnectionValidator can detect that a server has been replaced.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:35 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-1144) Extend connection identity to server side
[
https://issues.jboss.org/browse/JBREM-1144?page=com.atlassian.jira.plugin...
]
Ron Sigal commented on JBREM-1144:
----------------------------------
The need for a server identity has arisen in a support case, so this issue will be
implemented.
If org.jboss.remoting.Remoting.USE_SERVER_CONNECTION_IDENTITY (actual value
"useServerConnectionIdentity") is set to true, then
org.jboss.remoting.SocketInvoker will create for itself a unique serverId. Moreover, if
an org.jboss.remotinig.ConnectionListener is installed, which leads to the creation of an
org.jboss.remoting.ConnectionValidator, then the ConnectionValidator will get the serverId
from the ServerInvoker with its first PING, and it will compare the serverId returned with
each subsequent PING to the original serverId. If the serverId changes, then the
ServerInvoker has been replaced, and the ConnectionValidator will declare the connection
to be broken.
Note that the use of this feature will change the wire format of the response to the PING
if the ConnectionValidator has "tieToLease" set to true. However,
ConnectionValidator and ServerInvoker are written to accomodate older versions that do not
support this feature.
Testing:
* unit tests: org.jboss.test.remoting.connection.identity.ServerIdentityTestCase
* versioning tests:
*
org.jboss.test.remoting.versioning.identity.ServerIdentityWithLeasingVersionTestCase
*
org.jboss.test.remoting.versioning.identity.ServerIdentityWithoutLeasingVersionTestCase
The changes have been applied to the 2.2 and 2.x branches. Waiting for results in
hudson.
Extend connection identity to server side
-----------------------------------------
Key: JBREM-1144
URL: https://issues.jboss.org/browse/JBREM-1144
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.5.3.SP1, 2.2.3.SP3
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.3.SP2, 2.2.3.SP4
In JBREM-1128 "Introduce connection identity concept" and JBREM-1132
"CLONE [JBREM-1128] - Introduce connection identity concept", the server was
equipped to recognized when a client had been replaced by another client. In other words,
clients were assigned an identity. This concept should be extended to the server side, so
that ConnectionValidator can detect that a server has been replaced.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:04 p.m.
New subject: [JBoss JIRA] Resolved: (JBREM-1144) Extend connection identity to server side
[
https://issues.jboss.org/browse/JBREM-1144?page=com.atlassian.jira.plugin...
]
Ron Sigal resolved JBREM-1144.
------------------------------
Resolution: Done
Tests are passing in hudson.
Extend connection identity to server side
-----------------------------------------
Key: JBREM-1144
URL: https://issues.jboss.org/browse/JBREM-1144
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.5.3.SP1, 2.2.3.SP3
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.3.SP2, 2.2.3.SP4
In JBREM-1128 "Introduce connection identity concept" and JBREM-1132
"CLONE [JBREM-1128] - Introduce connection identity concept", the server was
equipped to recognized when a client had been replaced by another client. In other words,
clients were assigned an identity. This concept should be extended to the server side, so
that ConnectionValidator can detect that a server has been replaced.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:14 p.m.
New subject: [JBoss JIRA] Reopened: (JBREM-1144) Extend connection identity to server side
[
https://issues.jboss.org/browse/JBREM-1144?page=com.atlassian.jira.plugin...
]
Ron Sigal reopened JBREM-1144:
------------------------------
Reopening this issue in response to the problems discussed in the user forum:
http://community.jboss.org/thread/160465?tstart=0.
Extend connection identity to server side
-----------------------------------------
Key: JBREM-1144
URL: https://issues.jboss.org/browse/JBREM-1144
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.5.3.SP1, 2.2.3.SP3
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.3.SP2, 2.2.3.SP4
In JBREM-1128 "Introduce connection identity concept" and JBREM-1132
"CLONE [JBREM-1128] - Introduce connection identity concept", the server was
equipped to recognized when a client had been replaced by another client. In other words,
clients were assigned an identity. This concept should be extended to the server side, so
that ConnectionValidator can detect that a server has been replaced.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:48 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-1144) Extend connection identity to server side
[
https://issues.jboss.org/browse/JBREM-1144?page=com.atlassian.jira.plugin...
]
Ron Sigal commented on JBREM-1144:
----------------------------------
The solution is to give each Lease a unique identity and to return that instead of the
ServerInvoker's unique identity.
Testing: added testServerIdentityWithLeasingNewLease() to
org.jboss.test.remoting.connection.identity.ServerIdentityTestCase to cover the situation
when a lease changes and the ServerInvoker remains the same.
Waiting for results in hudson.
Extend connection identity to server side
-----------------------------------------
Key: JBREM-1144
URL: https://issues.jboss.org/browse/JBREM-1144
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.5.3.SP1, 2.2.3.SP3
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.3.SP2, 2.2.3.SP4
In JBREM-1128 "Introduce connection identity concept" and JBREM-1132
"CLONE [JBREM-1128] - Introduce connection identity concept", the server was
equipped to recognized when a client had been replaced by another client. In other words,
clients were assigned an identity. This concept should be extended to the server side, so
that ConnectionValidator can detect that a server has been replaced.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:57 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-1144) Extend connection identity to server side
[
https://issues.jboss.org/browse/JBREM-1144?page=com.atlassian.jira.plugin...
]
Ron Sigal updated JBREM-1144:
-----------------------------
Attachment: jboss-remoting.jar
Attaching jboss-remoting.jar, preview of version 2.2.3.SP4, with fix.
Extend connection identity to server side
-----------------------------------------
Key: JBREM-1144
URL: https://issues.jboss.org/browse/JBREM-1144
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.5.3.SP1, 2.2.3.SP3
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.3.SP2, 2.2.3.SP4
Attachments: jboss-remoting.jar
In JBREM-1128 "Introduce connection identity concept" and JBREM-1132
"CLONE [JBREM-1128] - Introduce connection identity concept", the server was
equipped to recognized when a client had been replaced by another client. In other words,
clients were assigned an identity. This concept should be extended to the server side, so
that ConnectionValidator can detect that a server has been replaced.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:02 p.m.
New subject: [JBoss JIRA] Resolved: (JBREM-1144) Extend connection identity to server side
[
https://issues.jboss.org/browse/JBREM-1144?page=com.atlassian.jira.plugin...
]
Ron Sigal resolved JBREM-1144.
------------------------------
Resolution: Done
Additional unit test is passing in hudson.
Extend connection identity to server side
-----------------------------------------
Key: JBREM-1144
URL: https://issues.jboss.org/browse/JBREM-1144
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.5.3.SP1, 2.2.3.SP3
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.3.SP2, 2.2.3.SP4
Attachments: jboss-remoting.jar
In JBREM-1128 "Introduce connection identity concept" and JBREM-1132
"CLONE [JBREM-1128] - Introduce connection identity concept", the server was
equipped to recognized when a client had been replaced by another client. In other words,
clients were assigned an identity. This concept should be extended to the server side, so
that ConnectionValidator can detect that a server has been replaced.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4837
days inactive
5403
days old
jboss-remoting-issues@lists.jboss.org
9 comments
1 participants
participants (1)
-
Ron Sigal (JIRA)