OWSM Error Message: WSM-02120 ... Connection refused; No available router to destination
(Doc ID 1569900.1)
Last updated on MAY 15, 2023
Applies to:
Oracle Web Services Manager - Version 11.1.1.4.0 to 11.1.1.9.0 [Release 11gR1 to 11g]Information in this document applies to any platform.
Symptoms
In the diagnostic log of the Weblogic Server, messages similar to the following are observed:
[ERROR] [WSM-02120] [oracle.wsm.resources.policymanager] [tid: [STANDBY].ExecuteThread: '3' for queue:
'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: <ECID>] [APP: wsm-pm] Unable to connect to the policy access service.[[
oracle.wsm.policymanager.PolicyManagerException: WSM-02120 : Unable to connect to the policy access service.
[...]
Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://<HOST>:<PORT>: Destination unreachable; nested exception is: java.net.ConnectException: Connection refused; No available router to destination]
'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: <ECID>] [APP: wsm-pm] Unable to connect to the policy access service.[[
oracle.wsm.policymanager.PolicyManagerException: WSM-02120 : Unable to connect to the policy access service.
[...]
Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://<HOST>:<PORT>: Destination unreachable; nested exception is: java.net.ConnectException: Connection refused; No available router to destination]
This can cause subsequent problems. For example, the server might fail to start up, or any web services with attached OWSM policies might fail.
Changes
The messages are normally harmless if observed during AdminServer startup in a domain where wsm-pm is not targeted to the AdminServer.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Potential Cause 1: servers not started up yet |
| Potential Cause 2: misconfigured Policy Accessor URL |
| Potential Cause 3: inconsistent SSL configuration |
| Potential Cause 4: ListenAddress |
| Solution |
| References |