Project: talendesb
Issue TESB-3007: Message IDs for same message are different on sender and receiver side
In a request-response scenario I would expect to talk about to messages I can identify by one ID. A message exchange would lead to two UUIDs in four SAM records (assuming that client and server are configured to use SAM). Still, considering the different event types, it would be easy to identify each part of the communication. Current implementation In SAM, I find four UUIDs: Client / Server MessageID_1 / REQ_OUT --> MessageID_2 / REQ_IN MessageID_3 / RESP_IN <-- MessageID_4 / RESP_OUT Expected behaviour: Client / Server MessageID_1 / REQ_OUT --> MessageID_1 / REQ_IN MessageID_2 / RESP_IN <-- MessageID_2 / RESP_OUT This expectation also is supported by comon definitions of "Message ID" like i.e. in WS-Addressing where Message ID is defined as: "A URI that uniquely identifies this message in time and space." To reproduce: Run a request-response http call and collect all events from sam db,the result is as follows when excute the sql: SELECT id,EI_TIMESTAMP,EI_EVENT_TYPE ,MI_MESSAGE_ID FROM events id | EI_TIMESTAMP | EI_EVENT_TYPE | MI_MESSAGE_ID 325, '2011-09-08 10:14:48', 'REQ_OUT', 'urn:uuid:ebfa86c3-bdac-4d1c-8f0c-3e4f33cc6035' 326, '2011-09-08 10:14:48', 'RESP_IN', 'urn:uuid:ecebc958-b601-407e-8dc0-b45a0b2dd77d' 327, '2011-09-08 10:14:48', 'REQ_IN', 'urn:uuid:360e8cb7-cd6b-4fd6-93a7-39d45a84ac7d' 331, '2011-09-08 10:14:48', 'RESP_OUT', 'urn:uuid:782d99fe-0001-45c9-9b3b-2824ead8d18f' Request from consumer(EI_EVENT_TYPE =REQ_OUT) to provider(EI_EVENT_TYPE =REQ_IN) are same message but these two message id are different. Response from provider(EI_EVENT_TYPE =RESP_OUT) to consume(EI_EVENT_TYPE =RESP_IN) are same message but these two message id are different. Expect result:Request from consumer(EI_EVENT_TYPE =REQ_OUT) to provider(EI_EVENT_TYPE =REQ_IN) are same message and these two message id should be same. Response from provider(EI_EVENT_TYPE =RESP_OUT) to consume(EI_EVENT_TYPE =RESP_IN) are same message and these two message id should be same.
Story points: 2