Discussion:
JaguarHTTPservlet.log: I/O error
(too old to reply)
unknown
2009-08-03 08:00:55 UTC
Permalink
Hi,

a set of PB 9 components running on a EAS 5.5 server behave very slowly
suddenly which is a show stopper for the system. There's no change in the
whole system (AFAIK only of course).
This behavior change seems to involve the following message in the
JaguarHTTPservlet.log file again and again:

Jul 27 08:24:59 2009: Servlet jspservlet: unable to service request due to
I/O error: Warning, some data was not written to the client.
java.io.IOException: Warning, some data was not written to the client.
at com.sybase.jaguar.servlet.JaguarConnection.writeClient(Native Method)
at
com.sybase.jaguar.servlet.JagHttp11OutputStream.writeChunk(JagHttp11OutputStream.java:391)
at
com.sybase.jaguar.servlet.JagHttp11OutputStream.writeOut(JagHttp11OutputStream.java:255)
at
com.sybase.jaguar.servlet.ResponseImpl.flushBuffer(ResponseImpl.java:2071)
at
com.sybase.jaguar.servlet.ResponseImpl.flushBuffer(ResponseImpl.java:2080)
at
com.sybase.jaguar.servlet.ResponseImpl.closeResponse(ResponseImpl.java:267)
at com.sybase.jaguar.servlet.ServletEngine._service(ServletEngine.java:878)
at com.sybase.jaguar.servlet.ServletEngine.service(ServletEngine.java:365)
at
com.sybase.jaguar.servlet.ServletServiceImpl.doService(ServletServiceImpl.java:58)
at
com.sybase.jaguar.servlet._sk_JaguarServlet_ServletService.remoteInvoke(_sk_JaguarServlet_ServletService.java:218)
at
com.sybase.jaguar.servlet._sk_JaguarServlet_ServletService.invoke(_sk_JaguarServlet_ServletService.java:125)





Any ideas whats wrong here?

TIA

Chris Werner
f+s software gmbh
unknown
2009-08-04 12:22:26 UTC
Permalink
In addition to the message in the original post I found the following error
messages
in JaguarHTTPservlet.log:

Aug 04 12:36:12 2009: Servlet jspservlet: unable to send error message to
client: java.lang.IllegalStateException: Response has been committed.
java.lang.IllegalStateException: Response has been committed.
at
com.sybase.jaguar.servlet.JagHttp11OutputStream.reset(JagHttp11OutputStream.java:63)
at com.sybase.jaguar.servlet.ResponseImpl.sendError(ResponseImpl.java:1461)
at
com.sybase.jaguar.servlet.JaguarResponse.sendError(JaguarResponse.java:430)
at com.sybase.jaguar.servlet.ServletEngine._service(ServletEngine.java:988)
at com.sybase.jaguar.servlet.ServletEngine.service(ServletEngine.java:365)
at
com.sybase.jaguar.servlet.ServletServiceImpl.doService(ServletServiceImpl.java:58)
at
com.sybase.jaguar.servlet._sk_JaguarServlet_ServletService.remoteInvoke(_sk_JaguarServlet_ServletService.java:218)
at
com.sybase.jaguar.servlet._sk_JaguarServlet_ServletService.invoke(_sk_JaguarServlet_ServletService.java:125)

Aug 04 14:16:40 2009: 060038-Error: Unable to service request for servlet:
jspservlet.
Aug 04 14:16:40 2009: 060039-Error: ServletException contained the following
root cause exception:
org.omg.CORBA.INTERNAL minor code: 0 completed: Yes
at java.lang.reflect.Constructor.newInstance(Native Method)
at
com.sybase.CORBA.iiop.Connection.createSystemException(Connection.java:5199)
at com.sybase.CORBA.iiop.Connection.invoke(Connection.java:3504)
at
LvsMntr._st_cn_lvs_mntr_view_vrld.cf_get_view(_st_cn_lvs_mntr_view_vrld.java:58)
at
com.sybase.jsp.lvs_0005fmntr_0005f03_0005flvs_0005fmntr_0005fview$jsp._jspService(lvs_0005fmntr_0005f03_0005flvs_0005fmntr_0005fview$jsp.java:135)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:299)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:492)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:584)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sybase.jaguar.servlet.JagServlet.service(JagServlet.java:718)
at
com.sybase.jaguar.servlet.JagRequestDispatcher.service(JagRequestDispatcher.java:971)
at com.sybase.jaguar.servlet.JagWebResource.service(JagWebResource.java:90)
at
com.sybase.jaguar.servlet.JagFilterChain.doFilter(JagFilterChain.java:133)
at com.sybase.jaguar.servlet.ServletEngine._service(ServletEngine.java:867)
at com.sybase.jaguar.servlet.ServletEngine.service(ServletEngine.java:365)
at
com.sybase.jaguar.servlet.ServletServiceImpl.doService(ServletServiceImpl.java:58)
at
com.sybase.jaguar.servlet._sk_JaguarServlet_ServletService.remoteInvoke(_sk_JaguarServlet_ServletService.java:218)
at
com.sybase.jaguar.servlet._sk_JaguarServlet_ServletService.invoke(_sk_JaguarServlet_ServletService.java:125)

I've really no clue what this means and how to search the reason for it? Any
hints?

TIA

Chris Werner
f+s software gmbh
Post by unknown
Hi,
a set of PB 9 components running on a EAS 5.5 server behave very slowly
suddenly which is a show stopper for the system. There's no change in the
whole system (AFAIK only of course).
This behavior change seems to involve the following message in the
Jul 27 08:24:59 2009: Servlet jspservlet: unable to service request due to
I/O error: Warning, some data was not written to the client.
java.io.IOException: Warning, some data was not written to the client.
at com.sybase.jaguar.servlet.JaguarConnection.writeClient(Native Method)
at
com.sybase.jaguar.servlet.JagHttp11OutputStream.writeChunk(JagHttp11OutputStream.java:391)
at
com.sybase.jaguar.servlet.JagHttp11OutputStream.writeOut(JagHttp11OutputStream.java:255)
at
com.sybase.jaguar.servlet.ResponseImpl.flushBuffer(ResponseImpl.java:2071)
at
com.sybase.jaguar.servlet.ResponseImpl.flushBuffer(ResponseImpl.java:2080)
at
com.sybase.jaguar.servlet.ResponseImpl.closeResponse(ResponseImpl.java:267)
at
com.sybase.jaguar.servlet.ServletEngine._service(ServletEngine.java:878)
at com.sybase.jaguar.servlet.ServletEngine.service(ServletEngine.java:365)
at
com.sybase.jaguar.servlet.ServletServiceImpl.doService(ServletServiceImpl.java:58)
at
com.sybase.jaguar.servlet._sk_JaguarServlet_ServletService.remoteInvoke(_sk_JaguarServlet_ServletService.java:218)
at
com.sybase.jaguar.servlet._sk_JaguarServlet_ServletService.invoke(_sk_JaguarServlet_ServletService.java:125)
Any ideas whats wrong here?
TIA
Chris Werner
f+s software gmbh
Loading...