OVD 11g Search Fails To Returns All Results / Search Halts And Throws Operations Error / OVD Log Shows java.lang.OutOfMemoryError Exception (Doc ID 1088258.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Virtual Directory - Version 11.1.1.1.0 to 11.1.1.2.0 [Release 11g]
Information in this document applies to any platform.

Symptoms

Oracle Virtual Directory (OVD) 11g (11.1.1.1.0 or 11.1.1.2.0)

OVD throwing a java out of memory exception during an ldapsearch.  The ldapsearch halts when OVD throws the error.

Steps to reproduce:
1. Install OVD 11g
2. Create adapters, i.e.:
- an Oracle Access Manager / Active Directory (OAM/AD) mapper adapter
- an Oracle Internet Directory (OID) adapter
- an eDirectory (eDir) adapter
3. Create a join adapter with AD as primary and OID and eDir as secondaries
4. Run a wildcard search against OVD that will return more than 7000 results, for example:

ldapsearch -x -h <ovd hostname> -p <ovd port> -D "cn=orcladmin" -w <password> -s sub -b "OU=JoinView,DC=mycompany,DC=com" objectclass=*



Upon further testing, found that the error is not thrown when searching through the OID adapters, but able to consistently reproduce the error when searching through the "OAM/AD with mapper" adapter which is used to connect to the AD backend(s).

By default the AD has size limit set to 1000 for ldapsearch returns, but able to get around it when searching directly against AD by using an ldap browser that has paging control options to return all entries from AD.

In trying to do the same with OVD, so that OVD can return all entries instead of capping at 1000, changed the proxied page size in the OVD adapter configuration from 0 to 500 but it did not help.  Also tried a few other values but OVD still does not return all the results from AD.  After a few minutes the ldapsearch just halts with an operational error (or operations error), and the OVD log files report the out of memory java exceptions.


The diagnostic.log shows:

]]
[2010-04-15T11:39:50.351-04:00] [octetstring] [ERROR] [OVD-60182] [com.octetstring.vde.OperationHandler] [tid: 14] [ecid: 0000IW284fFFo2Tqy8EgMG1BlRAX0000BM,0] [arg: null] Exception: null.[[
java.lang.OutOfMemoryError
    at com.octetstring.vde.backend.jndi.BackendJNDI.get(BackendJNDI.java:617)
    at com.octetstring.vde.chain.Chain.nextGet(Chain.java:297)
    at com.octetstring.vde.chain.plugins.performance.MonitorPerformance.monitorSearch(MonitorPerformance.java:506)
    at com.octetstring.vde.chain.plugins.performance.MonitorPerformance.get(MonitorPerformance.java:450)
    at com.octetstring.vde.chain.Chain.nextGet(Chain.java:308)
    at com.octetstring.vde.chain.PluginChain.runGet(PluginChain.java:234)
    at com.octetstring.vde.chain.PluginManager.runGet(PluginManager.java:489)
    at com.octetstring.vde.chain.PluginManager.runGet(PluginManager.java:427)
    at com.octetstring.vde.backend.AdapterServiceInterface.getByAdapter(AdapterServiceInterface.java:649)
    at com.octetstring.vde.backend.AdapterServiceInterface.getByAdapter(AdapterServiceInterface.java:606)
    at com.octetstring.vde.join.Joiner.joinByEntry(Joiner.java:509)
    at com.octetstring.vde.join.SimpleJoiner.joinByEntry(SimpleJoiner.java:340)
    at com.octetstring.vde.join.JoinerEntrySet.join(JoinerEntrySet.java:338)
    at com.octetstring.vde.join.JoinerEntrySet.getNext(JoinerEntrySet.java:264)
    at com.octetstring.vde.chain.ChainEntrySet.getNext(ChainEntrySet.java:114)
    at com.octetstring.vde.chain.plugins.forkjoin.LinkEntrySet.hasMore(LinkEntrySet.java:79)
    at com.octetstring.vde.operation.SearchOperation.run(SearchOperation.java:339)
    at com.octetstring.vde.MessageHandler.doSearch(MessageHandler.java:408)
    at com.octetstring.vde.MessageHandler.answerRequest(MessageHandler.java:139)
    at com.octetstring.vde.OperationHandler.run(OperationHandler.java:57)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:736)

]]


And a debugged diagnostic log (with TRACE:32 set for Dump debugging) may show:

]]
[2010-04-15T13:46:41.669-04:00] [octetstring] [ERROR] [OVD-60182] [com.octetstring.vde.OperationHandler] [tid: 36] [ecid: 0000IW2_6u5Fo2Tqy82jMG1BlbK400007Q,0] [arg: null] Exception: null.[[
java.lang.OutOfMemoryError
    at java.lang.J9VMInternals.getStackTrace(Native Method)
    at java.lang.Throwable.getInternalStackTrace(Throwable.java:198)
    at java.lang.Throwable.getStackTrace(Throwable.java:141)
    at oracle.core.ojdl.logging.ODLLogRecord.inferCaller(ODLLogRecord.java:137)
    at oracle.core.ojdl.logging.ODLLogRecord.getSourceClassName(ODLLogRecord.java:95)
    at oracle.core.ojdl.logging.ODLFormatter.toLogMessage(ODLFormatter.java:408)
    at oracle.core.ojdl.logging.ODLFormatter.toLogMessage(ODLFormatter.java:217)
    at oracle.core.ojdl.logging.ODLHandler.publish(ODLHandler.java:478)
    at oracle.core.ojdl.logging.ODLLogger.doLog(ODLLogger.java:732)
    at oracle.core.ojdl.logging.ODLLogger.logRec(ODLLogger.java:756)
    at oracle.core.ojdl.logging.ODLLogger.logRec(ODLLogger.java:743)
    at oracle.core.ojdl.logging.ODLLogger.log(ODLLogger.java:538)
    at com.octetstring.vde.util.VDELogger.debug(VDELogger.java:147)
    at com.octetstring.vde.join.JoinerEntrySet.join(JoinerEntrySet.java:323)
    at com.octetstring.vde.join.JoinerEntrySet.getNext(JoinerEntrySet.java:264)
    at com.octetstring.vde.chain.ChainEntrySet.getNext(ChainEntrySet.java:114)
    at com.octetstring.vde.chain.plugins.forkjoin.LinkEntrySet.hasMore(LinkEntrySet.java:79)
    at com.octetstring.vde.operation.SearchOperation.run(SearchOperation.java:339)
    at com.octetstring.vde.MessageHandler.doSearch(MessageHandler.java:408)
    at com.octetstring.vde.MessageHandler.answerRequest(MessageHandler.java:139)
    at com.octetstring.vde.OperationHandler.run(OperationHandler.java:57)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:736)

]]
[2010-04-15T13:46:41.670-04:00] [octetstring] [TRACE] [] [com.octetstring.vde.DoSManager] [tid: 36] [ecid: 0000IW2_6u5Fo2Tqy82jMG1BlbK400007Q,0] [SRC_METHOD: debug] [SRC_CLASS: com.octetstring.vde.util.VDELogger] UnBind: cn=orcladmin/<IP address>.


A javacore dump may also be generated.

Changes

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms