Last updated on JUNE 12, 2017
Applies to:
Oracle Real-Time Scheduler - Version 2.3.0.1.0 and laterOracle Utilities Mobile Workforce Management - Version 2.3.0.1.0 and later
Information in this document applies to any platform.
Symptoms
After re-configuring the environment to use SSL, the application comes up and IWS deploys. However, the threadpoolworker (TPW) is no longer working properly. Users are not able to use the Chooser or make appointment requests.
The following error is seen in the TPW log:
- 201x-06-05 16:21:49,835 [DEFAULTWorker:12] ERROR (process.request.JMSSchedulerRequest) Cannot initialize JMS scheduler request provider.
javax.naming.CommunicationException: t3s://server.com:7201: Destination 127.0.0.1, 7201 unreachable; nested exception is:
javax.net.ssl.SSLException: Received fatal alert: unexpected_message; No available router to destination [Root exception is java.net.ConnectException: t3s://server.com:7201: Destination 127.0.0.1, 7201 unreachable; nested exception is:
javax.net.ssl.SSLException: Received fatal alert: unexpected_message; No available router to destination]
javax.naming.CommunicationException: t3s://server.com:7201: Destination 127.0.0.1, 7201 unreachable; nested exception is:
javax.net.ssl.SSLException: Received fatal alert: unexpected_message; No available router to destination [Root exception is java.net.ConnectException: t3s://server.com:7201: Destination 127.0.0.1, 7201 unreachable; nested exception is:
javax.net.ssl.SSLException: Received fatal alert: unexpected_message; No available router to destination]
Cause
Sign In with your My Oracle Support account |
|
Don't have a My Oracle Support account? Click to get started |
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms