It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,537
×7,188
×4,223
×2,323

question asked: Sep 18 '15, 4:16 p.m.
question was seen: 2,490 times
last updated: Sep 28 '15, 10:00 a.m.

Related questions

FAQ - How this Forum works

CLM 4.0.3 on WAS 8.0 Base 64bit Windows server setup

0
Naveen V (79●7●49) | asked Sep 18 '15, 4:16 p.m.
edited Sep 20 '15, 7:14 p.m. by Stef van Dijk (2.0k●7●9)
Hi,

I am setting up the CLM 4.0.3 server in my windows machine to test upgrade it to CLM 5.0.2 but When I run jts/setup then giving me 404 error in browser. Systemout.log files says below

[9/18/15 16:12:34:194 EDT] 0000001d webapp        E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[equinoxbridgeservlet]: java.lang.IllegalStateException: Response already committed.
    at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sendError(WebAppDispatcherContext.java:597)
    at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sendError(WebAppDispatcherContext.java:642)
    at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendError(SRTServletResponse.java:1231)
    at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:78)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
    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:668)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1147)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:722)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:449)
    at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:125)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:92)
    at com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:139)
    at com.ibm.team.repository.server.servletbridge.BridgeFilter.initialize(BridgeFilter.java:293)
    at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:170)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:192)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:89)
    at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:919)
    at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1016)
    at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3639)
    at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304)
    at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:950)
    at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1659)
    at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:195)
    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:1048)
    at com.ibm.ws.ssl.channel.impl.SSLConnectionLink$MyReadCompletedCallback.complete(SSLConnectionLink.java:642)
    at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1784)
    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:1648)

[9/18/15 16:12:34:194 EDT] 0000001d srt           W com.ibm.ws.webcontainer.srt.SRTServletResponse setStatus WARNING: Cannot set status. Response already committed.
[9/18/15 16:12:34:196 EDT] 0000001d srt           W com.ibm.ws.webcontainer.srt.SRTServletResponse addHeader SRVE8094W: WARNING: Cannot set header. Response already committed.
[9/18/15 16:12:34:199 EDT] 0000001d servlet       I com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I: [jts_war] [/jts] [errorhandler]: Initialization successful.


Does any one have any idea ?

One answer

Most liked answers ↓|Newest answers|Oldest answers

0
permanent link
Donald Nong (14.5k●3●14) | answered Sep 20 '15, 9:16 p.m.
HTTP 404 on WAS server can usually caused by not correctly binding the web application to an HTTP host or assigning a context root. Re-deploy the web application following the instructions exactly.
Comments
Naveen V commented Sep 21 '15, 8:51 a.m. | edited Sep 21 '15, 7:51 p.m.

Hi Donald.

I had deployed the applications couple of times with proper context root but still no luck. I have windows 7 64 bit , IM -64bit and all other DB2 , CLM and WAS also on 64bit. Is anything else causing this issue.

Thanks

Donald Nong commented Sep 21 '15, 8:12 p.m.

If you have done it several times, it is probably you did not do it the right way. If you haven't tried that, use the Python scripts <Jazz Installation>/server/was/clm_depooy*.py to deploy the applications. Check SystemOut.log and SystemErr.log and confirm that the applications are correctly deployed, started, and bound to "default_host".

Naveen V commented Sep 28 '15, 10:00 a.m.

Thanks Donald, I have fixed it by setting up the global settings. Its prompted me the login screen too. I have done the setting without any issue after setting the global security and then application user/group settings.

Thanks,

Your answer

Register or to post your answer.