Adam Nemcek created PROTON-725:
--
Summary: pni_parse_url does not properly handle Base64 in URL
Key: PROTON-725
URL: https://issues.apache.org/jira/browse/PROTON-725
Project: Qpid Proton
Issue
Adam Nemcek created PROTON-726:
--
Summary: Macros to wrap malloc(), realloc(), free()
Key: PROTON-726
URL: https://issues.apache.org/jira/browse/PROTON-726
Project: Qpid Proton
Issue Type: Wish
German Shepherd created PROTON-727:
--
Summary: Add a NULL-pointer checks to malloc() and realloc() calls
Key: PROTON-727
URL: https://issues.apache.org/jira/browse/PROTON-727
Project: Qpid Proton
[
https://issues.apache.org/jira/browse/PROTON-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14182596#comment-14182596
]
Dominic Evans commented on PROTON-725:
--
[~E528527] this is what URL encoding was
[
https://issues.apache.org/jira/browse/PROTON-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14182604#comment-14182604
]
German Shepherd commented on PROTON-725:
Thanks for a response - you have a good
[ X ] Yes, release Proton 0.8 RC4 as 0.8 final.
I ran the C and Java build+tests, tried out the Java binaries with the JMS
client build+tests, all seemed fine.
Robbie
On 23 October 2014 17:21, Rafael Schloming r...@alum.mit.edu wrote:
Hi Everyone,
I've put together RC4. This is pretty much
[ X ] Yes, release Proton 0.8 RC4 as 0.8 final.
Tested Proton-J with ActiveMQ and the new JMS client and found no issues,
On 10/23/2014 12:21 PM, Rafael Schloming wrote:
Hi Everyone,
I've put together RC4. This is pretty much the same as RC3 with a number of
fixes to disable those SSL
[ X ] Yes, release Proton 0.8 RC4 as 0.8 final.
Compiled on Windows Server 2012, Visual Studios 2008, 2010, 2012, 2013.
Ran some tests on a few kits with no issues.
Hallo,
I used proton 0.7 and later when I had an error, proton 0.8 RC4 to build
qpid-cpp-0.30. In both cases at some time qpidd aborts in proton library
in the following location:
#0 0x003999432635 in raise () from /lib64/libc.so.6
#1 0x003999433e15 in abort () from /lib64/libc.so.6
From the trace, it seems like the broker is receiving a transfer whose
delivery id is out of order.
This shouldn't cause an abort - likely the result is an untested failure path,
in transport.c:781:
if (id_present id != state-id) {
int err = pn_do_error(transport,
I just rebuilt all client processes to use proton 0.8 (it was still 0.7 before)
Error is still the same.
Best regards,
24.10.2014 18:16, Ken Giusti пишет:
From the trace, it seems like the broker is receiving a transfer whose
delivery id is out of order.
This shouldn't cause an abort -
Rafael H. Schloming created PROTON-728:
--
Summary: transport aborts when delivery ids are out of sequence
Key: PROTON-728
URL: https://issues.apache.org/jira/browse/PROTON-728
Project: Qpid Proton
[
https://issues.apache.org/jira/browse/PROTON-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14183209#comment-14183209
]
ASF subversion and git services commented on PROTON-728:
Commit
Hi Michael,
I just committed the change Ken suggested to at least fix the abort. Is
there any way you could retest with trunk?
If the problem still occurs (I expect it will, just not quite so fatally)
it would be good to get the protocol trace for both the client and the
server and see if that
Sorry, should I check out the trunk from the repository or can I download
the new sources tar archive from somewhere? The last version I used I have
downloaded from
http://people.apache.org/~rhs/qpid-proton-0.8rc4/qpid-proton-0.8.tar.gz
If the sources are to be checked out which url should I use?
You can check out the trunk source code from here:
http://svn.apache.org/repos/asf/qpid/proton/trunk/
You should be able to turn on the protocol trace by setting the
PN_TRACE_FRM environment variable to 1, e.g.:
export PN_TRACE_FRM=1
run-client-program
You will need to do this on the
Ok I have some results. Now the core is not dumped but I have unusual delays
during application startup. I have started qpidd up with PN_TRACE_FRM set,
but do not see any trace output. Only thing I have are the following entries
from syslog:
Oct 24 21:17:24 ccsfat qpidd[28477]: 2014-10-24
Hi Michael,
Sorry for misleading you. I think the way qpidd integrates proton must
override the PN_TRACE_FRM configuration. I believe you should be able to
get the protocol trace from the broker by using the -t option, e.g. qpidd
-t. I'll take a look at the logs you posted, however I suspect the
Hallo Rafael,
Sorry, but this time I have to attach a file :-) (I was usually trying to
avoid it because sending to mailing list) But qpidd trace is uncompressed
2Mb, compressed 80Kb
So compressed qpidd log is attached.
Best regards,
25.10.2014 00:41, Rafael Schloming пишет:
Hi Michael,
The mailing list scrubs attachments so it didn't get included.
You can create an issue at
https://issues.apache.org/jira/secure/CreateIssue.jspa?pid=12313720issuetype=1priority=3
and post the trace there.
-Chuck
- Original Message -
From: Michael Ivanov iv...@logit-ag.de
To:
[
https://issues.apache.org/jira/browse/PROTON-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming resolved PROTON-728.
Resolution: Fixed
transport aborts when delivery ids are out of sequence
[
https://issues.apache.org/jira/browse/PROTON-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming updated PROTON-728:
---
Fix Version/s: 0.8
transport aborts when delivery ids are out of sequence
22 matches
Mail list logo
