This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours
Bug 867148 - After enabling encryption using sslsocket the agent fails to start if is missing from agent-configuration.xml
After enabling encryption using sslsocket the agent fails to start if rhq.age...
Status: NEW
Product: RHQ Project
Classification: Other
Component: Agent (Show other bugs)
All All
unspecified Severity medium (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
Depends On:
Blocks: 1302322
  Show dependency treegraph
Reported: 2012-10-16 17:39 EDT by Larry O'Leary
Modified: 2016-01-27 13:22 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:

Attachments (Terms of Use)

  None (edit)
Description Larry O'Leary 2012-10-16 17:39:30 EDT
Description of problem:
After enabling TLS encryption for agent-to-server communication, the agent will fail to start with the following exception:

            2012-10-15 13:30:06,346 ERROR [RHQ Server Polling Thread] (jboss.remoting.transport.socket.MicroSocketClientInvoker)- Error setting up SocketClientInvoker[72e5355f, sslsocket://]
	            at java.util.Hashtable.put(
	            at java.util.Hashtable.putAll(
	            at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.setup(
	            at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.<init>(
	            at org.jboss.remoting.transport.socket.SocketClientInvoker.<init>(
	            at org.jboss.remoting.transport.sslsocket.SSLSocketClientInvoker.<init>(
	            at org.jboss.remoting.transport.sslsocket.TransportClientFactory.createClientInvoker(
	            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	            at sun.reflect.NativeMethodAccessorImpl.invoke(
	            at sun.reflect.DelegatingMethodAccessorImpl.invoke(
	            at java.lang.reflect.Method.invoke(
	            at org.jboss.remoting.InvokerRegistry.loadClientInvoker(
	            at org.jboss.remoting.InvokerRegistry.createClientInvoker(
	            at org.jboss.remoting.Client.connect(
	            at org.rhq.enterprise.communications.command.client.JBossRemotingRemoteCommunicator.getRemotingClient(
	            at org.rhq.enterprise.communications.command.client.JBossRemotingRemoteCommunicator.rawSend(
	            at org.rhq.enterprise.communications.command.client.JBossRemotingRemoteCommunicator.sendWithoutCallbacks(
	            at org.rhq.enterprise.communications.command.client.JBossRemotingRemoteCommunicator.sendWithoutInitializeCallback(
	            at org.rhq.enterprise.communications.command.client.JBossRemotingRemoteCommunicator.send(
	            at org.rhq.enterprise.communications.command.client.AbstractCommandClient.invoke(
	            at org.rhq.enterprise.communications.command.client.ClientCommandSender.send(

This is due to and/or -- not sure which one -- not being defined in the agent's configuration. By default, these properties are commented out in agent-configuration.xml and also have an empty value.

These properties should not be defined in the configuration map if they were not specified by the agent configuration. The error occurs specifically due to the attempt to assign null as the value for the hash map.

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

How reproducible:

Steps to Reproduce:
1.  Enable SSL/TLS encryption using sslsocket for agent-to-server communication.

    This can be done as per the JBoss ON documentation[1].

2.  Start the agent
Actual results:
ERROR [RHQ Server Polling Thread] (jboss.remoting.transport.socket.MicroSocketClientInvoker)- Error setting up SocketClientInvoker[72e5355f, sslsocket://]

And agent fails to completely start and communicate with its configured server.

Expected results:
No error and agent-to-server communication should work just fine.

Additional info:
To work around the issue, one just needs to re-configure the agent with a dummy value provided for this property.

Comment 1 Larry O'Leary 2013-03-22 18:37:41 EDT
To clarify, the offending property is is not required. Only must get a dummy value set in order to workaround this issue. 

In case it is not clear, this is specifically due to how the Hashtable is being built and each property, regardless of its value, is being passed in but <null> is not an allowed value for a Hashtable entry.

Note You need to log in before you can comment on or make changes to this bug.