My Oracle Support Banner

OVD 11g: "Timer Already Cancelled" Error When Saving Adapter Changes in ODSM (Doc ID 2018912.1)

Last updated on NOVEMBER 22, 2019

Applies to:

Oracle Virtual Directory - Version 11.1.1.0 and later
Information in this document applies to any platform.

Symptoms

Receiving "Timer already cancelled" error when saving changes in Oracle Directory Services Manager (ODSM) to Oracle Virtual Directory (OVD) 11g.

Newly configured OVD server had been working fine. Made a change to utilize DN matching, and it seemed to work fine for a couple of days.
Then created a new LDAP adapter for and additional LDAP domain, and started getting error "Timer already cancelled."

The wls_ods1-diagnostic.log shows:

[2015-06-08T14:24:35.735-05:00] [wls_ods1] [NOTIFICATION] [] [oracle.ldap.odsm.ui.common.Visit] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: <ECID>] [APP: odsm#11.1.1.2.0] [DSID: xxxxxx] createNavigationItem constructor
[2015-06-08T14:24:39.788-05:00] [wls_ods1] [NOTIFICATION] [] [oracle.ldap.odsm.model.ovd.config.adapters.APBaseCfg] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: <ECID>] [APP: odsm#11.1.1.2.0] [DSID: xxxxx] saveChanges[[
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: Error loading adapter Adapter : java.lang.IllegalStateException: Timer already cancelled.
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:<HOSTNAME>

Error loading adapter Adapter : java.lang.IllegalStateException: Timer already cancelled.
at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1588)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:442)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:388)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:232)

...<etc>...

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.