Cargo

Hardcoded Resin management port is 7777

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 0.8
  • Fix Version/s: 1.2.0
  • Component/s: Resin
  • Labels:
    None
  • Number of attachments :
    0

Description

I'm having a problem getting two Resin instances running (to test clustering) on one machine using Cargo.

I'm using the Maven 1 plugin.

I've tracked the problem down to the fact Cargo grabs port 7777 (see DefaultServerRun class), and thus the second instance can't start up with a bind exception.

There seems to be an args[] map in the class with a "-port X" option to specify the port, but I can't for the life of me figure out where that argument comes from.

Anyway, I think it's a bug that you can't start two instances - so I'm filing it as such, feel free to change to an improvement request.

Request: make the Cargo management port for Resin 2 configurable via a simple property (like Orion's RMI port).

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Matt Ryall added a comment -

This is an issue with the Resin 3 container as well.

Show
Matt Ryall added a comment - This is an issue with the Resin 3 container as well.
Hide
Permalink
Vincent Massol added a comment -

Implementation idea: add a custom resin property by creating a ResinPropertySet class.

Show
Vincent Massol added a comment - Implementation idea: add a custom resin property by creating a ResinPropertySet class.
Hide
Permalink
Stéphane Nicoll added a comment -

AH! I got it too. At least it should be documented that 7777 is not a valid HTTP port for the resin integration.

Show
Stéphane Nicoll added a comment - AH! I got it too. At least it should be documented that 7777 is not a valid HTTP port for the resin integration.
Hide
Permalink
hal arnold added a comment -

Is there any chance that this issue will get fixed? If there is a way to set the configuration in maven2 so that the port -x will get set, I'd like to know. Please consider implementing this, so that we can run two instances of Cargo

Show
hal arnold added a comment - Is there any chance that this issue will get fixed? If there is a way to set the configuration in maven2 so that the port -x will get set, I'd like to know. Please consider implementing this, so that we can run two instances of Cargo
Hide
Permalink
Savas Ali Tokmen added a comment -

Please use JVM argument: -port <newPortValue>

Show
Savas Ali Tokmen added a comment - Please use JVM argument: -port <newPortValue>
Hide
Permalink
Savas Ali Tokmen added a comment -

Reopening issue as CARGO 1.1.5 / 1.2.0 will include a new property.

Show
Savas Ali Tokmen added a comment - Reopening issue as CARGO 1.1.5 / 1.2.0 will include a new property.
Hide
Permalink
Savas Ali Tokmen added a comment -

Committed revision 3194.

Added new property: cargo.resin.socketwait.port / ResinPropertySet.SOCKETWAIT_PORT

Show
Savas Ali Tokmen added a comment - Committed revision 3194. Added new property: cargo.resin.socketwait.port / ResinPropertySet.SOCKETWAIT_PORT

People

Vote (3)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.