10:58 a.m.
DLQ override depends on the queues definition order.
----------------------------------------------------
Key: JBMESSAGING-1374
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1374
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.4.0.SP3_CP03
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:20 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1374) DLQ override depends on the queues definition order.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1374?page=all ]
Tim Fox updated JBMESSAGING-1374:
---------------------------------
Fix Version/s: Unscheduled
(was: 1.4.0.SP3_CP03)
DLQ override depends on the queues definition order.
----------------------------------------------------
Key: JBMESSAGING-1374
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1374
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: Unscheduled
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:48 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1374) DLQ override depends on the queues definition order.
[ http://jira.jboss.com/jira/browse/JBMESSAGING-1374?page=all ]
Tim Fox updated JBMESSAGING-1374:
---------------------------------
Fix Version/s: 1.4.0.SP3.CP04
(was: Unscheduled)
DLQ override depends on the queues definition order.
----------------------------------------------------
Key: JBMESSAGING-1374
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1374
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.4.0.SP3.CP04
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:14 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1374) DLQ override depends on the queues definition order.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1374?page=com.atlassian.ji...
]
Tim Fox updated JBMESSAGING-1374:
---------------------------------
Fix Version/s: 1.4.1.GA
DLQ override depends on the queues definition order.
----------------------------------------------------
Key: JBMESSAGING-1374
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1374
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assignee: Tim Fox
Fix For: 1.4.0.SP3.CP04, 1.4.1.GA
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:08 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1374) DLQ override depends on the queues definition order.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1374?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1374:
-----------------------------------------
Same thing happens with ExpiryQueue. If in the destinations-service.xml a destination
mbean uses a DLQ or ExpiryQueue whose mbean element appears after it, it won't get the
DLQ/ExpiryQueue reference during service start, even though the DLQ/ExpiryQueue is
eventually started up. When the user tries to send the message, the server session
consumer endpoint will try to get the DLQ/ExpiryQueue ref from the destination, which in
that case is null, then the consumer endpoint will use default DLQ/ExpiryQueue instead.
However user can still see the correct DLQ/ExpiryQueue name from jmx console, that's
because the DLQ's ObjectName is in the destination service, and by clicking apply
button on the console will update the DLQ correctly. So the next consumer creation will
cause the right DLQ to be used.
We need to use a facility class to solve the dependency issue during the destination
service start stages, set them correctly if such cases happens.
DLQ override depends on the queues definition order.
----------------------------------------------------
Key: JBMESSAGING-1374
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1374
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assignee: Tim Fox
Fix For: 1.4.0.SP3.CP04, 1.4.1.GA
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:33 p.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-1374) DLQ override depends on the queues definition order.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1374?page=com.atlassian.ji...
]
Tim Fox reassigned JBMESSAGING-1374:
------------------------------------
Assignee: Howard Gao (was: Tim Fox)
DLQ override depends on the queues definition order.
----------------------------------------------------
Key: JBMESSAGING-1374
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1374
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP04, 1.4.1.GA
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:39 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1374) DLQ override depends on the queues definition order.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1374?page=com.atlassian.ji...
]
Tim Fox commented on JBMESSAGING-1374:
--------------------------------------
If the user adds a standards <depends> entry in the mbean config, then that will
ensure the dlq is started before the other queue.
So probably there is nothing much to do here.
DLQ override depends on the queues definition order.
----------------------------------------------------
Key: JBMESSAGING-1374
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1374
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP04, 1.4.1.GA
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:59 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1374) DLQ override depends on the queues definition order.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1374?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1374:
-----------------------------------------
It doesn't work with the <depends> entry. I tried to modify the config as
follows, and it turns out the DLQ won't get set unless the order is correct,
regardless of the <depends> entry.
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=QueueWithOwnDLQAndExpiryQueue"
xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends>jboss.messaging.destination:service=Queue,name=PrivateDLQ</depends>
<!-- *********************see this doesn't make the DLQ set************ -->
...
<attribute
name="DLQ">jboss.messaging.destination:service=Queue,name=PrivateDLQ</attribute>
<attribute
name="ExpiryQueue">jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue</attribute>
</mbean>
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=PrivateDLQ"
xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends
optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
<depends>jboss.messaging:service=PostOffice</depends>
</mbean>
<mbean code="org.jboss.jms.server.destination.TopicService"
name="jboss.messaging.destination:service=Topic,name=TopicWithOwnDLQAndExpiryQueue"
xmbean-dd="xmdesc/Topic-xmbean.xml">
<depends>jboss.messaging.destination:service=Queue,name=PrivateDLQ</depends>
<!-- ****************** this will get set because the DLQ is placed before the topic
*********** -->
<depends
optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
<depends>jboss.messaging:service=PostOffice</depends>
<attribute
name="DLQ">jboss.messaging.destination:service=Queue,name=PrivateDLQ</attribute>
<attribute
name="ExpiryQueue">jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue</attribute>
</mbean>
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue"
xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends
optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
<depends>jboss.messaging:service=PostOffice</depends>
</mbean>
DLQ override depends on the queues definition order.
----------------------------------------------------
Key: JBMESSAGING-1374
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1374
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP04, 1.4.1.GA
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:26 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1374) DLQ override depends on the queues definition order.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1374?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1374:
-----------------------------------------
If I add
if (this.dlqObjectName != null) {
this.setDLQ(dlqObjectName);
}
if (this.expiryQueueObjectName != null) {
this.setExpiryQueue(expiryQueueObjectName);
}
at the end of DestinationServiceSupport::startService(), the issue will be gone regardless
of the order of deployment and <depends> entry.
DLQ override depends on the queues definition order.
----------------------------------------------------
Key: JBMESSAGING-1374
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1374
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP04, 1.4.1.GA
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:04 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1374) DLQ override depends on the queues definition order.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1374?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1374:
-----------------------------------------
Further investigation on the reason why <depends> doesn't work:
- <depends> only affect the service start sequence, not the mbean load sequence. The
loading of mbeans should be in the order of that specified in the deploy config file.
- The original setDLQ() happens during the mbean loading(creation) time, which will try to
resolve the DLQ by JMXAccessor.getJMXAttributeOverSecurity(...) method. If at that time
the DLQ mbean service is not loaded (created), it simply gets null.
- the setDLQ() then is never called again during the rest of the server startup process.
Only if the user change it from the jmx console, it'll be changed.
- adding a setDLQ() at service start time can guarantee all the mbeans are created, so we
won't get null DLQ any more, and the real DLQ will be used instead of the default
one.
- same reason stays with the ExpiryQueue case.
DLQ override depends on the queues definition order.
----------------------------------------------------
Key: JBMESSAGING-1374
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1374
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP04, 1.4.1.GA
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:44 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1374) DLQ override depends on the queues definition order.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1374?page=com.atlassian.ji...
]
Tim Fox closed JBMESSAGING-1374.
--------------------------------
Resolution: Done
DLQ override depends on the queues definition order.
----------------------------------------------------
Key: JBMESSAGING-1374
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1374
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP04, 1.4.1.GA
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:15 a.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-1374) DLQ override depends on the queues definition order.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1374?page=com.atlassian.ji...
]
Clebert Suconic reopened JBMESSAGING-1374:
------------------------------------------
DLQ override depends on the queues definition order.
----------------------------------------------------
Key: JBMESSAGING-1374
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1374
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP04, 1.4.1.GA, 1.4.2.GA
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:15 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1374) DLQ override depends on the queues definition order.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1374?page=com.atlassian.ji...
]
Clebert Suconic closed JBMESSAGING-1374.
----------------------------------------
Fix Version/s: 1.4.1.GA
Resolution: Done
DLQ override depends on the queues definition order.
----------------------------------------------------
Key: JBMESSAGING-1374
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1374
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assignee: Howard Gao
Fix For: 1.4.1.GA, 1.4.2.GA, 1.4.0.SP3.CP04
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:05 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1374) DLQ override depends on the queues definition order.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1374?page=com.atlassian.ji...
]
Guillaume Jeudy commented on JBMESSAGING-1374:
----------------------------------------------
Is that fix supposed to work with a durable subscription? I have a durable subscriber MDB
to the topic defined below (in the correct order). It seems as though the DLQ
configuration is completely ignored and the messages are routed to the default DLQ.
I'm using jboss messaging 1.4.4.GA.
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=msdmiTopicDLQ"
xmbean-dd="xmdesc/Queue-xmbean.xml">
<depends
optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
<depends>jboss.messaging:service=PostOffice</depends>
<attribute
name="JNDIName">BOSS/DLQ/AuditServices/Events/Sharepoint</attribute>
</mbean>
<mbean code="org.jboss.jms.server.destination.TopicService"
name="jboss.messaging.destination:service=Topic,name=msdmiTopic"
xmbean-dd="xmdesc/Topic-xmbean.xml">
<depends
optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
<depends>jboss.messaging:service=PostOffice</depends>
<attribute
name="JNDIName">BOSS/AuditServices/Events/Sharepoint</attribute>
<attribute
name="DLQ">jboss.messaging.destination:service=Queue,name=msdmiTopicDLQ</attribute>
</mbean>
DLQ override depends on the queues definition order.
----------------------------------------------------
Key: JBMESSAGING-1374
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1374
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP04, 1.4.1.GA, 1.4.2.GA
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:37 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1374) DLQ override depends on the queues definition order.
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1374?page=com.atlassian.ji...
]
Guillaume Jeudy commented on JBMESSAGING-1374:
----------------------------------------------
I stumbled upon this case: https://64.74.196.157/jira/browse/JBPAPP-871. Apparently my MDB
had DLQMaxSent set to 2 so the MDB DLQ policy took precedence over JBM DLQ policy...
DLQ override depends on the queues definition order.
----------------------------------------------------
Key: JBMESSAGING-1374
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1374
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP04, 1.4.1.GA, 1.4.2.GA
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5504
days inactive
5856
days old
14 comments
4 participants
participants (4)
-
Clebert Suconic (JIRA) -
Guillaume Jeudy (JIRA)
-
Howard Gao (JIRA)
-
Tim Fox (JIRA)