Things to check that AJP works properly on the Axon.ivy Engine side: **Check that AJP is Enabled** and verify that you try to connect to the correct Port. By default AJP is enabled and bound to TCP port 8009. - you can the AJP settings in the EngineConfigUI: <img src="https://answers.axonivy.com/upfiles/WebServerPorts.png" height="300"> - or in the Admin UI. See System Properties > `Webserver.AJP.Enabled` and `Webserver.AJP.Port`. - changes on these properties (EngineConfigUi oder AdminUI) always require a restart of the Engine to take effect! ---------- **Verify that the TCP Port was bound** By default this is TCP Port 8009 which must be bound during the Engine boot and is waiting to receive packets. - on windows: execute `netstat` ![alt text][1] - on linux: execute `lsof -i` ![alt text][2] - if the port is not bound. Try to log the AJP connector bootstrap to get more results: https://answers.axonivy.com/questions/3318/how-to-log-ajp-connector-bootstrap ---------- **Examine IIS <-> Axon.ivyEngine communication** Enable isap-redirect trace logging to examine in detail the communication between the IIS and the Axon.ivy Engine. - Go to your IIS integration directory. By default `[engineDir]/misc/iis/isapi_redirect-1.2.42.properties`. In a productive installation you hopefully have copied that directory to another location outside your current installation directory. - Adjust the content of the file. Set `log_level=debug`, save it. And fire a request against the IIS frontend with your browser. <img src="https://answers.axonivy.com/upfiles/isapiDebugLog.png" height="200"/> [1]: https://answers.axonivy.com/upfiles/ajpListener_windows.png [2]: https://answers.axonivy.com/upfiles/ajpListenerLinux.png

Things to check that AJP works properly on the Axon.ivy Engine side: **Check that AJP is Enabled** and verify that you try to connect to the correct Port. By default AJP is enabled and bound to TCP port 8009. - you can the AJP settings in the EngineConfigUI: <img src="https://answers.axonivy.com/upfiles/WebServerPorts.png" height="300"> - or in the Admin UI. See System Properties > `Webserver.AJP.Enabled` and `Webserver.AJP.Port`. - changes on these properties (EngineConfigUi oder AdminUI) always require a restart of the Engine to take effect! ---------- **Verify that the TCP Port was bound** By default this is TCP Port 8009 which must be bound during the Engine boot and is waiting to receive packets. - on windows: execute `netstat` ![alt text][1] - on linux: execute `lsof -i`-i` ![alt text][2] ---------- **Examine IIS <-> Axon.ivyEngine communication** Enable isap-redirect trace logging to examine in detail the communication between the IIS and the Axon.ivy Engine. - Go to your IIS integration directory. By default `[engineDir]/misc/iis/isapi_redirect-1.2.42.properties`. In a productive installation you hopefully have copied that directory to another location outside your current installation directory. - Adjust the content of the file. Set `log_level=debug`, save it. And fire a request against the IIS frontend with your browser. <img src="https://answers.axonivy.com/upfiles/isapiDebugLog.png" height="200"/>height="200"/> [1]: https://answers.axonivy.com/upfiles/ajpListener_windows.png [2]: https://answers.axonivy.com/upfiles/ajpListenerLinux.png

Things to check that AJP works properly on the Axon.ivy Engine side: **Check that AJP is Enabled** and verify that you try to connect to the correct Port. By default AJP is enabled and bound to TCP port 8009. - you can the AJP settings in the EngineConfigUI: <img src="https://answers.axonivy.com/upfiles/WebServerPorts.png" height="300"> - or in the Admin UI. See System Properties > `Webserver.AJP.Enabled` and `Webserver.AJP.Port`. - changes on these properties (EngineConfigUi oder AdminUI) always require a restart of the Engine to take effect! **Verify that the TCP Port was bound** By default this is TCP Port 8009 which must be bound during the Engine boot and is waiting to receive packets. - on windows: execute `netstat` - on linux: execute `lsof -i` **Examine IIS <-> Axon.ivyEngine communication** Enable isap-redirect trace logging to examine in detail the communication between the IIS and the Axon.ivy Engine. - Go to your IIS integration directory. By default `[engineDir]/misc/iis/isapi_redirect-1.2.42.properties`. In a productive installation you hopefully have copied that directory to another location outside your current installation directory. - Adjust the content of the file. Set `log_level=debug`, save it. And fire a request against the IIS frontend with your browser. <img src="https://answers.axonivy.com/upfiles/isapiDebugLog.png" height="200"/>

Things to check that AJP works properly on the Axon.ivy Engine side: **Check that AJP is Enabled** and verify that you try to connect to the correct Port. By default AJP is enabled and bound to TCP port 8009. - you can the AJP settings in the EngineConfigUI: <img src="https://answers.axonivy.com/upfiles/WebServerPorts.png" height="300"> - or in the Admin UI. See System Properties > `Webserver.AJP.Enabled` and `Webserver.AJP.Port`. - changes on these properties (EngineConfigUi oder AdminUI) always require a restart of the Engine to take effect! **Verify that the TCP Port was bound** By default this is TCP Port 8009 which must be bound during the Engine boot and is waiting to receive packets. - on windows: execute `netstat` - on linux: execute `lsof -i` **Examine IIS <-> Communication logs**Axon.ivyEngine communication** Enable isap-redirect trace logging to examine detail the communication between the IIS and the Axon.ivy Engine. - Go to your IIS integration directory. By default `[engineDir]/misc/iis/isapi_redirect-1.2.42.properties`. In a productive installation you hopefully have copied that directory to another location outside your current installation directory. - Adjust the content of the file. Set `log_level=debug`, save it. And fire a request against the IIS frontend with your browser. <img src="https://answers.axonivy.com/upfiles/isapiDebugLog.png" height="200"/>

Things to check that AJP works properly on the Axon.ivy Engine side: - Check that AJP is Enabled **Check that AJP is Enabled** and verify that you try to connect to the correct Port. By default AJP is enabled and bound to TCP port 8009. 1. - you can the AJP settings in the EngineConfigUI: <img src="https://answers.axonivy.com/upfiles/WebServerPorts.png" height="300"> 2. - or in the Admin UI. See System Properties > `Webserver.AJP.Enabled` and `Webserver.AJP.Port`. 3. - changes on these properties (EngineConfigUi oder AdminUI) always require a restart of the Engine to take effect! - Verify **Verify that the TCP Port of AJP (default 8009) could was bound** By default this is TCP Port 8009 which must be bound on during the Engine boot and is waiting to receive packets. 1. - on windows: execute `netstat` 2. - on linux: execute `lsof -i` - **Examine IIS <-> Communication logs** Enable isap-redirect trace logging to examine detail the communication between the IIS and the Axon.ivy Engine. 1. - Go to your IIS integration directory. By default `[engineDir]/misc/iis/isapi_redirect-1.2.42.properties`. In a productive installation you hopefully have copied that directory to another location outside your current installation directory. 2. - Adjust the content of the file. Set `log_level=debug`, save it. And fire a request against the IIS frontend with your browser. <img src="https://answers.axonivy.com/upfiles/isapiDebugLog.png" height="200"/>

Things to check that AJP works properly on the Axon.ivy Engine side: - Check that AJP is Enabled and verify that you try to connect to the correct Port. By default AJP is enabled and bound to TCP port 8009. 1. you can the AJP settings in the EngineConfigUI: <img src="https://answers.axonivy.com/upfiles/WebServerPorts.png" height="300"> 2. or in the Admin UI. See System Properties > `Webserver.AJP.Enabled` and `Webserver.AJP.Port`. 3. changes on these properties (EngineConfigUi oder AdminUI) always require a restart of the Engine to take effect! - Verify that the TCP Port of AJP (default 8009) could be bound on Engine boot and is waiting to receive packets. 1. on windows: execute `netstat` 2. on linux: execute `lsof -i` - Enable isap-redirect trace logging to examine detail the communication between the IIS and the Axon.ivy Engine. 1. Go to your IIS integration directory. By default `[engineDir]/misc/iis/isapi_redirect-1.2.42.properties`. In a productive installation you hopefully have copied that directory to another location outside your current installation directory. 2. Adjust the content of the file. Set `log_level=debug`, save it. And fire a request against the IIS frontend with your browser. <img src="https://answers.axonivy.com/upfiles/isapiDebugLog.png" height="200"/>

Things to check that AJP works properly on the Axon.ivy Engine side: 1. - Check that AJP is Enabled and verify that you try to connect to the correct Port. By default AJP is enabled and bound to TCP port 8009. - 1. you can the AJP settings in the EngineConfigUI: <img src="https://answers.axonivy.com/upfiles/WebServerPorts.png" height="300"> - 2. or in the Admin UI. See System Properties > `Webserver.AJP.Enabled` and `Webserver.AJP.Port`. - 3. changes on these properties (EngineConfigUi oder AdminUI) always require a restart of the Engine to take effect! 2. - Verify that the TCP Port of AJP (default 8009) could be bound on Engine boot and is waiting to receive packets. - 1. on windows: execute `netstat` - 2. on linux: execute `lsof -i` 3. - Enable isap-redirect trace logging to examine detail the communication between the IIS and the Axon.ivy Engine. - 1. Go to your IIS integration directory. By default `[engineDir]/misc/iis/isapi_redirect-1.2.42.properties`. In a productive installation you hopefully have copied that directory to another location outside your current installation directory. - 2. Adjust the content of the file. Set `log_level=debug`, save it. And fire a request against the IIS frontend with your browser. <img src="https://answers.axonivy.com/upfiles/isapiDebugLog.png" height="200"/>

Things to check that AJP works properly on the Axon.ivy Engine side: 1. Check that AJP is Enabled and verify that you try to connect to the correct Port. By default AJP is enabled and bound to TCP port 8009. - you can the AJP settings in the EngineConfigUI: <img src="https://answers.axonivy.com/upfiles/WebServerPorts.png" height="300"> - or in the Admin UI. See System Properties > `Webserver.AJP.Enabled` and `Webserver.AJP.Port`. - changes on these properties (EngineConfigUi oder AdminUI) always require a restart of the Engine to take effect! 2. Verify that the TCP Port of AJP (default 8009) could be bound on Engine boot and is waiting to receive packets. - on windows: execute `netstat` - on linux: execute `lsof -i` 3. Enable isap-redirect trace logging to examine detail the communication between the IIS and the Axon.ivy Engine. - Go to your IIS integration directory. By default `[engineDir]/misc/iis/isapi_redirect-1.2.42.properties`. In a productive installation you hopefully have copied that directory to another location outside your current installation directory. - Adjust the content of the file. Set `log_level=debug`, save it. And fire a request against the IIS frontend with your browser. <img src="https://answers.axonivy.com/upfiles/isapiDebugLog.png" height="200"/>