[jira] [Created] (PROTON-893) Calling the session.close() on non-active session causes client seqfault
Petr Matousek created PROTON-893: Summary: Calling the session.close() on non-active session causes client seqfault Key: PROTON-893 URL: https://issues.apache.org/jira/browse/PROTON-893 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: 0.9.1 Environment: packages: qpid-proton-c-0.9-3 qpid-proton-c-devel-0.9-3 python-qpid-proton-0.9-3 Reporter: Petr Matousek Priority: Minor Calling the session.close() on non-active session causes client seqfault (see the attached reproducer session_close_con.py). Moreover calling connection.session().close() causes client seqfault even if the session shall be in active state (see the attached reproducer session_close_ssn.py). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-893) Calling the session.close() on non-active session causes client seqfault
[ https://issues.apache.org/jira/browse/PROTON-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Matousek updated PROTON-893: - Attachment: session_close_con.py > Calling the session.close() on non-active session causes client seqfault > > > Key: PROTON-893 > URL: https://issues.apache.org/jira/browse/PROTON-893 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.9.1 > Environment: packages: > qpid-proton-c-0.9-3 > qpid-proton-c-devel-0.9-3 > python-qpid-proton-0.9-3 >Reporter: Petr Matousek >Priority: Minor > Attachments: session_close_con.py > > > Calling the session.close() on non-active session causes client seqfault (see > the attached reproducer session_close_con.py). > Moreover calling connection.session().close() causes client seqfault even if > the session shall be in active state (see the attached reproducer > session_close_ssn.py). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-893) Calling the session.close() on non-active session causes client seqfault
[ https://issues.apache.org/jira/browse/PROTON-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Matousek updated PROTON-893: - Attachment: stacktrace.txt > Calling the session.close() on non-active session causes client seqfault > > > Key: PROTON-893 > URL: https://issues.apache.org/jira/browse/PROTON-893 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.9.1 > Environment: packages: > qpid-proton-c-0.9-3 > qpid-proton-c-devel-0.9-3 > python-qpid-proton-0.9-3 >Reporter: Petr Matousek >Priority: Minor > Attachments: session_close_con.py, session_close_ssn.py, > stacktrace.txt > > > Calling the session.close() on non-active session causes client seqfault (see > the attached reproducer session_close_con.py). > Moreover calling connection.session().close() causes client seqfault even if > the session shall be in active state (see the attached reproducer > session_close_ssn.py). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-893) Calling the session.close() on non-active session causes client seqfault
[ https://issues.apache.org/jira/browse/PROTON-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Matousek updated PROTON-893: - Attachment: session_close_ssn.py > Calling the session.close() on non-active session causes client seqfault > > > Key: PROTON-893 > URL: https://issues.apache.org/jira/browse/PROTON-893 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.9.1 > Environment: packages: > qpid-proton-c-0.9-3 > qpid-proton-c-devel-0.9-3 > python-qpid-proton-0.9-3 >Reporter: Petr Matousek >Priority: Minor > Attachments: session_close_con.py, session_close_ssn.py, > stacktrace.txt > > > Calling the session.close() on non-active session causes client seqfault (see > the attached reproducer session_close_con.py). > Moreover calling connection.session().close() causes client seqfault even if > the session shall be in active state (see the attached reproducer > session_close_ssn.py). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-893) Calling the session.close() on non-active session causes client seqfault
[ https://issues.apache.org/jira/browse/PROTON-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Matousek updated PROTON-893: - Component/s: proton-c > Calling the session.close() on non-active session causes client seqfault > > > Key: PROTON-893 > URL: https://issues.apache.org/jira/browse/PROTON-893 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c, python-binding >Affects Versions: 0.9.1 > Environment: packages: > qpid-proton-c-0.9-3 > qpid-proton-c-devel-0.9-3 > python-qpid-proton-0.9-3 >Reporter: Petr Matousek >Priority: Minor > Attachments: session_close_con.py, session_close_ssn.py, > stacktrace.txt > > > Calling the session.close() on non-active session causes client seqfault (see > the attached reproducer session_close_con.py). > Moreover calling connection.session().close() causes client seqfault even if > the session shall be in active state (see the attached reproducer > session_close_ssn.py). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-893) Calling the session.close() on non-active session causes client seqfault
[ https://issues.apache.org/jira/browse/PROTON-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Matousek updated PROTON-893: - Description: Calling the session.close() on non-active session causes client segfault (see the attached reproducer session_close_con.py). Moreover calling connection.session().close() causes client seqfault even if the session shall be in active state (see the attached reproducer session_close_ssn.py). was: Calling the session.close() on non-active session causes client seqfault (see the attached reproducer session_close_con.py). Moreover calling connection.session().close() causes client seqfault even if the session shall be in active state (see the attached reproducer session_close_ssn.py). > Calling the session.close() on non-active session causes client seqfault > > > Key: PROTON-893 > URL: https://issues.apache.org/jira/browse/PROTON-893 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c, python-binding >Affects Versions: 0.9.1 > Environment: packages: > qpid-proton-c-0.9-3 > qpid-proton-c-devel-0.9-3 > python-qpid-proton-0.9-3 >Reporter: Petr Matousek >Priority: Minor > Attachments: session_close_con.py, session_close_ssn.py, > stacktrace.txt > > > Calling the session.close() on non-active session causes client segfault (see > the attached reproducer session_close_con.py). > Moreover calling connection.session().close() causes client seqfault even if > the session shall be in active state (see the attached reproducer > session_close_ssn.py). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (PROTON-912) Improve SSL error reporting
Petr Matousek created PROTON-912: Summary: Improve SSL error reporting Key: PROTON-912 URL: https://issues.apache.org/jira/browse/PROTON-912 Project: Qpid Proton Issue Type: Improvement Components: python-binding Affects Versions: 0.9.1 Reporter: Petr Matousek Priority: Minor I've spent some time with configuring python client to talk with SSL ActiveMQ broker requesting client authentication. Majority of client configuration problems ends with just the following exception: "proton.SSLException: SSL failure.", that makes quite difficult to identify the actual problem. It would be great if the error reporting can be improved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (PROTON-913) Calling allow_unsecured_client() on SSLDomain.MODE_CLIENT causes client segfault
Petr Matousek created PROTON-913: Summary: Calling allow_unsecured_client() on SSLDomain.MODE_CLIENT causes client segfault Key: PROTON-913 URL: https://issues.apache.org/jira/browse/PROTON-913 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: 0.9.1 Environment: packages: qpid-proton-c-0.9-3 qpid-proton-c-devel-0.9-3 python-qpid-proton-0.9-3 Reporter: Petr Matousek Priority: Minor Calling allow_unsecured_client() on SSLDomain.CLIENT_MODE object causes client segmentation fault. It is not intended to call this method on client instance, but obviously the client segfault should not appear. Please see the attached reproducer ssl_client_allow_unsecured_client.py for details. Attaching also client traces. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-913) Calling allow_unsecured_client() on SSLDomain.MODE_CLIENT causes client segfault
[ https://issues.apache.org/jira/browse/PROTON-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Matousek updated PROTON-913: - Attachment: ssl_client_allow_unsecured_client.py reproducer > Calling allow_unsecured_client() on SSLDomain.MODE_CLIENT causes client > segfault > > > Key: PROTON-913 > URL: https://issues.apache.org/jira/browse/PROTON-913 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.9.1 > Environment: packages: > qpid-proton-c-0.9-3 > qpid-proton-c-devel-0.9-3 > python-qpid-proton-0.9-3 >Reporter: Petr Matousek >Priority: Minor > Attachments: ssl_client_allow_unsecured_client.py > > > Calling allow_unsecured_client() on SSLDomain.CLIENT_MODE object causes > client segmentation fault. It is not intended to call this method on client > instance, but obviously the client segfault should not appear. > Please see the attached reproducer ssl_client_allow_unsecured_client.py for > details. Attaching also client traces. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PROTON-913) Calling allow_unsecured_client() on SSLDomain.MODE_CLIENT causes client segfault
[ https://issues.apache.org/jira/browse/PROTON-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petr Matousek updated PROTON-913: - Attachment: stacktrace.txt client stack trace > Calling allow_unsecured_client() on SSLDomain.MODE_CLIENT causes client > segfault > > > Key: PROTON-913 > URL: https://issues.apache.org/jira/browse/PROTON-913 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.9.1 > Environment: packages: > qpid-proton-c-0.9-3 > qpid-proton-c-devel-0.9-3 > python-qpid-proton-0.9-3 >Reporter: Petr Matousek >Priority: Minor > Attachments: ssl_client_allow_unsecured_client.py, stacktrace.txt > > > Calling allow_unsecured_client() on SSLDomain.CLIENT_MODE object causes > client segmentation fault. It is not intended to call this method on client > instance, but obviously the client segfault should not appear. > Please see the attached reproducer ssl_client_allow_unsecured_client.py for > details. Attaching also client traces. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
