diff options
| author | Rajith Muditha Attapattu <rajith@apache.org> | 2011-02-09 21:09:28 +0000 |
|---|---|---|
| committer | Rajith Muditha Attapattu <rajith@apache.org> | 2011-02-09 21:09:28 +0000 |
| commit | 00cb5c0ca8f8267e7c9d6ccbb959887c9a21ebb3 (patch) | |
| tree | 4f206f5ac190bf53fa16cc6869d74951d47f76dd /cpp/bindings/qmf2/python | |
| parent | 3a9b86fa714730260beccacafe77f1e1939e7c33 (diff) | |
| download | qpid-python-00cb5c0ca8f8267e7c9d6ccbb959887c9a21ebb3.tar.gz | |
QPID-2994
The commit made in rev 1068661 will only close and throw an exception if the user tries to invoke an action (Ex sending a message or calling commit) on the transactional session while failover is in progress (i.e session in detached state).
We also need to handle the case where the application is not doing anything during failover. But the application may still be in the middle of an uncommitted transaction. Therefore any session that is marked transactional should not be resumed.
This commit removes tranactional sessions and close them inside the 'resume' method in Connection.java
Any subsequent operation on this session will cause an exception being thrown, saying the session is closed.
However the exception doesn't really contain the reason, other than to say the session is closed.
The Java client in general needs a better error reporting scheme to convey more information to a client application.
That will be handled under a separate JIRA.
For the purpose of this JIRA the session being closed is good enough for the time being.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@1069105 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'cpp/bindings/qmf2/python')
0 files changed, 0 insertions, 0 deletions
