Skip to main content

Support - Troubleshooting network problems (Ping test)

Updated over 2 months ago

If you are troubleshooting performance problems related to Coins ERP+, the Ping test can help to determine whether there are problems with the network. The Ping test runs on the userโ€™s browser so the affected users should leave it running on a tab in the background.

We recommend you run the Ping test on a good connection so you have a benchmark for comparison.

  1. Copy the URL from a Coins ERP+ screen on the environment you want to investigate.

  2. In a new browser tab or window, paste the URL into the address bar.

  3. Change the part of the URL that says wocoins.p (or wologin.p) to woping.p, and delete anything to the right of that.

    to

  4. Press Return.

  5. Set the Frequency.

    • For an intensive test over a short period, set to something like 10 seconds.

    • For background monitoring over a longer period of time, set to 30 or 60 seconds.

  6. If you want the test to stop automatically, set the Count. As an example, with a frequency of 60 and a count of 600, the test would run for 10 hours.

  7. Click Start.

    The test produces output similar to that shown below.

    • The Webserver Roundtrip is the time taken for a small request to be sent from the browser to the Apache web server and back again. It has no interaction with the application server so does not get delayed at all by any bottleneck with application server agents or with marshalling on or off the application server queues.

    • The Webspeed Roundtrip is the time taken for a small request to be sent from the browser to the Apache web server with a cgi request to the application server and back again. The request is tiny so the application server agent has to do very little, but it has to be available to respond so queuing would affect this.

    • The Webserver Load is the same timing as the Webserver Roundtrip above but with a much bigger payload to test for bandwidth/capacity.

The timings for the tests are also stored in the PASOE log file. You can view this using Log File Viewer if SY/WEBLOG is configured to include it.

Did this answer your question?