RPC Token Exceptions appear in the Webview Logs.

Document ID : KB000004156
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

 When a user logs into Webview, the following error message is logged:


      [ERROR] [/] Context Health: An RpcTokenException was thrown while processing this call. 
      com.google.gwt.user.client.rpc.RpcTokenException: Invalid RPC token (Invalid XSRF token) 
      at com.google.gwt.user.server.rpc.XsrfProtectedServiceServlet.validateXsrfToken(XsrfProtectedServiceServlet.java:120) 
      at com.google.gwt.user.server.rpc.AbstractXsrfProtectedServiceServlet.onAfterRequestDeserialized(AbstractXsrfProtectedServiceServlet.java:66) 
      at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:332) 
      at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:303) 
      at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:373) 
      at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)

Environment:
This error can affect any Webview user in APM 10.0 on any supported browser.
Cause:

  The error is caused by an enhancement to Webview in APM 10.0. When a user logs into Webview, a unique token is created and added to the service endpoint of each service class before the service is invoked in Webview. A new token is generated for every Webview session. If a user session times out, or Webview or EM connectivity is lost, a user is logged out of Webview. Once the connection is restored, usually by the EM or Webview service being restored or a user logging in again, and the same browser session is used, the error will occur because an invalid token is provided.

Resolution:

    After the user logs in again, a new token is created and Webview will function normally. The issue can be avoided entirely if user uses a new browser session.

Either way, there is no functionality loss caused by the error and it can be safely ignored. This issue is permanently addressed in APM 10.1.