The WebSphere® Administrative Server is designed to work
when the WLM facility is enabled. Disabling WLM for the Administrative
Server in the admin.config configuration file will cause numerous
problems.
There are several potentially serious problems that occur for multi-node,
horizontally-scaled configurations when WLM is turned off for the
Administrative Servers. For example:
1. There is no failover for administrative
functions if WLM is disabled; therefore, one Administrative Server might
use data that is cached rather than refreshing it.
2. Intermittent problems with topology not painting can occur in the
administrative console. The symptoms are erratic, depending on if one of
the multiple nodes was brought down. Trace symptoms can include an
interoperable object reference (IOR) with an incorrect port number or
incorrect node name.
3. CONM6000W: "Illegal use of single phase commit (1PC) resource in
transaction" will probably be in the tracefile when defining Java™ Virtual
Machine (JVM™) on multiple nodes.
4. Critical error messages might occur with getAttribute failed
when a remote administrative node is stopped and refreshed.
5. Server Groups do not start unless both nodes are running; previously
the Server Group started the appropriate clones.
6. When WLM is disabled, many additional symptoms are likely because of
the instability of the systems.
Items 1 through 4 are problems that were documented when a customer
disabled WLM on the Administrative Server. The problems were resolved when
the setting was correctly set to:
com.ibm.ejs.sm.adminServer.wlm=true
To summarize, do not disable WLM on an Administrative Server. |