[jira] Updated: (GERONIMO-1352) RMI port number is not specified in URL for JMXConnector in server config.xml files
[ http://issues.apache.org/jira/browse/GERONIMO-1352?page=all ] John Sisson updated GERONIMO-1352: -- Description: The port number should be specified in the JMXConnector URL so that a user can search and replace the current port number (e.g. 1099) with the new value. Currently the JMXConnector URL does not specified the port number therefore it always uses the default port. Currently if a user changes the RMI port number they will get exceptions at startup. I tried changing the JMXConnector URL to specify the port but it was not used. Basically this means if a site has port 1099 in use, they cannot run Geronimo. was: The port number should be specified in the JMXConnector URL so that a user can search and replace the current port number (e.g. 1099) with the new value. Currently the JMXConnector URL does not specified the port number therefore it always uses the default port. Currently if a user changes the RMI port number they will get exceptions at startup. > RMI port number is not specified in URL for JMXConnector in server config.xml > files > --- > > Key: GERONIMO-1352 > URL: http://issues.apache.org/jira/browse/GERONIMO-1352 > Project: Geronimo > Type: Bug > Components: startup/shutdown, usability > Reporter: John Sisson > Assignee: John Sisson > Fix For: 1.0 > > The port number should be specified in the JMXConnector URL so that a user > can search and replace the current port number (e.g. 1099) with the new value. > Currently the JMXConnector URL does not specified the port number therefore > it always uses the default port. > Currently if a user changes the RMI port number they will get exceptions at > startup. > I tried changing the JMXConnector URL to specify the port but it was not > used. Basically this means if a site has port 1099 in use, they cannot run > Geronimo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1352) RMI port number is not specified in URL for JMXConnector in server config.xml files
[ http://issues.apache.org/jira/browse/GERONIMO-1352?page=all ] John Sisson updated GERONIMO-1352: -- Fix Version: 1.1 (was: 1.0) Assign To: Aaron Mulder Assigned to you.. Matt made me! > RMI port number is not specified in URL for JMXConnector in server config.xml > files > --- > > Key: GERONIMO-1352 > URL: http://issues.apache.org/jira/browse/GERONIMO-1352 > Project: Geronimo > Type: Bug > Components: startup/shutdown, usability > Reporter: John Sisson > Assignee: Aaron Mulder > Fix For: 1.1 > > The port number should be specified in the JMXConnector URL so that a user > can search and replace the current port number (e.g. 1099) with the new value. > Currently the JMXConnector URL does not specified the port number therefore > it always uses the default port. > Currently if a user changes the RMI port number they will get exceptions at > startup. > I tried changing the JMXConnector URL to specify the port but it was not > used. Basically this means if a site has port 1099 in use, they cannot run > Geronimo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1352) RMI port number is not specified in URL for JMXConnector in server config.xml files
[ http://issues.apache.org/jira/browse/GERONIMO-1352?page=all ] John Sisson updated GERONIMO-1352: -- Fix Version: 1.0.1 (was: 1.1) Description: The port number should be specified in the JMXConnector URL so that a user can search and replace the current port number (e.g. 1099) with the new value. Currently the JMXConnector URL does not specified the port number therefore it always uses the default port. Currently if a user changes the RMI port number they will get exceptions at startup. *** I tried changing the JMXConnector URL to specify the port but it was not used. Basically this means if a site has port 1099 in use, they cannot run Geronimo. *** was: The port number should be specified in the JMXConnector URL so that a user can search and replace the current port number (e.g. 1099) with the new value. Currently the JMXConnector URL does not specified the port number therefore it always uses the default port. Currently if a user changes the RMI port number they will get exceptions at startup. I tried changing the JMXConnector URL to specify the port but it was not used. Basically this means if a site has port 1099 in use, they cannot run Geronimo. > RMI port number is not specified in URL for JMXConnector in server config.xml > files > --- > > Key: GERONIMO-1352 > URL: http://issues.apache.org/jira/browse/GERONIMO-1352 > Project: Geronimo > Type: Bug > Components: startup/shutdown, usability > Reporter: John Sisson > Assignee: Aaron Mulder > Fix For: 1.0.1 > > The port number should be specified in the JMXConnector URL so that a user > can search and replace the current port number (e.g. 1099) with the new value. > Currently the JMXConnector URL does not specified the port number therefore > it always uses the default port. > Currently if a user changes the RMI port number they will get exceptions at > startup. > *** I tried changing the JMXConnector URL to specify the port but it was not > used. Basically this means if a site has port 1099 in use, they cannot run > Geronimo. *** -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira