Pattern selector

Most relevant patterns first. Most helpful ones displayed. Click here to show all.

  1. WsClientProxyInvocationHandler.invoke() has thrown a JRFSOAPFaultException
    Unsorted
    0
    0
    0
  2. OracleDispatchImpl.invoke() has thrown a JRFSOAPFaultException
    Unsorted
    0
    0
    0

Your stack trace compared to the selected pattern

Jump to solutionsExpand frames
oracle.j2ee.ws.client.jaxws.JRFSOAPFaultException: Client received SOAP Fault from server : InvalidSecurityToken : The security token is not valid.
3 matching frames hidden
    at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:106)
    at oracle.j2ee.ws.client.jaxws.WsClientProxyInvocationHandler.invoke(WsClientProxyInvocationHandler.java:254)
    at com.sun.proxy.$Proxy28.genericSoapOperation(Unknown Source)
    at oracle.ucm.idcws.client.utils.GenericUtils.sendGenericRequest(GenericUtils.java:54)
3 frames hidden

External results for this pattern (2)

  1. Kotreshvia Oracle Community4 months ago
    failure to authenticate the user weblogic, due to: Unexpected error occurred, due to : oracle.j2ee.ws.client.jaxws.JRFSOAPFaultException: Client received SOAP Fault from server : SOAP must understand error. Server could not understand one or more SOAP headers : { http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd }Security
    Show stack trace
  2. ZubairAlivia Oracle Community2 years ago
    Client received SOAP Fault from server : InvalidSecurityToken : The security token is not valid.
    Show stack trace