Since RHQ-1145 has been implemented we need to actually use this feature to see if we have any more problems with large messages to/from the agent.
Read here to learn how to turn this on: http://support.rhq-project.org/display/RHQ/Design-DebuggingCommunications Basics: 1) Go to the agent's log4j.xml file and turn NONE to TRACE under the OutgoingCommandTrace category: <category name="org.rhq.enterprise.communications.command.client.OutgoingCommandTrace"> <priority value="TRACE"/> <appender-ref ref="COMMANDTRACE"/> </category> This assumes you are NOT using RHQ_AGENT_DEBUG=true. If you are, then copy log4j.xml and name it log4j-debug.xml and make the same change described above to it. 2) when you start the agent, pass in these options to rhq-agent.bat/sh: -Drhq.trace-command-size-threshold=99999 -Drhq.trace-command-response-size-threshold=99999 This will log messages in the command-trace.log if a command or response object is 100K large or larger. I think that should be a good threshold to look for.
You can use the agent prompt command "debug --comm=true" to turn on this tracing with a set of default rhq.trace-command sysprop settings.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1164
mass move off the qa triage list. These are tasks for dev.
Closing per triage, though will open a new qe task against provisioning so QE can see how this is used.