Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Document jar options

Description

Not being able to set a port for the java process to bind to is breaking any deployment not based on containers. Please change that - it's bad behavior for a software to only bind to a predefined (and even standardized alternative HTTP) port.

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Julian Ladisch November 11, 2020 at 10:02 AM

Johannes Drexl November 11, 2020 at 9:43 AM
Edited

Right, in the RMB-documentation. But I'm not installing RMB, nor does the module description page states anything about RMB or what that is used for.

Don't get me wrong: You're trying. But documentation is not done solely for devs. And at the moment it seems modules use -Dport, -Dhttp.port or none of it at all at random. So what worked for mod-test and mod-authtoken did not work for quite a lot of other modules, hence those tasks spawned.

Yes, -Dhttp.port works. Task may be switched to 'document the/all settings' and closed afterwards.

Julian Ladisch November 10, 2020 at 5:56 PM

Cannot reproduce.

v1.6.0:

git checkout v1.6.0 mvn clean install java -Dhttp.port=9999 -jar target/mod-event-config-fat.jar

Output shows

10 Nov. 2020 18:47:58:801 INFO LogUtil [] org.folio.rest.RestVerticle start http server for apis and docs started on port 9999.

and using http://localhost:9999 works, for example POST http://localhost:9999/_/tenant

Today's master:

git checkout 5e8884a81edf3dcf1ba047878251ba5c31515d10 mvn clean install java -Dhttp.port=9999 -jar target/mod-event-config-fat.jar

Logging is broken but http://localhost:9999 works, for example POST http://localhost:9999/_/tenant

The port option http.port works as documented in the RMB documentation: https://github.com/folio-org/raml-module-builder#command-line-options

Done

Details

Assignee

Reporter

Priority

Development Team

Core: Platform

Fix versions

Release

R1 2021

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created November 10, 2020 at 9:59 AM
Updated March 9, 2021 at 3:22 PM
Resolved March 9, 2021 at 3:22 PM
Configure
TestRail: Cases
TestRail: Runs

Flag notifications