[
https://issues.apache.org/jira/browse/QPID-5490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875035#comment-13875035
]
Dale Stansberry commented on QPID-5490:
---------------------------------------
Just discovered that my test case/analysis flawed - this segfault is being
caused by a call to Session.createReceiver() when the Session instance is
essentially uninitialized (created using default constructor). If the session
was properly initialized from a live Connection object (not using reconnect
option), and then the underlying connection is lost, calling
Session.createReceiver throws an exception as expected. Should I close this
issue and open a new one?
> Connection.createSession segfaults if not connected
> ---------------------------------------------------
>
> Key: QPID-5490
> URL: https://issues.apache.org/jira/browse/QPID-5490
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
> Affects Versions: 0.24
> Environment: Fedora 20, gcc 4.8.2, C++ Messaging API
> Reporter: Dale Stansberry
> Priority: Minor
>
> If createSession() is called on a Connection instance that is not currently
> connected, a segfault occurs. I would expect an exception to be thrown
> instead. Connection instance was created using default constructor, no Qpid
> broker is running/accessible. This is repeatable in my dev environment.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
