We have several junit tests that sends very big messages over
servicemix-http.
But maybe there are still cases where a problem happen.
If you could write a reproducible test case / configuration, it would help a
lot.

Cheers,
Guillaume Nodet

On 7/26/06, Sufyan Arif <[EMAIL PROTECTED]> wrote:


Hi,

I am using the latest version of servicemix compiled from subversion.

I am using the http component to act as a consumer to send documents
into the nmr. The message is sent in using commons-http client.  The NMR
routes the message(using EIP) to a http provider component which calls
out to the webservice.

I've placed a trap on the network card to sniff traffic as it comes back
from the web service. In addition I have placed tcpmon between the http
client and the servicmix-http consumer to see the result as it comes
back from servicemix.

The response as sniffed on the network card is complete and well formed
however the response as viewed in the tcpmon tool has been chopped and
is no longer well formed.  For e.g. one of the elements in the response
comes back as

<mortgageamountinterestonlypart>0</mortgag

My http components are configured as follows

<sm:activationSpec>
   <sm:component>
   <http:component>
      <http:endpoints>

         <http:endpoint service="my:mortgageSearchSingleApplicant"
                        endpoint="mortgageSearchSingleApplicant"
                        role="provider"
                        soap="true"
                        soapVersion="1.1"
                        soapAction="http://www.blah.blah";
                        locationURI="http://www.somelocation"/>

         <http:endpoint service="my:httpMessageConsumer"
                        endpoint="endpoint"
                        targetService="my:router"
                        role="consumer"
                        locationURI="http://localhost:8912/Service/";

defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
                        defaultOperation="initiate"
                        soap="false" />

         </http:endpoints>
   </http:component>
   </sm:component>
</sm:activationSpec>


Does anyone have a clue why this may be happening? Or where can I look
into to fix this problem. Any help would be most appreciated as I have
been tearing my hair out with this one.


Regards,


Sufyan.

This transmission is confidential and intended solely for the person or
organisation to whom it is addressed. It may contain privileged and
confidential information. If you are not the intended recipient, you should
not copy, distribute or take any action in reliance on it. If you have
received this transmission in error, please notify the sender immediately.
Any opinions or advice contained in this e-mail are those of the individual
sender except where they are stated to be the views of RDF Group plc. All
messages passing through this gateway are virus scanned.


Reply via email to