E1: WLS: Unable to Reach EnterpriseOne on Secondary JAS Nodes in a Weblogic Server Cluster (Doc ID 1506258.1)

Last updated on MAY 30, 2017

Applies to:

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

Symptoms

After adding additional nodes to a JAS instance running on WebLogic cluster, it is not possible to reach the application on the added nodes.  HTML client users get the following error on the browser:

404 Page Not Found

This happens when trying to access EnterpriseOne on any of the ports for the secondary nodes.  There is no problem accessing the JAS application on the first node of the cluster where it was originally installed.

When checking the logs it's noticeable that the cluster is not deploying E1 JAS to other nodes.   Logs from secondary nodes are showing the deployment task process as started but there is no sign of any application deployment.  When testing in a laboratory installation, it shows that the deployment task should take the JAS application and deploy it to the secondary nodes.

The WebLogic Server instance Log shows the following entry:

 

 

 

Cause

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