2.2 Embedded Agent
akarl Mar 6, 2009 9:11 AMI just installed the 2.2 beta and I am having trouble getting the embedded agent to connect to the instance. To be clear, I am running this in a VMWare instance of Ubuntu although I do not believe that to be the problem.
I have used all of the installation defaults for the server other than enabling the embedded agent per the following configuration.
rhq.server.embedded-agent.enabled=true rhq.server.embedded-agent.name=jopr-test-embedded rhq.server.embedded-agent.reset-configuration=true rhq.server.embedded-agent.disable-native-system=false
The embedded-agent.log shows the following error message indicating that is was not able to connect to the server to register.
I have not connected any other agents to the server although that is something I plan to try.
07:51:24,654 INFO [Embedded RHQ Agent Main] (org.rhq.enterprise.communications.ServiceContainer)- {ServiceContainer.global-concurrency-limit-disabled}Global concurrency limit has been disabled - there is no limit to the number of incoming commands allowed 07:51:26,227 INFO [Embedded RHQ Agent Main] (org.rhq.enterprise.communications.ServiceContainer)- {ServiceContainer.started}Service container started - ready to accept incoming commands 07:51:26,228 INFO [Embedded RHQ Agent Main] (org.rhq.enterprise.agent.AgentMain)- {AgentMain.no-auto-detect}Neither server auto-detection nor polling is enabled - the client will be allowed to start sending commands immediately, but when the server is offline, be prepared for alot of errors to be logged 07:51:27,651 ERROR [RHQ Agent Registration Thread] (enterprise.communications.command.client.ClientCommandSenderTask)- {ClientCommandSenderTask.send-failed}Failed to send command [Command: type=[remotepojo]; cmd-in-response=[false]; config=[{rhq.agent-name=jopr-test-embedded, rhq.send-throttle=true}]; params=[{invocation=NameBasedInvocation[registerAgent], targetInterfaceName=org.rhq.core.clientapi.server.core.CoreServerService}]]. Cause: org.jboss.remoting.CannotConnectException:Can not connect http client invoker. -> java.net.ConnectException:Connection refused. Cause: org.jboss.remoting.CannotConnectException: Can not connect http client invoker.
This error repeats as the agent retries.