Exception when trying to access runtime-queue information on dedicated HornetQ backup server on web console

Issue

I want to check the state of destinations on an active HornetQ-Backupserver (dedicated topology) via ManagementModel-GUI. When I click on an arbitrary queue-link (subsystem:messaging, hornetq-server=default, runtime-queue=XY) nothing but a small note indicating an error is displayed. Clicking on this note the following text is shown:

Failed to read resource: Unexpected HTTP response: 500 Request { "address" => [ ("subsystem" => "messaging"), ("hornetq-server" => "default"), ("runtime-queue" => "jms.queue.DLQ") ], "operation" => "read-resource", "include-runtime" => true } Response Internal Server Error { "outcome" => "failed", "rolled-back" => true }

On the corresponding server console I see the following message/ stacktrace:

16:39:22,644 ERROR [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 4) JBAS014612: Operation ("read-attribute") failed - address: ([
    ("subsystem" => "messaging"),
    ("hornetq-server" => "default"),
    ("runtime-queue" => "jms.queue.DLQ")
]): java.lang.IllegalArgumentException: newValue is null
        at org.jboss.dmr.ModelNode.set(ModelNode.java:499) [jboss-dmr-1.2.2.Final-redhat-1.jar:1.2.2.Final-redhat-1]
        at org.jboss.as.messaging.QueueReadAttributeHandler.executeRuntimeStep(QueueReadAttributeHandler.java:138)
        at org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:89) [jboss-as-controller-7.5.7.Final-redhat-3.jar:7.5.7.Final-redhat-3]
        at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:702) [jboss-as-controller-7.5.7.Final-redhat-3.jar:7.5.7.Final-redhat-3]
        at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:537) [jboss-as-controller-7.5.7.Final-redhat-3.jar:7.5.7.Final-redhat-3]
        at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:338) [jboss-as-controller-7.5.7.Final-redhat-3.jar:7.5.7.Final-redhat-3]
        at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:314) [jboss-as-controller-7.5.7.Final-redhat-3.jar:7.5.7.Final-redhat-3]
        at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1144) [jboss-as-controller-7.5.7.Final-redhat-3.jar:7.5.7.Final-redhat-3]
        at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:331) [jboss-as-controller-7.5.7.Final-redhat-3.jar:7.5.7.Final-redhat-3]
        at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:201) [jboss-as-controller-7.5.7.Final-redhat-3.jar:7.5.7.Final-redhat-3]
.. .. ..      
        at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81)
        at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:682)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_99]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_99]
        at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_99]
        at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1]

The same error is reproducible with the following CLI command
/subsystem=messaging/hornetq-server=default/runtime-queue=jms.queue.QueueName