Deployments Fail Due to Corruption in Version File Store, IOException in Log: Unexpected end of stream while reading deployment protocol
(Doc ID 1663392.1)
Last updated on OCTOBER 02, 2018
Applies to:Oracle Commerce Platform - Version 9.4 and later
Information in this document applies to any platform.
Deployments fail as a result of problems with a file asset, such as targeter or scenario .properties file, in the VersionFileStore . In the BCC UI, the deployment status shows that the deployment failed and references a versioned file that the VersionManagerService is trying to reference.
Deployment Status: Error Applying
Deployment FailedDeployment 'ID' to target 'TARGET' encountered a system level deployment error during data transfer.
The BCC log may show a general deployment error such as this:
It is possible, but not mandatory, that a problem occurred during a previous deployment. For example, a deployment was run and a target was restarted in the middle, or a previous deployment failed. It is also possible that no specific deployment problem was detected.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|1. Analyze Versioned Folder Data|
|2a. Corrupt Folder Not Needed|
|2b. Corrupt Folder Needs Correct Parent|
|3. Restart BCC and Re-Test|