0 votes
67 views
in Integrations by (16k points)

1 Answer

0 votes
by (16k points)
This is a known limitation/feature/issue of timer based UCAS, if the invoked service does not complete within a stipulated amount of time the UCA may fire twice/thrice.

There can be two solutions to this issue

1. Convert your service invocations to bpd instance based invocations, the UCA simply launches a BPD instance which in turn does the service call so that timeout does not happen in the UCA service.

2. another solution will be to create an EPV and record the date part of current datetime to it after every invocation and at the beginning of the invocation check if it is the same date do not invoke the activity.

Related questions

0 votes
0 answers 37 views
0 votes
1 answer 87 views
0 votes
2 answers 277 views
0 votes
0 answers 107 views
0 votes
1 answer 274 views
0 votes
0 answers 10 views
0 votes
0 answers 67 views
0 votes
3 answers 119 views

580 questions

482 answers

85 comments

1.7k users

Dosvak IBM BPM /BAW Products, Download Evaluation
Process & Performance Tools Process & Performance Tools
Code Analyzer Code Analyzer
UI Toolkit UI Toolkit
Integration Monitoring Integration Monitoring
Welcome to BPM Tips Q&A, Community wiki/forum where you can ask questions and receive answers from other IBM BPM experts and members of the community. Users with 2000 points will automatically be promoted to expert level.
Created by Dosvak LLC
Our Youtube Channel
...