Troubleshooting MoRE

You might encounter an issue when you install or use IBM® Modernized Runtime Extension for Java™.

Managed Liberty server information appears in collection after MoRE is uninstalled from the deployment manager

If you have a mixed-node environment and uninstall MoRE from the deployment manager, the Liberty version information for managed Liberty servers on MoRE-enabled nodes continues to appear in the WebSphere Application Server collection.

Troubleshooting problems when you start or stop managed Liberty servers

The following information describes troubleshooting start and stop problems for managed Liberty serves.

A managed Liberty server does not start successfully

If you attempt to access applications on a managed Liberty server too quickly after you create the server, it might appear that the server did not start successfully. Synchronize the nodes, wait one minute, and then try to access the server again.

If you stop a node agent immediately after the node synchronization process is complete, the server might not start successfully. Restart the node, wait one minute, and then try to access the server again.

A managed Liberty server is running and cannot be stopped

If the messages.log file indicates that the server is running, but you cannot stop it by using the administrative console or a wsadmin command, do the following actions:

Open a command window.
Change the directory to the bin directory of your WebSphere Application Server Liberty package that you installed with the Installation Manager; for example, /opt/IBM/WebSphere/Liberty/bin.
Set the following environment variable:
```
WLP_USER_DIR=<NODE_PROFILE_ROOT>/config/cells/<cellName>/nodes/<nodeName>/managedLiberty/usr
```
Replace <NODE_PROFILE_ROOT> with the root directory of the node profile where your managed Liberty server exists; for example, c:\IBM\WebSphere\AppServer\profiles\AppSrv01 or /opt/IBM/WebSphere/AppServer/profiles/AppSrv01
Run the following command:
```
server stop <server_name>
```
Replace <server_name> with the name of the managed Liberty server that you want to stop.

Logging and tracing on managed Liberty servers

The following information describes troubleshooting logging and tracing problems for managed Liberty serves.

Log and trace settings

For managed Liberty servers, HPEL mode is not available, and the only general properties available are Diagnostic trace and Change log detail levels. Other properties are not available.

For more information, see Log and trace settings.

Diagnostic trace settings

For managed Liberty servers, the Diagnostic trace page contains only the File option. Other options are not available.

For more information, see Diagnostic trace service settings.

Changing log detail levels

For managed Liberty servers, the Change log detail levels page contains only the option to Change log details level. Other options are not available.

For more information, see Log level settings.