There is no relationship between send/sendSync and the fact that the
provider implements (or does not implement) MessageExchangeListener.
If your sendSync times out, the usual reason is that the provider did not
answer the exchange.
The problem with the processor not begin able to use send is quite simple.
A JBI component can register more than one Endpoint. If the endpoint use
asynchronous send, the answer (or DONE status) will be delivered to the
component, which has to know something about the exchange so that it is able
to give it to the needed processor. This is all what the
sendConsumerExchange do: just keep track of the sent exchange.
I guess we could give the endpoint a wrapper that would do that
automatically though.
Cheers,
Guillaume Nodet
On 6/2/06, SP Liu <[EMAIL PROTECTED]> wrote:
I am confused why it has such difference if SE as initiator of ME.Since
client APIs are JBI compliant,it should has no distinguish to use them.
if using * channel.sendSync(mec),the TestComponent(provider) which did't
implement MessageExchangeListener interface can not accept the ME so that
the console will wait until timeout
//console
...
2006-06-02 22:12:30,125 [main ] DEBUG DeliveryChannel
- Sent: MessageExchange[
id: ID:spliu-4346-1149257547875-3:0
status: Active
role: consumer
service: receiver
in: <?xml version="1.0" encoding="UTF-8"?><payload/>
]
2006-06-02 22:12:30,125 [main ] DEBUG Broker
- Routing exchange [EMAIL PROTECTED]:
ServiceEndpoint[service=receiver,endpoint=endpoint]
2006-06-02 22:12:30,125 [main ] DEBUG AbstractFlow
- Called Flow send
2006-06-02 22:12:30,125 [main ] DEBUG AbstractFlow
- Called Flow doRouting
2006-06-02 22:12:39,187 [Timer-1 ] DEBUG AutoDeploymentService
- Monitoring directory ...
2006-06-02 22:12:39,187 [Timer-1 ] DEBUG AutoDeploymentService
- Monitoring directory ...
...
if using * BaseLifeCycle.sendConsumerExchange(MessageExchange exchange,
Endpoint endpoint),it wil fail to send ME
//console
...
2006-06-02 22:31:34,015 [main ] INFO JBIContainer
- Activating component for: [container=ServiceMix,name=consumer] with
service: null component:
[EMAIL PROTECTED]
2006-06-02 22:31:34,015 [main ] INFO ComponentMBeanImpl
- Initializing component: consumer
2006-06-02 22:31:34,015 [main ] DEBUG MySpringComponent
- Initializing component
2006-06-02 22:31:34,015 [main ] DEBUG JBIContainer
- No transaction manager found from naming context: scheme java not
recognized
2006-06-02 22:31:34,015 [main ] DEBUG JBIContainer
- No transaction manager found from naming context: scheme java not
recognized
2006-06-02 22:31:34,031 [main ] DEBUG MySpringComponent
- Component initialized
2006-06-02 22:31:34,031 [main ] INFO ComponentMBeanImpl
- Starting component: consumer
2006-06-02 22:31:34,046 [main ] DEBUG MySpringComponent
- Starting component
2006-06-02 22:31:34,078 [main ] DEBUG ComponentContextImpl
- Component: consumer activated endpoint: sender : endpoint
2006-06-02 22:31:34,078 [main ] DEBUG MySpringComponent
- Querying service description for
ServiceEndpoint[service=sender,endpoint=endpoint]
2006-06-02 22:31:34,078 [main ] DEBUG MySpringComponent
- No description found for {}sender:endpoint
2006-06-02 22:31:34,078 [main ] DEBUG EndpointRegistry
- Endpoint ServiceEndpoint[service=sender,endpoint=endpoint] has no
service
description
2006-06-02 22:31:34,078 [main ] DEBUG MySpringComponent
- Component started
2006-06-02 22:31:34,140 [main ] DEBUG MySpringComponent
- Stopping component
2006-06-02 22:31:34,140 [pool-2-thread-1] DEBUG MySpringComponent
- Polling thread will stop
2006-06-02 22:31:34,140 [main ] DEBUG MySpringComponent
- Component stopped
2006-06-02 22:31:34,140 [main ] DEBUG MySpringComponent
- Shutting down component
2006-06-02 22:31:34,140 [main ] DEBUG MySpringComponent
- Component shut down
2006-06-02 22:31:34,140 [main ] DEBUG AbstractFlow
- Called Flow stop
2006-06-02 22:31:34,140 [main ] DEBUG AbstractFlow
- Called Flow shutdown
2006-06-02 22:31:34,140 [main ] DEBUG AbstractFlow
- Called Flow stop
--
View this message in context:
http://www.nabble.com/%22No-processor-found%22-error-t1716357.html#a4680767
Sent from the ServiceMix - User forum at Nabble.com.
