Ironically we also hit this problem yesterday ,,, I don't know why it has waited this long to show up. Removing that piece of code will be the simplest fix but I suspect its a sign of a problem elsewhere.
On Fri, Oct 6, 2017 at 8:53 AM, Burn Lewis (JIRA) <[email protected]> wrote: > > [ https://issues.apache.org/jira/browse/UIMA-5605?page= > com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > > Burn Lewis updated UIMA-5605: > ----------------------------- > Fix Version/s: future-DUCC > > > DUCC scheduler ArrayIndexOutOfBoundsException > > --------------------------------------------- > > > > Key: UIMA-5605 > > URL: https://issues.apache.org/jira/browse/UIMA-5605 > > Project: UIMA > > Issue Type: Bug > > Components: DUCC > > Affects Versions: 2.2.1-Ducc > > Reporter: Jörg W > > Fix For: future-DUCC > > > > > > The scheduler stops scheduling and ducc-mon indicates inresposive > ResourceManager. > > rm.log (Trace): > > 05 Okt 2017 11:29:13,336 TRACE RM.NodepoolScheduler- N/A > detectFragmentation Freed shares 246 on machine xxx.xxx.xx > > 05 Okt 2017 11:29:13,336 TRACE RM.NodepoolScheduler- N/A > detectFragmentation Update v before: NP[ --default-- ] v: 0 0 0 0 > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > > 05 Okt 2017 11:29:13,336 FATAL RM.ResourceManagerComponent- N/A > runScheduler > > java.lang.ArrayIndexOutOfBoundsException > > An ArrayIndexOutOfBoundsException can occur in the NodepoolScheduler > class at line 2422: > > vmach_j[free]++; > > Quickfix: comment it out. It seems only be used for logging (trace). > > > > > > -- > This message was sent by Atlassian JIRA > (v6.4.14#64029) >
