[
https://issues.apache.org/jira/browse/QPID-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-3688:
---
Attachment: QPID-3688.patch
This patch doesn't change the AMQDestination into a Java bean
Yes Gordon alerted me to it last evening.
Weston and I are looking into it.
Rajith
On Fri, Dec 9, 2011 at 3:26 AM, Keith Wall (Reopened) (JIRA)
j...@apache.org wrote:
[
https://issues.apache.org/jira/browse/QPID-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
[
https://issues.apache.org/jira/browse/QPID-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13166382#comment-13166382
]
Rajith Attapattu commented on QPID-3625:
Keith, after some investigation we've
[
https://issues.apache.org/jira/browse/QPID-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-3625.
Resolution: Fixed
Fix Version/s: (was: 0.14)
0.15
This change
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3041/#review3701
---
On 2011-12-07 01:52:53, rajith attapattu wrote
[
https://issues.apache.org/jira/browse/QPID-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13164636#comment-13164636
]
Rajith Attapattu commented on QPID-3659:
It is indeed due to not being quoted
[
https://issues.apache.org/jira/browse/QPID-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-3659.
Resolution: Fixed
Assignee: Rajith Attapattu
Java client mishandles tcp_nodelay
On Tue, Dec 6, 2011 at 11:02 AM, Alan Conway acon...@redhat.com wrote:
On 12/06/2011 10:59 AM, Carl Trieloff wrote:
On 12/06/2011 10:56 AM, acon...@apache.org wrote:
NOTE 1: If you are using an ACL, the cluster-username must be allowed to
publish to the qpid.cluster-credentials exchange.
Components: C++ Broker
Affects Versions: 0.14
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.15
There have been several requests in the past to provide some sort of
functionality to add ACL rules dynamically.
Recently QPID-3652 needed a way
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3041/
---
Review request for qpid, Alan Conway, Gordon Sim, and Kim van der Riet.
Summary
[
https://issues.apache.org/jira/browse/QPID-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13160322#comment-13160322
]
Rajith Attapattu commented on QPID-3654:
I think this was overdue. Thanks Andrew
+1 to include this.
This error msg was really annoying :)
Rajith
On Wed, Nov 30, 2011 at 5:14 PM, Robbie Gemmell
robbie.gemm...@gmail.com wrote:
I would like to request merging the fix for QPID-3582: Client
reporting Unable to load custom SASL providers during connection.
The client logs out
As Robbie mentioned, most of the git fans are already using git-svn
(I'm one of them).
So we could perhaps wait for a bit to see how the trial unfolds.
My concern is, that not everybody may be ready to use git at this
point, so if we switch, then we will be disrupting the work for some
folks.
[
https://issues.apache.org/jira/browse/QPID-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13156879#comment-13156879
]
Rajith Attapattu commented on QPID-3640:
Alex,
I was about to attach my patch
[
https://issues.apache.org/jira/browse/QPID-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13156880#comment-13156880
]
Rajith Attapattu commented on QPID-3640:
I will be testing this along with the rest
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.12, 0.10
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.15
When releasing messages, for ex when the application calls recover
[
https://issues.apache.org/jira/browse/QPID-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-3640:
---
Attachment: RecoveryTest.java
The test case basically does the following.
It tries to receive
[
https://issues.apache.org/jira/browse/QPID-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155494#comment-13155494
]
Rajith Attapattu commented on QPID-3640:
Note this test depends
You could use -Dqpid.heartbeat=x or use heartbeat as a broker url property.
Btw, Please don't use the AMQ** classes. These are internal classes
that will not be there going forward.
It's better to use the JMS interfaces.
Rajith
On Fri, Nov 18, 2011 at 11:17 AM, Gaston Quezada
[
https://issues.apache.org/jira/browse/QPID-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13152096#comment-13152096
]
Rajith Attapattu commented on QPID-2703:
Part of the reason is in the java client
[
https://issues.apache.org/jira/browse/QPID-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13152129#comment-13152129
]
Rajith Attapattu commented on QPID-2703:
I think this is a good short term fix
On Thu, Nov 17, 2011 at 12:03 PM, Gordon Sim g...@redhat.com wrote:
On 11/17/2011 04:57 PM, Ken Giusti wrote:
Hi Justin,
Would it be possible to include the fix for QPID-3626 in the upcoming rc?
https://issues.apache.org/jira/browse/QPID-3626
Without it, any python client that would like
[
https://issues.apache.org/jira/browse/QPID-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13152382#comment-13152382
]
Rajith Attapattu commented on QPID-3562:
Thanks for the feedback. I was trying
of AMQSession#rejectMessage?
I wonder also if this logic sit better in AMQSession#notifyConsumer().
It already rejects messages if the consumer is closed. Could it not also
reject messages if the connection is no longer started?
rajith attapattu wrote:
Keith if you look
required for? You are releasing a message you
have just received, right? When is that required?
rajith attapattu wrote:
See the above for an explanation for why this is needed.
Gordon Sim wrote:
You mean this is here because of the lack of synchronization with the
dispatcher thread
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2853/#review3325
---
On 2011-11-16 18:31:12, rajith attapattu wrote:
---
This is an automatically generated
it over I think it seems fine due to the
processCompletions call in postDeliver(), but its possibly still worth a
check.
rajith attapattu wrote:
Your observation is correct, this deals with messages that were already
received by the application.
For recover(), we really don't need
-16 18:31:12, rajith attapattu wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2853/
---
(Updated 2011-11-16 18:31:12
do the
final commit :)
- rajith
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2832/#review3294
---
On 2011-11-15 15:36:36, rajith
[
https://issues.apache.org/jira/browse/QPID-3625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13151321#comment-13151321
]
Rajith Attapattu commented on QPID-3625:
Discussed this issue with Weston and I
[
https://issues.apache.org/jira/browse/QPID-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13151354#comment-13151354
]
Rajith Attapattu commented on QPID-3562:
I have the following test case
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2853/
---
Review request for qpid, Gordon Sim, Robbie Gemmell, Weston Price, Keith Wall,
of AMQSession#rejectMessage?
I wonder also if this logic sit better in AMQSession#notifyConsumer().
It already rejects messages if the consumer is closed. Could it not also
reject messages if the connection is no longer started?
rajith attapattu wrote:
Keith if you look
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2832/
---
Review request for qpid, Gordon Sim, Robbie Gemmell, Weston Price, and
Oleksandr
for an explanation for why this is needed.
- rajith
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2832/#review3264
---
On 2011-11-15 15:36:36, rajith
as part of the block here? If so are
there any lock ordering issues where you could be introducing a deadlock?
rajith attapattu wrote:
Not that I could think of. The message-delivery-lock is taken to ensure
that no messages are being served while we start pulling them out of the
queue
[
https://issues.apache.org/jira/browse/QPID-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13148507#comment-13148507
]
Rajith Attapattu commented on QPID-3610:
Robbie, lets make sure we document
The upcoming java client work will have this mind (in fact a requirement).
The core client will have minimum (if not any) dependencies to
facilitate mobile environments.
We expect to do something in the 0.16 (release) time frame, if not
0.18 for sure.
(We are currently about to release 0.14 and
Components: Java Client
Affects Versions: 0.14
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.15
Message credits are affected by Command Completions and not message-acks.
However in the current codebase,these two are intertwined
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.14
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.15
We currently calculate credit replenishment at the session level completely
[
https://issues.apache.org/jira/browse/QPID-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-3602:
---
Description:
Currently there are several issues related to message credits.
1. QPID-2604
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.14
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.15
When connection.stop() is called, the JMS client should release all it's
[
https://issues.apache.org/jira/browse/QPID-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-3602:
---
Description:
Currently there are several issues related to message credits.
1. QPID-2604
Hi Robbie (and co),
I noticed at least one behavioural changes that warrants a prominent
release note.
I've added a comment in QPID-3583 to cover the change of acking
behaviour for the AUTO_ACK case. See [1]
Could you guys help with some of the changes made in the failover side.
I'd let you
TCP_NODELAY makes a considerable improvement in synchronous cases
(sync pub, sync ack etc) and small tx cases and we generally recommend
that as a tuning option to our users/customers.
The reason for making TCP_NODELAY false by default is based on the
assumption that in most cases people will
Hi All,
Pavel has raised QPID-3575, where connections are not being closed
properly when session exceptions are raised via exception listeners.
He has also observed that, explicit closing of the session (after
receiving the exception) as a workaround doesn't work either.
We should investigate
[
https://issues.apache.org/jira/browse/QPID-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13141344#comment-13141344
]
Rajith Attapattu commented on QPID-3536:
For Topics we need to figure out
On Mon, Oct 31, 2011 at 9:18 AM, Robbie Gemmell
robbie.gemm...@gmail.com wrote:
Hi all,
Over the weekend I made a change to the 0-10 Java client so that using
prefetch=1 with transacted sessions and an OnMessage() listener would
result in the client only getting 1 message at a time, by moving
really makes any difference to asynchronous consumers.
I'm fine with the current change you've made.
Lets actually look at this credit issue in more detail after the release.
Robbie
On 31 October 2011 15:19, Rajith Attapattu rajit...@gmail.com wrote:
On Mon, Oct 31, 2011 at 9:18 AM, Robbie
that everybody feels is appropriate
and desirable.
Rajith
Cheers,
Rob
On 17 October 2011 23:09, Robbie Gemmell robbie.gemm...@gmail.com wrote:
On 17 October 2011 20:58, Rajith Attapattu rajit...@gmail.com wrote:
On Mon, Oct 17, 2011 at 12:39 PM, Robbie Gemmell
robbie.gemm...@gmail.com wrote:
On 17
On Thu, Oct 20, 2011 at 12:38 PM, Robbie Gemmell
robbie.gemm...@gmail.com wrote:
On 20 October 2011 16:36, Rajith Attapattu rajit...@gmail.com wrote:
On Thu, Oct 20, 2011 at 6:05 AM, Rob Godfrey rob.j.godf...@gmail.com wrote:
Sorry for being a little late responding to this thread...
Stepping
[
https://issues.apache.org/jira/browse/QPID-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13131835#comment-13131835
]
Rajith Attapattu commented on QPID-3532:
What kind of testing has been done
[
https://issues.apache.org/jira/browse/QPID-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13131926#comment-13131926
]
Rajith Attapattu commented on QPID-3532:
Robbie, thanks for the quick response.
I
[
https://issues.apache.org/jira/browse/QPID-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13132078#comment-13132078
]
Rajith Attapattu commented on QPID-3532:
Cool, go for it !
Fix
On Mon, Oct 17, 2011 at 5:54 AM, Robbie Gemmell
robbie.gemm...@gmail.com wrote:
Why do we resolve Address node types? This question arose during
review of proposed updates to the Address syntax implementation for
the Java client, but ultimately looks to be a wider question for all
the clients
On Mon, Oct 17, 2011 at 12:39 PM, Robbie Gemmell
robbie.gemm...@gmail.com wrote:
On 17 October 2011 16:01, Rajith Attapattu rajit...@gmail.com wrote:
On Mon, Oct 17, 2011 at 5:54 AM, Robbie Gemmell
robbie.gemm...@gmail.com wrote:
Why do we resolve Address node types? This question arose during
---
On 2011-10-12 21:09:40, rajith attapattu wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2364
of mutating operations we currently have in our
Destination implementations is rather incorrect (and also creates scope for
thread safety issues).
rajith attapattu wrote:
First up, thanks for taking the time to look at the patches. I appreciate
it.
As for the testing situation I
of mutating operations we currently have in our
Destination implementations is rather incorrect (and also creates scope for
thread safety issues).
rajith attapattu wrote:
First up, thanks for taking the time to look at the patches. I appreciate
it.
As for the testing situation I
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2364/#review2584
---
On 2011-10-12 21:09:40, rajith attapattu wrote
generated e-mail. To reply, visit:
https://reviews.apache.org/r/2366/#review2549
---
On 2011-10-12 21:02:31, rajith attapattu wrote:
---
This is an automatically generated e-mail. To reply
:
https://reviews.apache.org/r/2366/#review2551
---
On 2011-10-12 21:02:31, rajith attapattu wrote:
---
This is an automatically generated e-mail. To reply, visit:
https
-mail. To reply, visit:
https://reviews.apache.org/r/2366/#review2589
---
On 2011-10-12 21:02:31, rajith attapattu wrote:
---
This is an automatically generated e-mail. To reply
[
https://issues.apache.org/jira/browse/QPID-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13126878#comment-13126878
]
Rajith Attapattu commented on QPID-3538:
I could look at this along with the work I
[
https://issues.apache.org/jira/browse/QPID-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-3401:
---
Attachment: class_diagram.png
Class diagram that describes the new address implementation
[
https://issues.apache.org/jira/browse/QPID-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13125876#comment-13125876
]
Rajith Attapattu commented on QPID-3401:
The following set of patches aims
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2366/
---
Review request for qpid, Gordon Sim, Robbie Gemmell, Weston Price, and Keith
[
https://issues.apache.org/jira/browse/QPID-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-3401:
---
Attachment: QPID-3401.patch
QPID-3401-systests.patch
The systests patch
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2364/
---
(Updated 2011-10-12 21:09:40.553855)
Review request for qpid, Gordon Sim,
[
https://issues.apache.org/jira/browse/QPID-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13121309#comment-13121309
]
Rajith Attapattu commented on QPID-3527:
Actually acknowledgement happens in two
On Thu, Sep 22, 2011 at 12:19 PM, Oleksandr Rudyy oru...@gmail.com wrote:
Thanks Rajith for your commentaries.
I have discussed them with Robbie, our comments inline.
Qpid Java Client Failover Policy
1. Qpid client failover basic principles.
On Thu, Sep 29, 2011 at 12:02 PM, Oleksandr Rudyy oru...@gmail.com wrote:
Rajith,
Thanks a lot for your feedback.
Could you also have a look into the Failover Behaviour WIKI we created
to summarize the failover behaviour?
Alex nice work to get the wiki page up and running.
I added my
Hi Keith,
The system properties are documented here
http://qpid.apache.org/books/0.12/Programming-In-Apache-Qpid/html/ch03s06.html
It would be nice if you can add them here as well. These docs are version
controlled and is released along with the code/binaries.
So if you are planning any
Thanks for posting the write up.
Comments inline.
On Fri, Sep 16, 2011 at 12:26 PM, Oleksandr Rudyy oru...@gmail.com wrote:
Hi all,
Me and Robbie created the following draft of Failover Policy for Qpid
Java Client.
Could you please comment on it?
Qpid Java Client Failover Policy
1. Qpid
)
Review request for qpid and rajith attapattu.
Summary
---
This patch changes the 0-10 code path to create the SASL callback handler
using the CallbackHandlerRegistry. This allows the 0-10 code path to
support SASL mechanisms requiring other callback handlers, such as
CRAM-MD5-HASHED
[
https://issues.apache.org/jira/browse/QPID-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13106874#comment-13106874
]
Rajith Attapattu commented on QPID-3462:
When considering Failover with respect
[
https://issues.apache.org/jira/browse/QPID-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13106874#comment-13106874
]
Rajith Attapattu edited comment on QPID-3462 at 9/16/11 10:35 PM
The issues highlighted by Robbie are pretty much the problem areas
that I have identified as well (along with a few more).
All in all the failover code is the Achilles heel in the JMS client
and most of the stability issues, deadlocks and race conditions are
around this area.
I've been collecting
[
https://issues.apache.org/jira/browse/QPID-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13098960#comment-13098960
]
Rajith Attapattu commented on QPID-3473:
Thanks for taking care of this, makes my
[
https://issues.apache.org/jira/browse/QPID-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13099087#comment-13099087
]
Rajith Attapattu commented on QPID-3473:
Yes I understood that part. I think
[
https://issues.apache.org/jira/browse/QPID-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13098067#comment-13098067
]
Rajith Attapattu commented on QPID-3415:
Robbie,
Quick comment to say that I am
://reviews.apache.org/r/1608/
---
(Updated 2011-08-22 08:58:27)
Review request for qpid and rajith attapattu.
Summary
---
This patch changes the 0-10 code path to create the SASL callback handler
using the CallbackHandlerRegistry
[
https://issues.apache.org/jira/browse/QPID-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13098242#comment-13098242
]
Rajith Attapattu commented on QPID-3415:
I would also want to test this patch
[
https://issues.apache.org/jira/browse/QPID-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13098263#comment-13098263
]
Rajith Attapattu commented on QPID-3415:
I forgot to mention that this patch seems
: https://issues.apache.org/jira/browse/QPID-3466
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.12, 0.10
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Priority: Minor
Fix For: 0.14
[
https://issues.apache.org/jira/browse/QPID-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13095720#comment-13095720
]
Rajith Attapattu commented on QPID-3373:
Alex, I applied your patch and tested
Client
Affects Versions: 0.12, 0.10
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.14
If a session is using CLIENT_ACK mode fails over to another broker, and calls
acknowledge on a message it received before failover, the client throws
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.12, 0.10
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.14
If the broker throws a session level exception, during or just before
[
https://issues.apache.org/jira/browse/QPID-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13094988#comment-13094988
]
Rajith Attapattu commented on QPID-3461:
An easy way to reproduce the issue
[
https://issues.apache.org/jira/browse/QPID-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-3461:
---
Attachment: TxFailover.java
Attaching a reproducer created by Siddhesh Poyarekar.
To run
[
https://issues.apache.org/jira/browse/QPID-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-3395:
---
Fix Version/s: (was: 0.12)
0.14
Parsing exception of JNDI file should
[
https://issues.apache.org/jira/browse/QPID-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-3395.
Resolution: Fixed
Assignee: Rajith Attapattu
Applied Pavel's patch with minor
[
https://issues.apache.org/jira/browse/QPID-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-3373.
Resolution: Fixed
Fix Version/s: 0.14
Assignee: Rajith Attapattu
Fixed
[
https://issues.apache.org/jira/browse/QPID-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13091084#comment-13091084
]
Rajith Attapattu commented on QPID-3415:
Keith, I just skimmed through the patch
Welcome Keith !
Regards,
Rajith
On Wed, Aug 17, 2011 at 3:22 PM, Robbie Gemmell
robbie.gemm...@gmail.com wrote:
Welcome, Keith :)
Robbie
On 17 August 2011 18:22, Carl Trieloff cctriel...@redhat.com wrote:
Keith has been nominated and voted onto Qpid as a committer and has
accepted.
We had a contributor who did build ubuntu packages for Qpid.
However I am not sure about the current status and a bit of googling
found the following link
http://ubuntuforums.org/showthread.php?t=1785914
From searching the mailing lists for the contributor of ubuntu
packages I found Mike Owens.
On Thu, Aug 11, 2011 at 10:59 AM, Andrew Stitcher astitc...@redhat.com wrote:
I've been spending much of my time in the past few weeks getting support
for IPv6 in to the C++ and python code bases, and I expect to get it in
the code base in the next few days (unless someone can see a problem not
On 2011-08-10 14:15:46, Gordon Sim wrote:
As you have noted the python client doesn't support the AMQP 0-10 defined
url scheme. The c++ messaging API consequently supports the form of url
used by python in addition. That code is in
src/qpid/cpp/amqp_0_10/SimpleUrlParser.cpp and would
Attapattu
Assignee: Rajith Attapattu
Fix For: 0.14
After some thought it seems that the following JIRA's would benefit from some
reworking of the address resolution code as the original design had a few flaws
based on incorrect understanding of the address syntax.
QPID-3265
[
https://issues.apache.org/jira/browse/QPID-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13079018#comment-13079018
]
Rajith Attapattu commented on QPID-3381:
I forgot to account for the method name
401 - 500 of 1348 matches
Mail list logo
