While looking into QPID-1941 (moved messages remaining in the JMX
viewMessages() results for the old queue, but not being considered
still on the queue) for GSoC I have noticed an inconsistency between
the recovery behaviour of persistent messages which are moved, and
those handled only by the
[
https://issues.apache.org/jira/browse/QPID-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12728279#action_12728279
]
Rafael H. Schloming commented on QPID-1935:
---
I'm reverting the fix for this as it
Removing that check seems like the right thing to do to me. There's a
couple of other oddities like that elsewhere in the stores though. We
should really make a decision about how to treat them, but IMO the
right thing to do is to persist if *either* the queue or the message
is marked as durable.
Martin Ritchie wrote:
Java Broker Users,
I have been working on designs for improving the logging from the Java
Broker. The current logging is more aimed at developers so providing
more operational focused log messages would be good.
The design is up on the wiki here:
2009/7/7 Aidan Skinner ai...@apache.org:
Removing that check seems like the right thing to do to me. There's a
couple of other oddities like that elsewhere in the stores though. We
should really make a decision about how to treat them, but IMO the
right thing to do is to persist if *either*
[
https://issues.apache.org/jira/browse/QPID-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Huston resolved QPID-1952.
Resolution: Fixed
Fix Version/s: 0.6
Assignee: Steve Huston
I tested the patch here
[
https://issues.apache.org/jira/browse/QPID-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross reassigned QPID-1973:
--
Assignee: Ted Ross
Calling session.objects fails to return objects in certain cases
