Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    Expert tip

    Thrown to indicate that an index of some sort (such as to an array, to a string, or to a vector) is out of range. Applications can subclass this class to indicate similar exceptions.

  2. ,

    Thrown if trying to access an index which is out of bounds on objects like String, Array, or Vector. Any negative integer less than or equal to -1 and positive integer greater than or equal to the size of the object is an index which would be out of bounds

java.lang.IndexOutOfBoundsException: Index: 0, Size: 0	at java.util.ArrayList.rangeCheck(ArrayList.java:653)	at java.util.ArrayList.get(ArrayList.java:429)	at com.redhat.ceylon.compiler.java.runtime.metamodel.MethodHandleUtil.unboxArguments(MethodHandleUtil.java:94)	at com.redhat.ceylon.compiler.java.runtime.metamodel.MethodHandleUtil.unboxArguments(MethodHandleUtil.java:81)	at com.redhat.ceylon.compiler.java.runtime.metamodel.ConstructorDispatch.reflectionToMethodHandle(ConstructorDispatch.java:606)	at com.redhat.ceylon.compiler.java.runtime.metamodel.ConstructorDispatch.namedConstructorDispatch(ConstructorDispatch.java:354)	at com.redhat.ceylon.compiler.java.runtime.metamodel.ConstructorDispatch.(ConstructorDispatch.java:102)	at com.redhat.ceylon.compiler.java.runtime.metamodel.meta.CallableConstructorImpl.checkInit(CallableConstructorImpl.java:74)	at com.redhat.ceylon.compiler.java.runtime.metamodel.meta.CallableConstructorImpl.$call$(CallableConstructorImpl.java:167)	at simple.run_.run(run.ceylon:174)