-
Feature Request
-
Resolution: Done
-
Major
-
8.0.0.Alpha4
-
None
use case:
[standalone@localhost:9990 /] /subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory:undefine-attribute(name=connector)
{
"outcome" => "failed",
"failure-description" => "JBAS014749: Operation handler failed: JBAS011664: Runtime handling for connector is not implemented",
"rolled-back" => true
}
and the server outputs the error:
17:05:08,295 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014612: Operation ("undefine-attribute") failed - address: ([
("subsystem" => "messaging"),
("hornetq-server" => "default"),
("connection-factory" => "RemoteConnectionFactory")
]): java.lang.UnsupportedOperationException: JBAS011664: Runtime handling for connector is not implemented
at org.jboss.as.messaging.jms.ConnectionFactoryWriteAttributeHandler.applyOperationToHornetQService(ConnectionFactoryWriteAttributeHandler.java:184)
at org.jboss.as.messaging.jms.ConnectionFactoryWriteAttributeHandler.applyUpdateToRuntime(ConnectionFactoryWriteAttributeHandler.java:96)
at org.jboss.as.controller.AbstractWriteAttributeHandler$1.execute(AbstractWriteAttributeHandler.java:101) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:608) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
...
The operation should fail but for another reason: we must check whether the discovery-group-name attribute (which is an alternative to the connector) is defined on the model. If it is not, it's an error to undefine the connector.
However, the code in ConnectionFactoryWriteAttributeHandler must also be updated to prevent updating an attribute that has no corresponding field in the ConnectionFactoryControl interface.
- is incorporated by
-
WFLY-2069 can not switch from connector to discovery-group-name for JMS (pooled-) connection factories
-
- Closed
-
