I am using 2.7 b278 and have been receiving a lot of java errors lately. Last week we had an out of memory issue, we forced Omniscope to use 1600MB via the config file. We still received an error 2 days ago, report re-runs fine. It seems to be an issue with the scheduler itself.
Today I came into the office to find the below chains failed off with another Java error, please advise?
2012.03.08 01:30:52.222 ERROR: Could not execute action
2012.03.08 01:30:52.222 Warning: Action completed successfully but warnings generated:
Clearing soft references... 87 cleared Clearing object cache... 0 cleared Running extended garbage collector... Memory diagnostics: Used: 51.31 MB Allocated: 242.68 MB Max allocation: 1.51 GB Potential free: 1.46 GB Object cache: 0 (0/2 workers) Soft references: 1 Chain action "IBOPS,CSPlus,IBDashboard,IBEQT,FIDOV,FIDVolumeCU," failure: java.lang.IllegalStateException: Already open at com.visokio.util.un.c(un.java:58) at com.visokio.kindling.ad.a(ad.java:28) at com.visokio.kindling.ad.a(ad.java:11) at com.visokio.kindling.fd.a(fd.java:5) at com.visokio.kindling.fd.b(fd.java:8) at com.visokio.kindling.fd.b(fd.java:14) at com.visokio.kindling.fd.d(fd.java:30) at com.visokio.kindling.fd.a(fd.java:35) at com.visokio.kindling.fd.c(fd.java:25) at com.visokio.kindling.nc.a(nc.java:25) at com.visokio.kindling.nc.c(nc.java:9) at com.visokio.kindling.q.c(q.java:128) at com.visokio.util.gz.x(gz.java:19) at com.visokio.pub.fl.c(fl.java:1142) at com.visokio.pub.fl.a(fl.java:591) at com.visokio.pub.fl.a(fl.java:512) at com.visokio.pub.fl.a(fl.java:315) at com.visokio.pub.fl.a(fl.java:698) at com.visokio.pub.fl.a(fl.java:1263) at com.visokio.ent.actions.FileAction.a(FileAction.java:61) at com.visokio.ent.actions.ChainAction.a(ChainAction.java:49) at com.visokio.ent.actions.ChainAction.b(ChainAction.java:48) at com.visokio.ent.actions.ChainAction.a(ChainAction.java:76) at com.visokio.ent.actions.l.a(l.java:177) at com.visokio.ent.scheduler.k.m(k.java:290) at com.visokio.ent.scheduler.k.j(k.java:187) at com.visokio.ent.scheduler.k.a(k.java:317) at com.visokio.ent.scheduler.b.g(b.java:2) at com.visokio.util.q.run(q.java:20) Propagating chain action "IBOPS,CSPlus,IBDashboard,IBEQT,FIDOV,FIDVolumeCU," failure Could not execute action: Chain action "IBOPS,CSPlus,IBDashboard,IBEQT,FIDOV,FIDVolumeCU," failure
2012.03.08 08:10:21.370 Info: Executing task "TIS: Complexity" (TIS: Complexity, every day from Jun 1, 2011 5:30 PM, forever, ...)... 2012.03.08 08:10:21.808 ERROR: Could not execute action
Chain action "TIS: Complexity" failure
2012.03.08 08:10:21.808 Warning: Action completed successfully but warnings generated:
Chain action "TIS: Complexity" failure: java.lang.IllegalStateException: Already open at com.visokio.util.un.c(un.java:58) at com.visokio.kindling.ad.a(ad.java:28) at com.visokio.kindling.ad.a(ad.java:11) at com.visokio.kindling.fd.a(fd.java:5) at com.visokio.kindling.fd.b(fd.java:8) at com.visokio.kindling.fd.b(fd.java:14) at com.visokio.kindling.fd.d(fd.java:30) at com.visokio.kindling.fd.a(fd.java:35) at com.visokio.kindling.fd.c(fd.java:25) at com.visokio.kindling.nc.a(nc.java:25) at com.visokio.kindling.nc.c(nc.java:9) at com.visokio.kindling.q.c(q.java:128) at com.visokio.util.gz.x(gz.java:19) at com.visokio.pub.fl.c(fl.java:1142) at com.visokio.pub.fl.a(fl.java:591) at com.visokio.pub.fl.a(fl.java:512) at com.visokio.pub.fl.a(fl.java:315) at com.visokio.pub.fl.a(fl.java:698) at com.visokio.pub.fl.a(fl.java:1263) at com.visokio.ent.actions.FileAction.a(FileAction.java:61) at com.visokio.ent.actions.ChainAction.a(ChainAction.java:49) at com.visokio.ent.actions.ChainAction.b(ChainAction.java:48) at com.visokio.ent.actions.ChainAction.a(ChainAction.java:76) at com.visokio.ent.actions.l.a(l.java:177) at com.visokio.ent.scheduler.k.m(k.java:290) at com.visokio.ent.scheduler.k.j(k.java:187) at com.visokio.ent.scheduler.k.a(k.java:317) at com.visokio.ent.scheduler.b.g(b.java:2) at com.visokio.util.q.run(q.java:20) Propagating chain action "TIS: Complexity" failure Could not execute action: Chain action "TIS: Complexity" failure
On another note, when you try to manually re-run the chain "Test" mode it works perfectly. It seems the automatic scheduler itself keeps having issues, not when you run it yourself. I am unable to recreate the error, it only occurs once automated.
Please note that the errors have decreased substantially. Maybe once a week. We are currently procuring a new server that is 64-bit which should completly solve this issue as we have spoke in the past. I will reply back if we continue to have problems after the upgrade.