OpenSRF

  1. Bug #1703411
  2. Comment #5

Comment 5 for bug 1703411

Revision history for this message
Bill Erickson (berick) wrote :

I think this is the smoking gun (from router.log):

router 2018-08-28 12:02:20 [INT :11785:socket_bundle.c:891:] Socket 3 Read 178 bytes and data: <message xml:lang='en' <email address hidden>/router' <email address hidden>/opensrf.settings_listener_localhost_11792'><body>registering</body><thread/></message>
router 2018-08-28 12:02:20 [DEBG:11785:osrf_router.c:284:] osrfRouterHandleIncoming(): investigating message from <email address hidden>/opensrf.settings_listener_localhost_11792
router 2018-08-28 12:02:20 [ERR :11785:osrf_parse_json.c:844:] *JSON Parser Error
 - char = r
 - index = 1
 - near => registering
 - Unexpected character
router 2018-08-28 12:02:20 [WARN:11785:osrf_message.c:548:] osrfMessageDeserialize() unable to parse data: registering

It looks like the local/custom router XML attributes (router_command, router_class, osrf_xid, etc.) are getting stripped from the message, so the router doesn't know how to handle the message.