<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<body link="#355491" alink="#4262a1" vlink="#355491" style="background: #e2e2e2; margin: 0; padding: 20px;">
<div>
<table cellpadding="0" bgcolor="#FFFFFF" border="0" cellspacing="0" style="border: 1px solid #dadada; margin-bottom: 30px; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td>
<table border="0" cellpadding="0" cellspacing="0" bgcolor="#FFFFFF" style="border: solid 2px #ccc; background: #dadada; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td bgcolor="#000000" valign="middle" height="58px" style="border-bottom: 1px solid #ccc; padding: 20px; -moz-border-radius-topleft: 3px; -moz-border-radius-topright: 3px; -webkit-border-top-right-radius: 5px; -webkit-border-top-left-radius: 5px;">
<h1 style="color: #333333; font: bold 22px Arial, Helvetica, sans-serif; margin: 0; display: block !important;">
<!-- To have a header image/logo replace the name below with your img tag -->
<!-- Email clients will render the images when the message is read so any image -->
<!-- must be made available on a public server, so that all recipients can load the image. -->
<a href="https://community.jboss.org/index.jspa" style="text-decoration: none; color: #E1E1E1">JBoss Community</a></h1>
</td>
</tr>
<tr>
<td bgcolor="#FFFFFF" style="font: normal 12px Arial, Helvetica, sans-serif; color:#333333; padding: 20px; -moz-border-radius-bottomleft: 4px; -moz-border-radius-bottomright: 4px; -webkit-border-bottom-right-radius: 5px; -webkit-border-bottom-left-radius: 5px;"><h3 style="margin: 10px 0 5px; font-size: 17px; font-weight: normal;">
Management of HornetQ core queues
</h3>
<span style="margin-bottom: 10px;">
created by <a href="https://community.jboss.org/people/jmesnil">Jeff Mesnil</a> in <i>JBoss AS 7 Development</i> - <a href="https://community.jboss.org/message/773191#773191">View the full discussion</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><p>While working on AS7-1960[1] Kabir noticed that HornetQ core queues created with the HornetQ API (eg ClientSession.createQueue) were not exposed correctly as AS7 resources. The resource does not exist (:read-resource & :write-attribute fails) but it is still possible to interact with it (eg invoke :read-attribute or other queue-specific operations such as :pause or :resume)[2].</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>The problem is more general for HornetQ. When HornetQ creates JMS resources, it also creates underlying core queues for them (1 core queue per JMS queue and 1 + n core queues for 1 JMS topic with n subscribers).</p><p>These core queues are not exposed by AS7 either[3].</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>My first idea was to materialize these resources correctly but this brings more problems. Their resource definitions flagged them as stored in the configuration. I don't think that queues created outside of the AS7 management API should be stored in its configuration.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>At the same time, for backwards compatibility, we must continue to support the management operations on these core queues at their current addresses (/subsystem=messaging/hornetq-server=XXX/queue=YYY)</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>After talking to Kabir on IRC, the idea would be to:</p><ul><li>expose all HornetQ core queues as runtime read-only resources in a separate address (eg /subsystem=messaging/hornetq-server=XXX/runtime-queue=YYY). These resources would be handled dynamically based on HornetQServer management service (like it's done for core-address resources)</li><li>for backwards compatibility, forward the "read-only" and runtime management operations (read-attribute, queue-specific operations) from /subsystem=messaging/hornetq-server=XXX/queue=YYY to /subsystem=messaging/hornetq-server=XXX/runtime-queue=YYY</li><li>Queues created by AS7 management API will remain at their current address and support read/write attributes and be persisted in AS7 configuration</li></ul><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p><span>[1] </span><a class="jive-link-external-small" href="https://issues.jboss.org/browse/AS7-1960" target="_blank">https://issues.jboss.org/browse/AS7-1960</a></p><p><span>[2] </span><a class="jive-link-external-small" href="https://issues.jboss.org/browse/AS7-5850" target="_blank">https://issues.jboss.org/browse/AS7-5850</a></p><p><span>[3] </span><a class="jive-link-external-small" href="https://issues.jboss.org/browse/AS7-4960" target="_blank">https://issues.jboss.org/browse/AS7-4960</a></p></div>
<div style="background-color: #f4f4f4; padding: 10px; margin-top: 20px;">
<p style="margin: 0;">Reply to this message by <a href="https://community.jboss.org/message/773191#773191">going to Community</a></p>
<p style="margin: 0;">Start a new discussion in JBoss AS 7 Development at <a href="https://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2225">Community</a></p>
</div></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>