[
https://issues.apache.org/jira/browse/PROTON-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438208#comment-15438208
]
James Birdsall commented on PROTON-1275:
I got a chance to pull down your ch
[
https://issues.apache.org/jira/browse/PROTON-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414534#comment-15414534
]
James Birdsall commented on PROTON-1276:
It looks like this issue was cause
James Birdsall created PROTON-1276:
--
Summary: Reactor: Race between CollectorImpl peek and pop can
result in dispatching freed events
Key: PROTON-1276
URL: https://issues.apache.org/jira/browse/PROTON-1276
James Birdsall created PROTON-1275:
--
Summary: Proton-J reactor: socket connection interrupt causes
unhandled IllegalArgumentException
Key: PROTON-1275
URL: https://issues.apache.org/jira/browse/PROTON-1275
[
https://issues.apache.org/jira/browse/QPID-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Birdsall updated QPID-2194:
-
Attachment: Qpid Persistence Provider Test Plan V2.3.pdf
This is the test plan I came up with for
On Tuesday, November 10, 2009 5:42 AM, Aidan Skinner
[mailto:aidan.skin...@gmail.com] wrote:
>On Tue, Nov 10, 2009 at 3:33 AM, James Birdsall wrote:
>> The mailing list strips attachments and I don't have permissions to add a
>> page to the wiki (I can't even LOOK at
On Monday, November 09, 2009 12:41 PM, Alan Conway wrote:
>On 11/09/2009 11:45 AM, Kim van der Riet wrote:
>> It would be a good idea to standardize store tests if we can. If we can
>> agree that no matter what store is used, the end-result from a client
>> perspective would be the same, then test
[
https://issues.apache.org/jira/browse/QPID-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Birdsall closed QPID-2167.
Resolution: Cannot Reproduce
I can't reproduce the problem with exchangeQuery anymore. I gu
[
https://issues.apache.org/jira/browse/QPID-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Birdsall closed QPID-2170.
Confirmed, this works OK now.
> Enqueuing a durable message with SQL persistence provider loa
[
https://issues.apache.org/jira/browse/QPID-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772209#action_12772209
]
James Birdsall commented on QPID-2170:
--
Still seeing this problem, doesn'
[
https://issues.apache.org/jira/browse/QPID-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Birdsall closed QPID-2169.
> Cannot delete durable exchanges or queues with SQL persistence provider loa
[
https://issues.apache.org/jira/browse/QPID-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Birdsall closed QPID-2168.
> C++ broker crashes when declaring durable binding with SQL persistence
> provider
[
https://issues.apache.org/jira/browse/QPID-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772208#action_12772208
]
James Birdsall commented on QPID-2169:
--
Confirmed, I can delete persisted excha
[
https://issues.apache.org/jira/browse/QPID-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772206#action_12772206
]
James Birdsall commented on QPID-2168:
--
Confirmed, the broker no longer crashes.
[
https://issues.apache.org/jira/browse/QPID-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771726#action_12771726
]
James Birdsall commented on QPID-2167:
--
Trying to check whether an exchange ex
[
https://issues.apache.org/jira/browse/QPID-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Birdsall updated QPID-2170:
-
Attachment: issue3-server-disconnect.txt
Trace on the server up to the disconnect is attached
-2170
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.6
Environment: Windows Server 2008
Reporter: James Birdsall
Fix For: 0.6
This is related to Qpid-2168, but happens when the QpidStore database already
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.6
Environment: Windows Server 2008
Reporter: James Birdsall
Fix For: 0.6
After declaring a durable exchange or queue with the SQL persistence provider
loaded, and then cycling the broker
: Qpid
Issue Type: Bug
Components: C++ Broker
Affects Versions: 0.6
Environment: Windows Server 2008
Reporter: James Birdsall
Fix For: 0.6
The SQL persistence provider creates the QpidStore database on startup if it is
not already present
When there is no persistence provider, what is the expected behavior for Qpid
when trying to declare a durable exchange or queue? I thought it was supposed
to fail, but I have been seeing it succeed (C++ client and broker built from
the trunk on Windows).
If we can confirm that this is not the
Project: Qpid
Issue Type: Bug
Components: C++ Client
Affects Versions: 0.6
Environment: Windows Server 2008
Reporter: James Birdsall
Fix For: 0.6
In a program using the C++ client, running against the C++ broker, trying to do
a
Looks like the mailing list stripped the attachment, sorry. Please ping me
directly if you'd like to see the plan.
From: James Birdsall [mailto:jb...@microsoft.com]
Sent: Tuesday, September 29, 2009 3:39 PM
To: dev@qpid.apache.org
Subject: Qpid persistence provider test plan
Steve Hust
uture -- some parts of the
plan are specific to using a database and/or Windows, but most of it should be
applicable to any persistence provider.
Thanks to Gordon Sim over on the users list for some valuable input which is
incorporated in this draft.
--James Bir
23 matches
Mail list logo
