ConversationEndedException is not thrown if you reuse a service after you have ended the conversation or the conversation has expired. Instead it starts a new conversation with the same conversation id. This can be seen in the conversationPreInvoke method in the JDKInvocationHandler. Where conversations are re-used even if they are in the ended state.
|Field||Original Value||New Value|
[ I am working on a patch for this issue. Will take into account Simons comments and ensure that the exception is thrown on expired conversations.
With regards to conversations that have have ended through an @EndsConversations method I have noticed that if it uses a System generated Conversation ID it will reuse this ID. Should it not instead create a new one?
|Resolution||Invalid [ 6 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Component/s||SCA Java Runtime [ 12313754 ]|
|Component/s||Java SCA Core Runtime [ 12310647 ]|