This issue does not occur when deploy the EARs manually.It occurs
intermittently when deploying the EARs using LCM and it is specific to
Weblogic only. Reason behind this is Weblogic (as opposed to JBoss and
Websphere) does not guarantee a particular start-up order of WARs within
an EAR.The initialization does rely on a particular start-up order.Thus
the null folder gets created sometimes.Hence it is always suggested to
restart the server in a particular order to ensure that intialization
happen...