Rod Simpson created USERGRID-228:
------------------------------------
Summary: Portal should not give username/password error when error
was due to some other problem
Key: USERGRID-228
URL: https://issues.apache.org/jira/browse/USERGRID-228
Project: Usergrid
Issue Type: Story
Components: Portal
Reporter: Rod Simpson
Assignee: Rod Simpson
Sometimes when Usergrid starts it errors gracefully if one of the ports is in
use (7000) sometimes it gives a timeout (8080) and sometimes it works (8080)
even though the port is used but then when you try the portal it tells you the
username/password was not valid when in fact the error is a 501 on ‘OPTIONS’,
though it could be a different error depending on what is already using the
port (screenshot below). This same behavior happens if the port cannot be
reached. So, the questions are:
1) Can we configure all the different ports using the Launcher JAR?
Including Cassandra?
2) Can we update the portal to display something other than invalid
user/name when this happens?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
