javax.naming.CommunicationException Root exception is java.net.ConnectException t3://servername:port: Destination unreachable

Issues in hyperion 11:

Error msg:

javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://<servername>:<port>: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:47)
atweblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:618)
atweblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:306) at weblogic.jndi.Environment.getContext(Environment.java:166)
at weblogic.jndi.Environment.getInitialContext(Environment.java:145)
atweblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(MBeanHomeTool.java:172)
at weblogic.Deployer.runBody(Deployer.java:709)
at weblogic.utils.compiler.Tool.run(Tool.java:146)
at weblogic.utils.compiler.Tool.run(Tool.java:103)
at weblogic.Deployer.runMain(Deployer.java:566)
at weblogic.Deployer.main(Deployer.java:549)
Caused by: java.net.ConnectException: t3://ep-prdapp1:10080: Destination unreachable; nested exception is java.net.ConnectException: Connection refused; No available router to destination 

at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
atweblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296)
... 8 more 

Solution:

This is an issue with the replication of the Embedded LDAP updates and is defined by the replicas.prop property file.

Find user_domain \ user_server \ ldap \ conf \ replicas.prop, edit this file, deleted all the content and add the following text: 

Replica.num = 0

Re-start the server.

Note: You can back up the replicas.prop file before editing it. The file may be empty or have some text.

JPS-01050: Opening of wallet based credential store failed.

JPS-01050: Opening of wallet based credential store failed. 

Reason java.io.IOException: PKI-02002: Unable to open the wallet.

Check password.

Server state changed to FORCE_SHUTTING_DOWN (Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.)

 When starting Weblogic, we are getting the issue in weblogic and it going down automatically.

 <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.

weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException: PKI-02002: Unable to open the wallet. Check password.

Solution:

We navigated to <Middleware_Home>/user_projects/domains/<Your Domain>/config/fmwconfig/ folder and observed that cwallet.sso is corrupted and file size is 0(zero) kb . Here we renamed this file(cwallet.sso_bkp) and successfully started Adminserver .