[JBoss JIRA] Created: (JBREM-581) can not do connection validation with ssl transport (only impacts detection)
11:48 a.m.
can not do connection validation with ssl transport (only impacts detection)
----------------------------------------------------------------------------
Key: JBREM-581
URL: http://jira.jboss.com/jira/browse/JBREM-581
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: detection
Affects Versions: 2.0.0.CR1 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta1 (Bluto)
When a detector gets the detection message from a server, the detection message does not
include (nor should it), the ssl info needed to make the ping invocation on that server to
verify it is indeed dead. Per JBREM-580, will currently just avoid making ping invocation
if transport supports ssl. This means that never does the ping invocation to ensure that
the server is really down (and not just lack of getting detection message update), but
instead will just consider it dead if detection message is stale.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:32 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-581) can not do connection validation with ssl transport (only impacts detection)
[ http://jira.jboss.com/jira/browse/JBREM-581?page=comments#action_12341277 ]
Tom Elrod commented on JBREM-581:
----------------------------------
"Suppose I have an app for Kramerica Industries running in the kramerica domain
(sparky, lucy, and pippin, say), and a client on pippin is looking for servers on sparky
and lucy. If the servers use SSL transports, then the client would need a truststore to
connect to the servers, so why couldn't the detector on pippin be supplied with the
same truststore? In other words, if you have a sort of "closed" system where
you know the components, wouldn't this work? I can imagine a more open SOA sort of
public system where a client is looking for any suitable server to connect to, where you
don't know all the components, but in that case I imagine the certificates would be
signed by some public authority."
can not do connection validation with ssl transport (only impacts
detection)
----------------------------------------------------------------------------
Key: JBREM-581
URL: http://jira.jboss.com/jira/browse/JBREM-581
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: detection
Affects Versions: 2.0.0.CR1 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta1 (Bluto)
When a detector gets the detection message from a server, the detection message does not
include (nor should it), the ssl info needed to make the ping invocation on that server to
verify it is indeed dead. Per JBREM-580, will currently just avoid making ping invocation
if transport supports ssl. This means that never does the ping invocation to ensure that
the server is really down (and not just lack of getting detection message update), but
instead will just consider it dead if detection message is stale.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:52 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-581) can not do connection validation with ssl transport (only impacts detection)
[ http://jira.jboss.com/jira/browse/JBREM-581?page=all ]
Ron Sigal updated JBREM-581:
----------------------------
Affects: [Documentation (Ref Guide, User Guide, etc.)]
Assignee: Ron Sigal (was: Tom Elrod)
can not do connection validation with ssl transport (only impacts
detection)
----------------------------------------------------------------------------
Key: JBREM-581
URL: http://jira.jboss.com/jira/browse/JBREM-581
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: detection
Affects Versions: 2.0.0.CR1 (Boon)
Reporter: Tom Elrod
Assigned To: Ron Sigal
Fix For: 2.2.0.Beta1 (Bluto)
When a detector gets the detection message from a server, the detection message does not
include (nor should it), the ssl info needed to make the ping invocation on that server to
verify it is indeed dead. Per JBREM-580, will currently just avoid making ping invocation
if transport supports ssl. This means that never does the ping invocation to ensure that
the server is really down (and not just lack of getting detection message update), but
instead will just consider it dead if detection message is stale.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:52 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-581) can not do connection validation with ssl transport (only impacts detection)
[ http://jira.jboss.com/jira/browse/JBREM-581?page=comments#action_12345118 ]
Ron Sigal commented on JBREM-581:
---------------------------------
AbstractDetector and JNDIDetector have been updated with constructors that accept
configuration Maps, which can include SSL information (e.g., truststore path and
password). The configuration Map is passed in the call to
ConnectionValidator.checkConnection(), which the heartbeat and failure detection threads
use to try to contact a known server. ConnectionValidator.checkConnection() passes it to
the appropriate client invoker. Therefore, it is now possible for the detectors to
contact servers that use SSL connections, if the appropriate SSL information is made
available.
The test for SSL transports, added for JBREM-580, has been backed out.
Sample code can be found in org.jboss.remoting.samples.detection.jndi.ssl.
A new unit test has been added, org.jboss.test.remoting.detection.jndi.RestartTestCase, in
which a client detects that a server starts, stops, and starts again. That test is also
extended to an SSL specific version:
org.jboss.test.remoting.detection.jndi.ssl.SSLRestartTestCase,
can not do connection validation with ssl transport (only impacts
detection)
----------------------------------------------------------------------------
Key: JBREM-581
URL: http://jira.jboss.com/jira/browse/JBREM-581
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: detection
Affects Versions: 2.0.0.CR1 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta1 (Bluto)
When a detector gets the detection message from a server, the detection message does not
include (nor should it), the ssl info needed to make the ping invocation on that server to
verify it is indeed dead. Per JBREM-580, will currently just avoid making ping invocation
if transport supports ssl. This means that never does the ping invocation to ensure that
the server is really down (and not just lack of getting detection message update), but
instead will just consider it dead if detection message is stale.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:52 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-581) can not do connection validation with ssl transport (only impacts detection)
[ http://jira.jboss.com/jira/browse/JBREM-581?page=all ]
Tom Elrod updated JBREM-581:
-----------------------------
Fix Version/s: 2.2.0.Beta1 (Bluto)
(was: 2.2.0.Alpha3 (Bluto))
can not do connection validation with ssl transport (only impacts
detection)
----------------------------------------------------------------------------
Key: JBREM-581
URL: http://jira.jboss.com/jira/browse/JBREM-581
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: detection
Affects Versions: 2.0.0.CR1 (Boon)
Reporter: Tom Elrod
Assigned To: Ron Sigal
Fix For: 2.2.0.Beta1 (Bluto)
When a detector gets the detection message from a server, the detection message does not
include (nor should it), the ssl info needed to make the ping invocation on that server to
verify it is indeed dead. Per JBREM-580, will currently just avoid making ping invocation
if transport supports ssl. This means that never does the ping invocation to ensure that
the server is really down (and not just lack of getting detection message update), but
instead will just consider it dead if detection message is stale.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:42 p.m.
New subject: [JBoss JIRA] Closed: (JBREM-581) can not do connection validation with ssl transport (only impacts detection)
[ http://jira.jboss.com/jira/browse/JBREM-581?page=all ]
Ron Sigal closed JBREM-581.
---------------------------
Resolution: Done
Fixed a race condition in the unit tests, and now they pass.
can not do connection validation with ssl transport (only impacts
detection)
----------------------------------------------------------------------------
Key: JBREM-581
URL: http://jira.jboss.com/jira/browse/JBREM-581
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: detection
Affects Versions: 2.0.0.CR1 (Boon)
Reporter: Tom Elrod
Assigned To: Ron Sigal
Fix For: 2.2.0.Beta1 (Bluto)
When a detector gets the detection message from a server, the detection message does not
include (nor should it), the ssl info needed to make the ping invocation on that server to
verify it is indeed dead. Per JBREM-580, will currently just avoid making ping invocation
if transport supports ssl. This means that never does the ping invocation to ensure that
the server is really down (and not just lack of getting detection message update), but
instead will just consider it dead if detection message is stale.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7203
days inactive
7289
days old
5 comments
2 participants
participants (2)
-
Ron Sigal (JIRA) -
Tom Elrod (JIRA)