Project: talendesb
Issue TESB-6277: Talend route based on cCXF component with enabled SAM feature do not fill (or fill incorrectly) some fields in SAM events
In our system tests we developed route (from usual cxf consumer to usual cxf provider) in studio based on cCXF components. Both these components have feature "Service Activity Monitoring" enabled. After successful request-response call database stores four (as expected) messages produced by route: SamEvent [id=119, timestamp=2012-06-21 17:36:26.68, eventType=REQ_IN, processId=2452, ip=127.0.1.1, hostName=apaltoNB, customId=null, principal=null, messageId=null, flowId=urn:uuid:5a9b1686-d1ec-4 535-9983-a2bfa9a2a71e, portType={http://services.test.esb.talend.org/Standard}StandardTestService, operationName={http://services.test.esb.talend.org/Standard}doRequestResponse, transportType=http: //schemas.xmlsoap.org/soap/http, contentCut=false, messageContent=urt0010] SamEvent [id=121, timestamp=2012-06-21 17:36:26.702, eventType=REQ_OUT, processId=2452, ip=127.0.1.1, hostName=apaltoNB, customId=null, principal=null, messageId=urn:uuid:8a17b04a-9be5-43ae-b5e6-31 84cdd16cbc, flowId=urn:uuid:5a9b1686-d1ec-4535-9983-a2bfa9a2a71e, portType={http://services.test.esb.talend.org/Standard}StandardTestService, operationName={http://services.test.esb.talend.org/Stan dard}doRequestResponse, transportType=http://schemas.xmlsoap.org/soap/http, contentCut=false, messageContent=urn:uuid:5a9b1686-d1ec-4535-9983-a2bfa9a2a71ehttp://http://services.test.esb.talend. org/Standard/StandardTestServiceProvider/doRequestResponseurn:uuid:8a17b04a-9be5-43ae-b5e6-3184cdd16cbchttp://provider:9088/services/tesb.test.participants.osgi.ufp.provider/soap/StandardTestServiceProvider/http://www.w3.org/2005/08/addressing/anonymous

urt0010] SamEvent [id=123, timestamp=2012-06-21 17:36:26.823, eventType=RESP_IN, processId=2452, ip=127.0.1.1, hostName=apaltoNB, customId=null, principal=null, messageId=null, flowId=urn:uuid:5a9b1686-d1ec -4535-9983-a2bfa9a2a71e, portType={http://services.test.esb.talend.org/Standard}StandardTestService, operationName={http://services.test.esb.talend.org/Standard}doRequestResponse, transportType=htt p://schemas.xmlsoap.org/soap/http, contentCut=false, messageContent=URT0010] SamEvent [id=125, timestamp=2012-06-21 17:36:26.845, eventType=RESP_OUT, processId=2452, ip=127.0.1.1, hostName=apaltoNB, customId=null, principal=null, messageId=null, flowId=urn:uuid:5a9b1686-d1e c-4535-9983-a2bfa9a2a71e, portType={http://services.test.esb.talend.org/Standard}StandardTestService, operationName={http://services.test.esb.talend.org/Standard}doRequestResponse, transportType=http://schemas.xmlsoap.org/soap/http, contentCut=false, messageContent=urn:uuid:5a9b1686-d1ec-4535-9983-a2bfa9a2a71eURT0010] There are some problems here: 1) field message_id always filled only for REQ_OUT event (message out from route). 2) field message_content is not the same for all events. Somewhere it contents much more information, somewhere -- much less. Similar behaviour (both problems) are reproduced for oneway operations. Situation became much more interesting, when we are using sam enabled consumer with usual provider. In that case only one message doesn't(!!) contain message_id (some of RESP_IN message, it impossible to find out from where exactly this message by info from events). Other events -- contains the same message id. And the same message has shortened (as in previous example) message content. Other have the same message content which include a lot of different information in header of envelop (flow id, etc..). The difference between two these experiments -- only enabling of sam feature on consumer's side. See exported route in attachments. UPD: I prepared maven project with simple example. See steps to Reproduce.
Story points: 3