DX Application Performance Management

 View Only
  • 1.  Prod Collectors start and then shutdown

    Posted Jul 25, 2019 09:57 AM
    Edited by Manish Parikh Jul 25, 2019 09:59 AM
    I get the following ERRORs...
    ------------------------------------

    7/24/19 08:03:04.181 PM EDT [INFO] [main] [Manager.HighConcurrencyTransportServer] Starting High Concurrency Transport Server
    7/24/19 08:03:04.184 PM EDT [ERROR] [main] [Manager.PostOfficeHub] The EM server was unable to bind to a port. This could be caused by another EM or some other process binding to the same port. Server failed to start listening for incoming default socket connections on port 5001

    7/24/19 08:05:04.685 PM EDT [ERROR] [Thread-29] [Manager.com.timestock.tess.services.initialization.RunInitializers] Exception in bean initializer; some features won't work
    java.util.concurrent.ExecutionException: com.wily.util.exception.UnexpectedExceptionError: Service com.wily.apm.tess.isengard.ITessMessageSubscriptionServiceLocal not found
    at java.util.concurrent.FutureTask.report(FutureTask.java:122)
    at java.util.concurrent.FutureTask.get(FutureTask.java:192)
    at com.timestock.tess.services.initialization.RunInitializers$RunInitializeMethods.run(RunInitializers.java:111)
    Caused by: com.wily.util.exception.UnexpectedExceptionError: Service com.wily.apm.tess.isengard.ITessMessageSubscriptionServiceLocal not found
    at com.wily.introscope.osgi.BundleUtilities.getLocalServiceSafe(BundleUtilities.java:113)
    at com.wily.introscope.osgi.BundleUtilities.getLocalServiceSafe(BundleUtilities.java:99)
    at com.wily.introscope.osgi.ABundleActivator.getLocalServiceSafe(ABundleActivator.java:149)
    at com.timestock.tess.services.service.ServicesManager.initialize(ServicesManager.java:194)
    at com.timestock.tess.services.initialization.RunInitializers$IntializeWrapper.call(RunInitializers.java:87)
    at com.timestock.tess.services.initialization.RunInitializers$IntializeWrapper.call(RunInitializers.java:1)
    at com.timestock.tess.util.ThreadPool$ConcurrentCallableTask.call(ThreadPool.java:218)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)
    Caused by: com.wily.introscope.osgi.LocalServiceNotFoundException: Service com.wily.apm.tess.isengard.ITessMessageSubscriptionServiceLocal not found
    at com.wily.introscope.osgi.BundleUtilities.getLocalService(BundleUtilities.java:161)
    at com.wily.introscope.osgi.BundleUtilities.getLocalServiceSafe(BundleUtilities.java:107)
    -------------------------------------------
    Any idea how I can fix this?

    ------------------------------
    Thanks in advance,

    Cheers,
    Manish A. Parikh
    BAE Systems Inc.
    ------------------------------


  • 2.  RE: Prod Collectors start and then shutdown

    Broadcom Employee
    Posted Jul 25, 2019 09:59 AM
    Manish,
    We're going to need the entire EM log in DEBUG mode.

    ------------------------------
    Custom Solution Architect
    Broadcom
    ------------------------------



  • 3.  RE: Prod Collectors start and then shutdown
    Best Answer

    Posted Jul 25, 2019 11:08 AM
    nvrmd, looks like it's all gone now. I restarted the EM and all looks good.

    Thanks

    ------------------------------
    Thanks in advance,

    Manish A. Parikh
    BAE Systems Inc.
    ------------------------------



  • 4.  RE: Prod Collectors start and then shutdown

    Posted Jul 25, 2019 02:19 PM

    Hello,
    are you on a Linux system?

    > The EM server was unable to bind to a port. This could be caused by another EM or some other
    > process binding to the same port. Server failed to start listening for incoming default socket
    > connections on port 5001

    The port is still in use, we get this problem all the time we restart der EM to fast.
    We wait some minutes after the EM stopped and every thing works well.
    Ugly, but a general tcp/ip problem.

    With regards,
    Lutz

    p.s.
    You can set introscope.enterprisemanager.serversockets.reuseaddr=true
    in the IntroscopeEnterpriseManager.properties file, to reuse the ports, but this is not a good idea in general, but fix problems like yours.



    ------------------------------
    Finanz Informatik
    ------------------------------