check the subscribing trigger and the processing service...and see why they are not getting picked up...if the data in the queue is not so important and if you want to clean it up...then you can clear the queue...you will find the clear queue button if you open the client queue ...
Thanks Pavanarab. Data is important here, b'coz it happened in Production. Documents are stuck in subscriber trigger. It was working fine some time back. But all of sudden, processing stopped. Don't see any issue in IS server logs.
@ Srinik, open the queue and check 1st document in the trigger client queue. That should be the one which is causing the problem. if its a large document or or having the problem then that document will not be subscribed. That blocks the remaining incomin
note - deleting the blocked document from queue totally depends on how important the transaction is. the above solution is only ideal. so get a suggestion from your team and then go ahead
Thanks all for ur suggestion. IS restart worked here, but this is not the ideal solution. Everything was looking correct. Nothing found in error/server logs related to this Document/FS. Memory space, Available thread were enough
Srinik
There are many request (documents) stuck in broker trigger from long time. How to release them
Pavan
check the subscribing trigger and the processing service...and see why they are not getting picked up...if the data in the queue is not so important and if you want to clean it up...then you can clear the queue...you will find the clear queue button if you open the client queue ...
Srinik
Thanks Pavanarab. Data is important here, b'coz it happened in Production. Documents are stuck in subscriber trigger. It was working fine some time back. But all of sudden, processing stopped. Don't see any issue in IS server logs.
Neelima
Srinik If the trigger is enable but still docs are not flowing try disabling/enabling from developer.
Check the trigger filter condition.
Pavan
Do you see the documents getting piled up or do you see them getting processed slowly ??
Srinik
Pavanarab & Nelsiri, piled up it did not work
Pavan
ould you check the cpu and memory usage of the machine on which you broker and the subscribing IS are running..
Neelima
Srinik, after disabling from Developer , wait for sometime and then enable it. Also is it Serial or Concurrent processing ?
Srinik
It is Serial processing. cpu and memory usage r fine.
Nancy
@ Srinik, open the queue and check 1st document in the trigger client queue. That should be the one which is causing the problem. if its a large document or or having the problem then that document will not be subscribed. That blocks the remaining incomin
Nancy
note - deleting the blocked document from queue totally depends on how important the transaction is. the above solution is only ideal. so get a suggestion from your team and then go ahead
Srinik
Thanks all for ur suggestion. IS restart worked here, but this is not the ideal solution. Everything was looking correct. Nothing found in error/server logs related to this Document/FS. Memory space, Available thread were enough