You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Performing large Fetch's in batch, x number of records at a time... starting with position "start" continuing with "current". But experiencing a "StreamPut" unrecoverable disconnection from the host after a while. I establish a connection to IMu again, however, now all continued hits to Fetch at position "current" just result in StreamPut errors too. If I restart the search at position "start" again, it works... How do I pick up where I left off in a batch search when disconnected like this? It seems like the disconnection wipes out my current position in my batch fetches and it no longer knows what "current" means when I try to fetch my next page of results. How do I pick up where I left off at the last batch without having to start my entire search completely over again?
Can not find anything in the Axiell IMu documentation regarding StreamPut errors let alone any methods of "reconnecting".
The text was updated successfully, but these errors were encountered:
Performing large Fetch's in batch, x number of records at a time... starting with position "start" continuing with "current". But experiencing a "StreamPut" unrecoverable disconnection from the host after a while. I establish a connection to IMu again, however, now all continued hits to Fetch at position "current" just result in StreamPut errors too. If I restart the search at position "start" again, it works... How do I pick up where I left off in a batch search when disconnected like this? It seems like the disconnection wipes out my current position in my batch fetches and it no longer knows what "current" means when I try to fetch my next page of results. How do I pick up where I left off at the last batch without having to start my entire search completely over again?
Can not find anything in the Axiell IMu documentation regarding StreamPut errors let alone any methods of "reconnecting".
The text was updated successfully, but these errors were encountered: