DX Application Performance Management

  • Private Community
Back to discussions
Expand all | Collapse all

Failed to connect to the Introscope Enterprise Manager at localhost:5001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory

  • 1.  Failed to connect to the Introscope Enterprise Manager at localhost:5001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory

    Posted Oct 16, 2014 09:38 AM

    Hai Everybody,

     

    We have installed APM Agent for weblogic. The Agent is started and it trying to connect Enterprise mnager at localhost:5001 even though the Enterprise manager host name & port number are mentioned properly on IntroscopeAgent.profile

     

    introscope.agent.enterprisemanager.transport.tcp.host.DEFAULT=qdcls1158

    introscope.agent.enterprisemanager.transport.tcp.port.DEFAULT=5014

    introscope.agent.enterprisemanager.transport.tcp.socketfactory.DEFAULT=com.wily.isengard.postofficehub.link.net.DefaultSocketFactory

     

    Could you advise?

     

    Regards,

     

    Francis.



  • 2.  Re: Failed to connect to the Introscope Enterprise Manager at localhost:5001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory

    Broadcom Employee
    Posted Oct 16, 2014 09:44 AM

    It sounds like the agent profile cannot be found, can you check the path to the agent profile and make sure it is correct. If the Agent.jar can be loaded but the agent profile cannot be found, the Agent will automatically try to connect to an EM on localhost at 5001.



  • 3.  Re: Failed to connect to the Introscope Enterprise Manager at localhost:5001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory

    Posted Oct 24, 2014 03:29 PM

    The agent has configuration locations that it searches when it can not load the configuration file named within the JVM bootstrap path.

    1.  Check your bootstrap argument to insure the path is correct (escaped maybe)

    2.  Check the permissions of the configuration file.  In WebSphere we had to put the agent directory under the websphere directory so that it could be read.

    3.  Do a system search for the intorscopeAgent.profile to see if there are any other instances and one by one, change it to see if the agent is picking a different configuration file up.

     

    Hope this helps

     

    Billy