[FELIX-2063] [karaf] hardcoding org.ops4j.pax.exam.rbc.rmi.port property in raw pax runner --vmOptions is problematic when 1099 is not the next free port

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: karaf-1.4.0
• Fix Version/s: karaf-1.4.0
• Component/s: Karaf
• Assignee: Chris Custine
• Reporter: Eoghan Glynn
• Created: 10/Feb/10 01:00
• Updated: 10/Feb/10 06:41
• Resolved: 10/Feb/10 06:41

Description

Pax-runner calculates the next free port to use on the "client side" of the RMI connection, whereas the "server side" RMI registry takes its port from the org.ops4j.pax.exam.rbc.rmi.port property regardless of whether this is free or not.

Therefore the org.ops4j.pax.exam.rbc.rmi.port should not be hard-coded via the rawPaxRunnerOption("--vmOptions", ...) mechanism.

Now the whole point of setting the raw --vmOptions was to avoid the karaf-specific system.packages setting being overridden by pax-runner. However a similar effect can be achieved without having to specify a org.ops4j.pax.exam.rbc.rmi.port property if the org.ops4j.pax.exam.container.def.PaxRunnerOptions.vmOption is used instead of the org.ops4j.pax.exam.container.def.PaxRunnerOptions.rawPaxRunnerOption.

This approach appears to work even when another process is hogging port 1099.