Hi. I’m investigating some peculiar behavior we have started seeing with the
DB2 adapter receive locations and I was wondering if anyone has any advice.
We have been using DB2 adapter on a few ports with no issues, but recently
we started using it for more workflows. What we have started to experience
is that from time to time our receive locations appear to stop polling the
AS400 file. The selection criteria for a our receive location is simple.
“Select * from some file where status = ‘x’’”. The receive location is
enabled, but records with a status of ‘x’ just stop getting pulled into
Biztalk even though they meet the select criteria.
If we disable/enable the receive location it pulls in the ‘x’ records right
away and will work for awhile (sometimes hours, sometimes days), but will
eventually stop and force us to disable/enable again.
Is this a known issue? I’d be most grateful for any advice. We have a load
balancing configuration with 2 Biztalk severs each running a host for the
adapter. We also have a multi-AS400 environment and monitor DB2 files on
multiple AS400’s.