I found only the following thing missing in the logs of 3.3.1 which was
present in 3.2.2  after  my responsegenerator service send a done message
but I am unable to find why is it so. No where in my ResponseGeneartor bean
I have set a status as error.

ERROR - DeadLetterChannel              - Failed delivery for exchangeId:
ID-test-smx/48463-1268370611187/0-0. Handled by the failure processor:
Pipeline[setBody(<response><status>4000</status><message>Connection
Error</message></response>),
sendTo(Endpoint[service:http://servicemix.in2m.com/operations/changepassword/ResponseGeneratorService?mep=in-out])]
DEBUG - DeliveryChannelImpl            - Send ID:127.0.1.1-12750c79e7f-4:0
in DeliveryChannel{servicemix-camel}
DEBUG - SecuredBroker                  - send exchange with secure broker
DEBUG - SedaFlow                       - Called Flow send
DEBUG - SedaQueue                      -
org.apache.servicemix.jbi.nmr.flow.seda.sedaqueu...@70c221d7 dequeued
exchange: InOut[
  id: ID:127.0.1.1-12750c79e7f-4:0
  status: Active
  role: consumer
  service:
{http://servicemix.in2m.com/operations/changepassword}RoutingService
  endpoint: camel127-0-1-1-12750c79e7f-6-1
  in: <?xml version="1.0"
encoding="UTF-8"?><response><status>4000</status><message>Connection
Error</message></response>
  out: <?xml version="1.0"
encoding="UTF-8"?><response><status>4000</status><message>Connection
Error</message></response>
]
DEBUG - DeliveryChannelImpl            - Notifying exchange
ID:127.0.1.1-12750c79e7f-4:0(203eb8a) in DeliveryChannel{servicemix-camel}
from processInboundSynchronousExchange
DEBUG - DeliveryChannelImpl            - Notified:
ID:127.0.1.1-12750c79e7f-4:0(203eb8a) in DeliveryChannel{servicemix-camel}
from sendSync
DEBUG - DeliveryChannelImpl            - Send ID:127.0.1.1-12750c79e7f-4:0
in DeliveryChannel{servicemix-camel}
DEBUG - SecuredBroker                  - send exchange with secure broker
DEBUG - SedaFlow                       - Called Flow send
DEBUG - SedaQueue                      -
org.apache.servicemix.jbi.nmr.flow.seda.sedaqueu...@7fad552c dequeued
exchange: InOut[
  id: ID:127.0.1.1-12750c79e7f-4:0
  status: Done
  role: provider
  service:
{http://servicemix.in2m.com/operations/changepassword}RoutingService
  endpoint: camel127-0-1-1-12750c79e7f-6-1
  in: <?xml version="1.0"
encoding="UTF-8"?><response><status>4000</status><message>Connection
Error</message></response>
  out: <?xml version="1.0"
encoding="UTF-8"?><response><status>4000</status><message>Connection
Error</message></response>
] 
-- 
View this message in context: 
http://old.nabble.com/An-Operation-working-with-3.2.2-now-does-not-work-with-3.3.1-tp27873544p27900502.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to