Bug 1058254 - A spring application is not initialized on a windows machine
Summary: A spring application is not initialized on a windows machine
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: BRE
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER2
: 6.0.1
Assignee: Mario Fusco
QA Contact: Ivo Bek
URL:
Whiteboard:
Depends On: 1051585
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-27 10:53 UTC by Ivo Bek
Modified: 2014-08-06 19:59 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Windows 2012
Last Closed: 2014-08-06 19:59:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
the spring application (4.53 MB, application/zip)
2014-01-27 10:53 UTC, Ivo Bek
no flags Details
spring framework module (2.74 MB, application/zip)
2014-01-27 10:54 UTC, Ivo Bek
no flags Details
server log on Windows 2012 (139.65 KB, text/x-log)
2014-01-27 10:55 UTC, Ivo Bek
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker DROOLS-364 0 Major Resolved ClasspathKieProject fails vfs: path for jar deployments and exploded ear 2014-05-12 19:02:25 UTC

Description Ivo Bek 2014-01-27 10:53:21 UTC
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:

Comment 1 Ivo Bek 2014-01-27 10:54:56 UTC
Created attachment 856010 [details]
spring framework module

Comment 2 Ivo Bek 2014-01-27 10:55:40 UTC
Created attachment 856011 [details]
server log on Windows 2012

Comment 3 Marek Winkler 2014-01-27 11:21:02 UTC
Possible duplicate of BZ 1051585.

Comment 4 Edson Tirelli 2014-01-28 13:54:43 UTC
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.

Comment 5 Mario Fusco 2014-01-30 16:02:17 UTC
Fixed by https://github.com/droolsjbpm/drools/commit/dc0b5f293

Comment 6 JBoss JIRA Server 2014-01-30 16:05:16 UTC
Mario Fusco <mario.fusco> updated the status of jira DROOLS-364 to Resolved

Comment 7 Lukáš Petrovický 2014-02-07 16:19:21 UTC
This no longer has a target release of 6.0.0.

Comment 8 Marek Winkler 2014-02-21 16:38:43 UTC
The problem persists. Fixing this issue very likely depends on (or even might be fixed) by fixing BZ 1051585. Please see the reproducer there.

Comment 10 Ivo Bek 2014-03-11 10:06:35 UTC
Verified in BPMS 6.0.1.ER2


Note You need to log in before you can comment on or make changes to this bug.