[jira] [Created] (PROTON-1310) proton-j reactor transport head never closes
Daniel Evans created PROTON-1310: Summary: proton-j reactor transport head never closes Key: PROTON-1310 URL: https://issues.apache.org/jira/browse/PROTON-1310 Project: Qpid Proton Issue Type: Bug Components: proton-j Affects Versions: 0.15.0 Reporter: Daniel Evans With a server (listener) test class and a client test class, I'm able to disconnect the client such that occasionally on the server the TRANSPORT_ERROR and TRANSPORT_TAIL_CLOSED events fire but TRANSPORT_HEAD_CLOSED and TRANSPORT_CLOSED do not. A timer selectable running to keep the reactor alive then causes repeated TRANSPORT events that all report -1 pending and isClosed == true. This goes on forever. In the good case, the global event logger sequence is: TRANSPORT_ERROR TRANSPORT_TAIL_CLOSED SELECTABLE_UPDATED REACTOR_QUIESCED TRANSPORT_HEAD_CLOSED TRANSPORT_CLOSED SELECTABLE_FINAL CONNECTION_UNBOUND TRANSPORT And in the bad case: TRANSPORT_ERROR TRANSPORT_TAIL_CLOSED SELECTABLE_UPDATED REACTOR_QUIESCED SELECTABLE_FINAL REACTOR_QUIESCED SELECTABLE_UPDATED TRANSPORT REACTOR_QUIESCED SELECTABLE_UPDATED TRANSPORT ... etc. Digging around with the debugger I verified that no selectables were writable in the IOHandler and TransportImpl's pop() was never being called when the output pending was -1. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1295) [proton-j] some unencrypted private keys won't load
[ https://issues.apache.org/jira/browse/PROTON-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15459371#comment-15459371 ] Daniel Evans commented on PROTON-1295: -- Thanks for jumping on it. > [proton-j] some unencrypted private keys won't load > --- > > Key: PROTON-1295 > URL: https://issues.apache.org/jira/browse/PROTON-1295 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Affects Versions: 0.15.0 >Reporter: Daniel Evans > > In SslEngineFacadeFactory, line 469, > privateKey = (PrivateKey) getPrivateKeyMethod.invoke(pemObject); > I think should read > privateKey = (PrivateKey) getPrivateKeyMethod.invoke(keyConverter, pemObject); > At the moment it throws an exception on method evocation since the method > doesn't exist in pemObject. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1295) Proton-j unencrypted private key won't load
Daniel Evans created PROTON-1295: Summary: Proton-j unencrypted private key won't load Key: PROTON-1295 URL: https://issues.apache.org/jira/browse/PROTON-1295 Project: Qpid Proton Issue Type: Bug Components: proton-j Affects Versions: 0.15.0 Reporter: Daniel Evans In SslEngineFacadeFactory, line 469, privateKey = (PrivateKey) getPrivateKeyMethod.invoke(pemObject); I think should read privateKey = (PrivateKey) getPrivateKeyMethod.invoke(keyConverter, pemObject); At the moment it throws an exception on method evocation since the method doesn't exist in pemObject. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5303) AMQP 1.0 -> 0-10 doesn't map 'exchange' delivery property
Daniel Evans created QPID-5303: -- Summary: AMQP 1.0 -> 0-10 doesn't map 'exchange' delivery property Key: QPID-5303 URL: https://issues.apache.org/jira/browse/QPID-5303 Project: Qpid Issue Type: Bug Reporter: Daniel Evans When a publisher publishes an AMQP 1.0 message to an exchange (i.e. amqp://0.0.0.0/someExchange), a regular AMQP 0-10 subscriber will be delivered a message that doesn't include the exchange delivery property. Since the translation here seems to be intending to present the "normal" users of the broker with the same model regardless of whether the message source was 1.0, I'm assuming it would be more correct to have that delivery property set. We use it in some of our AMQP applications. I poked around and part of the problem seems to be that the name of the exchange resolved from the 1.0 address has long been discarded by the time the broker is delivering the message from the queue. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
