I have two cxf-se components (SE1 and SE2). SE1 uses cxfse:proxy to call
another one (SE2).
When I removing SE2 from servicemix and try to invoke SE1 operation, as I
expect, exception occurs:
javax.jbi.messaging.MessagingException: Could not find route for exchange...
and servicemix logs this exception to stacktrace.
But SE1 still wait for response. In threads dump I see, that SE1 waits in
waitResponse() method:
pool-flow.seda.servicemix-cxf-se-thread...@2190, priority=5, in group
'main', status: 'WAIT'
wait():-1, Object.java
waitResponse():534, ClientImpl.java
processResult():480, ClientImpl.java
invoke():448, ClientImpl.java
invoke():279, ClientImpl.java
invoke():231, ClientImpl.java
...........
and SE1 stops waiting only after timeout.
Why SE1 doesn't stop waiting immediately?
What should I do to an exception found in SE1?
Sorry for bad English.
Can anyone help me? Thanks in advance.
--
View this message in context:
http://www.nabble.com/cxf-se-proxy-doesn%27t-know-that-target-component-doesn%27t-exist-tp22491107p22491107.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
