[jira] [Updated] (PROTON-671) proton-c: Messenger doesn't provide a way to set the link settlement modes it uses

[ https://issues.apache.org/jira/browse/PROTON-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-671: - Attachment: 13_add_pn_messenger_set_settle_mode_functions_to_header.patch

[jira] [Updated] (PROTON-671) proton-c: Messenger doesn't provide a way to set the link settlement modes it uses

[ https://issues.apache.org/jira/browse/PROTON-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-671: - Attachment: (was: 13_add_pn_messenger_set_settle_mode_functions.patch) proton-c: Messenger

[jira] [Updated] (PROTON-671) proton-c: Messenger doesn't provide a way to set the link settlement modes it uses

[ https://issues.apache.org/jira/browse/PROTON-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-671: - Attachment: 13_add_pn_messenger_set_settle_mode_functions_to_header.patch

[jira] [Created] (PROTON-672) proton-c: Messenger doesn't support setting the transport tracer

Dominic Evans created PROTON-672: Summary: proton-c: Messenger doesn't support setting the transport tracer Key: PROTON-672 URL: https://issues.apache.org/jira/browse/PROTON-672 Project: Qpid Proton

[jira] [Updated] (PROTON-672) proton-c: Messenger doesn't support setting the transport tracer

[ https://issues.apache.org/jira/browse/PROTON-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-672: - Attachment: 14_add_tracer_to_messenger.h.patch 14_add_tracer_to_messenger.c.patch

[jira] [Updated] (PROTON-672) proton-c: Messenger doesn't support setting the transport tracer

[ https://issues.apache.org/jira/browse/PROTON-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-672: - Attachment: 15_get_connection_from_transport.h.patch

[jira] [Updated] (PROTON-673) proton-c: Messenger doesn't provide a way to obtain the remote idle timeout

[ https://issues.apache.org/jira/browse/PROTON-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-673: - Attachment: 19_add_get_remote_idle_timeout_to_messenger.h.patch

[jira] [Created] (PROTON-673) proton-c: Messenger doesn't provide a way to obtain the remote idle timeout

Dominic Evans created PROTON-673: Summary: proton-c: Messenger doesn't provide a way to obtain the remote idle timeout Key: PROTON-673 URL: https://issues.apache.org/jira/browse/PROTON-673 Project

[jira] [Updated] (PROTON-571) proton-c: Messenger outputs errors to stderr rather than setting messenger-error

[ https://issues.apache.org/jira/browse/PROTON-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-571: - Attachment: 21_improve_perror_printing_windows_io.c.patch

[jira] [Commented] (PROTON-571) proton-c: Messenger outputs errors to stderr rather than setting messenger-error

[ https://issues.apache.org/jira/browse/PROTON-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14129889#comment-14129889 ] Dominic Evans commented on PROTON-571: -- Additional patchset to fix Windows socket

[jira] [Created] (PROTON-674) proton-c: Messenger doesn't provide a way of setting the TTL on a subscription

Dominic Evans created PROTON-674: Summary: proton-c: Messenger doesn't provide a way of setting the TTL on a subscription Key: PROTON-674 URL: https://issues.apache.org/jira/browse/PROTON-674 Project

[jira] [Updated] (PROTON-674) proton-c: Messenger doesn't provide a way of setting the TTL on a subscription

[ https://issues.apache.org/jira/browse/PROTON-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-674: - Attachment: 22_add_messenger_subscribe_ttl_method_messenger.h.patch

[jira] [Created] (PROTON-675) proton-c: Messenger doesn't provide a way of setting the SSL peer authentication mode

Dominic Evans created PROTON-675: Summary: proton-c: Messenger doesn't provide a way of setting the SSL peer authentication mode Key: PROTON-675 URL: https://issues.apache.org/jira/browse/PROTON-675

[jira] [Updated] (PROTON-675) proton-c: Messenger doesn't provide a way of setting the SSL peer authentication mode

[ https://issues.apache.org/jira/browse/PROTON-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-675: - Attachment: 23_add_messenger_set_ssl_peer_authentication_mode_method_messenger.h.patch

[jira] [Created] (PROTON-676) proton-c: transport layer SSL failures not propagated back to Messenger in pni_connection_readable

Dominic Evans created PROTON-676: Summary: proton-c: transport layer SSL failures not propagated back to Messenger in pni_connection_readable Key: PROTON-676 URL: https://issues.apache.org/jira/browse/PROTON-676

[jira] [Updated] (PROTON-660) Fix openssl.c build on windows

[ https://issues.apache.org/jira/browse/PROTON-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-660: - Attachment: 25_openssl_fix_for_windows_platform.h.patch

[jira] [Updated] (PROTON-677) proton-c: transport incorrectly detaches all links with closed=true by default

[ https://issues.apache.org/jira/browse/PROTON-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-677: - Attachment: 26_stop_link_detach_closed_if_sub_ttl_transport.c.patch proton-c: transport

[jira] [Created] (PROTON-678) proton-c: (Win 32-bit) pn_post_frame misinterprets variable argument data when ERROR is used

Dominic Evans created PROTON-678: Summary: proton-c: (Win 32-bit) pn_post_frame misinterprets variable argument data when ERROR is used Key: PROTON-678 URL: https://issues.apache.org/jira/browse/PROTON-678

[jira] [Updated] (PROTON-678) proton-c: (Win 32-bit) pn_post_frame misinterprets variable argument data when ERROR is used

[ https://issues.apache.org/jira/browse/PROTON-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-678: - Attachment: 27_32bit_windows_fix_transport.c.patch proton-c: (Win 32-bit) pn_post_frame

[jira] [Updated] (PROTON-680) proton-c: Messenger doesn't provide a way of obtaining link or delivery information

[ https://issues.apache.org/jira/browse/PROTON-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-680: - Attachment: 31_access_messenger_deliveries_messenger.h.patch

[jira] [Updated] (PROTON-571) proton-c: Messenger outputs errors to stderr rather than setting messenger-error

[ https://issues.apache.org/jira/browse/PROTON-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-571: - Attachment: 02_set_pn_error_when_printing_connection_errors.patch proton-c: Messenger outputs

[jira] [Updated] (PROTON-571) proton-c: Messenger outputs errors to stderr rather than setting messenger-error

[ https://issues.apache.org/jira/browse/PROTON-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-571: - Attachment: (was: 02_set_pn_error_when_printing_connection_errors.patch) proton-c: Messenger

[jira] [Commented] (PROTON-681) proton-c: pni_map_ensure infinite loop if `load = map-load_factor`

[ https://issues.apache.org/jira/browse/PROTON-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14129960#comment-14129960 ] Dominic Evans commented on PROTON-681: -- [~gemmellr] yep you're correct, looks like

[jira] [Resolved] (PROTON-681) proton-c: pni_map_ensure infinite loop if `load = map-load_factor`

[ https://issues.apache.org/jira/browse/PROTON-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans resolved PROTON-681. -- Resolution: Duplicate Closing as dupe. proton-c: pni_map_ensure infinite loop if `load = map

[jira] [Closed] (PROTON-611) [proton-c] transport buffer increased to peer's max frame size if initial output_size is not enough

[ https://issues.apache.org/jira/browse/PROTON-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans closed PROTON-611. [proton-c] transport buffer increased to peer's max frame size if initial output_size is not enough

[jira] [Closed] (PROTON-573) proton-c: Messenger appears to have hard-coded address limits of 1024

[ https://issues.apache.org/jira/browse/PROTON-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans closed PROTON-573. proton-c: Messenger appears to have hard-coded address limits of 1024

[jira] [Created] (PROTON-682) proton-c: a call to pn_messenger_stop can get into an infinite loop if the remote connection is severed

Dominic Evans created PROTON-682: Summary: proton-c: a call to pn_messenger_stop can get into an infinite loop if the remote connection is severed Key: PROTON-682 URL: https://issues.apache.org/jira/browse/PROTON

Re: proton javascript binding problem/question

fadams wrote What do you think of the approach that I've taken? My rationale for compiling proton-c to JavaScript and using a thin (ish) binding layer rather than doing a ground-up native JavaScript rewrite was primarily about support. I figured that there was a lot of effort being put into

AUTO: Dominic Evans is on vacation (returning 09/09/2014)

I am out of the office until 09/09/2014. Hi all, I shall be on vacation from Monday 25th August to Monday 8th September.Back in the office on Tuesday 9th September. Best regards, Dom -- Dominic Evans WebSphere MQ - Development IBM Software Group, Hursley Park, UK Note: This is an automated

[jira] [Updated] (PROTON-610) proton-c: messenger doesn't honour an advertised remote idle timeout

[ https://issues.apache.org/jira/browse/PROTON-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-610: - Attachment: 0001-ensure-messenger-honours-remote-idle-timeout.patch Updated patch

[jira] [Commented] (PROTON-610) proton-c: messenger doesn't honour an advertised remote idle timeout

[ https://issues.apache.org/jira/browse/PROTON-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14101161#comment-14101161 ] Dominic Evans commented on PROTON-610: -- [~astitcher] updated patch attached

[jira] [Updated] (PROTON-610) proton-c: messenger doesn't honour an advertised remote idle timeout

[ https://issues.apache.org/jira/browse/PROTON-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-610: - Attachment: (was: 0001-ensure-messenger-honours-remote-idle-timeout.patch) proton-c

[jira] [Commented] (PROTON-610) proton-c: messenger doesn't honour an advertised remote idle timeout

[ https://issues.apache.org/jira/browse/PROTON-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14097597#comment-14097597 ] Dominic Evans commented on PROTON-610: -- [~astitcher] thanks for looking at this issue

[jira] [Updated] (PROTON-576) proton-j: codec support for UTF-8 encoding and decoding appears broken?

[ https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-576: - Attachment: (was: benchmark-src.zip) proton-j: codec support for UTF-8 encoding

[jira] [Updated] (PROTON-576) proton-j: codec support for UTF-8 encoding and decoding appears broken?

[ https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-576: - Attachment: (was: 02_fix_stringtype_encode_decode.patch) proton-j: codec support for UTF-8

[jira] [Updated] (PROTON-576) proton-j: codec support for UTF-8 encoding and decoding appears broken?

[ https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-576: - Attachment: (was: Utf8Samples.txt) proton-j: codec support for UTF-8 encoding and decoding

[jira] [Updated] (PROTON-576) proton-j: codec support for UTF-8 encoding and decoding appears broken?

[ https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-576: - Attachment: (was: benchmark.jar) proton-j: codec support for UTF-8 encoding and decoding

[jira] [Updated] (PROTON-576) proton-j: codec support for UTF-8 encoding and decoding appears broken?

[ https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-576: - Attachment: 02_fix_stringtype_encode_decode.patch Updated patch that also contains

[jira] [Created] (PROTON-618) proton-j: some of the .java source files incorrectly have crlf line endings

Dominic Evans created PROTON-618: Summary: proton-j: some of the .java source files incorrectly have crlf line endings Key: PROTON-618 URL: https://issues.apache.org/jira/browse/PROTON-618 Project

[jira] [Commented] (PROTON-611) [proton-c] transport buffer increased to peer's max frame size if initial output_size is not enough

[ https://issues.apache.org/jira/browse/PROTON-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045839#comment-14045839 ] Dominic Evans commented on PROTON-611: -- [~astitcher] I can confirm it is a problem

[jira] [Created] (PROTON-611) [proton-c] transport buffer increased to peer's max frame size if initial output_size is not enough

Dominic Evans created PROTON-611: Summary: [proton-c] transport buffer increased to peer's max frame size if initial output_size is not enough Key: PROTON-611 URL: https://issues.apache.org/jira/browse/PROTON-611

[jira] [Updated] (PROTON-611) [proton-c] transport buffer increased to peer's max frame size if initial output_size is not enough

[ https://issues.apache.org/jira/browse/PROTON-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-611: - Attachment: 20_fix_bad_malloc_in_transport_produce.patch Patch attached to tidyup the logic

[jira] [Commented] (PROTON-611) [proton-c] transport buffer increased to peer's max frame size if initial output_size is not enough

[ https://issues.apache.org/jira/browse/PROTON-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14037136#comment-14037136 ] Dominic Evans commented on PROTON-611: -- ( similar to PROTON-516 ) [proton-c

[jira] [Created] (PROTON-610) proton-c: messenger doesn't honour an advertised remote idle timeout

Dominic Evans created PROTON-610: Summary: proton-c: messenger doesn't honour an advertised remote idle timeout Key: PROTON-610 URL: https://issues.apache.org/jira/browse/PROTON-610 Project: Qpid

[jira] [Updated] (PROTON-610) proton-c: messenger doesn't honour an advertised remote idle timeout

[ https://issues.apache.org/jira/browse/PROTON-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-610: - Attachment: 0001-ensure-messenger-honours-remote-idle-timeout.patch Attached a proposed patch

[jira] [Commented] (PROTON-516) [proton-c] Dispatcher frame buffer set to peer's max frame size.

[ https://issues.apache.org/jira/browse/PROTON-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14032367#comment-14032367 ] Dominic Evans commented on PROTON-516: -- This is actually a particularly nasty bug

[jira] [Commented] (PROTON-548) Proton-C driver and URL Parsers don't support AF_INET6 (IPv6)

[ https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14025170#comment-14025170 ] Dominic Evans commented on PROTON-548: -- [~tr...@redhat.com] did you seem my comment

[jira] [Commented] (PROTON-573) proton-c: Messenger appears to have hard-coded address limits of 1024

[ https://issues.apache.org/jira/browse/PROTON-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14010980#comment-14010980 ] Dominic Evans commented on PROTON-573: -- Thanks [~rhs] - have replaced our local patch

[jira] [Updated] (PROTON-548) Proton-C driver and URL Parsers don't support AF_INET6 (IPv6)

[ https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-548: - Attachment: 14_fix_ipv6_windows.patch The commit 1583673 supported AF_INET6 on Posix, but didn't

[jira] [Created] (PROTON-578) proton-c: windows/io.c prints Unknown error for all winsock errors

Dominic Evans created PROTON-578: Summary: proton-c: windows/io.c prints Unknown error for all winsock errors Key: PROTON-578 URL: https://issues.apache.org/jira/browse/PROTON-578 Project: Qpid

[jira] [Updated] (PROTON-578) proton-c: windows/io.c prints Unknown error for all winsock errors

[ https://issues.apache.org/jira/browse/PROTON-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-578: - Attachment: 17_fix_winsock_error_code_printing.patch Attached patch will use FormatMessage

[jira] [Commented] (PROTON-576) proton-j: codec support for UTF-8 encoding and decoding appears broken?

[ https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13987543#comment-13987543 ] Dominic Evans commented on PROTON-576: -- Similar results for 4096 samples

[jira] [Updated] (PROTON-576) proton-j: codec support for UTF-8 encoding and decoding appears broken?

[ https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-576: - Attachment: (was: 02_fix_stringtype_encode_decode.patch) proton-j: codec support for UTF-8

[jira] [Updated] (PROTON-576) proton-j: codec support for UTF-8 encoding and decoding appears broken?

[ https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-576: - Attachment: Utf8Samples.txt 02_fix_stringtype_encode_decode.patch Updated patch

[jira] [Updated] (PROTON-571) proton-c: Messenger outputs errors to stderr rather than setting messenger-error

[ https://issues.apache.org/jira/browse/PROTON-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-571: - Attachment: 03_set_pn_error_when_printing_connection_errors.patch Small patch to set messenger

[jira] [Created] (PROTON-572) proton-c: Messenger interprets a '#' topic to actually be a request for a dynamic link

Dominic Evans created PROTON-572: Summary: proton-c: Messenger interprets a '#' topic to actually be a request for a dynamic link Key: PROTON-572 URL: https://issues.apache.org/jira/browse/PROTON-572

[jira] [Updated] (PROTON-572) proton-c: Messenger interprets a '#' topic to actually be a request for a dynamic link

[ https://issues.apache.org/jira/browse/PROTON-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-572: - Attachment: 05_remove_messenger_request_dynamic_via_hash.patch Patch to remove dynamic link

[jira] [Created] (PROTON-574) proton-c: Messenger doesn't indicate when connection is aborted for a SASL negotation failure

Dominic Evans created PROTON-574: Summary: proton-c: Messenger doesn't indicate when connection is aborted for a SASL negotation failure Key: PROTON-574 URL: https://issues.apache.org/jira/browse/PROTON-574

[jira] [Updated] (PROTON-574) proton-c: Messenger doesn't indicate when connection is aborted for a SASL negotation failure

[ https://issues.apache.org/jira/browse/PROTON-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-574: - Attachment: 08_return_sasl_auth_errors_transport.h.patch

[jira] [Created] (PROTON-575) proton-j: LoggingProtocolTracer used by FrameWriter cannot be overridden

Dominic Evans created PROTON-575: Summary: proton-j: LoggingProtocolTracer used by FrameWriter cannot be overridden Key: PROTON-575 URL: https://issues.apache.org/jira/browse/PROTON-575 Project: Qpid

[jira] [Updated] (PROTON-575) proton-j: LoggingProtocolTracer used by FrameWriter cannot be overridden

[ https://issues.apache.org/jira/browse/PROTON-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-575: - Attachment: 01_allow_access_to_protocolTracer_in_TransportImpl.patch Currently, we're just using

[jira] [Created] (PROTON-576) proton-j: codec support for UTF-8 encoding and decoding appears broken?

Dominic Evans created PROTON-576: Summary: proton-j: codec support for UTF-8 encoding and decoding appears broken? Key: PROTON-576 URL: https://issues.apache.org/jira/browse/PROTON-576 Project: Qpid

[jira] [Updated] (PROTON-576) proton-j: codec support for UTF-8 encoding and decoding appears broken?

[ https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-576: - Attachment: 02_fix_stringtype_encode_decode.patch I'm not sure why the code was originally

[jira] [Comment Edited] (PROTON-576) proton-j: codec support for UTF-8 encoding and decoding appears broken?

[ https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13986753#comment-13986753 ] Dominic Evans edited comment on PROTON-576 at 5/1/14 5:30 PM

[jira] [Commented] (PROTON-576) proton-j: codec support for UTF-8 encoding and decoding appears broken?

[ https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13986890#comment-13986890 ] Dominic Evans commented on PROTON-576: -- {code:title=results|borderStyle=solid

[jira] [Updated] (PROTON-576) proton-j: codec support for UTF-8 encoding and decoding appears broken?

[ https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Evans updated PROTON-576: - Attachment: benchmark-src.zip benchmark.jar Benchmark jar (and src) as requested

Messenger: pn_delivery leaking pn_disposition memory?

In one of our automated client stress tests, we've noticed that we seem to be leaking memory. We were previously seeing this on qpid-proton 0.6 and I've retested on 0.7 RC3 and it is still occurring ==16195== 45,326,848 bytes in 25,294 blocks are possibly lost in loss record 1,865 of 1,867

Re: Using the messenger API to connect to a server without sending or subscribing

undefined

Re: Using the messenger API to connect to a server without sending or subscribing

undefined

[jira] [Created] (PROTON-492) proton-c: Messenger should allow custom link name to be specificied

Dominic Evans created PROTON-492: Summary: proton-c: Messenger should allow custom link name to be specificied Key: PROTON-492 URL: https://issues.apache.org/jira/browse/PROTON-492 Project: Qpid

<    1   2