search cancel

Error Index 63 out of bounds for length 63 when adding resource

book

Article ID: 228790

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

When adding a resource to Team - Staff in Classic or Modern UX anerror is thrown:

Error message: Index 63 out of bounds for length 63
One or more resources could not be added. Possibly due to security.

Full Error:

INFO  2021-11-17 13:05:15,116 [http-nio-8080-exec-23] niku.blobcrack (clarity:admin:18580081__CB1801A4-2692-4233-B1DB-563794ABA4E8:PPM_REST_API) ### Curve set size is 1
INFO  2021-11-17 13:05:15,125 [http-nio-8080-exec-23] niku.blobcrack (clarity:admin:18580081__CB1801A4-2692-4233-B1DB-563794ABA4E8:PPM_REST_API) delete for request W_ALC completed in 1 MS 
INFO  2021-11-17 13:05:15,126 [http-nio-8080-exec-23] niku.blobcrack (clarity:admin:18580081__CB1801A4-2692-4233-B1DB-563794ABA4E8:PPM_REST_API) 
java.lang.IndexOutOfBoundsException: Index 63 out of bounds for length 63 
at java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64) 
at java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70) 
at java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248) 
at java.base/java.util.Objects.checkIndex(Objects.java:372) 
at java.base/java.util.ArrayList.get(ArrayList.java:459) 
at com.niku.blobcrack.BlobCrackDB.addSlices(BlobCrackDB.java:923) 
at com.niku.blobcrack.BlobCrackDB.processBatchData(BlobCrackDB.java:1305) 
at com.niku.blobcrack.BlobCrackDB.processRecordSet(BlobCrackDB.java:1254) 
at com.niku.blobcrack.InstaSlice.createSlices(InstaSlice.java:282) 
at com.niku.xql2.rules.BaseRule.invokeBlobcrackSlicer(BaseRule.java:1010) 
at com.niku.xql2.rules.BaseRule.invokeBlobcrackSlicer(BaseRule.java:987) 
at com.niku.xql2.pmd.rules.TeamRule.onPostUpdate(TeamRule.java:730) 
at com.niku.xql2.odf.ODFRecord.update(ODFRecord.java:263)

Environment

Release : 15.9.3

Component : CLARITY TIME SLICING

Resolution

This error typically resolves by itself. Running the jobs or clearing application cache may help