E1: BSSV: Getting WAS Authentication Errors Under Load when running BSSV (Doc ID 1097015.1)

Last updated on MARCH 04, 2014

Applies to:

JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.
checked for relevance on 21-Jun-2012

Goal

Scenario 1. WSEC6735E: Failed to login error seen in the WebSphere logs. Symptom is: BSSV Server stops processing requests for a given user until the BSSV Server is restarted OR after 10-12 minutes of incativity for that particular user. This errror was encountered on WebSphere 6.1

In load testing the BSSV server all published business services fail for a distinct user account after approximately 110 minutes of activity. WebSphere is unable to find the user account. The BSSV server does not become available again until the JVM is restarted OR the server does not receive a request for 10-12 minutes. During this period all requests for the user account are rejected with an authentication error.

Certain real time integrations continuously process large volumes of records. An outage of even 10 minutes is an unacceptable delay.

The error returned via SOAP is:
<soapenv:Fault>
<faultcode xmlns:p55="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">p55:FailedAuthentication</faultcode>
<faultstring>com.ibm.wsspi.wssecurity.SoapSecurityException: WSEC6510E: Failed to login: com.ibm.websphere.security.auth.WSLoginFailedException: No user DN=jbenbow,ENV=JDV812,ROLE=\*ALL found</faultstring>
<detail encodingStyle=""/>
</soapenv:Fault>


The error written to SystemOut.log is:

 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms