4:42 a.m.
Jeff Mesnil created AS7-4956:
--------------------------------
Summary: Deployed JMS destinations are not manageable
Key: AS7-4956
URL: https://issues.jboss.org/browse/AS7-4956
Project: Application Server 7
Issue Type: Bug
Components: JMS
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
1.deploy the helloworld-mdb quickstart
=> this deploys a HELLOWORLDMDBQueue JMS Queue from its webapp/WEB-INF/hornetq-jms.xml
2. this JMS queue is not exposed in the admin CLI or web console
$ ./bin/jboss-cli.sh --connect
[standalone@localhost:9999 /]
/subsystem=messaging/hornetq-server=default/jms-queue=HELLOWORLDMDBQueue:read-resource
{
"outcome" => "failed",
"failure-description" => "JBAS014807: Management resource '[
(\"subsystem\" => \"messaging\"),
(\"hornetq-server\" => \"default\"),
(\"jms-queue\" => \"HELLOWORLDMDBQueue\")
]' not found",
"rolled-back" => true
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:09 a.m.
[
https://issues.jboss.org/browse/AS7-4956?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-4956:
-----------------------------------
From what I know, resources like JMS queues and datasources which are
added as deployments are not expected to be managed. The datasource documentation has a
note about this
https://docs.jboss.org/author/display/AS71/Admin+Guide#AdminGuide-Deploym....
I think the same applies to JMS queues via hornetq-jms.xml
Deployed JMS destinations are not manageable
--------------------------------------------
Key: AS7-4956
URL: https://issues.jboss.org/browse/AS7-4956
Project: Application Server 7
Issue Type: Bug
Components: JMS
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
1.deploy the helloworld-mdb quickstart
=> this deploys a HELLOWORLDMDBQueue JMS Queue from its
webapp/WEB-INF/hornetq-jms.xml
2. this JMS queue is not exposed in the admin CLI or web console
$ ./bin/jboss-cli.sh --connect
[standalone@localhost:9999 /]
/subsystem=messaging/hornetq-server=default/jms-queue=HELLOWORLDMDBQueue:read-resource
{
"outcome" => "failed",
"failure-description" => "JBAS014807: Management resource '[
(\"subsystem\" => \"messaging\"),
(\"hornetq-server\" => \"default\"),
(\"jms-queue\" => \"HELLOWORLDMDBQueue\")
]' not found",
"rolled-back" => true
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:52 a.m.
[
https://issues.jboss.org/browse/AS7-4956?page=com.atlassian.jira.plugin.s...
]
Jeff Mesnil commented on AS7-4956:
----------------------------------
Thnkas for the link, I was not aware of this limitation.
Is it on purpose? or was it not implemented due to time constraints?
I can understand that this feature is for development only. However by featuring it in our
quickstart example, we promote it as a correct way to deploy JMS destinations.
imho either we make these deployed resources manageable or we need to find a way to
configure "correctly" JMS destinations in our quickstarts.
Deployed JMS destinations are not manageable
--------------------------------------------
Key: AS7-4956
URL: https://issues.jboss.org/browse/AS7-4956
Project: Application Server 7
Issue Type: Bug
Components: JMS
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
1.deploy the helloworld-mdb quickstart
=> this deploys a HELLOWORLDMDBQueue JMS Queue from its
webapp/WEB-INF/hornetq-jms.xml
2. this JMS queue is not exposed in the admin CLI or web console
$ ./bin/jboss-cli.sh --connect
[standalone@localhost:9999 /]
/subsystem=messaging/hornetq-server=default/jms-queue=HELLOWORLDMDBQueue:read-resource
{
"outcome" => "failed",
"failure-description" => "JBAS014807: Management resource '[
(\"subsystem\" => \"messaging\"),
(\"hornetq-server\" => \"default\"),
(\"jms-queue\" => \"HELLOWORLDMDBQueue\")
]' not found",
"rolled-back" => true
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:31 a.m.
[
https://issues.jboss.org/browse/AS7-4956?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-4956:
-----------------------------------
{quote}
Is it on purpose? or was it not implemented due to time constraints?
{quote}
I believe it was intentional. However, I'm not sure if that's what it will be,
going forward (7.2.x). Brian would be the right person to know more about this.
Deployed JMS destinations are not manageable
--------------------------------------------
Key: AS7-4956
URL: https://issues.jboss.org/browse/AS7-4956
Project: Application Server 7
Issue Type: Bug
Components: JMS
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
1.deploy the helloworld-mdb quickstart
=> this deploys a HELLOWORLDMDBQueue JMS Queue from its
webapp/WEB-INF/hornetq-jms.xml
2. this JMS queue is not exposed in the admin CLI or web console
$ ./bin/jboss-cli.sh --connect
[standalone@localhost:9999 /]
/subsystem=messaging/hornetq-server=default/jms-queue=HELLOWORLDMDBQueue:read-resource
{
"outcome" => "failed",
"failure-description" => "JBAS014807: Management resource '[
(\"subsystem\" => \"messaging\"),
(\"hornetq-server\" => \"default\"),
(\"jms-queue\" => \"HELLOWORLDMDBQueue\")
]' not found",
"rolled-back" => true
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:01 a.m.
[
https://issues.jboss.org/browse/AS7-4956?page=com.atlassian.jira.plugin.s...
]
Jeff Mesnil commented on AS7-4956:
----------------------------------
In fact, I was not looking at the right place: deployed JMS destinations *are* manageable
but they are under the tree of the deployed archive:
[standalone@localhost:9999 /]
/deployment=jboss-as-helloworld-mdb.war/subsystem=messaging/hornetq-server=default/jms-queue=HELLOWORLDMDBQueue:read-resource(include-runtime=true)
{
"outcome" => "success",
"result" => {
"consumer-count" => 0,
"dead-letter-address" => "jms.queue.DLQ",
"delivering-count" => 0,
"durable" => undefined,
"entries" => ["/queue/HELLOWORLDMDBQueue"],
...
}
Their attributes are declared as runtime read-only (as expected).
Deployed JMS destinations are not manageable
--------------------------------------------
Key: AS7-4956
URL: https://issues.jboss.org/browse/AS7-4956
Project: Application Server 7
Issue Type: Bug
Components: JMS
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
1.deploy the helloworld-mdb quickstart
=> this deploys a HELLOWORLDMDBQueue JMS Queue from its
webapp/WEB-INF/hornetq-jms.xml
2. this JMS queue is not exposed in the admin CLI or web console
$ ./bin/jboss-cli.sh --connect
[standalone@localhost:9999 /]
/subsystem=messaging/hornetq-server=default/jms-queue=HELLOWORLDMDBQueue:read-resource
{
"outcome" => "failed",
"failure-description" => "JBAS014807: Management resource '[
(\"subsystem\" => \"messaging\"),
(\"hornetq-server\" => \"default\"),
(\"jms-queue\" => \"HELLOWORLDMDBQueue\")
]' not found",
"rolled-back" => true
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:04 a.m.
[
https://issues.jboss.org/browse/AS7-4956?page=com.atlassian.jira.plugin.s...
]
Jeff Mesnil edited comment on AS7-4956 at 7/13/12 5:03 AM:
-----------------------------------------------------------
In fact, I was not looking at the right place: deployed JMS destinations *are* manageable
but they are under the tree of the deployed archive:
{noformat}
[standalone@localhost:9999 /]
/deployment=jboss-as-helloworld-mdb.war/subsystem=messaging/hornetq-server=default/jms-queue=HELLOWORLDMDBQueue:read-resource(include-runtime=true)
{
"outcome" => "success",
"result" => {
"consumer-count" => 0,
"dead-letter-address" => "jms.queue.DLQ",
"delivering-count" => 0,
"durable" => undefined,
"entries" => ["/queue/HELLOWORLDMDBQueue"],
...
}
{noformat}
Their attributes are declared as runtime read-only (as expected).
was (Author: jmesnil):
In fact, I was not looking at the right place: deployed JMS destinations *are*
manageable but they are under the tree of the deployed archive:
[standalone@localhost:9999 /]
/deployment=jboss-as-helloworld-mdb.war/subsystem=messaging/hornetq-server=default/jms-queue=HELLOWORLDMDBQueue:read-resource(include-runtime=true)
{
"outcome" => "success",
"result" => {
"consumer-count" => 0,
"dead-letter-address" => "jms.queue.DLQ",
"delivering-count" => 0,
"durable" => undefined,
"entries" => ["/queue/HELLOWORLDMDBQueue"],
...
}
Their attributes are declared as runtime read-only (as expected).
Deployed JMS destinations are not manageable
--------------------------------------------
Key: AS7-4956
URL: https://issues.jboss.org/browse/AS7-4956
Project: Application Server 7
Issue Type: Bug
Components: JMS
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
1.deploy the helloworld-mdb quickstart
=> this deploys a HELLOWORLDMDBQueue JMS Queue from its
webapp/WEB-INF/hornetq-jms.xml
2. this JMS queue is not exposed in the admin CLI or web console
$ ./bin/jboss-cli.sh --connect
[standalone@localhost:9999 /]
/subsystem=messaging/hornetq-server=default/jms-queue=HELLOWORLDMDBQueue:read-resource
{
"outcome" => "failed",
"failure-description" => "JBAS014807: Management resource '[
(\"subsystem\" => \"messaging\"),
(\"hornetq-server\" => \"default\"),
(\"jms-queue\" => \"HELLOWORLDMDBQueue\")
]' not found",
"rolled-back" => true
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:08 a.m.
[
https://issues.jboss.org/browse/AS7-4956?page=com.atlassian.jira.plugin.s...
]
Jeff Mesnil resolved AS7-4956.
------------------------------
Resolution: Rejected
deployed jms destinations are manageable under the deployed archive resource
Deployed JMS destinations are not manageable
--------------------------------------------
Key: AS7-4956
URL: https://issues.jboss.org/browse/AS7-4956
Project: Application Server 7
Issue Type: Bug
Components: JMS
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
1.deploy the helloworld-mdb quickstart
=> this deploys a HELLOWORLDMDBQueue JMS Queue from its
webapp/WEB-INF/hornetq-jms.xml
2. this JMS queue is not exposed in the admin CLI or web console
$ ./bin/jboss-cli.sh --connect
[standalone@localhost:9999 /]
/subsystem=messaging/hornetq-server=default/jms-queue=HELLOWORLDMDBQueue:read-resource
{
"outcome" => "failed",
"failure-description" => "JBAS014807: Management resource '[
(\"subsystem\" => \"messaging\"),
(\"hornetq-server\" => \"default\"),
(\"jms-queue\" => \"HELLOWORLDMDBQueue\")
]' not found",
"rolled-back" => true
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5036
days inactive
5073
days old
6 comments
2 participants
participants (2)
-
jaikiran pai (JIRA) -
Jeff Mesnil (JIRA)