This content has been marked as final.
Show 6 replies
-
1. Re: WFLYCTL0013: Operation ("dummy_operation_name") failed since upgrade to Wildfly
ctomc Dec 16, 2016 8:04 AM (in response to java_dev_from_autria)Where does this dummy_operation_name and dummy_queue_name comes from?
Is that from some monitoring tool you are using?
-
2. Re: WFLYCTL0013: Operation ("dummy_operation_name") failed since upgrade to Wildfly
ctomc Dec 16, 2016 8:10 AM (in response to ctomc)Also what version of wildfly?
-
3. Re: WFLYCTL0013: Operation ("dummy_operation_name") failed since upgrade to Wildfly
java_dev_from_autria Dec 21, 2016 8:26 AM (in response to ctomc)I replaced the real operation- and queue-names in the stacktrace with dummy values;
we use Wildfly version 10.1.0.Final
-
4. Re: WFLYCTL0013: Operation ("dummy_operation_name") failed since upgrade to Wildfly
java_dev_from_autria Mar 29, 2017 11:57 AM (in response to ctomc)Hi.
Have your read my last comment about the Wildfly version (10.1.0.Final)?
Br
-
5. Re: WFLYCTL0013: Operation ("dummy_operation_name") failed since upgrade to Wildfly
jaikiran Mar 30, 2017 1:34 AM (in response to java_dev_from_autria)It's confusing to see "dummy_operation_name" in there. Can you tell us what exact operation name it is? It's fine if you don't post the queue name but the operation name isn't really application specific, to hide it.
-
6. Re: WFLYCTL0013: Operation ("dummy_operation_name") failed since upgrade to Wildfly
java_dev_from_autria Mar 30, 2017 3:18 AM (in response to jaikiran)WFLYCTL0013: Operation ("count-messages") failed - address: ([
("subsystem" => "messaging-activemq"),
("server" => "default"),
("jms-queue" => "dummy_queue_name")