My Oracle Support Banner

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

Last updated on APRIL 26, 2018

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:

####<15-Nov-2012 20:17:03 o'clock CET> <Info> <Deployer> <SERVERNAME> <testnode> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1353007023569> <BEA-149209> <Resuming.>

 
No further deployer activity. A normal cluster environment with an application deployed across the cluster should show information or the status of the deployment of such applications.
In this case, it seems that the "Deployer" service does not have any application to deploy or verify accross the cluster.

When comparing the WebLogic server instances log entries from a lab test install:

####<Nov 15, 2012 5:29:51 PM CLST> <Info> <Deployer> <WLSLab> <VC2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1353011391339> <BEA-149209> <Resuming.>
####<Nov 15, 2012 5:30:19 PM CLST> <Info> <Deployer> <WLSLab> <VC2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <4e69a3d1d5fa9b95:797100a9:13b05c366a8:-8000-0000000000000002> <1353011419855> <BEA-149059> <Module jde of application JASV1 is transitioning from STATE_NEW to STATE_PREPARED on server VC2.>
####<Nov 15, 2012 5:30:21 PM CLST> <Info> <Deployer> <WLSLab> <VC2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <4e69a3d1d5fa9b95:797100a9:13b05c366a8:-8000-0000000000000002> <1353011421917> <BEA-149060> <Module jde of application JASV1 successfully transitioned from STATE_NEW to STATE_PREPARED on server VC2.>

The above log has additional information about the application deployment, since the application is correctly deployed to all nodes:

<Module jde of application JASV1 successfully transitioned from STATE_NEW to STATE_PREPARED on server VC2.>

 

 

 

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
Cause
Solution
References


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