Uploaded image for project: 'JS - JobScheduler'
  1. JS - JobScheduler
  2. JS-209

Job Scheduler crashes with "Connection reset by peer" (on web service call)

    XMLWordPrintable

Details

    Description

      A Web Service is called once a minute.
      2-3 times a week the Job Scheduler crashes:
      00:03:23.424 scheduler 59985 4956.384 207.227MB .

      {scheduler.call} Java_module_instance.spooler_process() begin
      00:03:23.439 scheduler 15 4956.384 207.227MB .xsltApplyStylesheet( "config/scheduler_soap_request.xslt" )
      00:03:23.455 scheduler 31 4812.129C 217.273MB ..{scheduler} [info] (Task monitor_check_status:3534) message stack has been reset
      00:03:23.470 scheduler 16 4812.129C 217.273MB ..{scheduler} [info] (Task monitor_check_status:3534) Message ignored cause Parameter exclude messages found for [logline=2007-12-19 00:02:42.955 [WARN] (Supervisor_client 10.84.180.37/abslls037.sto.alfredberg.se:4444) WINSOCK-10061 Socket is not connected - Connection refused [connect] [10.84.180.37:4444][report_counter=1]]
      00:03:23.470 scheduler 0 4812.129C 217.273MB ..{scheduler} [info] (Task monitor_check_status:3534) 0 errors, 0 warnings found
      00:03:23.486 scheduler 15 4812.129C 217.273MB ..open("C:/scheduler/logs/order.monitor_service.100715.log") => 20
      00:03:23.486 scheduler 0 4812.129C 217.273MB ..close(20) C:/scheduler/logs/order.monitor_service.100715.log
      00:03:23.486 scheduler 47 4956.384 207.227MB .xsltApplyStylesheet( "config/scheduler_soap_response.xslt" )
      00:03:23.486 scheduler 0 4956.384 207.227MB .{scheduler.call}

      Java_module_instance.spooler_process() end
      00:03:23.502 scheduler 16 4812.129C 217.273MB .

      {scheduler}

      Execute <?xml version="1.0" encoding="ISO-8859-1"?><show_state what="" max_orders="0"/>
      00:03:23.502 scheduler 0 4812.129C 217.273MB .xmlSchemaValidateDoc()
      00:03:30.549 scheduler 7063 4956.384 207.227MB [ERROR WINSOCK-10054 WSAECONNRESET - Connection reset by peer [recv]]
      00:03:30.549 scheduler 0 4956.384 207.227MB [ERROR WINSOCK-10054 WSAECONNRESET - Connection reset by peer [recv]]
      00:03:30.549 scheduler 0 4956.384 207.227MB [xc.append "pid=0"]
      00:03:30.549 scheduler 0 4956.384 207.227MB zschimmer::Async_operation::async_continue ERROR WINSOCK-10054 WSAECONNRESET - Connection reset by peer [recv] / pid=0, Simple_operation(state=waiting,method=Release)
      00:03:30.564 scheduler 15 4956.384 207.227MB [ERROR WINSOCK-10054 WSAECONNRESET - Connection reset by peer [recv] / pid=0]
      00:03:30.564 scheduler 0 4956.384 207.227MB [xc.append "zschimmer::com::object_server::Connection::pop_operation"]
      00:03:30.564 scheduler 0 4956.384 207.227MB ERROR in zschimmer::com::object_server::Proxy::~Proxy, calling release(): WINSOCK-10054 WSAECONNRESET - Connection reset by peer [recv] / pid=0 / zschimmer::com::object_server::Connection::pop_operation
      00:03:30.564 scheduler 0 4956.384 207.227MB [ERROR WINSOCK-10054 WSAECONNRESET - Connection reset by peer [send]]
      00:03:30.564 scheduler 0 4956.384 207.227MB [ERROR WINSOCK-10054 WSAECONNRESET - Connection reset by peer [send]]
      00:03:30.564 scheduler 0 4956.384 207.227MB [xc.append "pid=0"]

      This has been observed on Windows and Linux

      Attachments

        1. error.txt
          12 kB
        2. hs_err_pid20517.log
          20 kB

        Activity

          People

            al Andreas Liebert (Inactive)
            al Andreas Liebert (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: