Bug 1278061 - Optaplanner-examples uses same jvm instance as maven when exec plugin is used
Optaplanner-examples uses same jvm instance as maven when exec plugin is used
Status: NEW
Product: JBoss BRMS Platform 6
Classification: JBoss
Component: OptaPlanner (Show other bugs)
6.2.0
Unspecified Unspecified
low Severity medium
: ---
: ---
Assigned To: Geoffrey De Smet
Jiri Locker
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-04 11:02 EST by jvahala
Modified: 2016-04-28 01:08 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description jvahala 2015-11-04 11:02:45 EST
Description of problem:
running optaplanner-examples in command line is done by command "mvn exec:java" right now. Problem is, that maven doesn't fork this into separated JVM instance, so examples are not executed with JVM arguments in plugin. This might cause non trivial performance issues. 

Actual results:
maven should execute examples in separated JVM

Expected results:
examples are executed in default jvm for maven

how to reproduce: 
1. build optaplanner-examples
2. run mvn exec:java
3. open jvisualvm and see actual java instances
Comment 2 Geoffrey De Smet 2015-11-04 11:17:03 EST
From maven-exec-plugin's exec:java goal: "Note: as the execution is not forked, some system properties required by the JVM cannot be passed here. Use MAVEN_OPTS or the exec:exec instead."


For some time we used exec:exec, but for some reason we had to switch:
  https://github.com/droolsjbpm/optaplanner/commit/bedf8dc913ed86fd17a7e2a353b15e7601f851c0

I've recall correctly the main reason was that users were expecting exec:java to work, and it was too much trouble to educate them to use exec:exec.
Comment 3 Geoffrey De Smet 2015-11-04 11:46:52 EST
This issue is blocked by this upstream issue in the maven-exec-plugin:
  https://github.com/mojohaus/exec-maven-plugin/issues/10

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