Remove the class printing from the log4j layout as the (%F:%L) provides
sufficient debug information
-
Key: QPID-2911
URL:
[
https://issues.apache.org/jira/browse/QPID-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2911:
--
Attachment: qpid-2911.patch
Remove the class printing from the log4j layout as the (%F:%L) provides
[
https://issues.apache.org/jira/browse/QPID-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu reassigned QPID-2911:
-
Assignee: Andrew Kennedy (was: Sorin Suciu)
Andrew, can you review please?
Remove the class
[
https://issues.apache.org/jira/browse/QPID-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2912:
--
Component/s: Python Test Suite
Modify python-test.xml to use ant to run the python tests
Hi all,
As indicated below I have now created an initial test build for early
review. Can all developers please give their preferred sections a once over
for issues, e.g. to update any missing licences and check for any packaging
problems etc (whether they be inherent, or the result of my build
On 10/21/2010 05:23 PM, Robert Schweikert wrote:
If I add the include file and the code cahnges for the return value
things compile.
Gotcha. I just checked the svn revisions, and I added support for XQilla
2.2.3 just after 0.6 was released. Sorry I didn't catch this earlier!
The released
[
https://issues.apache.org/jira/browse/QPID-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12923873#action_12923873
]
Jonathan Robie commented on QPID-2725:
--
I've left some files here that I should remove,
[
https://issues.apache.org/jira/browse/QPID-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12923883#action_12923883
]
Alan Conway commented on QPID-2492:
---
I withdraw my objection to subprocess. Its already
Currently, if you specify qpid.max_size=3, the broker accepts the
string value, and does not convert it to the expected integer type.
I want to change this to either:
1. Reject string arguments when numeric types are accepted, or
2. Accept arguments of any type if the value can be converted to
On Fri, 2010-10-22 at 12:06 -0400, Jonathan Robie wrote:
Currently, if you specify qpid.max_size=3, the broker accepts the
string value, and does not convert it to the expected integer type.
Some context might help here -
Where do you specify qpid.max_size?
Which broker are you talking about?
On 10/22/2010 12:22 PM, Andrew Stitcher wrote:
On Fri, 2010-10-22 at 12:06 -0400, Jonathan Robie wrote:
Currently, if you specify qpid.max_size=3, the broker accepts the
string value, and does not convert it to the expected integer type.
Some context might help here -
Where do you
On 10/22/2010 12:22 PM, Andrew Stitcher wrote:
Where do you specify qpid.max_size?
Which broker are you talking about?
I'm talking about the C++ implementation of the broker.
On 10/22/2010 12:37 PM, Ted Ross wrote:
Is this related to https://issues.apache.org/jira/browse/QPID-2896 ?
Yes:
QPID Cpp Messaging Libraries for WinSDK Are Not Signed
--
Key: QPID-2913
URL: https://issues.apache.org/jira/browse/QPID-2913
Project: Qpid
Issue Type: Improvement
Reporter:
On 10/22/2010 01:31 PM, Jonathan Robie wrote:
On 10/22/2010 12:22 PM, Andrew Stitcher wrote:
Where do you specify qpid.max_size?
Which broker are you talking about?
I'm talking about the C++ implementation of the broker.
On 10/22/2010 12:37 PM, Ted Ross wrote:
Is this related to
[
https://issues.apache.org/jira/browse/QPID-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Robie reassigned QPID-2896:
Assignee: Jonathan Robie
Incorrect detection of data types in address parameters - C++
On 10/22/2010 02:04 PM, Ted Ross wrote:
I'm trying to fix both bugs. In the broker, should it reject the
string value when it expects an integer, or should it do the conversion?
Just my opinion: The broker should use isdigit() or equivalent to
determine if it can convert and if so, convert.
On 10/22/2010 09:24 AM, Jonathan Robie wrote:
On 10/21/2010 05:23 PM, Robert Schweikert wrote:
If I add the include file and the code cahnges for the return value
things compile.
Gotcha. I just checked the svn revisions, and I added support for XQilla
2.2.3 just after 0.6 was released.
On a Windows box broker.cpp can't include sasl/sasl.h because it doesn't exist.
On the Windows side Sasl is present only as a handler to reject anything but
Plain or Anonymous
I suggest that the broker.cpp changes get rewritten to use platform-dependant
saslFactory calls. Then the linux
18 matches
Mail list logo
