Skip to main content
A
Anonymous
August 3, 2011
Answered

generic ColdFusion error thrown by Java?

  • August 3, 2011
  • 1 reply
  • 2680 views

Hi All,

Every couple of days or so I'm randomly getting this error thrown by my production server:

DIAGNOSTICS: Index: 5, Size: 5 null
The error occurred on line -1

Where the number  in Index: x, Size x null changes. Sometimes its Index 2, Size: 2 null  but it varies from time to time. Either way there is no specific  debugging info I can find nor any specific CF lines of code I need to  look into. This started about 2 months ago out of the blue and I cannot  tell why. If a page throws this error and you refresh the page  immediately... there will be no error. It's sporadic and random at best.

Here  is the stack trace info I was able to dig up. Anyone every faced with a  similar problem and how did you overcome it? By the way I'm running 8,0,1,195765 Enterprise edition.

Stack Trace info:

java.lang.IndexOutOfBoundsException:  Index: 5, Size: 5 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.remove(ArrayList.java:387) at coldfusion.monitor.util.MonitorList.add(MonitorList.java:159) at coldfusion.monitor.memory.SessionMemoryMonitor.record(SessionMemoryMonitor.java:49) at coldfusion.monitor.memory.SessionMemoryMonitor.record(SessionMemoryMonitor.java:37) at  coldfusion.monitor.memory.MemoryMonitor.record(MemoryMonitor.java:261)  at coldfusion.monitor.memory.MemoryRequestEventHandler.onRequestComplete(MemoryRequestEventHandler.java:23) at coldfusion.monitor.event.RequestMonitorEventProcessor.onRequestComplete(RequestMonitorEventProcessor.java:246) at  coldfusion.filter.MonitoringFilter.invoke(MonitoringFilter.java:46) at  coldfusion.filter.PathFilter.invoke(PathFilter.java:86) at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:70) at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28) at  coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38) at coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:46) at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38) at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22) at coldfusion.CfmServlet.service(CfmServlet.java:175) at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89)  at jrun.servlet.FilterChain.doFilter(FilterChain.java:86) at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42) at  coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)  at jrun.servlet.FilterChain.doFilter(FilterChain.java:94) at jrun.servlet.FilterChain.service(FilterChain.java:101) at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106) at  jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at  jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286)  at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)  at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203)  at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:320) at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428) at   jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266) at  jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

    This topic has been closed for replies.
    Correct answer 12Robots

    ok thanks. so in the CF monitor... there are 3 buttons. is it ok to keep sever monitoring on but profiling and memory tracking off?


    That's the least memory intensive if memory (no pun intended) serves me right, but I would turn them all off if it were my server and then only turn them on if I was looking for something specific.

    I suspect you'll find your whole environemnt works better.  By all means though, read the article and make the determination for yourself as to what you need.

    Good luck

    1 reply

    A
    Avatar
    Participating Frequently
    August 3, 2011

    Are you using Rob Gonda's sql.cfc perchance? I did a quick Google search and found another user with a similar problem that had narrowed it down to this component though never truly had an answer. They ended up rewriting their code and not using said component.

    A separate user logged this as a bug with Adobe but the bug has since been closed and no comments were ever given.

    I take it you have Coldfusion's monitoring/profiling enabled? Maybe try disabling that and see if that is contributing to this problem.

    A
    Anonymous
    October 18, 2011

    no i am not using sql.cfc. I applied the latest Coldfusion 8 hotfix 4 and still receive this error almost every day now. anyone else have this problem and find a solution? by the error message its something deep in the code of JRUN and is a bug that should be addressed by Adobe.

    12Robots
    12Robots
    Participating Frequently
    October 18, 2011

    Are you running profiling services? If so, why? Running profiling services in production is not recommended. Have you looked at how much memory is being used? How much memory do you have allocated to CF? Is it possible it is being exceeded?

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices