You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "John Sisson (JIRA)" <de...@geronimo.apache.org> on 2005/12/13 22:53:47 UTC
[jira] Created: (GERONIMO-1352) RMI port number is not specified in URL for JMXConnector in server config.xml files
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
Assigned to: 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.
--
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] Assigned: (GERONIMO-1352) RMI port number is not specified
in URL for JMXConnector in server config.xml files
Posted by "John Sisson (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1352?page=all ]
John Sisson reassigned GERONIMO-1352:
-------------------------------------
Assign To: John Sisson (was: Aaron Mulder)
> 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.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] Assigned: (GERONIMO-1352) RMI port number is not specified in URL for JMXConnector in server config.xml files
Posted by "John Sisson (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1352?page=all ]
John Sisson reassigned GERONIMO-1352:
-------------------------------------
Assign To: (was: John Sisson)
> 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
> 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
Posted by "John Sisson (JIRA)" <de...@geronimo.apache.org>.
[ 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] Closed: (GERONIMO-1352) RMI port number is not specified in
URL for JMXConnector in server config.xml files
Posted by "John Sisson (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1352?page=all ]
John Sisson closed GERONIMO-1352:
---------------------------------
> 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.1, 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
Posted by "John Sisson (JIRA)" <de...@geronimo.apache.org>.
[ 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] Commented: (GERONIMO-1352) RMI port number is not specified
in URL for JMXConnector in server config.xml files
Posted by "Lin Sun (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1352?page=comments#action_12362479 ]
Lin Sun commented on GERONIMO-1352:
-----------------------------------
If it helps, here's the syntax I used to specify the port, which worked well for me:
<gbean name="JMXService">
<attribute name="url">service:jmx:rmi://0.0.0.0/jndi/rmi://localhost:1098/JMXConnector</attribute>
</gbean>
> 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
[jira] Updated: (GERONIMO-1352) RMI port number is not specified in
URL for JMXConnector in server config.xml files
Posted by "John Sisson (JIRA)" <de...@geronimo.apache.org>.
[ 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
[jira] Resolved: (GERONIMO-1352) RMI port number is not specified
in URL for JMXConnector in server config.xml files
Posted by "John Sisson (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1352?page=all ]
John Sisson resolved GERONIMO-1352:
-----------------------------------
Fix Version: 1.1
Resolution: Fixed
> 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.1, 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