import qpid ; then
PYTHON_TESTS=
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
--
Regards,
Rajith Attapattu
Red Hat
http
On Fri, Mar 12, 2010 at 8:59 AM, Alan Conway acon...@redhat.com wrote:
On 03/11/2010 06:41 PM, Rajith Attapattu wrote:
Hi All,
Currently quite a bit of options can be configured via the Java
Connection URL, which tends to make it ungainly and quite error prone.
If we are to think in terms
[
https://issues.apache.org/jira/browse/QPID-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-2444:
---
Summary: JMS client does not verify that the hostname connected to matches
that specified
/jira/browse/QPID-2444
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.6
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.7
The JMS client will succeed in connecting to a broker whose
-2445
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.6
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.7
The JMS client needs to extract the user ID from the external mechanism
Issue Type: Bug
Components: Java Client
Affects Versions: 0.6
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.7
The JMS client needs to extract the user ID from the external mechanism when
SASL EXTERNAL is used.
Ex. If we use
[
https://issues.apache.org/jira/browse/QPID-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-2446:
---
Description:
In some cases you would need to create connections with multiple SSL
-2447
Project: Qpid
Issue Type: Improvement
Components: Java Client
Affects Versions: 0.6
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.7
In some cases you would need to create connections with multiple SSL
[
https://issues.apache.org/jira/browse/QPID-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-2446:
---
Description:
In some cases you would need to create connections with multiple SSL
...@qpid.apache.org
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
trivially have a connection property file per connection).
Comments and suggestions are most welcomed !
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
-
Apache Qpid - AMQP Messaging Implementation
Project: http
Use/Interact: mailto:dev-subscr...@qpid.apache.org
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
--
Regards,
Rajith Attapattu
[
https://issues.apache.org/jira/browse/QPID-2437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842677#action_12842677
]
Rajith Attapattu commented on QPID-2437:
I hope both the c++ and python clients
Hi All,
The current out of the box performance for the java client is somewhat
impacted by the log4j issues.
The solution I provided (adding a log4j.xml) for the client jar is
totally wrong and no better than the previous solution.
Also the code base is littered with log4j.xml files, especially
Robbie thx for your comments !
On Mon, Mar 8, 2010 at 2:27 PM, Robbie Gemmell robbie.gemm...@gmail.com wrote:
From: Rajith Attapattu [mailto:rajit...@gmail.com]
Sent: 08 March 2010 15:42
To: dev@qpid.apache.org
Subject: Java Client Logging (yet again !)
Hi All,
The current out of the box
: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use
On Mon, Mar 8, 2010 at 6:09 PM, Rafael Schloming rafa...@redhat.com wrote:
Rajith Attapattu wrote:
On Mon, Mar 8, 2010 at 3:16 PM, Rafael Schloming rafa...@redhat.com
wrote:
Robbie Gemmell wrote:
3. From the next release we need to ship separate binaries for the
broker, client
[
https://issues.apache.org/jira/browse/QPID-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842116#action_12842116
]
Rajith Attapattu commented on QPID-2432:
I added fix in rev 919666 in Qpid trunk
: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use
Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
-
Apache Qpid - AMQP Messaging Implementation
Project
Issue Type: Bug
Components: C++ Client, Java Client, Python Client
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
If the address specifies a subject, then the out going message should set the
qpid.subject property as an application property
[
https://issues.apache.org/jira/browse/QPID-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12841046#action_12841046
]
Rajith Attapattu commented on QPID-2428:
The python client already contains a fix
+To
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
-
Apache
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.7
The c++ broker accepts illegal values for the following ACL properties
maxqueuesize, maxqueuecount, policytype,
Only valid ACL rules should be accepted and an exception should thrown at
startup
[
https://issues.apache.org/jira/browse/QPID-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12835320#action_12835320
]
Rajith Attapattu commented on QPID-2413:
In rev 911509 in Qpid trunk, I added some
/Interact: mailto:commits-subscr...@qpid.apache.org
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr
[
https://issues.apache.org/jira/browse/QPID-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12834774#action_12834774
]
Rajith Attapattu commented on QPID-1575:
I reversed the above commit in rev 910987
working as expected.
Perhaps a start would be to have clear documentation around the API,
the address syntax, what message types are supported etc...
Rafi has done some work on the docs, so perhaps we could use that as a guide.
Based on that we could then create a set of tests.
Regards,
Rajith
[
https://issues.apache.org/jira/browse/QPID-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12835108#action_12835108
]
Rajith Attapattu commented on QPID-1831:
The address based parser was committed
[
https://issues.apache.org/jira/browse/QPID-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12835108#action_12835108
]
Rajith Attapattu edited comment on QPID-1831 at 2/18/10 3:45 AM
[
https://issues.apache.org/jira/browse/QPID-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12835111#action_12835111
]
Rajith Attapattu commented on QPID-2242:
There were several bugs in the 0-10 code
Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
-
Apache Qpid - AMQP Messaging
[
https://issues.apache.org/jira/browse/QPID-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12834325#action_12834325
]
Rajith Attapattu commented on QPID-1575:
Kims fix at rev 910289 in Qpid trunk seems
[
https://issues.apache.org/jira/browse/QPID-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12834555#action_12834555
]
Rajith Attapattu commented on QPID-1575:
The testActiveTTL fails due to the c
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com
[
https://issues.apache.org/jira/browse/QPID-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12833200#action_12833200
]
Rajith Attapattu commented on QPID-2404:
Fixed the files with an extra licensing
[
https://issues.apache.org/jira/browse/QPID-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12833205#action_12833205
]
Rajith Attapattu commented on QPID-2404:
Added license headers to missing files
.
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
-
Apache Qpid
a linear sweep of all
queues with TTL messages so there may be some impact on performance during
the sweep if you have a lot of deep queues.
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
-
Apache Qpid - AMQP
[
https://issues.apache.org/jira/browse/QPID-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu reassigned QPID-2404:
--
Assignee: Rajith Attapattu
The following files does not have the ASL license header
: Licensing
Reporter: Rajith Attapattu
Priority: Blocker
Fix For: 0.6
./cpp/examples/README.verify
./cpp/src/qpid/framing/Blob.h
./cpp/src/qpid/framing/BodyHolder.cpp
./cpp/src/qpid/framing/BodyHolder.h
./cpp/src/tests/Blob.cpp
./cpp/src/tests
[
https://issues.apache.org/jira/browse/QPID-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12832834#action_12832834
]
Rajith Attapattu commented on QPID-2404:
@Steve
I also noticed that these files were
[
https://issues.apache.org/jira/browse/QPID-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-2404:
---
Attachment: rat_feb_11_2005_06_branch
I have checked in the license headers for the missing
[
https://issues.apache.org/jira/browse/QPID-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12832835#action_12832835
]
Rajith Attapattu commented on QPID-2404:
I will fix trunk with the same tomorrow
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com
Had a look at this closely and figured it was due to a classpath class
due to Sun bundling an older version of Xalan jar.
I have disabled this test until we come up with a decent solution.
Rajith
On Tue, Feb 2, 2010 at 9:39 AM, Rajith Attapattu rajit...@gmail.com wrote:
Hi
07:53 PM, Rajith Attapattu wrote:
Hi All,
There have been several attempts to use Qpid JMS client within various
containers like Application Servers, Servlet containers etc.
However there have been a few issues around this.
1. Qpid JMS client does not implement the optional methods nor
[
https://issues.apache.org/jira/browse/QPID-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12829119#action_12829119
]
Rajith Attapattu commented on QPID-2386:
Please attach the above code segment
On Wed, Feb 3, 2010 at 7:16 AM, Rafael Schloming rafa...@redhat.com wrote:
Rajith Attapattu wrote:
On Tue, Feb 2, 2010 at 4:23 PM, Rafael Schloming rafa...@redhat.com
wrote:
Some of you may recall that I ranted a bit just prior to the freeze for
the
0.6 release about how lots of non-client
Godfrey mentioned about using JNDI for any options that doesn't
fit into the above methods, which I think is a good solution.
Again I would like to hear any thoughts and suggestions around this.
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com
(WSDMArtifactsDirector.java:110)
at
org.apache.qpid.management.wsdm.capabilities.WSDMArtifactsDirector.direct(WSDMArtifactsDirector.java:71)
at
org.apache.qpid.management.wsdm.capabilities.WsArtifactsFactory.getArtifactsFor(WsArtifactsFactory.java:99)
... 66 more
Regards,
Rajith
kotasixtyn...@gmail.com wrote:
I have done a little patch. Should I register in JIRA to send it or may I
send it to somebody of developers?
2009/12/11 Alan Conway acon...@redhat.com
On 12/10/2009 10:43 AM, Andrew Stitcher wrote:
On Thu, 2009-12-10 at 10:30 -0500, Rajith Attapattu wrote
://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact
--
Martin Ritchie
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com
!
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
-
Apache Qpid - AMQP
[
https://issues.apache.org/jira/browse/QPID-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805535#action_12805535
]
Rajith Attapattu commented on QPID-2363:
The amqp/map MIME type is used by the other
[
https://issues.apache.org/jira/browse/QPID-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805541#action_12805541
]
Rajith Attapattu commented on QPID-2363:
My bad. It should be QPID-2226, not QPID
[
https://issues.apache.org/jira/browse/QPID-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805745#action_12805745
]
Rajith Attapattu commented on QPID-2363:
In rev 903911 I committed the above patch
[
https://issues.apache.org/jira/browse/QPID-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805747#action_12805747
]
Rajith Attapattu commented on QPID-2363:
Please note that the default for both 0-8
[
https://issues.apache.org/jira/browse/QPID-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805750#action_12805750
]
Rajith Attapattu commented on QPID-2352:
I have committed the above patch at rev
Feature
Components: Interop Testing, Java Client
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.7
As part of the new API initiative in Qpid, the C++ client and python client
have added support for a map message, where the content
[
https://issues.apache.org/jira/browse/QPID-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-2363:
---
Attachment: QPID-2363.patch
Attached is a patch that implements the AMQP 0-10 encoded Map
[
https://issues.apache.org/jira/browse/QPID-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805237#action_12805237
]
Rajith Attapattu commented on QPID-2363:
I presume we are going to use a message
[
https://issues.apache.org/jira/browse/QPID-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805261#action_12805261
]
Rajith Attapattu commented on QPID-2363:
For the 1st iteration for testing I did
[
https://issues.apache.org/jira/browse/QPID-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12803293#action_12803293
]
Rajith Attapattu commented on QPID-2350:
In rev 901000 in Qpid trunk, I have already
[
https://issues.apache.org/jira/browse/QPID-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12803295#action_12803295
]
Rajith Attapattu commented on QPID-2351:
I committed some ground work in rev 901506
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
-
Apache Qpid - AMQP
[
https://issues.apache.org/jira/browse/QPID-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-2352:
---
Attachment: QPID-2352.patch
The attached patch contains the code required to do SASL
Components: Java Client
Affects Versions: 0.5
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.7
Currently the JMS Client has two different properties for handling heartbeats
in 0-10 and 0-8/0-9 clients.
One property is in secs
: Improvement
Components: Java Client
Affects Versions: 0.5
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.7
It would be nice if the following properties could be set in the Connection URL
as individual broker properties.
Currently
: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.7
Currently the c++ broker supports SASL based encryption as an alternative for
SSL.
The Java client needs to add support for negotiating a security layer with
integrity and confidentially support and then use
[
https://issues.apache.org/jira/browse/QPID-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12802505#action_12802505
]
Rajith Attapattu commented on QPID-2262:
I will keep an eye on the automated builds
[
https://issues.apache.org/jira/browse/QPID-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-2343:
---
Attachment: QPID-2343_take2.patch
This patch contains a more improved version.
The strategy
[
https://issues.apache.org/jira/browse/QPID-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12802509#action_12802509
]
Rajith Attapattu commented on QPID-2343:
The second patch was based on comments
[
https://issues.apache.org/jira/browse/QPID-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12802539#action_12802539
]
Rajith Attapattu commented on QPID-2343:
The QPID-2343_take2.patch was applied
at end of file
+}
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:commits-subscr...@qpid.apache.org
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com
Components: Java Client
Affects Versions: 0.6
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.7
It would be nice if all Qpid clients followed a similar convention for naming
configuration properties.
The C++ client currently use
[
https://issues.apache.org/jira/browse/QPID-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12801982#action_12801982
]
Rajith Attapattu commented on QPID-2343:
The ClientProperties.java was moved
On Mon, Jan 18, 2010 at 6:10 PM, Robert Godfrey rob.j.godf...@gmail.com wrote:
Hi Rajith,
2010/1/18 Rajith Attapattu rajit...@gmail.com
Rob,
I noticed the following in AMQSession_0_8.java
+ public void sync() throws AMQException
+ {
+ declareExchange(new AMQShortString
[
https://issues.apache.org/jira/browse/QPID-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-2343:
---
Attachment: QPID-2343.patch
This contains a mechanism for standardizing the new property
[
https://issues.apache.org/jira/browse/QPID-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12799230#action_12799230
]
Rajith Attapattu commented on QPID-2108:
Applied the patch at rev 819948 in Qpid
[
https://issues.apache.org/jira/browse/QPID-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12799317#action_12799317
]
Rajith Attapattu commented on QPID-2108:
that's a good point.
I will ping Tim
[
https://issues.apache.org/jira/browse/QPID-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-2174.
Resolution: Fixed
I have checked in a fix at rev 898505 in Qpid trunk.
When kerberos auth
[
https://issues.apache.org/jira/browse/QPID-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-1839.
Resolution: Fixed
This was reviewed with the help of Rafi
SSLSender waits indefinitely
[
https://issues.apache.org/jira/browse/QPID-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-1609.
Resolution: Fixed
The remaining portion was added by Rafael in Qpid trunk at 782633.
see
[
https://issues.apache.org/jira/browse/QPID-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-1893.
Resolution: Fixed
The fix was added by Rafael in Qpid trunk at 782633.
I have reviewed
[
https://issues.apache.org/jira/browse/QPID-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-1677.
Resolution: Fixed
I am resolving this as there are no further comments or concerns
[
https://issues.apache.org/jira/browse/QPID-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-1720.
Resolution: Fixed
If client id contains an underscore it is not recognized in connection
[
https://issues.apache.org/jira/browse/QPID-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-1773.
Resolution: Fixed
Reviewed with the help of Rafi
If a session exception is thrown while
[
https://issues.apache.org/jira/browse/QPID-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-2074.
Resolution: Fixed
The DurableSubscriptionTest which was failing due to the issue described
[
https://issues.apache.org/jira/browse/QPID-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-1640.
Resolution: Fixed
A modified version of this patch was committed at rev 750203 in Qpid
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.6
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.7
JMS (0-10 client) does not verify if it supports the SASL mechanisms sent by
the broker
[
https://issues.apache.org/jira/browse/QPID-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12799460#action_12799460
]
Rajith Attapattu commented on QPID-2339:
A fix for this has been committed at rev
On Mon, Jan 11, 2010 at 8:55 AM, Robert Godfrey rob.j.godf...@gmail.com wrote:
2010/1/8 Rajith Attapattu rajit...@gmail.com
Hi All,
The JMS client does not have a consistent naming convention for system
properties, connection URL properties or extension properties
specified in extra
[
https://issues.apache.org/jira/browse/QPID-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-2336.
Resolution: Fixed
A fix for this was committed at rev 897922 in Qpid trunk.
Cannot
[
https://issues.apache.org/jira/browse/QPID-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-2173.
Resolution: Fixed
A fix for this has been committed at rev 897985 in Qpid trunk
[
https://issues.apache.org/jira/browse/QPID-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12798807#action_12798807
]
Rajith Attapattu commented on QPID-2175:
An improvement is added at rev 898021
this in the new svn documentation that jonathan is
putting together.
A preliminary version could be added in the wiki.
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
-
Apache Qpid - AMQP Messaging Implementation
Project
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.7
Currently you cannot set zero as the idle_timeout in the JMS client as it is
ignored and the brokers max timeout of 120 secs is selected instead.
--
This message is automatically generated
[
https://issues.apache.org/jira/browse/QPID-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-1831:
---
Attachment: QPID-1831.patch
The attached patch contains basic support for the common
1001 - 1100 of 1348 matches
Mail list logo
