Categories
Knowledge Support Support exacqVision Webservice Categories Products

Web service rendered unresponsive if push notifications cannot reach AWS

Affected platforms

Web Service 7.2.0, 7.2.1

<br>

Symptom

In the 7.2.0 release candidate of web service, if the machine the web service is running on does not have access to Amazon Web Services (AWS) for push notifications, the web service will crash on start.

In the 7.2.1 release candidate of web service, if the machine the web service is running on does not have access to AWS for push notifications, the web service will block other HTTP requests to the web server while trying to reach AWS, rendering the web server unresponsive.

<br>

Workaround

If the machine does not have access to AWS (e.g. behind a corporate firewall with no Internet access) push notifications will not work and should be disabled. This ensures that the web service won’t crash or become unresponsive.

To disable push notifications:

  1. Login to the webservice configuration page service.web.
  2. Uncheck all of the power user process checkboxes (if any)

Leaving the power user processes enabled without internet access can cause the web service to not respond to any HTTP requests while it is busy trying to contact AWS services.

<br>

Resolution

No resolution available at this time.

Categories
Knowledge Support Support exacqVision Mobile Categories Products

Push Notifications only received from one web service

Affected platforms

  • Exacq Mobile 3, version 7.2.0

<br>

Symptom

The Exacq Mobile 3 app can connect to multiple different web servers, but Exacq Mobile 3 will only be able to receive push notifications from the first web service even though Event Monitors from different web services are enabled in the push notification configuration.

<br>

Workaround

Uninstall and reinstall the app to configure and receive push notifications from a different web server.

<br>

Resolution

Fixed in Exacq Mobile 3, version 7.2.1