Transport Headers are not accessible at client

Question

Hi,
We are using OSB 11g for sending message to external client.
we are setting Headers "JMSType" in set Transport Header. but Client is not able to recieve the JMSType header at there side.
we have read many forums for the same and turned on
Pass all Headers through Pipeline
Get All Headers
then I put one publish action and keep my "Set Transport Header" inside that. still client is not able to find the same
In out outbound request we can see the header as following.
$outbound = <con:endpoint name="BusinessService$Notification$BusinessService$external$BUSINESSSERVICE:con="http://www.bea.com/wli/sb/context">
<con:service/>
<con:transport>
<con:uri></con:uri>
<con:mode>request</con:mode>
<con:qualityOfService>exactly-once</con:qualityOfService>
<con:request xsi:type="http:HttpRequestMetaData" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<tran:headers xsi:type="http:HttpRequestHeaders" xmlns:tran="http://www.bea.com/wli/sb/transports">
<tran:user-header name="JMSType" value="XXXXXXX">
<http:Content-Type>text/plain; charset=utf-8</http:Content-Type>
</tran:headers>
<tran:encoding xmlns:tran="http://www.bea.com/wli/sb/transports">utf-8</tran:encoding>
</con:request>
<con:response xsi:type="http:HttpResponseMetaData" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<tran:headers xsi:type="http:HttpResponseHeaders" xmlns:tran="http://www.bea.com/wli/sb/transports">
<tran:user-header name="content-description" value="SOAP"/>
<tran:user-header name="content-disposition" value="attachment;filename=&quot;[email protected]&quot;"/>
<tran:user-header name="content-id" value="&lt;[email protected]>"/>
<http:Cache-Control>proxy-revalidate</http:Cache-Control>
<http:Connection>Keep-Alive</http:Connection>
<http:Content-Length>112</http:Content-Length>
<http:Content-Type>text/xml; charset=utf-8</http:Content-Type>
<http:Date>Sun, 02 Sep 2012 04:06:43 GMT</http:Date>
<http:Server>XXXXXXXXXerver>
<http:Set-Cookie><![CDATA[<cookie-values xmlns="http://www.bea.com/wli/sb/transports/http">
  <value>JSESSIONID=m2RvGs2_Lvk_AZgyVJIv_e2-vSiFOQFi_mIA_SAPULGAKriCp_hbBD8uC0e8pEXt; Version=1; Path=/</value>
  <value>saplb_*=(spspiq_PIQ_00)6487650; Version=1; Path=/</value>
</cookie-values>]]></http:Set-Cookie>
</tran:headers>
<tran:response-code xmlns:tran="http://www.bea.com/wli/sb/transports">0</tran:response-code>
<tran:response-message xmlns:tran="http://www.bea.com/wli/sb/transports">OK</tran:response-message>
<tran:encoding xmlns:tran="http://www.bea.com/wli/sb/transports">utf-8</tran:encoding>
<http:http-response-code>200</http:http-response-code>
</con:response>
</con:transport>
<con:security>
<con:doOutboundWss>false</con:doOutboundWss>
</con:security>
</con:endpoint>

Answer 1

It seems like you are setting JMSType header while calling an HTTP business service. What I see is that a header called JMSType is attached as a HTTP transport custom header and the target system should be able to fetch the JMSType as HTTP header. They should try to see on their side what exact message they are receiving.
Also, why are you setting JMSType header when calling an HTTP service?