[
http://issues.ops4j.org/browse/PAXRUNNER-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13370#action_13370
]
christophe commented on PAXRUNNER-334:
--------------------------------------
Yes, I meant : --vmOptions="-DMY_VAR1=var1 -DMY_VAR2=var2"
But this is not working ; however, I found a way to make it work, doing this :
PAX-RUND.SH --startd <provision_file>
With <provision_file> contents :
file:/path/to/bundle1/bundle1
file:/path/to/bundle2/bundle2
...
-DMY_VAR1=var1
-DMY_VAR2=var2
(instead of doing this :
PAX-RUND.SH --startd --vmOptions="-DMY_VAR1=var1 -DMY_VAR2=var2"
<provision_file>
With <provision_file> contents :
file:/path/to/bundle1/bundle1
file:/path/to/bundle2/bundle2
...
)
=> I would therefore suggest to move this defect to "Improvement" type (so that
-vmOptions can be interpreted by PAX-RUND.SH like it is by PAX-RUN.SH)
> PAX DAEMON : pax-rund.sh --startd run failure with vmOptions
> ------------------------------------------------------------
>
> Key: PAXRUNNER-334
> URL: http://issues.ops4j.org/browse/PAXRUNNER-334
> Project: Pax Runner
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: christophe
> Assignee: Alin Dreghiciu
>
> PAX-RUND.SH (PAX daemon launch command) does not work with the "--vmOptions"
> option, when this option contains several settings:
> => e.g.: PAX-RUND.SH --startd --vmOptions="-DMY_VAR1=var1" : works fine :-)
> => e.g.: PAX-RUND.SH --startd --vmOptions="-DMY_VAR1=var1 MY_VAR2=var2" :
> fails !
> Here is an example, obtained with PAXRUNNER 1.4.0 :
> PAX-RUND.SH --startd --vmOptions="-Dhttp.proxyHost=xx.yy.zz.tt
> -Dhttp.proxyPort=pppp -DMY_VAR=/tmp" <provision_file>
> => fails with this exception :
> Exception in thread "RunnerLauncher" java.lang.RuntimeException:
> org.ops4j.pax.scanner.MalformedSpecificationException: Specification
> [-DMY_VAR=/tmp] could not be used
> at org.ops4j.pax.runner.Run.installBundles(Run.java:490)
> at org.ops4j.pax.runner.Run.start(Run.java:216)
> at org.ops4j.pax.runner.Run.main(Run.java:147)
> While these same --vmOptions do work fine with the PAX-RUN command.
> This therefore appears to be a limitation related to the PAX-RUND --startd
> command...
> Thanking you for any fix (or workaround) on this isssue.
> Best Regards,
> Christophe.
> Nota: with (older) PAXRUNNER 1.1.0, the error obtained is different :
> PAX-RUND complains with:
> Exception in thread "RunnerLauncher" java.lang.RuntimeException:
> org.ops4j.pax.runner.provision.ScannerException: Could not parse the
> provision file
> => but the Exception obtained above with PAXRUNNER 1.4.0 looks more
> appropriate...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
