[
https://issues.apache.org/jira/browse/QPID-5344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ingham updated QPID-5344:
---
Attachment: QPID-5344.patch
A patch is attached (QPID-5344.patch) to address this issue.
> [AMQP
[
https://issues.apache.org/jira/browse/QPID-5344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ingham updated QPID-5344:
---
Attachment: DeadlockTrace2.txt
DeadlockTrace1.txt
Attaching traces per issue
David Ingham created QPID-5344:
--
Summary: [AMQP 1.0 JMS] Thread deadlock related to session close
Key: QPID-5344
URL: https://issues.apache.org/jira/browse/QPID-5344
Project: Qpid
Issue Type
[
https://issues.apache.org/jira/browse/QPID-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ingham updated QPID-5295:
---
Attachment: QPID-5295.patch
Proposed fix attach as QPID-5295.patch.
> [AMQP 1.0 JMS] Thread deadl
David Ingham created QPID-5295:
--
Summary: [AMQP 1.0 JMS] Thread deadlock
Key: QPID-5295
URL: https://issues.apache.org/jira/browse/QPID-5295
Project: Qpid
Issue Type: Bug
Components
[
https://issues.apache.org/jira/browse/QPID-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ingham updated QPID-5294:
---
Attachment: QPID-5294.patch
Workaround fix provided in QPID-5294.patch.
> [AMQP 1.0 JMS] Thr
David Ingham created QPID-5294:
--
Summary: [AMQP 1.0 JMS] Thread deadlock due to JVM bug JDK-8022788
Key: QPID-5294
URL: https://issues.apache.org/jira/browse/QPID-5294
Project: Qpid
Issue Type
[
https://issues.apache.org/jira/browse/QPID-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ingham updated QPID-5293:
---
Attachment: QPID-5293.patch
Fix provided in QPID-5293.patch.
> [AMQP 1.0 JMS] Thread deadlock w
David Ingham created QPID-5293:
--
Summary: [AMQP 1.0 JMS] Thread deadlock when closing connection
Key: QPID-5293
URL: https://issues.apache.org/jira/browse/QPID-5293
Project: Qpid
Issue Type
[
https://issues.apache.org/jira/browse/QPID-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ingham updated QPID-5245:
---
Attachment: (was: SessionException.java)
> [AMQP 1.0 JMS] Provide additional information thro
[
https://issues.apache.org/jira/browse/QPID-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ingham updated QPID-5245:
---
Attachment: SessionException.java
> [AMQP 1.0 JMS] Provide additional information through excepti
[
https://issues.apache.org/jira/browse/QPID-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799128#comment-13799128
]
David Ingham commented on QPID-5245:
A fix is attached in the form of the QPID-
[
https://issues.apache.org/jira/browse/QPID-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ingham updated QPID-5245:
---
Attachment: ErrorCodes.java
> [AMQP 1.0 JMS] Provide additional information through excepti
[
https://issues.apache.org/jira/browse/QPID-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ingham updated QPID-5245:
---
Attachment: QPID-5245.patch
SessionException.java
David Ingham created QPID-5245:
--
Summary: [AMQP 1.0 JMS] Provide additional information through
exceptions
Key: QPID-5245
URL: https://issues.apache.org/jira/browse/QPID-5245
Project: Qpid
[
https://issues.apache.org/jira/browse/QPID-5206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ingham updated QPID-5206:
---
Attachment: QPID-5206.patch
Patch containing proposed fix attached as QPID-5206.patch
> [AMQP
David Ingham created QPID-5206:
--
Summary: [AMQP 1.0 JMS] Occasional null pointer exception seen in
org.apache.qpid.amqp_1_0.client.Sender$1.remoteDetached(Sender.java:181)
Key: QPID-5206
URL: https
[
https://issues.apache.org/jira/browse/QPID-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ingham updated QPID-5194:
---
Attachment: QPID-5194.patch
Fix for negative timeout issue attached as QPID-5194.patch
David Ingham created QPID-5194:
--
Summary: Occasionally see ERROR (221): Caught Exception:
java.lang.IllegalArgumentException: timeout value is negative
Key: QPID-5194
URL: https://issues.apache.org/jira/browse/QPID
[
https://issues.apache.org/jira/browse/QPID-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ingham updated QPID-5182:
---
Attachment: QPID-5182.patch
Attached patch (developed with Rob Godfrey)
>
David Ingham created QPID-5182:
--
Summary: The details of custom error-conditions are not being
preserved up to the Error object
Key: QPID-5182
URL: https://issues.apache.org/jira/browse/QPID-5182
[
https://issues.apache.org/jira/browse/QPID-5178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ingham updated QPID-5178:
---
Attachment: QPID-5178.patch
Fix provided in QPID-5178.patch.
> Flow detail f
David Ingham created QPID-5178:
--
Summary: Flow detail from Rejected outcome though to
MessageRejectedException
Key: QPID-5178
URL: https://issues.apache.org/jira/browse/QPID-5178
Project: Qpid
[
https://issues.apache.org/jira/browse/QPID-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777492#comment-13777492
]
David Ingham commented on QPID-5165:
How would Message.getPropertyNames work in
[
https://issues.apache.org/jira/browse/QPID-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ingham updated QPID-5172:
---
Attachment: QPID-5172.patch
Fix for StringTypeConstructor and SymbolTypeConstructor. Developed with
[
https://issues.apache.org/jira/browse/QPID-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ingham updated QPID-5172:
---
Attachment: QPID-5172-stacktrace.txt
Stack trace showing the manifestation of the bug
David Ingham created QPID-5172:
--
Summary: Thread safety issue in StringTypeConstructor.construct
and SymbolTypeConstructor.construct
Key: QPID-5172
URL: https://issues.apache.org/jira/browse/QPID-5172
[
https://issues.apache.org/jira/browse/QPID-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ingham updated QPID-5167:
---
Attachment: QPID-5167.patch
This patch allows configuration of the sync_publish property via the
David Ingham created QPID-5167:
--
Summary: Allow sync_publish flag to be controlled from the
ConnectionFactory connection string
Key: QPID-5167
URL: https://issues.apache.org/jira/browse/QPID-5167
[
https://issues.apache.org/jira/browse/QPID-5166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ingham updated QPID-5166:
---
Attachment: QPID-5166.patch
This patch updates SessionImpl to create the dispatcher thread when
David Ingham created QPID-5166:
--
Summary: Lazily create dispatcher thread in JMS Session
implementation
Key: QPID-5166
URL: https://issues.apache.org/jira/browse/QPID-5166
Project: Qpid
Issue
David Ingham created QPID-5165:
--
Summary: No mapping from JMS JMSXGroupID property to AMQP message
group-id
Key: QPID-5165
URL: https://issues.apache.org/jira/browse/QPID-5165
Project: Qpid
[
https://issues.apache.org/jira/browse/QPID-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ingham updated QPID-5165:
---
Attachment: QPID-5165.patch
The attached patch implements the mapping between JMSXGroupID and group
[
https://issues.apache.org/jira/browse/QPID-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ingham updated QPID-2204:
---
Attachment: DBI_2.diff
DBI_1.diff
The proposed fix is to update the AssemblyInfo
Environment: Windows
Reporter: David Ingham
The two assemblies for the WCF channel (Apache.Qpid.Channel and
Apache.Qpid.Interop) are not currently visible to COM components. This causes
problems for integration into Excel using the Excel RealTimeData mechanism
which uses COM objects
A quick update on ApacheCon...
First was BarCamp. If you haven't heard of BarCamp, it works like this - the
organizers provide some basic infrastructure (rooms, projectors, etc.) but
there is no program defined in advance. The attendees turn up prepared to speak
on some topic and then spend the
Versions: 0.6
Environment: Client and broker running on Windows 7. SQL Express used
for the broker store. Python 2.5 used for Python QMF management tools.
Reporter: David Ingham
The default exchange binding to a durable queue is not restored on broker
restart.
Here are the
just posted a link to a Qpid meetup:
http://cwiki.apache.org/confluence/display/qpid/Qpid+Meetup+at+ApacheCon+2009
Any chance you or one of your colleagues could do a presentation at the
meetup?
Jonathan
David Ingham wrote:
> Hi Jonathan,
>
> One of my colleagues here is doing a session
bject: Re: ApacheCon
Jonathan Robie wrote:
> David Ingham wrote:
>> I'm planning on attending ApacheCon next week in Oakland. Anyone else
>> going to be there?
>>
>
> Is Microsoft doing a session at ApacheCon?
I will be at ApacheCon and I have heard that you are invo
I'm planning on attending ApacheCon next week in Oakland. Anyone else going to
be there?
Dave.
Hi all,
There has been a change of plan regarding PDC. We've cancelled the AMQP-related
session in which I was planning to talk about Qpid. We weren't able to get all
the various pieces lined up in time for this event. Next time.
Thanks,
Dave.
-Original Message-----
From: Da
Hi all,
I just wanted to let you know that we're planning on showcasing Qpid at the
upcoming Microsoft PDC (Professional Developers Conference) [1]. We're planning
a session focused on queuing and pub/sub in a heterogeneous environment. This
will cover existing bridging solutions as a way to co
bject: Re: Opportunity: 0.6 Release Manager - C++ Volunteers
On Fri, Oct 2, 2009 at 7:01 PM, David Ingham wrote:
> Hi Marnie,
>
> On the Windows side, we'd like to get see the following items in 0.6:
>
> * Steve's refactoring of the C++ message store with support for Mic
Hi Marnie,
On the Windows side, we'd like to get see the following items in 0.6:
* Steve's refactoring of the C++ message store with support for Microsoft SQL
Server
(https://issues.apache.org/jira/browse/QPID-1726)
* Cliff's update to the WCF channel to add transaction support
(https://iss
That makes sense Robert. We're planning the Windows persistence work in two
phases, initially SQL Server for everything and then add in the CLFS piece for
the message log for systems that support it. Hopefully the SQL layer piece
should be portable enough to make a SQLLite mapping fairly straigh
Hey John,
As Steve mentioned we're working to implement a Windows persistence provider
for Qpid/C++. We want this to be based on freely available components that
won't require purchasing any proprietary software (over and above Windows
itself). Our current thoughts are to build a hybrid store t
David,
Apologies for the complete radio silence on the 0.5 release. I have
completed the reassembly of the Java broker and local testing is
looking good. So we should be in good shape to create an RC for review
at the end of next week.
Regards
Martin
2009/4/22 David Ingham :
> Hi Aidan,
>
&
Hi Aidan,
I was wondering whether you have an update on the planned schedule for 0.5. I
know you're all working hard to stabilize the Java side of the house but,
selfishly, I'm keen to get the Windows updates to the C++ that Steve has been
working on out to the public in an official build. I kn
Thanks for taking the time to explain Aidan - I think we're in sync.
Dave.
-Original Message-
From: aidan.skin...@gmail.com [mailto:aidan.skin...@gmail.com] On Behalf Of
Aidan Skinner
Sent: Friday, February 20, 2009 1:39 PM
To: David Ingham
Cc: dev@qpid.apache.org
Subject: Re: wa
Hi Aidan,
I'm struggling to think of a business case for why I'd want to mix and match
C++ and Java brokers in a cluster. I'm not pushing back; I'm just interested as
to why you think this is important.
FWIW, I think that there's great value in having a common clustering design
across the diff
Hey Etienne, good to hear from you. Arnaud blazed the trail and now there's a
bit of an Arjuna alumni thing starting here ;-)
-Original Message-
From: etienne.antoniu...@gmail.com [mailto:etienne.antoniu...@gmail.com] On
Behalf Of Etienne Antoniutti Di Muro
Sent: Thursday, February 19, 2
Hi Rafael,
I think that the spec extract that you quote is addressing a different issue
from how I understood Rajith's original ask.
I believe that the extract you quote below is talking about what happens when I
consume messages via different routes from the same MessageConsumer. That is,
if
There's no requirement in JMS for all the MessageListeners to be created before
the Connection is started. That is, you should be able to add new
MessageConsumers to a Session created from an already started Connection and
receive messages through that MessageConsumer.
-Original Message
Hi all,
Just a quick intro for the list since I've been quiet to date. I work on
messaging technologies in the Connected Systems Division at Microsoft. I've
been tracking AMQP since early 2005 when John Davies first announced its
existence at the Web Services on Wall Street Conference. In a pre
54 matches
Mail list logo
