On Thu, Jan 17, 2013 at 5:27 PM, Robbie Gemmell
wrote:
> I was actually asking Hiram what ActiveMQ does...
Gotcha. It would be interesting to know the details.
Rajith
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
Fo
On 17 January 2013 22:19, Rajith Attapattu wrote:
> On Thu, Jan 17, 2013 at 5:00 PM, Robbie Gemmell
> wrote:
> >
> > ( ( ...and in continuation of this one-thought-per-email demonstration,
> it
> > further occurs to me that you can reset 'read only' messages and then use
> > them again so I gues
On Thu, Jan 17, 2013 at 5:00 PM, Robbie Gemmell
wrote:
>
> ( ( ...and in continuation of this one-thought-per-email demonstration, it
> further occurs to me that you can reset 'read only' messages and then use
> them again so I guess thats going back to the original question hehe ) )
The default
On 17 January 2013 21:54, Robbie Gemmell wrote:
>
>
>
> On 17 January 2013 21:51, Robbie Gemmell wrote:
>
>>
>> On 17 January 2013 21:06, Hiram Chirino wrote:
>>
>>> FYI there is a good reason to NOT preserve the message id. It's fairly
>>> common for clients to do things like:
>>>
>>> msg = s
On 17 January 2013 21:51, Robbie Gemmell wrote:
>
> On 17 January 2013 21:06, Hiram Chirino wrote:
>
>> FYI there is a good reason to NOT preserve the message id. It's fairly
>> common for clients to do things like:
>>
>> msg = session.createTextMessage();
>> msg.setText("Hello");
>> sender.sen
On 17 January 2013 21:06, Hiram Chirino wrote:
> FYI there is a good reason to NOT preserve the message id. It's fairly
> common for clients to do things like:
>
> msg = session.createTextMessage();
> msg.setText("Hello");
> sender.send(msg);
> msg.setText("World");
> sender.send(msg);
>
> You d
On Thu, Jan 17, 2013 at 4:06 PM, Hiram Chirino wrote:
> FYI there is a good reason to NOT preserve the message id. It's fairly
> common for clients to do things like:
>
> msg = session.createTextMessage();
> msg.setText("Hello");
> sender.send(msg);
> msg.setText("World");
> sender.send(msg);
>
>
FYI there is a good reason to NOT preserve the message id. It's fairly
common for clients to do things like:
msg = session.createTextMessage();
msg.setText("Hello");
sender.send(msg);
msg.setText("World");
sender.send(msg);
You don't want the 2nd msg sent /w the message id used in the 1st.
The
[
https://issues.apache.org/jira/browse/QPID-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl L. Pierce updated QPID-4371:
---
Fix Version/s: (was: 0.19)
0.21
> The extra_dist/Makefile does not
[
https://issues.apache.org/jira/browse/QPID-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl L. Pierce updated QPID-4372:
---
Fix Version/s: 0.21
> Have the C++ examples use CMake rather than static Makefiles.
>
[
https://issues.apache.org/jira/browse/QPID-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross resolved QPID-4537.
Resolution: Fixed
> qpid-stat: fix undefined name error
> ---
>
>
[
https://issues.apache.org/jira/browse/QPID-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated QPID-4537:
---
Fix Version/s: (was: 0.19)
0.21
> qpid-stat: fix undefined name error
> ---
[
https://issues.apache.org/jira/browse/QPID-4537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross reassigned QPID-4537:
--
Assignee: Ted Ross
> qpid-stat: fix undefined name error
> ---
>
>
[
https://issues.apache.org/jira/browse/QPID-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated QPID-3175:
---
Fix Version/s: (was: 0.19)
0.21
> SSL support in Python client libraries
>
Hi, folks.
The vote has passed, with eight votes in favor and none against.
I'll also be generating the final release notes soon, so please promptly
close out the issues that Robbie mentioned on another thread.
Thanks!
Justin
On Wed, 16 Jan 2013, Keith W wrote:
+1
I retested the Java Brok
On Thu, Jan 17, 2013 at 12:43 PM, Robbie Gemmell
wrote:
>>
> Yep, 3272
Gotcha.
> Seperate as in store the provided String in a field which is separate from
> the UUID in the header where we would normally store the passed in message
> id value, and return this when getJMSMessageID is called.
Th
On 17 January 2013 17:30, Rajith Attapattu wrote:
> On Thu, Jan 17, 2013 at 11:52 AM, Robbie Gemmell
> wrote:
> > It would be good to add the additional detail to the JIRA (QPID-3273),
> its
> > useful in considering the actual intent of the setJMSMessageID call.
>
> Is there a typo in the JIRA
On Thu, Jan 17, 2013 at 11:52 AM, Robbie Gemmell
wrote:
> It would be good to add the additional detail to the JIRA (QPID-3273), its
> useful in considering the actual intent of the setJMSMessageID call.
Is there a typo in the JIRA id ?
> From reading of the stacktraces, I'd say it looks like th
Weston M. Price created QPID-4541:
-
Summary: Messages are replayed after XA commit in a failover
scenario
Key: QPID-4541
URL: https://issues.apache.org/jira/browse/QPID-4541
Project: Qpid
Is
[
https://issues.apache.org/jira/browse/QPID-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved QPID-4181.
Resolution: Fixed
Fix Version/s: 0.21
Fixed r1434577, r1434587, and r1434712
See also https:
It would be good to add the additional detail to the JIRA (QPID-3273), its
useful in considering the actual intent of the setJMSMessageID call.
>From reading of the stacktraces, I'd say it looks like the foreign senders
are setting their new message ID on our message object, and then probably
subs
[
https://issues.apache.org/jira/browse/QPID-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway resolved QPID-4201.
---
Resolution: Won't Fix
Fix Version/s: (was: 0.19)
0.20
This issue affects
After some further investigation it appears I have got the
requirements wrong. Sorry about that.
The second issue I mentioned (provider overriding the message -id)
*may* no longer be a concern here.
(My original email was based on a conversation I had when trying to
find the use cases behind the re
[
https://issues.apache.org/jira/browse/QPID-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-4502:
-
Fix Version/s: (was: 0.20)
> Document Handing Undeliverable Messages (DLQ/Maximum Delivery Count f
[
https://issues.apache.org/jira/browse/QPID-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-4502:
-
Fix Version/s: 0.20
> Document Handing Undeliverable Messages (DLQ/Maximum Delivery Count features)
>
Hi everyone,
I just took a look through the outstanding JIRAs assigned to 0.19/0.20 and
cleaned up a bunch of them. There are now only 4 remaining.
Could people take a look and update them appropriately, so that we could
ship a release without any open JIRAs being assigned to it for once :)
See:
[
https://issues.apache.org/jira/browse/QPID-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey resolved QPID-4384.
---
Resolution: Fixed
Fix Version/s: 0.20
Fixed in revision 1400447
> [Java AMQP 1
[
https://issues.apache.org/jira/browse/QPID-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556228#comment-13556228
]
Robbie Gemmell commented on QPID-4357:
--
Dont see any commits indicating this was chang
[
https://issues.apache.org/jira/browse/QPID-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-4357:
-
Fix Version/s: (was: 0.19)
0.21
> If an exception is received while the
[
https://issues.apache.org/jira/browse/QPID-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-4357:
-
Affects Version/s: 0.20
> If an exception is received while the client is blocked on sync, the
[
https://issues.apache.org/jira/browse/QPID-4342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-4342:
-
Fix Version/s: (was: 0.19)
0.21
> Derby profile keeps timing out on Jen
[
https://issues.apache.org/jira/browse/QPID-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved QPID-4314.
--
Resolution: Fixed
Resolving.
> [Java Distributed Tests] Add performance tests m
[
https://issues.apache.org/jira/browse/QPID-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl L. Pierce resolved QPID-4501.
Resolution: Fixed
> Fix build issues regarding language bindings and autotools
> ---
[
https://issues.apache.org/jira/browse/QPID-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved QPID-4341.
--
Resolution: Fixed
> ensure the Topic perftests actually use Topic destinations
> ---
[
https://issues.apache.org/jira/browse/QPID-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556225#comment-13556225
]
Robbie Gemmell commented on QPID-4181:
--
Has this been moved over to the Proton JIRA pr
[
https://issues.apache.org/jira/browse/QPID-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-4181:
-
Fix Version/s: (was: 0.19)
> proton porting work on Windows
>
[
https://issues.apache.org/jira/browse/QPID-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-3966:
-
Fix Version/s: (was: 0.19)
0.21
> Add missing license headers to projec
[
https://issues.apache.org/jira/browse/QPID-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556222#comment-13556222
]
Robbie Gemmell commented on QPID-4281:
--
Marking as RtR, 0.21 fix-for.
[
https://issues.apache.org/jira/browse/QPID-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-4281:
-
Fix Version/s: (was: 0.19)
0.21
> Java tests logging broken because log
[
https://issues.apache.org/jira/browse/QPID-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-4281:
-
Status: Ready To Review (was: In Progress)
> Java tests logging broken because log4j.configur
[
https://issues.apache.org/jira/browse/QPID-4254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-4254:
-
Fix Version/s: (was: 0.19)
> Java Broker - make Group Database closeable
> --
[
https://issues.apache.org/jira/browse/QPID-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-3587:
-
Fix Version/s: (was: 0.19)
> Certain python tests fail against the Java broker due to queu
[
https://issues.apache.org/jira/browse/QPID-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556220#comment-13556220
]
Robbie Gemmell commented on QPID-4501:
--
Can this be marked resolved then?
[
https://issues.apache.org/jira/browse/QPID-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-4362:
-
Fix Version/s: (was: 0.19)
> Performance test charting: support the configuration of optional seri
[
https://issues.apache.org/jira/browse/QPID-4419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell resolved QPID-4419.
--
Resolution: Fixed
Resolving, 0.20 is now baked.
> [Java Broker] incorrect handl
I would echo Keiths point, and also have some other items to consider.
I'm not sure I think the spec really is all that loose on this subject, and
the bit you quoted was just a natural phrasing and not really intended to
implying you can feel free not to overwrite it. For example, I can quote a
bi
Hi Rajith,
I'm interested to know more background. When exactly is the ability
to preserve JMSMessageIDs in this way useful? Does this change give
us compatibility with particular (bridging) product(s)? If so, which
ones?
Thanks, Keith.
47 matches
Mail list logo
