Reputation: 813
I am testing a wait notify workflow as shown in the pic. I am using "${fragment.identifier}" as "Release Signal Identifier" for both WAIT and NOTIFY. "Signal Counter Name" is default/empty. "Target Signal Count" for wait is "${fragment.count}". Not sure why the WAIT is indefinitely waiting even after all the split fragments are processed and notified by NOTIFY. Please help. Is there a way to view the contents of Distributed Map Cache to identify what is going on - i.e value of signal counters etc
UPDATE:
Solved the indefinite wait issue by adding a self-loop on "wait" from WAIT processor onto itself as shown in the pic.
PENDING: Still need a way to view entries in Distributed Map Cache.
Upvotes: 1
Views: 1799
Reputation: 1700
To see the cache entries you can do this:
Configure the DistributedMapCacheServer to use a persistence directory like this:
After that you can take a look at the folder content and check what do you have in the cache.
Upvotes: 4