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

Solutions on the web

via Oracle Community by 3004, 1 year ago
9 > at java.io.BufferedOutputStream.write(BufferedOutputStream.j > ava:112) > at weblogic.servlet.internal.HttpClusterServlet$Server.write> PostData(HttpClusterServlet.java:389) > at weblogic.servlet.internal.HttpClusterServlet$Server.proxy
java.lang.ArrayIndexOutOfBoundsException: 9
> >
at java.io.BufferedOutputStream.write(BufferedOutputStream.j
> > ava:112)
> >
    at weblogic.servlet.internal.HttpClusterServlet$Server.write> > PostData(HttpClusterServlet.java:389)
> >
    at weblogic.servlet.internal.HttpClusterServlet$Server.proxy> > (HttpClusterServlet.java:588)
> >
at weblogic.servlet.internal.HttpClusterServlet.service(Http
> > ClusterServlet.java:55)
> >
at javax.servlet.http.HttpServlet.service(HttpServlet.java:8
> > 53)
> >
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(S
> > ervletStubImpl.java:120)
> >
    at weblogic.servlet.internal.ServletContextImpl.invokeServle> > t(ServletContextImpl.java:741)
> >
    at weblogic.servlet.internal.ServletContextImpl.invokeServle> > t(ServletContextImpl.java:682)
> >
    at weblogic.servlet.internal.ServletContextManager.invokeSer> > vlet(ServletContextManager.java:146)
> >
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSo
> > cketHTTP.java:383)
> >
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHT
> > TP.java:257)
> >	at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)