UPDATE_STOP Messages Indicate "Unable To Connect To Geocode Server" and "STOP could not be geocoded" (Doc ID 1370089.1)

Last updated on JULY 31, 2012

Applies to:

Oracle Real-Time Scheduler - Version: 10.4.9 and later   [Release: 10.4 and later ]
Information in this document applies to any platform.

Goal

Why are we seeing Geocode errors when processing stop updates?


RTS_WS388 18/10/11 16:00:01.06 MethodName : UPDATE_STOP
...
RTS_WS388 18/10/11 16:00:01.08 STOP <1234567> does not exist in the Data Base, it will be considered as new
RTS_WS388 18/10/11 16:00:02.14 send 84967 >><...<ns2:UPDATE_STOP_RESPONSE><<
RTS_WS388 18/10/11 16:00:02.14 send 84967 >><ns2:RESULT><ns3:RESULT>FAIL</ns3:RESULT><ns3:CLASS>REQUEST</ns3:CLASS></ns2:RESULT><<
RTS_WS388 18/10/11 16:00:02.14 send 84967 >><ns2:ERROR><ns3:TEXT>Unable to connect to GeoCode server on localhost:9010</ns3:TEXT></ns2:ERROR><<
RTS_WS388 18/10/11 16:00:02.14 send 84967 >><ns2:ERROR><ns3:TEXT>STOP <1234567> could not be geocoded</ns3:TEXT></ns2:ERROR><<



Solution

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