Report this

What is the reason for this report?

Running 2 WLS instance on a same server

Posted on February 12, 2018

Hi,

I have a WLS 12.1.3 running on an instance.

I was working to spin up WLS 12.2.1.3 on the same machine on a different port.

After the 12.2 installation i confirmed that ./startWeblogic.sh and ./startNodeManager runs fine.

but when I try to start the ManagedServer in WLS console, i get an error

**For server ManagedServer, the Node Manager associated with machine Machine-1 is not reachable. Message icon - Warning All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.

In WLS console, under environment>machine>machine_1>monitoring I see an error even tho Keystore/SSL tab is configured correctly (configured same as 12.1.3 which has no problem starting managed server)

**Status: | Inactive | Current status of this Node Manager.More Info… Problem description: | javax.net.ssl.SSLHandshakeException | Exception encountered while communicating with this node manager.More Info… Version: | (not available)

To add a little more context, nodemanager.properties is pointing to port 5557 same as nodemanager in WLS console.

when i upgraded one of our training environment from 12.1.3. to 12.2.1.3, it had no issue. Is it not feasible to run parallel WLS on a same machine?

Any feedback will be appreciated and please let me know if more information is needed.

Thank you,



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hello,

for anyone that might stumble upon this question

It is feasible to run parallel WebLogic Server (WLS) instances on the same machine, but you need to ensure that they are correctly configured to avoid conflicts. From the information provided, it seems that there might be an issue with the Node Manager or SSL configuration.

Here are some suggestions to troubleshoot and resolve the issue:

  1. Check Node Manager logs: Inspect the Node Manager logs in the 12.2.1.3 installation to see if there are any error messages or warnings related to the SSL handshake or other issues. The log files are typically located in the $DOMAIN_HOME/nodemanager directory.

  2. Verify SSL configuration: Double-check the SSL configuration for the Node Manager in the 12.2.1.3 installation. Ensure that the keystore, truststore, and associated passwords are correctly configured, and that the paths are accessible.

  3. Check for port conflicts: Make sure there are no port conflicts between the two installations. The Node Managers for the two installations should listen on different ports. You mentioned that the nodemanager.properties file is pointing to port 5557. Ensure that the 12.1.3 installation is using a different port for its Node Manager, and that both ports are not in use by other applications.

  4. Check host and port configuration in the WLS Console: Double-check the machine configuration in the WLS Console for the 12.2.1.3 installation. Make sure the Node Manager hostname and port match the values specified in the nodemanager.properties file.

  5. Firewall rules: Check if there are any firewall rules that might be preventing communication between the Admin Server and the Node Manager in the 12.2.1.3 installation.

  6. Test Node Manager SSL connectivity: You can use a tool like openssl to test the SSL connectivity to the Node Manager. Run the following command and check if the SSL handshake is successful:

  1. openssl s_client -connect <hostname>:<nodemanager_port>

Replace <hostname> with the Node Manager’s hostname and <nodemanager_port> with the appropriate port number.

If you still face issues after trying the above suggestions, providing additional information such as Node Manager logs, SSL configuration, and machine configuration would be useful

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.