My Oracle Support Banner

E1: JAS: Login on Jas Server Is Taking Long Time or the First Login of the Day is Failing with Error 'Could not reach security server <SERVERNAME>, Connection reset' (Doc ID 2435021.1)

Last updated on MAY 08, 2023

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.

Symptoms

After sometime when JD Edwards EnterpriseOne hasn't been used by any user, the first user who logs in, spends around 2 to 3 minutes to be logged on.

Having "netTrace=TRUE" set in jas.ini and "netTrace=7" set for the Security Kernel on Enterprise Server, there is no information captured into the Security Kernel debug log at the time the JAS server is sending the request to authenticate the user, but after the JDENetTimeout value is reached, the Security Kernel debug log has the information about JAS server is trying to authenticate the user.

In JAS debug log the following message are captured (JDENetTimeOut is set to 90 seconds):

Changes

 N/A

Cause

To view full details, sign in with your My Oracle Support account.

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

In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.