Bug 674302 - RfE: Hard code port 7080 as default
Summary: RfE: Hard code port 7080 as default
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: CLI
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified vote
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-01 11:36 UTC by Heiko W. Rupp
Modified: 2022-03-31 04:27 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Heiko W. Rupp 2011-02-01 11:36:19 UTC
RHQ cli when started without  a host parameter (i.e. using localhost) is using port 7080:

snert:~/webinar/rhq-remoting-cli-4.0.0.B02 hrupp$ bin/rhq-cli.sh
RHQ - RHQ Enterprise Remote CLI 4.0.0.B02
unconnected$ login rhqadmin rhqadmin
Remote server version is: 4.0.0-SNAPSHOT(09b2f64)
Login successful

rhqadmin@localhost:7080$ quit


CLi when connecting to a different host is not assuming port 7080 which is not user friendly -- even if the login help message says [host port]:

snert:~/webinar/rhq-remoting-cli-4.0.0.B02 hrupp$ bin/rhq-cli.sh
RHQ - RHQ Enterprise Remote CLI 4.0.0.B02
unconnected$ login rhqadmin rhqadmin pintsize
org.jboss.remoting.CannotConnectException: Can not connect http client invoker. Connection refused.
....
Login failed: org.jboss.remoting.CannotConnectException: Can not connect http client invoker. Connection refused.
login username password [host port [transport]]

unconnected$ login rhqadmin rhqadmin pintsize 7080
Remote server version is: 4.0.0.B02(8308155)
Login successful

rhqadmin@pintsize:7080$ 



Btw; this should not print ArrayOutOfBoundsException, but "credentials missing":
unconnected$ login
Login failed: java.lang.ArrayIndexOutOfBoundsException: 1
login username password [host port [transport]]

Comment 1 Heiko W. Rupp 2011-02-01 12:36:09 UTC
Actually the 'help' message "login username password [host port [transport]]" is wrong, as the port is not needed if the server listens to the "right" port (probably 80).


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