Article - CS367831

Unable to access the Windchill Application showing, "502 Bad Gateway Microsoft-Azure-Application-Gateway/v2" in web page

Modified: 29-Oct-2024   


Applies To

  • Windchill PDMLink 11.2 to 12.1

Description

  • Not able to access the Windchill PDMLink
  • Method sever logs shows "MethodServer ready" but Windchill application not starting
  • 502 Bad Gateway Error after updating SSL Certificates 
  • Method Server fails to start 
  • Error showed in web page
  • 502 Bad Gateway Error
  • Error in mod_jk.log file:
[error] service::jk_lb_worker.c (1685): All tomcat instances failed, no more workers left
[error] ajp_send_request::jk_ajp_common.c (1733): (tomcat1) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=111)
[error] ajp_service::jk_ajp_common.c (2817): (tomcat1) connecting to tomcat failed (rc=-3, errors=7, client_errors=0).
[error] service::jk_lb_worker.c (1685): All tomcat instances failed, no more workers left
This is a printer-friendly version of Article 367831 and may be out of date. For the latest version click CS367831