Could you post a log file at debug level and
put a tcp monitor [1] to check the http request sent
by servicemix-http ?

[1] 
http://ws.apache.org/axis/java/user-guide.html#AppendixUsingTheAxisTCPMonitorTcpmon

On 10/31/06, Raghul Nandagopal <[EMAIL PROTECTED]> wrote:

Hi,

Here is my sm.xml configuration deployed in JBoss

<sm:activationSpec>
                <sm:component>
                    <http:component>
                        <http:endpoints>
                            <http:endpoint
                                service="sterling:MySoapClient"
                                endpoint="MySoapClient"
                                targetService="form:SoapProcessor"
                                role="consumer"
                                soap="true"

locationURI="http://localhost:8192/SoapService/";

defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; />
                            <http:endpoint
                                service="sterling:MySoapServer"
                                endpoint="MySoapServer"
                                role="provider"

locationURI="http://localhost:8192/SoapService/"; />
                        </http:endpoints>
                    </http:component>
                </sm:component>
            </sm:activationSpec>

            <sm:activationSpec componentName="SoapProcessor"
service="form:SoapProcessor" destinationService="sterling:MySoapServer">
                <sm:component><bean class="MyProcessor" /></sm:component>
            </sm:activationSpec>

---------------------

Here is the error message - what's going wrong - help :(

00:09:11,984 ERROR [HttpSpringComponent] Error processing exchange InOnly[
  id: ID:ThunderBird-1519-1162319929984-19:0
  status: Active
  role: provider
  service: MySoapServer
  endpoint: MySoapServer
  in: <?xml version="1.0" encoding="UTF-8"?>
]
java.lang.Exception: Invalid status response: 400
        at
org.apache.servicemix.http.processors.ProviderProcessor.process(ProviderProcessor.java:175)
        at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:410)
        at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:43)
        at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:624)
        at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:169)
        at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:177)
        at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:227)
        at
org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java:291)
        at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
        at java.lang.Thread.run(Thread.java:595)
00:09:11,984 INFO  [STDOUT] Completed Processing
--
View this message in context: 
http://www.nabble.com/HTTP-EndPoint---response-getting-truncated.-tf2547553.html#a7099823
Sent from the ServiceMix - User mailing list archive at Nabble.com.




--
Cheers,
Guillaume Nodet

Reply via email to