You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2014/11/13 02:00:40 UTC

[jira] [Commented] (PROTON-741) Proton-J fails to properly negotiate a connection

    [ https://issues.apache.org/jira/browse/PROTON-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14209016#comment-14209016 ] 

clebert suconic commented on PROTON-741:
----------------------------------------

An example replicating it would be nice. It could be something from your network layer.. I don't see such issues on activemq-6

> Proton-J fails to properly negotiate a connection
> -------------------------------------------------
>
>                 Key: PROTON-741
>                 URL: https://issues.apache.org/jira/browse/PROTON-741
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-j
>    Affects Versions: 0.8
>         Environment: Mac OSX, Centos 6.4, RHEL 6.3, Proton-J .8 & trunk. Qpid-CPP trunk
>            Reporter: Jack Gibson
>
> When using the proton-j examples the client does not respond either in time or properly when running normally.  As a result the client, hangs indefinitely on Messenger.send()
> However, when client is placed in a debugger and a break point is placed at Messenger.send().  The client functions as expected and sends/recieves messages.  This only appears to affect the java client as Python and C seem to be fine.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)