Self Service Console
Error: "Error 408--Request Time -out The client did not produce a request within the time that server was prepared to wait. The client MAY repeat the request without modifications at any later time." appears on Security Console when administrator tries to unassign a token.
RSA AM 81. Security Console performance is slow. Data is not loaded in Dash board sometimes. Unassigning a token takes long time.
The console.log file shows an exception but it is caused by the same "SocketTimeoutException: Read timed out" as seen in the slow performance with Self Service Portal.
####<Aug 7, 2014 10:26:04 AM PDT> <Error> <HTTP> <p1ahmlonrsamg01> <console>
<[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'>
<<WLS Kernel>> <> <69f34036cd726e80:-f7e3a7d:1478d7ef323:-8000-0000000000004b57>
<1407432364594> <BEA-101019>
<[ServletContext@414341645[app:console-ims module:console-ims-8.1.0.2.0.war
path:null spec-version:3.0]]
Servlet failed with an IOException
weblogic.utils.NestedRuntimeException:
Cannot parse POST parameters of request: '/console-ims/AddUser.do
at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.mergePostParams(ServletRequestImpl.java:2335)
at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.parseQueryParams(ServletRequestImpl.java:2215)
at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.getQueryParams(ServletRequestImpl.java:2054)
at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.getParameter(ServletRequestImpl.java:2168)
at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.access$800(ServletRequestImpl.java:1952)
at weblogic.servlet.internal.ServletRequestImpl.getParameter(ServletRequestImpl.java:839)
at com.rsa.ims.sso.filter.SSOFilter.doFilter(SSOFilter.java:463)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:74)
at com.rsa.ui.common.filter.I18NFilter.doFilter(I18NFilter.java:96)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:74)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3288)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3254)
at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2074)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1512)
at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:255)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: java.net.SocketTimeoutException: Read timed out
at jrockit.net.SocketNativeIO.readBytesPinned(Native Method)
at jrockit.net.SocketNativeIO.socketRead(SocketNativeIO.java:32)
at java.net.SocketInputStream.socketRead0(SocketInputStream.java)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at weblogic.socket.JSSEFilterImpl.readFromNetwork(JSSEFilterImpl.java:445)
at weblogic.socket.JSSEFilterImpl.handleUnwrapResults(JSSEFilterImpl.java:616)
at weblogic.socket.JSSEFilterImpl.unwrapAndHandleResults(JSSEFilterImpl.java:498)
at weblogic.socket.JSSEFilterImpl.read(JSSEFilterImpl.java:414)
at weblogic.socket.JSSESocket$JSSEInputStream.read(JSSESocket.java:58)
at weblogic.servlet.internal.PostInputStream.read(PostInputStream.java:194)
at weblogic.servlet.internal.ServletInputStreamImpl.read(ServletInputStreamImpl.java:228)
at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.mergePostParams(ServletRequestImpl.java:2309)
at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.parseQueryParams(ServletRequestImpl.java:2215)
at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.getQueryParams(ServletRequestImpl.java:2054)
at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.getParameter(ServletRequestImpl.java:2168)
at weblogic.servlet.internal.ServletRequestImpl$RequestParameters.access$800(ServletRequestImpl.java:1952)
at weblogic.servlet.internal.ServletRequestImpl.getParameter(ServletRequestImpl.java:839)
at com.rsa.ims.sso.filter.SSOFilter.doFilter(SSOFilter.java:463)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:74)
at com.rsa.ui.common.filter.I18NFilter.doFilter(I18NFilter.java:96)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:74)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3288)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3254)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)
at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2163)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2089)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2074)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1512)
at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:254)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
AM8.log has below lines:
INFO | jvm 1 | main | 2014/08/03 21:29:53 | <Aug 3, 2014 9:29:53 PM PDT> <Error> <HTTP> <BEA-101019> <[ServletContext@450683934[app:am-app module:/ims-ws path:null spec-version:3.0]] Servlet failed with an IOException
INFO | jvm 1 | main | 2014/08/03 21:29:53 | java.net.SocketTimeoutException: Read timed out
INFO | jvm 1 | main | 2014/08/03 21:29:53 | at jrockit.net.SocketNativeIO.readBytesPinned(Native Method)
Customer noticed significant packet loss using PingPlotter from both Primary and Replica servers. This is outside all RSA consoles.
This issue can be caused by a bad NIC on that VM server. Move RSA servers to another VM host using vmotion to resolve this issue.
Related Articles
Overall slow performance navigating the user interface and user sessions are timing out when displaying new pages in RSA I… 327Number of Views Logging on to security console is very slow after updating to AM 8.5 158Number of Views Unable to login to RSA Authentication Manager Security Console as super admin 5.06KNumber of Views Firefox reports Secure Connection Failed when connecting to the RSA Security Console 509Number of Views How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. 731Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records Unable to login to RSA Authentication Manager Security Console as super admin RSA Authentication Manager 8.9 Release Notes (January 2026) How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Connection fails to Cloud Authentication Service when connecting through a proxy server from RSA Authentication Manager to…