Unfortunately I am also still observing issues with idle processes that eventually cause Iman to stop processing further integrations even after updating to v3.2. I believe I have in my case traced it to an integration that was using the native Iman Sage 300 printer to print invoices, I have modified this integration to use an independent report printer and an Iman process task as well as separating the report printing onto a separate integration, this for now seems to have worked around the issue. Hope this helps.   

John, Browndog, can you explain your issues further?

In v3.2 we took two steps to reduce this from occurring:

a. Every single integration under it's own process.

b. Re-worked the integration concurrency to remove the semaphore issue.

If you have a locked up integration, you should be able to kill the integration and the it should fire after that.

The scheduler not running other integrations should only occur when you have concurrency enabled.

The locking up issue is a difficult one, as it's 100% outside of our code...it's all Sage300 AND SQL and can be easily created in a sample application outside of IMan.

When I last experienced this after the upgrade there were over 30 Iman processes that locked up, as you say I don't believe this was an Iman issue but more of a Sage 300 Printing Mechanism since the integration in question printed an invoice on every run and processed a large volume of files in a short time period .Since reworking the integration and using a third party tool to take care of the printing so far everything has been fine for me. 

Yes, What Browndog described is EXACTLY what is happening to us as well. The integration is used for printing invoices and credit notes. Any help would be great! Thanks guys!

I'm experiencing some of these and I'm not engaging in any printing at all. 

NVM - figured out my issue.  A stored procedure wasn't running properly affecting IMan in some way.

jpage, we have been running for a week now with no further issues. It does seems that in our case it was related to the native Iman printing connector, I believe Iman's native printing connector is pretty much just utilising the Sage 300 printing mechanism which does not have a great reputation for reliability. Realisable might be able to program around these errors but fundamentally the underlying issue of reliability would still be there. So we now use a third party tool for all of our report printing done by Iman, the reports are initiated by Iman using a process task and values passed across so the result is the same, the advantage of using such a tool is that reports such a shipments for which Iman has no native support at the moment can also be printed.

jpage, Browndog, thanks for your replies.

We may have just inadvertently kicked the SQL lockup issue a bit further down the road.

We will organise a test session for tomorrow to see if we can replicate the issue.

Browndog,

If you don't mind me asking, what third party tool are you using to print?

Thanks!

Sure, we use report commander, link below. 

Report Commander

see sample Iman process task command below

"C:\Program Files (x86)\Arcana Development\Report Commander 2\adrcexec.exe" -project="P:\IMan\RCProjects\AllShipperInvoice.rcproject" SORTFROM=%Record.INVNUMBER SORTTO=%Record.INVNUMBER PRINTNAME=%Record.ExportPath