[
https://issues.apache.org/jira/browse/QPID-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway updated QPID-555:
-----------------------------
This is a special case of a more general bug: exceptions thrown in qpid
background threads on the client are not propagated to the user thread waiting
in some qpid API call. Instead they kill the background thread, and the
foreground thread is hung forever.
We needto ensure that exceptions thrown in background threads will interrupt
the correct user call, where there might be more than one user call in progress
on separate sessions. We can handle this on a per-session basis, sessions are
explicitly not thread safe so users should only have one thread in a given
session at any time.
> c++ client hangs if broker closes connection unexpectedly.
> ----------------------------------------------------------
>
> Key: QPID-555
> URL: https://issues.apache.org/jira/browse/QPID-555
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
> Affects Versions: M2
> Reporter: Alan Conway
> Priority: Critical
>
> Run the broker, start tests/perftest, kill the broker. The client logs the
> socket error but never exits.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
