I have servicemix-camel 3.2.2 snapshot in my ServiceMix 3.2.1 instance.I have
following message flow for a use case:
App 1 --> Http-SU(consumer) --> EIP-SU --
(in-only)->JMSProvider-SU(topic) ----> JMSConsumer-SU -->Camel-SU
---->Http-SU(Provider) --> App 2
|
|---(mep=in-out)--> Bean-SU
That is:
1) Http-SU(consumer) gets message from application and sends it to
EIP-SU
2) Here EIP is Wire-tap pattern. In wiretap JMSProvider-SU is a tap and
Bean-Su is target (see above flow)
3) JMSProvider sends message to topic say "topic1".
4)JMSConsumer SU will consume the message from "topic1".
5)CamelSU routes the message from JMSConsumer to Http-SU(provider).
Now here I am facing problem with communication between Camel-SU and
Http-SU(provider).
This is my Camel configuration for routing the message from JMSConsumer to
Http-SU(provider) :
<route>
<from
uri="jbi:service:http://servicemix.in2m.com/operations/updateprofile/JMSConsumerService"/>
<to
uri="jbi:service:http://servicemix.in2m.com/operations/updateprofile/DirectorService?mep=in-out"/>
</route>
This is Http-Su(Provider):
<http:endpoint service="hello:DirectorService"
endpoint="DirectorEndpoint"
role="provider"
locationURI="http://localhost:8080/webapp/control/MyService";
defaultMep="http://www.w3.org/2004/08/wsdl/in-out"/>
Since I configured ServiceMix with Servicemix-Camel 3.2.2 snapshot it is
giving error. The error says that my servicemix is considering the
Http-Su(Provider) as IN-ONLY instead of IN_OUT even if I specify it to be
IN_OUT.
But this same configuration works with Servicemix-Camel-3.2.1 version. Is
this a problem with using Servicemix-Camel3.2.2 snapshot with ServiceMix
3.2.1 or a bug in component itself ?
Following is what I get at smx logs:
DEBUG - SedaQueue -
[EMAIL PROTECTED] dequeued
exchange: InOnly[
id: ID:192.168.2.53-11a96c0f7c3-10:4
status: Active
role: provider
service:
{http://servicemix.in2m.com/operations/updateprofile}DirectorService
endpoint: DirectorEndpoint
in: <?xml version="1.0" encoding="UTF-8"?><request
xmlns="http://www.finicity.com";>
<updateUserProfile>
<lastName>reddy</lastName>
<firstName>sandeep</firstName>
<userName>sandeep37</userName>
<emailAddress>[EMAIL PROTECTED]</emailAddress>
</updateUserProfile>
</request>
]
DEBUG - HttpComponent - Received exchange: status: Active, role: provider
DEBUG - HttpComponent - Retrieved correlation id: null
DEBUG - DefaultHttpParams - Set parameter http.method.retry-handler =
[EMAIL PROTECTED]
DEBUG - MultiThreadedHttpConnectionManager -
HttpConnectionManager.getConnection: config =
HostConfiguration[host=http://localhost:8080], timeout = 0
DEBUG - MultiThreadedHttpConnectionManager - Getting free connection,
hostConfig=HostConfiguration[host=http://localhost:8080]
DEBUG - HttpConnection - Connection is stale, closing...
DEBUG - HttpConnection - Open connection to localhost:8080
DEBUG - HttpMethodBase - Adding Host request header
DEBUG - EntityEnclosingMethod - Request body sent
DEBUG - JettyContextManager - Dispatching job:
[EMAIL PROTECTED],io=1,w=true,b=false|false]
DEBUG - DeliveryChannelImpl - Send ID:192.168.2.53-11a96c0f7c3-10:4 in
DeliveryChannel{servicemix-http}
DEBUG - SedaFlow - Called Flow send
DEBUG - HttpMethodBase - Resorting to protocol version default close
connection policy
DEBUG - HttpMethodBase - Should NOT close connection, using HTTP/1.1
DEBUG - HttpConnection - Releasing connection back to connection manager.
DEBUG - MultiThreadedHttpConnectionManager - Freeing connection,
hostConfig=HostConfiguration[host=http://localhost:8080]
DEBUG - IdleConnectionHandler - Adding connection at: 1213710716032
DEBUG - MultiThreadedHttpConnectionManager - Notifying no-one, there are no
waiting threads
DEBUG - SedaQueue -
[EMAIL PROTECTED] dequeued
exchange: InOnly[
id: ID:192.168.2.53-11a96c0f7c3-10:4
status: Done
role: consumer
service:
{http://servicemix.in2m.com/operations/updateprofile}DirectorService
endpoint: DirectorEndpoint
in: <?xml version="1.0" encoding="UTF-8"?><request
xmlns="http://www.finicity.com";>
<updateUserProfile>
<lastName>reddy</lastName>
<firstName>sandeep</firstName>
<userName>sandeep37</userName>
<emailAddress>[EMAIL PROTECTED]</emailAddress>
</updateUserProfile>
</request>
]
DEBUG - DeliveryChannelImpl - Notifying exchange
ID:192.168.2.53-11a96c0f7c3-10:4(76ae8e) in
DeliveryChannel{servicemix-camel} from processInboundSynchronousExchange
DEBUG - DeliveryChannelImpl - Notified:
ID:192.168.2.53-11a96c0f7c3-10:4(76ae8e) in
DeliveryChannel{servicemix-camel} from sendSync
DEBUG - DeliveryChannelImpl - Send ID:192.168.2.53-11a96c0f7c3-9:2 in
DeliveryChannel{servicemix-camel}
DEBUG - SedaFlow - Called Flow send
DEBUG - SedaQueue -
[EMAIL PROTECTED] dequeued
exchange: InOnly[
id: ID:192.168.2.53-11a96c0f7c3-9:2
status: Done
role: consumer
service:
{http://servicemix.in2m.com/operations/updateprofile}JMSConsumerService
endpoint: camel192-168-2-53-11a96c0f7c3-25-0
in: <?xml version="1.0" encoding="UTF-8"?><request
xmlns="http://www.finicity.com";>
<updateUserProfile>
<lastName>reddy</lastName>
<firstName>sandeep</firstName>
<userName>sandeep37</userName>
<emailAddress>[EMAIL PROTECTED]</emailAddress>
</updateUserProfile>
</request>
-Pratibha
--
View this message in context:
http://www.nabble.com/Servicemix-Camel-3.2.2--does-not-send-in-out-message-to-http-provider-tp17904724p17904724.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
