Article - CS285508
503 error is seen when accessing Composer in a ThingWorx High Availability(Active-Standby) envionrment in ThingWorx Platform
Modified: 19-Jul-2022
Applies To
- ThingWorx Platform 8.0 to 8.5
Description
- ThingWorx is not starting and am getting 503 error when accessing Composer in an HA(Active-Standby) structure
- ThingWorx starts with a 503 error indicating that the Platform is unavailable
- After several minutes the 503 error is resolved
- Following errors are seen in the Apache Tomcat and ThingWorx logs:
- Catalina.out in <Tomcat Home>\logs
- org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for servlet [LeaderCheck] in context with path [/Thingworx] threw exception
java.lang.IllegalStateException: Cannot call sendError() after the response has been committed - org.apache.catalina.core.StandardHostValve.custom Exception Processing ErrorPage[errorCode=500, location=/UnexpectedExceptionHandler]
java.lang.IllegalStateException: getOutputStream() has already been called for this response
- org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for servlet [LeaderCheck] in context with path [/Thingworx] threw exception
- ApplicationLog in <ThingworxStorage>\logs
- Authentication request failed for URI: /Thingworx/Admin/HA/LeaderCheck from RemoteAddress=<Instance IP Address> java.io.IOException: Connection reset by peer
- Catalina.out in <Tomcat Home>\logs
This is a printer-friendly version of Article 285508 and may be out of date. For the latest version click CS285508