Web UI problem: "Error viewing work item (OK)"
When I try to click a work item in a browser (IE6), the message "Error viewing work item (OK)" will pop up.
I also found that when I click the "Work Items" tab, the tomcat console has following message: ------------------------------------------------------------- 15:28:37,250 WARN .team.repository.servlet.AbstractTeam ServerServlet - IOException processing request for GET com.ibm.team.workitem.co mmon.internal.model.IImageContentService for: ADMIN - Exception message: null ClientAbortException: java.net.SocketException: Connection reset by peer: socke t write error at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java: 327) at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:29 3) at org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputSt ream.java:97) at com.ibm.team.workitem.service.internal.ImageContentService.perform_GE T(ImageContentService.java:86) at com.ibm.team.repository.service.TeamRawService.service(TeamRawService .java:79) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.doRestServi ce(AbstractTeamServerServlet.java:624) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(Abs tractTeamServerServlet.java:1044) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrap per.service(ServletManager.java:177) at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleR equest(ServletRegistration.java:91) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(P roxyServlet.java:110) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyS ervlet.java:76) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet .java:115) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV alve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV alve.java:178) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authentica torBase.java:524) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j ava:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j ava:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal ve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav a:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java :869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.p rocessConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo int.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol lowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP ool.java:684) at java.lang.Thread.run(Thread.java:803) Caused by: java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:105) at java.net.SocketOutputStream.write(SocketOutputStream.java:149) at com.ibm.jsse2.c.a(c.java:91) at com.ibm.jsse2.c.a(c.java:161) at com.ibm.jsse2.jc.a(jc.java:224) at com.ibm.jsse2.j.write(j.java:2) at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(Internal OutputBuffer.java:746) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:433) at org.apache.coyote.http11.InternalOutputBuffer.flush(InternalOutputBuf fer.java:304) at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java: 991) at org.apache.coyote.Response.action(Response.java:182) at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java: 322) ... 29 more |
6 answers
This is now fixed on Jazz.net and via integration build ​I20070628-​0026 (https://jazz.net/downloads/NewDownloadItem.jsp?type=integration&href=integration/data/I20070628-0026)
|
Here's a comment I posted on bug 26016 that I'll post here for people who are blocked from viewing work items.
------------------------------------------------------------ I'm now able to reproduce this by setting the following two environmental factors: 1) Using Internet Explorer v6/v7 on Microsoft Windows 2) Having your Regional and Language Option set to something other than English or German We're not yet sure why this is happening but until we fix it, you can perform the following two workarounds: 1) Use the Mozilla Firefox browser for work items ( http://www.mozilla.org/firefox ) 2) If you want to use Internet Explorer, change your Standards and format preference to English (Start -> Control Panel -> Regional and Language Options, under "Standards and formats" change to English and press "Apply") |
16523 just got fixed yesterday.
|
The exception seen in the log has already been reported in No, the message is not directly related to the error on opening the work item. In fact, this message occurs when I go to the "Work Items" tab. I don't know whether you meet the same scenario or not. The message is the same. Any progress on the work item 16523? Thanks! |
The exception seen in the log has already been reported in
http://jazzdev.torolab.ibm.com:9980/jazz/service/%7Bdefault%7D/com.ibm.team.repository/itemName/com.ibm.team.workitem.WorkItem/16523 I don't think it is related to the error on opening the workitem. |
This is Bill Higgins from the web UI team. Several people have noticed a similar inability to open work items with the same unhelpful error message.
I've opened up Jazz.net Defect 26016 and subscribed you to track this issue. Also, there's a question in there for you that I'd ask you to please answer to help us track this down. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.