Stop Errors in Introscope.log for [ERROR] [IntroscopeAgent.EPAgent] jetty start fail in MQ Monitor agent log

Products

• DX Application Performance Management
• DX APM SaaS
• CA Application Performance Management (APM / Wily / Introscope)
• CA Application Performance Management Agent (APM / Wily / Introscope)

Issue/Introduction

Is there a way to stop the following errors coming out at agent start up - when another agent is already running - the errors appear in the IIB IntroscopeAgent.log

2/01/22 11:30:58 AM GMT [ERROR] [IntroscopeAgent.EPAgent] jetty start fail
java.io.IOException: Failed to bind to 0.0.0.0/0.0.0.0:8080
        at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:349)
        at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:310)
        at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
        at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:234)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:72)
        at org.eclipse.jetty.server.Server.doStart(Server.java:386)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:72)
        at com.wily.introscope.epagent.http.HttpServer.start(HttpServer.java:132)
        at com.wily.introscope.agent.epa.EPAPluginRunner.start(EPAPluginRunner.java:151)
        at com.wily.introscope.agent.uma.UnifiedMonitoringAgent.start(UnifiedMonitoringAgent.java:241)
        at com.wily.introscope.agent.uma.UnifiedMonitoringAgent.main(UnifiedMonitoringAgent.java:290)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
        at java.lang.reflect.Method.invoke(Method.java:508)
        at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:325)
        at java.lang.Thread.run(Thread.java:811)
Caused by:
java.net.BindException: Address already in use
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:460)
        at sun.nio.ch.Net.bind(Net.java:452)
        at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:253)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:86)
        at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:345)
        ... 16 more
2/01/22 11:30:58 AM GMT [INFO] [IntroscopeAgent.EPAgent] EPAgent Plugins successfully loaded.

Environment

Release : 2x.x

Component :

Cause

By default the APMIA agent (which the MQ monitor agent uses) has the http listener enabled and configured to use port 8080. There for if multipe agents are started on the same machine with the default setting they will conflict.

Resolution

. If you are only using the agent for IIB / MQ purposes the you can safely disable the EPA Listen port by commenting the following entry in the IntroscopeAgent.profile

# Network port on which to listen for HTTP GET commands. If commented out or
# left unconfigured then EPAgent will not listen for HTTP commands
#
# Changing this property requires restarting the Monitored Process
introscope.epagent.config.httpServerPort=8080

If you wish to keep the feature open then you would need to define a unique port for each agent instance that could be running on that system via that property value