The warning message in the agent log:
2022-01-18T09:07:05.708-05:00 | WARN | instana-http-client-thread-2 | LoggerEndpoint | com.instana.agent - 1.1.619 | JVM (45104) - execute query failed: WFLYCTL0217: Child resource '"socket-binding-group" => "standard-sockets"' not foundappears every 10 minutes because the agent cannot read socket-binding-group as defined in
<JBOSS_INSTALL_DIR>standalone/configuration/standalone.xml
Ask for sharing share that file here (or at least the <socket-binding-group> and the <interfaces> sections)?
It is most probably renamed and the agent does not find it using the common socket-binding-group name.
Additionally, this warning message is not related to monitoring EJB-deployments.
When we noticed messages like:
2022-01-16T07:37:35.891-05:00 | WARN | instana-agent-scheduler-thread-4 | yDiscoveryTicker | com.instana.agent - 1.1.619 | Discovery for com.instana.plugin.jbossas took too long (23034 ms)
Customer should add more heap memory to the Instana agent by increasing DEFAULT_AGENT_MAX_MEM and DEFAULT_HEAP_MAX_MEM values in the agent's bin/setenv script and restart the agent.
The standalone controller version that uses standard-sockets by default is supported by Instana, whereas the domain controller uses server-group definitions with a socket-binding-group reference is not.
If the customer is using the full profile that uses full-sockets as the socket-binding-group, as the domain.xml configuration shows:
<server-groups>
<server-group name="main-server-group" profile="full">
<jvm name="default">
<heap size="1000m" max-size="1000m"/>
<permgen max-size="256m"/>
</jvm>
<socket-binding-group ref="full-sockets"/>
</server-group>
<server-group name="other-server-group" profile="full-ha">
<jvm name="default">
<heap size="1000m" max-size="1000m"/>
<permgen max-size="256m"/>
</jvm>
<socket-binding-group ref="full-ha-sockets"/>
</server-group>
</server-groups>
It can be supported in the future by converting this ticket to a feature request.
Comments