HTTP/1.1 500 Internal Server Error when opening dashboards.
Hi.
This week a WAS administrator changed some parameters in the WAS Admin Console. I reviewed the required settings for jazz in the interactive installation guide and everithing is ok, but the following error is showing when opening the dashboard:
This week a WAS administrator changed some parameters in the WAS Admin Console. I reviewed the required settings for jazz in the interactive installation guide and everithing is ok, but the following error is showing when opening the dashboard:
com.ibm.team.jfs.app.http.HttpMethodNotAllowedException: Method Not Allowed <H1>Error Page Exception</H1> <H4>SRVE0260E: The server cannot use the error page specified for your application to handle the Original Exception printed below.</H4> <BR><H3>Original Exception: </H3> <B>Error Message: </B>java.lang.IllegalStateException<BR> <B>Error Code: </B>500<BR> <B>Target Servlet: </B>equinoxbridgeservlet<BR> <B>Error Stack: </B><BR> java.lang.IllegalStateException
<BR> <BR> <BR><BR><H3>Error Page Exception: </H3> <B>Error Message: </B>HTTP method POST is not supported by this URL<BR> <B>Error Code: </B>405<BR> <B>Target Servlet: </B>errorhandler<BR> <B>Error Stack: </B><BR> com.ibm.ws.webcontainer.webapp.WebAppErrorReport: HTTP method POST is not supported by this URL
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:56) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39) at java.lang.reflect.Constructor.newInstance(Constructor.java:527) at com.ibm.team.jfs.app.util.ErrorUtils.handleErrorResponse(ErrorUtils.java:480) at com.ibm.team.jfs.app.util.ErrorUtils.handleErrorResponse(ErrorUtils.java:405) at com.ibm.team.dashboard.service.internal.jfs.HttpUtil.throwJfsHttpException(HttpUtil.java:252) at com.ibm.team.dashboard.service.internal.jfs.HttpUtil.checkResponse(HttpUtil.java:86) at com.ibm.team.dashboard.service.internal.jfs.HttpResourceClient.executeRequest(HttpResourceClient.java:343) at com.ibm.team.dashboard.service.internal.jfs.DashboardClient.runSparqlQueryRaw(DashboardClient.java:224) at com.ibm.team.dashboard.service.internal.jfs.DashboardClient.runSparqlQuery(DashboardClient.java:199) at com.ibm.team.dashboard.service.internal.legacy.LegacyDashboardRestService.getDashboard(LegacyDashboardRestService.java:232) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) at com.sun.proxy.$Proxy3598.getDashboard(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.doModelledRestService(AbstractTeamServerServlet.java:573) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:2525) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:2316) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1795) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180) at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:126) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:76) 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:74) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1227) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:776) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:458) at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:136) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:97) at com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:165) at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:198) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:928) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1025) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3761) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:976) at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:459) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:526) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:312) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:88) at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1784) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175) 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:1862)
How can I correct the configuration?
3 answers
Problem solved. :D
The server needed more HDD space, more RAM memory and more processing power.
Also, the number of sessions the WAS server can sustain should be more than the number of threads that the server opens at any given time.
This is changed in the session management section of the Websphere Aplication Server administation console.
Thank you.
The server needed more HDD space, more RAM memory and more processing power.
Also, the number of sessions the WAS server can sustain should be more than the number of threads that the server opens at any given time.
This is changed in the session management section of the Websphere Aplication Server administation console.
Thank you.
From this Websphere application Server documentation: ftp://public.dhe.ibm.com/software/webserver/appserv/library/v60/wasv600base_app.pdf:
Ensure that your Web server is configured to perform operations required by Web applications, such as GET and POST. Typically, this involves setting a directive in the Web server configuration file (such as the httpd.conf file for an IBM HTTP Server). Refer to the Web server documentation for instructions. If an operation is not enabled when a servlet or JSP file requiring the operation is accessed, an error message displays, such as this one from the IBM HTTP Server: HTTP method POST is not supported by this URL.
Ensure that your Web server is configured to perform operations required by Web applications, such as GET and POST. Typically, this involves setting a directive in the Web server configuration file (such as the httpd.conf file for an IBM HTTP Server). Refer to the Web server documentation for instructions. If an operation is not enabled when a servlet or JSP file requiring the operation is accessed, an error message displays, such as this one from the IBM HTTP Server: HTTP method POST is not supported by this URL.
Comments
Hi, I tried this and did not work. The xml files have the next security constraints:
<url-pattern>/ ; /_theming/ ; /web/ ; /repo/ ; /xip_server ; /admin/ ; /auth/ , /oauth/; /oauth-request-token ; /oauth-access-token ; /secure/oauth/ ; /secure/oauth-request-token ; /secure/oauth-access-token</url-pattern>
Those are all the URL options that CLM uses.
I have more information:
DOORS NG application is not accessible either.
The error trace shows ID CRRRW7553E A message that was recieved from the server indicates an error with no specific handler.
Unable to load https://<servername>:9443/rm/admin-home?dojo.preventCache=1445446814380 status:400.
The navigation buttons from within the apps are also not working (the house on the upper left corner).
***When DOORS was functioning there was the following error in a banner:
ID CRRRW7556E The application cannot connect to the server. There might be a problem with your network connection or the server might not be available.
Timeout exceeded.
Even more, the server was restarted and the features listed worked for about 20 minutes. After this time, the problem is persistent for the dashboards and DOORS NG.
It seems that the error is related to the servlet.
Thank you for your help
The WAS server that is installed is version 8.5.5.