Deployment Gets Stuck for 2 Hours if A Non Essential Agent Not Responding

(Doc ID 2113068.1)

Last updated on MARCH 08, 2016

Applies to:

Oracle Commerce Platform - Version and later
Information in this document applies to any platform.


If a non-essential deployment agent is good before deployment and then goes down during deployment, the CA server will get stuck for 2 hours until RMI connection is timed out. Following are the reproducible steps:

1. Make sure all non-essential deployment agents are good and accessible;

2. Start deployment;

3. Bring down a non-essential agent during the ACTIVE_ACTIVATE stage. The deployment thread on CA server looks fine as shown below: 

5. Restart the non-essential agent before 2 hours. The problem is even after the problematic agent is available again before the 2 hours, the deployment is still stuck until after 2 hours. 


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms