Could you check the log and see if something weird has happened
before these errors appear ? I've already seen ServiceMix running
out of file descriptors and the hot deployer would behave madly,
thus telling the container that some jars were removed ....
However such a thing usually requires restarting the container
(and it seems you did not do that).
I think I have already seen such errors after a redeploy that
failed somehow: these problems may be caused to old
versions of the ServiceEndpoint being held somehow ...
IIRC, the matching is done on the object itself and not on
the service / endpoint name. This needs further investigation ...
On 3/14/07, Gert Vanthienen <[EMAIL PROTECTED]> wrote:
L.S.,
This morning, we had problems with ServiceMix not finding some
service/endpoint, causing messages not to be processed. An excerpt of
the log:
08:56:08,152 | WARN | pool-component.servicemix-ftp-thread-3 |
FtpComponent | mon.endpoints.ConsumerEndpoint 148 | Target
service ({http://www.javafresh.eu/servicemix}archive-wiretap) and
endpoint (out) specified, but no matching endpoint found. Only the
service will be used for routing.
08:56:08,152 | WARN | pool-component.servicemix-ftp-thread-3 |
DefaultBroker | rvicemix.jbi.nmr.DefaultBroker 341 |
ServiceName ({http://www.javafresh.eu/servicemix}archive-wiretap)
specified for routing, but can't find it registered
08:56:08,527 | ERROR | pool-component.servicemix-ftp-thread-3 |
FtpComponent | rvicemix.ftp.FtpPollerEndpoint 280 | Failed
to process file: /out/GASTRO-order-20070309123804794.xml. Reason:
javax.jbi.messaging.MessagingException: Could not find route for
exchange: InOnly[...
These services had been running for several weeks without problems up to
now. I solved the problem by removing the SA from the deploy directory
and then copying it back again. The service assembly was redeployed and
everything was working again as before. Do you have any idea what might
have caused these problems? How can we avoid them?
Regards,
Gert Vanthienen
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
