Hey fellow listers.
I've got an issue with an embedded instance of apacheds in a trivial
piece of java code. For reasons I have been unable to diagnose
so far, it will run happily for about a week or so, then it will
suddenly ramp up the load on the server it's running on, with the only
way to recover it, being to delete the physical directory where the
records are stored and start from scratch. What's puzzling me is
that it's definitely not load related as the queries an operations to
LDAP are very lightweight and infrequent. What I do get in the logs
are loads of these
pool-4-thread-18 ERROR registries.DefaultAttributeTypeRegistry -
attributeType w/ OID 1.3.6.1.4.1.1466.115.121.1.12 not registered!
pool-4-thread-19 ERROR registries.DefaultAttributeTypeRegistry -
attributeType w/ OID 1.3.6.1.4.1.1466.115.121.1.12 not registered!
pool-4-thread-19 WARN context.SearchingOperationContext - Requested
attribute dn does not exist in the schema, it will be ignored
pool-4-thread-18 WARN context.SearchingOperationContext - Requested
attribute dn does not exist in the schema, it will be ignored
NioProcessor-2 WARN ldap.LdapProtocolHandler - Null LdapSession given
to cleanUpSession.
pool-4-thread-19 ERROR registries.DefaultAttributeTypeRegistry -
attributeType w/ OID 1.3.6.1.4.1.1466.115.121.1.12 not registered!
pool-4-thread-17 ERROR registries.DefaultAttributeTypeRegistry -
attributeType w/ OID 1.3.6.1.4.1.1466.115.121.1.12 not registered!
and
pool-4-thread-19 WARN ldap.LdapProtocolHandler - Unexpected exception
forcing session to close: sending disconnect notice to client.
java.lang.NullPointerException
at
org
.apache
.directory
.server
.ldap
.handlers.LdapRequestHandler.handleMessage(LdapRequestHandler.java:129)
at
org
.apache
.directory
.server
.ldap
.handlers.LdapRequestHandler.handleMessage(LdapRequestHandler.java:56)
at
org
.apache
.mina
.handler
.demux.DemuxingIoHandler.messageReceived(DemuxingIoHandler.java:232)
at
org
.apache
.directory
.server
.ldap.LdapProtocolHandler.messageReceived(LdapProtocolHandler.java:194)
at org.apache.mina.core.filterchain.DefaultIoFilterChain
$TailFilter.messageReceived(DefaultIoFilterChain.java:721)
at
org
.apache
.mina
.core
.filterchain
.DefaultIoFilterChain
.callNextMessageReceived(DefaultIoFilterChain.java:433)
at
org.apache.mina.core.filterchain.DefaultIoFilterChain.access
$1200(DefaultIoFilterChain.java:47)
at org.apache.mina.core.filterchain.DefaultIoFilterChain
$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:801)
at
org.apache.mina.core.filterchain.IoFilterEvent.fire(IoFilterEvent.java:
71)
at org.apache.mina.core.session.IoEvent.run(IoEvent.java:63)
at org.apache.mina.filter.executor.UnorderedThreadPoolExecutor
$Worker.runTask(UnorderedThreadPoolExecutor.java:480)
at org.apache.mina.filter.executor.UnorderedThreadPoolExecutor
$Worker.run(UnorderedThreadPoolExecutor.java:434)
at java.lang.Thread.run(Thread.java:619)
pool-4-thread-19 WARN ldap.LdapProtocolHandler - Null LdapSession
given to cleanUpSession.
NioProcessor-3 WARN ldap.LdapProtocolHandler - Null LdapSession given
to cleanUpSession.
The only thing I can think of causing the NPE's is a monitoring
application that we have, that connects and disconnects from ADS to
confirm
that it's still there...Apart from that I have no plausible
explanation for the high load. I'm currently using 1.5.6 compiled from
source.
Thanks,
Yiannis
