RTC 4.0 Error : jts/setup : Error 404: ProxyServlet: /jts/setup
Environment: RTC 4.0, WAS 7.0.0.23.
When I try to configure RTC by issue : https://<hostname>:9445/jts/setup, browser shows the error
Error 404: ProxyServlet: /jts/setup
when I checked the log, found error in SystemErr as
[8/21/12 19:58:30:707 EDT] 00000066 SystemErr R Aug 21, 2012 7:58:30 PM com.ibm.ws.webcontainer.servlet.ServletWrapper service
SEVERE: SRVE0068E: Uncaught exception created in one of the service methods of the servlet equinoxbridgeservlet in application jts_war. Exception created : java.lang.IllegalStateException: Response already committed.
at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sendError(WebAppDispatcherContext.java:602)
at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendError(SRTServletResponse.java:1187)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:78)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1657)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1597)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:131)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:133)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.initialize(BridgeFilter.java:264)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:149)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:934)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:181)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3935)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1592)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:452)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.determineNextChannel(SSLConnectionLink.java:1049)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.readyInboundPostHandshake(SSLConnectionLink.java:717)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.readyInbound(SSLConnectionLink.java:571)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.ready(SSLConnectionLink.java:295)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1613)
[8/21/12 19:58:30:719 EDT] 00000066 SystemErr R Aug 21, 2012 7:58:30 PM com.ibm.ws.webcontainer.srt.SRTServletResponse setStatus
WARNING: WARNING: Cannot set status. Response already committed.
[8/21/12 19:58:30:724 EDT] 00000066 SystemErr R Aug 21, 2012 7:58:30 PM com.ibm.ws.webcontainer.srt.SRTServletResponse addHeader
WARNING: WARNING: Cannot set header. Response already committed.
can some one guide , what would have gone wrong here
Accepted answer
I ran into a similar error when I installed a new environment today for a large scale reproduction. I saw the same error as you when I tried to open the setup page:
https://<hostname>:9445/jts/setup, browser shows the error
Error 404: ProxyServlet: /jts/setup
Basically, I scoured the WebSphere Application profile and then went back to my logs and noted the following:
Log file started at: [10/10/12 22:00:41:352 EDT]************* End Display Current Environment *************[10/12/12 1:56:52:179 EDT] 00000014 SystemErr R java.io.FileNotFoundException: /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/temp/jazzNode01/server1/clmhelp_war/clmhelp.war/eclipse/features/com.ibm.team.scm.svn.cshelp.feature_3.0.1.v20120619_1802/uadelivery.properties (Too many open files)
I then went back and adjusted my max open files per the following documentation:
Special instructions for UNIX systems
Once I set the corrected values, I rebooted the server and then removed the corrupted WebSphere profile and recreated:
- /opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -delete -profileName AppSrv01
- rm -Rf /opt/IBM/WebSphere/AppServer/profiles/AppSrv01
- /opt/IBM/WebSphere/AppServer/bin/manageprofiles.sh -create -profileName AppSrv01 -profilePath /opt/IBM/WebSphere/AppServer/profiles/AppSrv01 -enableAdminSecurity true -adminUserName wasadmin -adminPassword wasadmin
***Keep in mind that I was working with a new installation of WebSphere ND 8.0.0.4 and was NOT configured prior to my configuration of RTC. The point is that the above commands may not be applicable to an established environment.
Once the profile was recreated, I went through the entire configure of the server and noted that the problem was mitigated and I was able to open https://<hostname>:9445/jts/setup
Hope this helps.
-Chris