[
https://jira.jboss.org/jira/browse/JOPR-50?page=com.atlassian.jira.plugin...
]
Heiko W. Rupp commented on JOPR-50:
-----------------------------------
This looks like sort of intentional:
// Attempt to load the connection now. If we cannot, do not consider the start
operation as failed. The only
// exception to this rule is if the connection cannot be made due to a JMX
security exception. In this case,
// we treat it as an invalid plugin configuration and throw the appropriate
exception (see the javadoc for
// ResourceComponent)
try {
loadConnection();
Underlying issue is here (as in JOPR-60) the unability to do a 2pc for plugin config
changes.
See also
http://jira.rhq-project.org/browse/RHQ-1475
Specifying wrong jnp port when connecting to JBAS doesn't prevent
plugin config from being saved
------------------------------------------------------------------------------------------------
Key: JOPR-50
URL:
https://jira.jboss.org/jira/browse/JOPR-50
Project: Jopr
Issue Type: Bug
Components: Plugin - JBoss AS 4
Reporter: Charles Crouch
Assignee: Heiko W. Rupp
Priority: Critical
Fix For: 2.2
I thought previously we would get an exception when updating the plugin config if we
couldnt connect to the server with the new settings.
e.g. specifying "jnp://127.0.0.1:23499" results in "Connection properties
updated. ", but no new services are discovered because we can't actually connect
on that port.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira