MDCSiftingAppender with custom Sift keys fails randomly to append to appropriate log files after fabric child container restarts

1. Unzip the testcase.zip to your local file system; 2. go to the project "mdcProfile" and build entire project by "mvn install"; 3. create a fabric and then create a child container with "gateway-http" profile: container-create-child --profile gateway-http root gateway 4. create another child container called "child"; container-create-child root child 5. import the profile with command" profile-import file:/local/testcase/01917967/spring/mdcProfile/target/mdcProfile-1.0-solution.zip 6. add the profile "mdc" to the child container "child" container-add-profile child mdc 7. then go to the child container's log folder "jboss-fuse-6.3.0.redhat-310/instances/child/data/log/", you will see the only log file "fuse.log" since I only had "MDCSiftingAppender" logger enabled but not the default "RollingFileAppender". 8. send a HTTP request using "curl" command: curl -H "Accept: application/json" -X GET http://localhost:8183/cxf/CxfRsRouterTest/route/customerservice/customers/123 and you will see these two new log files created "mywebproxy.log" and "mywebsrv.log. 9. restart the child container with command "container-stop child" and then "container-start child". You will see a file ".log" created without any prefix. 10. repeat the step #8 to send another request using utility "curl" to the service and then check for the two application specific log files "mywebproxy.log" and "mywebsrv.log. The MDCSiftingAppender fails randomly putting logs to the two application logs. Instead, those logs are always sent to the log file ".log". 11. If the steps #10 works somehow, then just repeat the step #9 and #10. It will fail randomly.