|
»
»
« Return to Thread: Mule FTP polling dies silently
RE: Mule FTP polling dies silently
by antoine.borg
::
Rate this Message:
Hi,
In your case, the connection-strategy has nothing to do with your problem.
If the remote FTP server was unavailable for a few minutes, the
connection-strategy will force Mule to retry connections. However, this is
not happening (according to your description), what is happening is that
some sort of internal thread (or threads) are being closed/terminated.
Since there is no reported fault in the communication with the FTP server,
the connection-strategy is not being used.
You are right in your understanding of the polling properties. I mistakenly
mis-read the config and thought that you set the property on the connector
and on the endpoints.
Can you post a full stack trace here? Perhaps there is some information that
will help your problem be diagnosed. What was the difference when you
changed the doThreading attribute?
Regards
Antoine Borg, Senior Consultant | Tel: +32 28 504 696
ricston Ltd., BP 2, 1180 Uccle, Brussels, BELGIUM
email: antoine.borg@... | blog: blog.ricston.com | web: ricston.com
-----Original Message-----
From: Glenn Murray [mailto:gmurray@...]
Sent: Friday, August 29, 2008 7:15 AM
To: user@...
Subject: RE: [mule-user] Mule FTP polling dies silently
Hi,
Thanks for the reply. It is important that the application start and
continue running even if some of the FTP endpoints fail. My understanding
is that the connection-strategy I am using will allow that---if I am
incorrect, please let me know!
It is also my understanding that I am not "polling twice", but that I am
retrying failed connections every 600000ms (10min) and polling every 60000ms
(1min). Again, please correct me if I am wrong.
Thanks again,
Glenn
antoine.borg wrote:
>
> Hi,
>
> Not sure if this will help but ...
>
> If receiver.5 (or any other receiver) does not re-appear in the logs,
> I would suspect a threading issue as this suggests that a thread is
> lost/closed/disappears. My first suggestion would be to change that
> doThreading attribute. One reason for using it is to allow Mule to
> start even if the connector hasn't which may not be a problem in your
> situation (is it?).
>
> Also, why do you set the polling frequency on both the connector and
> the endpoint?
>
> Regards
>
>
> Antoine Borg, Senior Consultant | Tel: +32 28 504 696 ricston Ltd., BP
> 2, 1180 Uccle, Brussels, BELGIUM
> email: antoine.borg@... | blog: blog.ricston.com | web:
> ricston.com
>
>
>
--
View this message in context:
http://www.nabble.com/Mule-FTP-polling-dies-silently-tp19169571p19213789.htm
l
Sent from the Mule - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
In your case, the connection-strategy has nothing to do with your problem.
If the remote FTP server was unavailable for a few minutes, the
connection-strategy will force Mule to retry connections. However, this is
not happening (according to your description), what is happening is that
some sort of internal thread (or threads) are being closed/terminated.
Since there is no reported fault in the communication with the FTP server,
the connection-strategy is not being used.
You are right in your understanding of the polling properties. I mistakenly
mis-read the config and thought that you set the property on the connector
and on the endpoints.
Can you post a full stack trace here? Perhaps there is some information that
will help your problem be diagnosed. What was the difference when you
changed the doThreading attribute?
Regards
Antoine Borg, Senior Consultant | Tel: +32 28 504 696
ricston Ltd., BP 2, 1180 Uccle, Brussels, BELGIUM
email: antoine.borg@... | blog: blog.ricston.com | web: ricston.com
-----Original Message-----
From: Glenn Murray [mailto:gmurray@...]
Sent: Friday, August 29, 2008 7:15 AM
To: user@...
Subject: RE: [mule-user] Mule FTP polling dies silently
Hi,
Thanks for the reply. It is important that the application start and
continue running even if some of the FTP endpoints fail. My understanding
is that the connection-strategy I am using will allow that---if I am
incorrect, please let me know!
It is also my understanding that I am not "polling twice", but that I am
retrying failed connections every 600000ms (10min) and polling every 60000ms
(1min). Again, please correct me if I am wrong.
Thanks again,
Glenn
antoine.borg wrote:
>
> Hi,
>
> Not sure if this will help but ...
>
> If receiver.5 (or any other receiver) does not re-appear in the logs,
> I would suspect a threading issue as this suggests that a thread is
> lost/closed/disappears. My first suggestion would be to change that
> doThreading attribute. One reason for using it is to allow Mule to
> start even if the connector hasn't which may not be a problem in your
> situation (is it?).
>
> Also, why do you set the polling frequency on both the connector and
> the endpoint?
>
> Regards
>
>
> Antoine Borg, Senior Consultant | Tel: +32 28 504 696 ricston Ltd., BP
> 2, 1180 Uccle, Brussels, BELGIUM
> email: antoine.borg@... | blog: blog.ricston.com | web:
> ricston.com
>
>
>
--
View this message in context:
http://www.nabble.com/Mule-FTP-polling-dies-silently-tp19169571p19213789.htm
l
Sent from the Mule - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
« Return to Thread: Mule FTP polling dies silently
| Free embeddable forum powered by Nabble | Forum Help |
