directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Temple (JIRA)" <directory-...@incubator.apache.org>
Subject [jira] Commented: (DIREVE-329) JDBM - ArrayIndexOutOfBoundsException
Date Fri, 27 Jan 2006 10:06:58 GMT
    [ http://issues.apache.org/jira/browse/DIREVE-329?page=comments#action_12364198 ] 

Simon Temple commented on DIREVE-329:
-------------------------------------

This appears to be a problem with IBMs java optimisation.

The JVM was being invoked with -opt40

    -X  -opt<number>      optimization level for java program 0(interpret), 10,30, 40

The problem does not occur when optimisation is set to 10 or is not used.

Not using optimisation is now IBMs recommend approach as the JIT will execute code up to 15%
faster than that executed with optimisation level 40!

I suggest this issue is closed.

> JDBM - ArrayIndexOutOfBoundsException
> -------------------------------------
>
>          Key: DIREVE-329
>          URL: http://issues.apache.org/jira/browse/DIREVE-329
>      Project: Directory Server
>         Type: Bug
>   Components: jdbm database
>     Versions: 0.9.4
>  Environment:   	 IBM iSeries ( V5R2), Directory 0.9.4 SNAPSHOT (Nov 2005) IBM JDK 1.4.2
>     Reporter: Simon Temple
>     Assignee: Alex Karasulu

>
> 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. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message