SAP components fail to start when child container is first deployed in Fabric environment. Components fail to start due to class loading issue: JCo classes not found. This only happens on the initial deployment of child container and subsequent restarts of the container always succeed.

I believe there is a race condition between the SAP libraries being first deployed to the child container's environment and the initial startup of the child container. The libraries most likely are not fully deployed when the child container first starts up.

In general, I think the deployment of libraries to a child container's environment needs to be coordinated with the start up of that child container and the startup of that child container be delayed until the deployment of libraries is complete.