Managed Gateway system driver is getting stopped immedietely


I am facing an issue with Managed Gateway system driver.
It is getting stopped immediately after starting driver.
I checked the driver logs. I am finding below error:
Unable to start MSGateway server:
java.lang.IllegalStateException: Timer already cancelled.

Kindly help ASAP. :(


--
anjha0049
------------------------------------------------------------------------
anjha0049's Profile: https://forums.netiq.com/member.php?userid=5837
View this thread: https://forums.netiq.com/showthread.php?t=55427

  • As always, please provide a trace. The driver logs are not meant for
    troubleshooting, and traces are.


    --
    Good luck.

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below...

  • ab;265491 Wrote:
    > As always, please provide a trace. The driver logs are not meant for
    > troubleshooting, and traces are.
    >
    >
    > --
    > Good luck.
    >
    > If you find this post helpful and are logged into the web interface,
    > show your appreciation and click on the star below...



    Hi,

    Kindly find the trace statements below:

    <nds dtdversion="3.5" ndsversion="8.x">
    <source>
    <product build="20150810130956" instance="Managed System Gateway
    Driver" version="4.0.2.0">Identity Manager Managed System Gateway
    Driver</product>
    <contact>NetIQ Corporation</contact>
    </source>
    <output>
    <status level="fatal" type="driver-general">Unable to start
    MSGateway server:
    java.lang.IllegalStateException: Timer already cancelled.</status>
    </output>
    </nds>
    [02/24/16 13:41:59.482]:gateway PT:Applying input transformation
    policies.
    [02/24/16 13:41:59.482]:gateway PT:Applying policy:
    % CCNOVLIDMMSGWB-itp-InitServerCache%-C.
    [02/24/16 13:41:59.482]:gateway PT: Applying to status #1.
    [02/24/16 13:41:59.482]:gateway PT: Evaluating selection criteria for
    rule 'Make sure we only run once and when we're ready'.
    [02/24/16 13:41:59.482]:gateway PT: (if-local-variable
    'objectClass' match ". ") = TRUE.
    [02/24/16 13:41:59.482]:gateway PT: (if-local-variable
    'srvrCacheInitialized' equal "true") = TRUE.
    [02/24/16 13:41:59.482]:gateway PT: Rule selected.
    [02/24/16 13:41:59.482]:gateway PT: Applying rule 'Make sure we only
    run once and when we're ready'.
    [02/24/16 13:41:59.482]:gateway PT: Action: do-break().
    [02/24/16 13:41:59.482]:gateway PT:Policy returned:
    [02/24/16 13:41:59.482]:gateway PT:
    <nds dtdversion="3.5" ndsversion="8.x">
    <source>
    <product build="20150810130956" instance="Managed System Gateway
    Driver" version="4.0.2.0">Identity Manager Managed System Gateway
    Driver</product>
    <contact>NetIQ Corporation</contact>
    </source>
    <output>
    <status level="fatal" type="driver-general">Unable to start
    MSGateway server:
    java.lang.IllegalStateException: Timer already cancelled.</status>
    </output>


    --
    anjha0049
    ------------------------------------------------------------------------
    anjha0049's Profile: https://forums.netiq.com/member.php?userid=5837
    View this thread: https://forums.netiq.com/showthread.php?t=55427

  • anjha0049 wrote:

    >
    > ab;265491 Wrote:
    > > As always, please provide a trace. The driver logs are not meant
    > > for troubleshooting, and traces are.
    > >
    > >
    > > --
    > > Good luck.
    > >
    > > If you find this post helpful and are logged into the web interface,
    > > show your appreciation and click on the star below...

    >
    >
    > Hi,
    >
    > Kindly find the trace statements below:
    >


    This is not sufficent, we need a level 3 trace of the entire driver
    startup up until this point.

  • Hi NNTP,


    Thanks for your suggestion.
    I got it resolved.Actually, my environment is comprising of windows
    servers and iManager is deployed over Tomcat.
    This warning is part of memory leak protection which got shipped with
    Tomcat 6.0.26. In this particular issue, you seem to be using
    commons-pool as connection pool. It is not properly terminating the
    timer thread. This has already been reported as a bug: issue POOL-161.
    It's not fixed yet.
    In order to resolve this, I restarted the EDirectory (Although not
    required), along with tomcat restart (Required).
    Once, iManager was up. I started the driver