This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.

AnnouncementAnnouncement Module

Collapse

No announcement yet.

ImapIdleChannelAdapter does not re-establish connectionPage Title Module

As you can see it tries to re-establish the connection every 5 minutes and when it receives an e-mail at 11:01 it hangs. It seems that it remains in the blocked state and the only way to reconnect to MS Exchange is by restarting the adapter (via control bus) or restarting app server itself.

I would like to add that I set up the mail.imap.timeout parameter to 300000 milisec in order to give adapter a chance to reconnect after 5 minutes.

Has anybody faced similar issues with imap-idle-channel-adapter?

Help is needed since described issue happens on production environment

I think someone had reported something similar and it was fixed. Also there was some refactoring done last week to that module. Could you please run it against the lates snapshot and see if the problem is still there?

Comment

Thanks for your response. Did you remember in which version It was fixed? Currently we're running 2.0.5 version on production and problem occurred a few days ago. I will run it against the latest snapshot version and let you know.

Comment

Right, it has to be https://jira.springsource.org/browse/INT-2104, As I can see in Jira the fix was applied to 2.1.0.M1 which was already released. Do you think that 2.1.0.M1 is stable enough to use it on prod or should I rather move back to 2.0.4 version in which the described issue was not present.

I would not recommend using a Milestone in production. Other than features that are still in development (which you probably wouldn't be using yet), it should be relatively stable, but the idea behind our milestone phases is that anything *can* change until we get into the RCs. Our goal is to have Spring Integration 2.1 GA in November.

We will most likely release 2.0.6 as soon as possible after 2.1 GA since it might contain more backported fixes between now and the time the GA is ready.

I guess I'd recommend using 2.0.4 if there is nothing else in 2.0.5 that you really needed, and then as soon as 2.0.6 is available you could skip ahead. Another thing you can try is downgrading just the mail module to 2.0.4. It wouldn't be an officially supported configuration, and it can add a bit extra to your Maven configuration, but that module is fairly independent. If you can run some tests and that seems okay, it might be a temporary option to consider.

We would definitely like to hear from you if you get a chance to test the 2.0.6.BUILD-SNAPSHOT version as well.