Thursday, April 16, 2020
Start Weblogic managed-server with error The object identified by: '31' could not be found
Symptoms:
Starting the Weblogic managed-server via startManagedWebLogic.sh script get the error:
Caused by: java.rmi.NoSuchObjectException: The object identified by: '31' could not be found. Either it was has not been exported or it has been collected by the distributed garbage collector.
Cause:
This error has several reasons, but if you search on the web or Oracle Support, the first results will be port misconfigured somewhere
Solution:
Option 1: Check the Weblogic admin server listener address if its empty: <listen-address></listen-address>
To fix:
1. Go to $DOMAIN_HOME/config/config.xml file
2. Edit config.xml and set valid listen-address for admin server.
<listen-address></listen-address>
3. Restart the server.
Option 2: The script or command to start the managed-server is wrong, it should be the Admin Server port, instead the managed-server.
Example:
$ startManagedWebLogic.sh your_managed_server t3://yourWLS:7010 &
Your AdminServer is running on port 7001 and you tried to launch on the managed-server port (7010), that's why the error.
It might have other solutions for the same message error, so if you know, let us know.
Hope this help.
Subscribe to:
Post Comments (Atom)
Configure the Oracle DB Access Control List to avoid error like ORA-24247: network access denied
Symptoms: You try to make external connections from the Oracle Database and receive erros like ORA-24247: network access denied by access c...
-
Symptoms: When trying to compile an Oracle Forms, it gives an error such as "FRM-30085: Unable to adjust form for output." Si...
-
Symptoms : When starting the Weblogic it presents error such as this: Error message: JPS-01055: Could not create credential store instanc...
-
Symptoms : When having a transaction with database link involved, it results in an error that says: ORA-03150: end-of-file on communicati...
No comments:
Post a Comment