Cliff Jansen created PROTON-1744:
Summary: bug in c-proactor-tests
Key: PROTON-1744
URL: https://issues.apache.org/jira/browse/PROTON-1744
Project: Qpid Proton
Issue Type: Bug
[
https://issues.apache.org/jira/browse/PROTON-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16329877#comment-16329877
]
Cliff Jansen commented on PROTON-1745:
--
Try the attached patch and see if that works. If so, we
[
https://issues.apache.org/jira/browse/PROTON-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen updated PROTON-1745:
-
Attachment: p1745_0.diff
> [proton-c, regression] PN_CONNECTION_BOUND event is emitted too s
[
https://issues.apache.org/jira/browse/PROTON-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-1842.
--
Resolution: Fixed
Fix Version/s: proton-c-0.25.0
> [c] Dispatch/Proton crashes w
Cliff Jansen created PROTON-1750:
Summary: Create test for address info on inbound sockets
Key: PROTON-1750
URL: https://issues.apache.org/jira/browse/PROTON-1750
Project: Qpid Proton
Issue
[
https://issues.apache.org/jira/browse/PROTON-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-1745.
--
Resolution: Fixed
Separate issue create for future test:
https://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/PROTON-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-1788.
--
Resolution: Won't Fix
See comment regarding further work for generic platforms.
This can
[
https://issues.apache.org/jira/browse/PROTON-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen updated PROTON-1788:
-
Attachment: p1788_0.patch
> Thread-safe schedule for 0.1
Cliff Jansen created PROTON-1788:
Summary: Thread-safe schedule for 0.16 C++
Key: PROTON-1788
URL: https://issues.apache.org/jira/browse/PROTON-1788
Project: Qpid Proton
Issue Type: Wish
[
https://issues.apache.org/jira/browse/PROTON-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16391674#comment-16391674
]
Cliff Jansen commented on PROTON-1788:
--
p17988_0.patch is a sample implementation that works
[
https://issues.apache.org/jira/browse/PROTON-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425053#comment-16425053
]
Cliff Jansen commented on PROTON-1800:
--
As a workaround, adding
client.receiver = None
[
https://issues.apache.org/jira/browse/PROTON-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16410314#comment-16410314
]
Cliff Jansen commented on PROTON-1514:
--
prior to reversion saw errors in qpid-dispatch
[
https://issues.apache.org/jira/browse/QPID-8209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved QPID-8209.
Resolution: Fixed
Fix Version/s: qpid-cpp-1.37.0
> qpidd segfault with huge backtrace w
[
https://issues.apache.org/jira/browse/PROTON-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16717563#comment-16717563
]
Cliff Jansen commented on PROTON-1982:
--
For me, the builds work up to f53c768 and fail after
Cliff Jansen created PROTON-1981:
Summary: Wrong posix time for pn_proactor_now()
Key: PROTON-1981
URL: https://issues.apache.org/jira/browse/PROTON-1981
Project: Qpid Proton
Issue Type: Bug
[
https://issues.apache.org/jira/browse/PROTON-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715515#comment-16715515
]
Cliff Jansen commented on PROTON-1981:
--
Looking at the doc for pn_proactor_now() in proactor.h
Cliff Jansen created PROTON-1982:
Summary: Proton C build fails on debian:stretch
Key: PROTON-1982
URL: https://issues.apache.org/jira/browse/PROTON-1982
Project: Qpid Proton
Issue Type: Bug
[
https://issues.apache.org/jira/browse/PROTON-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-1982.
--
Resolution: Fixed
Fix Version/s: proton-c-0.27.0
Debian:stretch build is now happy
[
https://issues.apache.org/jira/browse/QPID-8209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16614430#comment-16614430
]
Cliff Jansen commented on QPID-8209:
The value Queue::deleted can be set arbitrarily late because
[
https://issues.apache.org/jira/browse/DISPATCH-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16800883#comment-16800883
]
Cliff Jansen commented on DISPATCH-1274:
The connector timer is sometimes zero and sometimes
Cliff Jansen created PROTON-2027:
Summary: Proactor connection wake after memory freed when using
pn_proactor_disconnect().
Key: PROTON-2027
URL: https://issues.apache.org/jira/browse/PROTON-2027
[
https://issues.apache.org/jira/browse/PROTON-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-2027.
--
Resolution: Fixed
Fix Version/s: proton-c-0.28.0
> Proactor connection wake af
[
https://issues.apache.org/jira/browse/PROTON-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen updated PROTON-2027:
-
Affects Version/s: (was: proton-j-0.32.0)
proton-c-0.27.0
> Proac
Cliff Jansen created DISPATCH-1295:
--
Summary: reduce cpu and locking in timer/immediate code.
Key: DISPATCH-1295
URL: https://issues.apache.org/jira/browse/DISPATCH-1295
Project: Qpid Dispatch
Cliff Jansen created QPID-8278:
--
Summary: Build failure on Windows
Key: QPID-8278
URL: https://issues.apache.org/jira/browse/QPID-8278
Project: Qpid
Issue Type: Bug
Components: C
[
https://issues.apache.org/jira/browse/PROTON-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755400#comment-16755400
]
Cliff Jansen commented on PROTON-1999:
--
In example2.cpp
sender.work_queue()
is not thread safe
[
https://issues.apache.org/jira/browse/PROTON-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen reassigned PROTON-1999:
Assignee: Cliff Jansen
> [c] Crash in pn_connection_final
[
https://issues.apache.org/jira/browse/PROTON-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-1990.
--
Resolution: Fixed
Added a test.
Found a second instance of un-toggled drain that required
[
https://issues.apache.org/jira/browse/PROTON-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759664#comment-16759664
]
Cliff Jansen commented on PROTON-1999:
--
Olivier Delbeke: the mapping mechanism between Proton-C
[
https://issues.apache.org/jira/browse/PROTON-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759665#comment-16759665
]
Cliff Jansen commented on PROTON-1999:
--
Jeremy: I did not fully understand the scenario you have
[
https://issues.apache.org/jira/browse/PROTON-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen reopened PROTON-1990:
--
Naughty and unnecessary C++11 usage.
> drain gets st
[
https://issues.apache.org/jira/browse/PROTON-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-2027.
--
Resolution: Fixed
Test also works now on CentOS 6
> Proactor connection wake after mem
[
https://issues.apache.org/jira/browse/PROTON-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen reopened PROTON-2027:
--
Use make_work for more platform coverage.
> Proactor connection wake after memory freed w
[
https://issues.apache.org/jira/browse/PROTON-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16830729#comment-16830729
]
Cliff Jansen commented on PROTON-2036:
--
Also add a clearer description that
proton
Cliff Jansen created PROTON-2036:
Summary: Additional C++ threading documentation
Key: PROTON-2036
URL: https://issues.apache.org/jira/browse/PROTON-2036
Project: Qpid Proton
Issue Type
Cliff Jansen created PROTON-2081:
Summary: Hang in Windows proactor during connect
Key: PROTON-2081
URL: https://issues.apache.org/jira/browse/PROTON-2081
Project: Qpid Proton
Issue Type
[
https://issues.apache.org/jira/browse/PROTON-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cliff Jansen resolved PROTON-2081.
--
Resolution: Fixed
Fix Version/s: proton-c-0.29.0
> Hang in Windows proactor dur
Please apply QPID-2378 to the 0.6 branch to pick up the WCF client
specific release notes
I'm sorry. I mean QPID-2313.
Cliff
-Original Message-
From: Cliff Jansen (Interop Systems Inc) [mailto:v-clj...@microsoft.com]
Sent: Friday, January 29, 2010 12:07 PM
To: dev@qpid.apache.org
Cliff Jansen)
QPID-2313: Update to WCF Release notes (from Cliff Jansen)
Revised release notes for 0.6
== qpid-0.6rc4 ==
QPID-2137 : Commit patch to address StringIndexOutOfBounds during status
logging. Merge of trunk r898821.
QPID-2320: merged fix from trunk to 0.6 release branch.
== qpid-0.6rc3
Hi Kerry,
By coincidence, I have gone through the certificate learning curve in
the last few days.
The Windows broker currently supports registry based (as opposed to
file based) certificates that are in a certificate store that is
scoped to the local machine (not the current user). I am not up
Thanks for the info, Cliff! You've done some great work on this.
On 02/04/2010 07:54 PM, Cliff Jansen (Interop Systems Inc) wrote:
The existing 0.6 version of the WCF/C++ client provides basic WCF
functionality. Its most significant additional feature is distributed
transaction support
Subject: Re: WCF/C++ client feature work for 0.7
On 02/10/2010 07:41 AM, Cliff Jansen (Interop Systems Inc) wrote:
Hi Gordon,
I'd be keen to hear more of your thoughts an opinions on the new API
for the c++ client.
I will try to take another look at it shortly.
It would be worth seeing if we can
There are
certainly other csproj files with the license in at the top of the file
- do these cause problems for MSVC?
These C# project files are just XML. Putting the Apache license in
an XML comment at the top of the file will not adversely affect MSVC.
Cliff
-Original Message-
Hi Carl,
I've taken a look at QMFv2 and hope I understand it well enough to
give useful feedback.
On the whole, I think your characterization of the options is correct.
However, I would suggest you should not think of WCF merely as a SOAPy
WSDL provider, but more as a layered architecture. WCF
: QMF and .NET
On 03/08/2010 07:11 AM, Gordon Sim wrote:
On 03/05/2010 08:56 AM, Cliff Jansen (Interop Systems Inc) wrote:
Hi Carl,
I've taken a look at QMFv2 and hope I understand it well enough to
give useful feedback.
On the whole, I think your characterization of the options is correct
On 03/05/2010 08:56 AM, Cliff Jansen (Interop Systems Inc) wrote:
Hi Carl,
I've taken a look at QMFv2 and hope I understand it well enough to
give useful feedback.
On the whole, I think your characterization of the options is correct.
However, I would suggest you should not think of WCF merely
-Original Message-
From: Gordon Sim [mailto:g...@redhat.com]
Sent: Tuesday, March 09, 2010 5:37 AM
To: dev@qpid.apache.org
Subject: Re: QMF and .NET
On 03/08/2010 09:32 PM, Cliff Jansen (Interop Systems Inc) wrote:
Hi Gordon,
I'd suggest we don't focus exclusively on 'QMF' here
I agree
Hi Jonathan,
Great stuff!
I'll try to put together some WCF/C++ client related material over the weekend.
Cheers.
Cliff
-Original Message-
From: Jonathan Robie [mailto:jonathan.ro...@redhat.com]
Sent: Thursday, March 11, 2010 6:32 AM
To: dev@qpid.apache.org
Subject: Qpid Wiki in
Hi Rajith,
I think we as a project *must* have the same connection url/string
syntax across all clients.
I don't think this works in the WCF context. But I believe it is
merely because WCF has different conventions, not that the proposal
lacks merit in general.
In WCF, the constituents of
I would be very interested to join the conference call. Thanks.
Cliff
-Original Message-
From: Marnie McCormack [mailto:marnie.mccorm...@googlemail.com]
Sent: Thursday, January 08, 2009 1:53 AM
To: qpid-...@apache.org
Subject: Qpid .NET Strategy - Interested ?
All,
We are currently
Hi all,
Windows is a newly supported C++ platform in M4 and we are beginning
to see some early adopters having difficulty.
May I suggest a Windows area on qpid.apache.org with:
- more elaborate install and run doc
- clear info on differences compared to the Linux implementation
i.e.
Hi Danushka,
That was another subject I was going to broach for M5, probably on the heels of
the C++ build system.
I would suggest to export the needed symbols rather than all of them if
possible. I would also recommend defining the exports in source (as the Boost
libraries do), rather than
The protocol_gen.mak step is only required if you are building straight
from the svn repository. Since you are building from the source distribution,
you should just proceed to building the broker or client from the qpid.sln
file in the src directory.
Cliff
-Original Message-
From:
Ted Ross wrote:
Regarding the .Net client in general... It's my understanding that
there are some contributors at Microsoft that are working on this part
of the code but I don't know what the status of that work is. Maybe
somebody who knows will chime in.
Since David Ingham has just become a
Hi Gordon,
Jonathan previously requested support for the stream operator and I've
had a tentative stab at exploring what that might look like as well.
In addition, I would like to see the some stream-ish functions that
are friendly to char* blobs that are not null terminated. Something
along
I like the discussion on message content.
Given Alan's recent suggestions, I can easily envisage how an
implementation could optimize the Receiver case and lazily extract the
content from the underlying protocol frames into the form required by
the application, and avoid an intermediate memory
Hi Ishara,
Hi Carl,
Thanks a lot for your reply.I,m interested to contribute to the C# client.
That would be great. I would be happy to give you any help to get
started.
Carl Trieloff wrote:
- Cliff from Microsoft has submitted a C# client over the C++ client.
This client is written in
The Linux C++ code base is certainly more mature, but features for Windows
users are under very active development.
New for 0.6 is a persistent store module, SSL support (shortly), a greatly
improved build experience.
Clustering support is high on the wish list, but planning and development on
Robert Greig wrote:
Having said that, I did take a look at this question (could WCF be a
generic messaging API) for other reasons related to my day job a
while ago and concluded that it could be. You would simply have to
define some very simple contracts (e.g. with a single method
Robert Greig wrote:
I can see that it would be nice to have a completely managed code .NET
library (for example, I think you need to be fully managed to support
one click deployment?). However I can also see that leveraging the
existing C++ codebase is very attractive since the core of it has
Robert Greig wrote:
Finally, there are performance issue with managed/non-managed heap
copies in Java that makes JNI unattractive (I don't know if this
applies to .NET too - although I did ask the question on this mailing
list some time ago without receiving any answer).
I'll take a stab at
Another thing I have noticed is that there is no WCF component
artifact in the beta build, is that something we plan to release with
0.6?
Yes. I contacted Andrew about this yesterday. JIRA coming soon.
Cliff
-Original Message-
From: Robbie Gemmell [mailto:robbie.gemm...@gmail.com]
I have taken a first stab at providing the release artifact for
WCF. (QPID-2267)
Like the python and ruby cases, it consists of a static snapshot of
the relevant subdirectory.
Unlike those cases, it cannot be built by the user unless the C++
artifact is also downloaded and built to provide the
Cliff can you comment on these bugs? Are they truly as important as
blocker/critical? If so unless there are patches attached to the jiras
very soon I think we'll have to omit the specific WCF source code from
this release [...]
Agreed. These were marked as such because they would make a
401 - 464 of 464 matches
Mail list logo
