Bug 849786 - Documentation incorrectly suggests that sslservlet should be used for the agent's communication transport - rhq.communications.connector.transport
Summary: Documentation incorrectly suggests that sslservlet should be used for the age...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Documentation
Version: JON 3.1.0
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
: ---
Assignee: Deon Ballard
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-20 21:08 UTC by Larry O'Leary
Modified: 2018-11-28 19:28 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-01 00:33:19 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 190693 0 None None None 2012-08-20 21:12:18 UTC

Description Larry O'Leary 2012-08-20 21:08:58 UTC 
Description of problem:
Agent configuration described in https://access.redhat.com/knowledge/docs/en-US/JBoss_Operations_Network/3.1/html/Admin_Configuring_JON_Servers_and_Agents/configuring-ssl.html#JBoss_ON_and_SSL-Encryption suggests using `sslservlet` as the transport however this transport is invalid. On the JON/RHQ agent, the only supported transports are `socket` and `sslsocket`. In the case of enabling SSL/TLS on the agent, sslsocket should be used. The only place `sslservlet` can be used is for the `rhq.agent.server.transport` property.

Version-Release number of selected component (if applicable):
JON 3.1.0

Additional info:
By using `sslservlet` for `rhq.communications.connector.transport` as indicated in step 2.c. the result is the agent will fail to start due to the invalid transport being used.
Comment 1 Deon Ballard 2013-03-01 00:33:19 UTC 
Mass closure.
Note You need to log in before you can comment on or make changes to this bug.