Created attachment 856009 [details] the spring application Description of problem: When I try to deploy the attached spring application on a windows machine, I will get exception whenever I start a business process because the process id is unknown. That is probably because pom.properties cannot be found though it is there and in RHEL this appplication works. I noticed one difference in server logs between RHEL 6 and Windows 2012. Virtual file physical path = /mnt/hudson_workspace/workspace/bpms-integration-os/648dab17/jboss-eap-6.1/standalone/tmp/vfs/temp3a40a14fd2aa82b3/content-d63ff8c2a28085c4/WEB-INF/classes versus this path on Windows which must be wrong: Virtual file physical path = w:\content\springapp.war\WEB-INF\classes I would say that the problem lies here: https://github.com/droolsjbpm/drools/blob/6.0.0.GA.x/drools-compiler/src/main/java/org/drools/compiler/kie/builder/impl/ClasspathKieProject.java#L342 It seems that jarFolderPath is empty and I believe this is the problem or something similar. There is also one important additional warning in the server log on Windows. 01:49:39,690 WARN [org.drools.compiler.kie.builder.impl.AbstractKieModule] (ServerService Thread Pool -- 138) No files found for KieBase kbase1, searching folder \workspace\bpms-integration-single\jboss-eap-6.1\modules\system\layers\base\sun\jdk\main\service-loader-resources Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Unzip spring framework archive into BPMS base org modules 2. Unzip the spring application archive and copy the war file into BPMS 6.0.0.CR2 deployments directory. 3. Start BPMS 6.0.0.CR2 and see the warnings in server log. Actual results: Expected results: Additional info:
Created attachment 856010 [details] spring framework module
Created attachment 856011 [details] server log on Windows 2012
Possible duplicate of BZ 1051585.
Mario, can you please double check if this problem is fixed by your changes on https://bugzilla.redhat.com/show_bug.cgi?id=1051585 . Thank you.
Fixed by https://github.com/droolsjbpm/drools/commit/dc0b5f293
Mario Fusco <mario.fusco> updated the status of jira DROOLS-364 to Resolved
This no longer has a target release of 6.0.0.
The problem persists. Fixing this issue very likely depends on (or even might be fixed) by fixing BZ 1051585. Please see the reproducer there.
Fixed by https://github.com/droolsjbpm/droolsjbpm-integration/commit/268fe7547
Verified in BPMS 6.0.1.ER2