CLI doesn't work when agent-server communication uses sslsocket in JBoss ON 3.3

Environment

• Red Hat JBoss Operations Network (ON) 3.3.0
• ON Server configured for sslsocket:

rhq.communications.connector.transport=sslsocket
rhq.communications.connector.bind-address=
rhq.communications.connector.bind-port=7800
rhq.communications.connector.transport-params=

Issue

• CLI cannot connect to the JBoss ON server when it is configured to use agent-server communication over sslsocket.

./rhq-cli.sh -u rhqadmin -p rhqadmin -s jonserver.local -t 7443 --transport sslsocket
Invalid transport [sslsocket], should be either http or https

Resolution

• This has been logged as This content is not included.Red Hat Bug 1194690 to be fixed in a future release of JBoss ON. Until this This content is not included.Red Hat Bug 1194690 is fixed use servlet or sslservlet to connect JON server with rhq-cli.

Root Cause

The CLI client can only use "servlet" or "sslservlet" to make the connections, but the "login" command only accepts http or https and if not specified makes a guess based on the port number ending in 443.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.