My Oracle Support Banner

Cannot Activate Changes in WLS Console due to Request Entity Too Large (Doc ID 2636713.1)

Last updated on JANUARY 13, 2023

Applies to:

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


When operating on the WLS console in production mode, changes are distributed to the managed servers when clicking on the Active Changes button. That action can be considered a transaction and it will be complete once the changes have been propagated to all the managed servers, however, multiple situations could prevent this operation to finish successfully. If a timeout was configured, a timeout exception could occur, if no, most probably the server will be affected by STUCK threads.
We understand that multiple reasons could explain this behavior, but this article refers to a particular case, where the log file shows as main tip the "Request Entity Too Large" message.
This situation was found in an SOA domain with multiple managed servers, where no change could be applied successfully and the WLS Console displayed these messages:

The last message shows the list of servers where this change failed, which seems to be a good tip to keep on digging.
The admin server log file gave more details to understand this situation:

Even when there were multiple managed servers on this domain, the message referred to specific managed servers, from here, the failed-servers.
Somehow that failed-server would be unable to process a large message via POST method or the limit assigned to this server, should be extended to match the real needs of it.


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

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