Welcome, guest ( Login )

» Home (JDC Blog)
» Forums

Page Tags

None yet -- tag this page

Search Tags:
WikiHome » DevForums » GeneralForum » DevQuestion807

DevQuestion807

Version 1, changed by mmatthews. 11/08/2006.   Show version history


java.lang.ArrayIndexOutOfBoundsException in jot console(Back to Forum)

Posted by mmatthews on 11/08/2006

Tags: none


I was working debugging an event trigger script a little while ago, and the console gave me a stack trace error like this:

java.lang.ArrayIndexOutOfBoundsException?: -1
at com.s3.xmlproc.Locator.getTop(Locator.java:166)
at com.s3.xmlproc.UserLocator?.getTop(UserLocator?.java:61)
at com.s3.jotlib.admin.GetLogEventsFunction?.getRow(GetLogEventsFunction?.java:258)
at com.s3.jotlib.admin.GetLogEventsFunction?.access$100(GetLogEventsFunction?.java:37)
at com.s3.jotlib.admin.GetLogEventsFunction?$LogResult?.describeXHTML(GetLogEventsFunction?.java:222)
at com.s3.jotlib.admin.GetLogEventsFunction?$LogResult?.describe(GetLogEventsFunction?.java:162)
at com.s3.script.desc.DescribeUtil?.describeXHTML(DescribeUtil?.java:39)
at com.s3.script.js.gw.OutFunctionObject?.write(OutFunctionObject?.java:232)
at com.s3.xform.tag.ScriptTag?.handleImpl(ScriptTag?.java:238)
...

The problem is that I can't get the console to display anything except the java exception.

I have eliminated the script that I was working on when I started getting the error. Is there any way to reset the console so that I can see log messages again?

The application itself seems to be working okay. I just can't see any new messages in the console.

Thanks!

5 replies

Reply by dantila on 01/05/2007 (Permalink )

Tags: none


If this is still occurring, send me the link and we'll look at it.

Reply by dantila on 11/30/2007 (Permalink )

Tags: none


We're experiencing the same problem, also while we're working w/ the event subsystem. We're also experiecing difficulty in resetting the console once this problem manifests.

What are the solutions?

Reply by bhaugen on 11/30/2007 (Permalink )

Tags: none


Not exactly a solution, but I've seen this several times when I had committed some kinds of server-side javascript code errors. (Sorry, don't have a good list of the kinds of errors.)

The only thing I found to do was to post enough log messages to flush the problem out of the console log.

Reply by dantila on 11/30/2007 (Permalink )

Tags: none


Brilliant as usual!
add the code to a page and save/reload to clear the log by virtue of the error scrolling out of view

<html xmlns="http://www.w3.org/1999/xhtml" xmlns:jot="http://www.foopee.com/ns/s3/srvtmpl/">
<jot:script>
// <![CDATA[
for (x=0;x<=100;x++){
jot.lib.admin.log(x);
}
//]]>
</jot:script>
</html>

Reply by dantila on 11/30/2007 (Permalink )

Tags: none


Additional note: 100 items is the log limit, hence the 100-item loop in the reply above.

Please log in to post to this forum