Problem

The orchestrator pod(s) in your private data-plane are unexpectedly restarting. Additionally, this error is often present in the orchestrator logs:

IntegrationException: Tunnel failed, got: 503

Resolution

This is most likely caused by having an HTTP proxy configured within a "Java Service" component, and used in an integration. When a Java service implements an HTTP proxy, it affects all integrations running on the same pod.

Therefore, it is recommended to avoid using HTTP proxy within a Java Service component. There are tools and techniques in Fusion that should make it possible to overcome this issue. Feel free to contact Axway Support if you're encountering this issue and can't find a solution.