
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
IBM iSeries ( V5R2), Directory 0.9.4 SNAPSHOT (Nov 2005) IBM JDK 1.4.2
|
|
| Resolution Date: |
27/Jan/06 10:31 PM
|
|
I call InitialDirContext every 40 seconds and after about fourty five minutes I get this exception.
java.lang.ArrayIndexOutOfBoundsException
at jdbm/recman/TranslationPage.get(TranslationPage.java:86)
at jdbm/recman/LogicalRowIdManager.fetch(LogicalRowIdManager.java:135)
at jdbm/recman/BaseRecordManager.update(BaseRecordManager.java:284)
at jdbm/recman/CacheRecordManager.updateCacheEntries(CacheRecordManager.java:405)
at jdbm/recman/CacheRecordManager.commit(CacheRecordManager.java:339)
at org/apache/ldap/server/partition/impl/btree/jdbm/JdbmIndex.sync(JdbmIndex.java:489)
at org/apache/ldap/server/partition/impl/btree/jdbm/JdbmDirectoryPartition.sync(JdbmDirectoryPartition.java:248)
at org/apache/ldap/server/partition/DefaultDirectoryPartitionNexus.sync(DefaultDirectoryPartitionNexus.java:290)
at org/apache/ldap/server/DefaultDirectoryService.sync(DefaultDirectoryService.java:223)
at org/apache/ldap/server/jndi/AbstractContextFactory.getInitialContext(AbstractContextFactory.java:82)
at javax/naming/spi/NamingManager.getInitialContext(NamingManager.java:662)
at javax/naming/InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax/naming/InitialContext.init(InitialContext.java:219)
at javax/naming/directory/InitialDirContext.<init>(InitialDirContext.java:80)
2006-01-24 13:30:44,544 First Call
2006-01-24 14:18:56,444 First Error
Restarting normally fixes the problem (for another 40-60 mins).
We do not experience these problems on our Windows or UNIX platforms.
|
|
Description
|
I call InitialDirContext every 40 seconds and after about fourty five minutes I get this exception.
java.lang.ArrayIndexOutOfBoundsException
at jdbm/recman/TranslationPage.get(TranslationPage.java:86)
at jdbm/recman/LogicalRowIdManager.fetch(LogicalRowIdManager.java:135)
at jdbm/recman/BaseRecordManager.update(BaseRecordManager.java:284)
at jdbm/recman/CacheRecordManager.updateCacheEntries(CacheRecordManager.java:405)
at jdbm/recman/CacheRecordManager.commit(CacheRecordManager.java:339)
at org/apache/ldap/server/partition/impl/btree/jdbm/JdbmIndex.sync(JdbmIndex.java:489)
at org/apache/ldap/server/partition/impl/btree/jdbm/JdbmDirectoryPartition.sync(JdbmDirectoryPartition.java:248)
at org/apache/ldap/server/partition/DefaultDirectoryPartitionNexus.sync(DefaultDirectoryPartitionNexus.java:290)
at org/apache/ldap/server/DefaultDirectoryService.sync(DefaultDirectoryService.java:223)
at org/apache/ldap/server/jndi/AbstractContextFactory.getInitialContext(AbstractContextFactory.java:82)
at javax/naming/spi/NamingManager.getInitialContext(NamingManager.java:662)
at javax/naming/InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax/naming/InitialContext.init(InitialContext.java:219)
at javax/naming/directory/InitialDirContext.<init>(InitialDirContext.java:80)
2006-01-24 13:30:44,544 First Call
2006-01-24 14:18:56,444 First Error
Restarting normally fixes the problem (for another 40-60 mins).
We do not experience these problems on our Windows or UNIX platforms. |
Show » |
| No work has yet been logged on this issue.
|
|