Application Stops At STATE_ADMIN And Not STATE_ACTIVE In Nodes On Second Machine (Doc ID 2047912.1)

Last updated on SEPTEMBER 14, 2015

Applies to:

Oracle WebLogic Server - Version 10.3 and later
Information in this document applies to any platform.

Symptoms

After deploying an ear on 8 managed servers housed on 2 machines, the application reaches STATE_ACTIVE on machine 1 but only STATE_ADMIN on machine 2. The ear is targeted to all 8 servers in the config.xml configuration file. The expectation is that the application should reach STATE_ACTIVE on all 8 servers across both machines.

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