Thanks Huisheng,
I have solved the issue. The reason we did not use default jbpm cfg file is because the spring support in jbpm4.2 is not very smoothy, we load every element into a single configuration file so can easily do troubleshooting. We will consider to use the default jbpm cfg file in future. Thanks to your advise