[jboss-jira] [JBoss JIRA] (AS7-5713) Attribute ha for connection-factory cannot be set using CLI
Miroslav Novak created AS7-5713:
-----------------------------------
Summary: Attribute ha for connection-factory cannot be set using CLI
Key: AS7-5713
URL: https://issues.jboss.org/browse/AS7-5713
Project: Application Server 7
Issue Type: Bug
Components: JMS
Reporter: Miroslav Novak
Assignee: Jeff Mesnil
Fix For: 7.2.0.Alpha1
Attribute ha for connection-factory cannot be set using CLI.
{code}
[standalone@localhost:9999 connection-factory=RemoteConnectionFactory]
:write-attribute(name=ha, value=true)
{
"outcome" => "failed",
"failure-description" => "JBAS014749: Operation handler failed:
JBAS011664: Runtime handling for ha is not implemented",
"rolled-back" => true
}
{code}
Server log:
{code}
17:44:55,993 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS
7.2.0.Alpha1-SNAPSHOT "Steropes" started in 2397ms - Started 159 of 312 services
(152 services are passive or on-demand)
17:45:33,152 ERROR [org.jboss.as.controller.management-operation]
(management-handler-thread - 3) JBAS014612: Operation ("write-attribute") failed
- address: ([
("subsystem" => "messaging"),
("hornetq-server" => "default"),
("connection-factory" => "RemoteConnectionFactory")
]): java.lang.UnsupportedOperationException: JBAS011664: Runtime handling for ha is not
implemented
at
org.jboss.as.messaging.jms.ConnectionFactoryWriteAttributeHandler.applyOperationToHornetQService(ConnectionFactoryWriteAttributeHandler.java:172)
at
org.jboss.as.messaging.jms.ConnectionFactoryWriteAttributeHandler.applyUpdateToRuntime(ConnectionFactoryWriteAttributeHandler.java:84)
at
org.jboss.as.controller.AbstractWriteAttributeHandler$1.execute(AbstractWriteAttributeHandler.java:116)
[jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:439)
[jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:321)
[jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:228)
[jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:223)
[jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:135)
[jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:111)
[jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139)
[jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108)
[jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296)
[jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at
org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518)
[jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[rt.jar:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[rt.jar:1.6.0_24]
at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
[jboss-threads-2.0.0.GA.jar:2.0.0.GA]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira