diff options
authorVrishali Doke2013-09-30 08:51:15 (EDT)
committerStephan Born2013-10-23 06:48:35 (EDT)
commita7019db3f4272b1fe3239235155f871dfe793cf4 (patch)
parente995cbd3d9cc9ebb3266fe00ce080bfb844df410 (diff)
CRNT-30740 - Added details for corelation
git-svn-id: 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b Signed-off-by: Vrishali Doke <>
1 files changed, 11 insertions, 1 deletions
diff --git a/ b/
index 6e735df..f5143fd 100644
--- a/
+++ b/
@@ -459,7 +459,17 @@ derived from configuration variables.
<p>There are multiple ways to address the correct activity instance to be
-completed by adding certain header fields to the Camel message.
+completed by adding certain header fields to the Camel message.</p>
+For the following cases, when we use corelation it should always use activity ID, process ID and data
+of the same consumer application.
+In this case only consumer activity will get completed.
+For example, when we corelate an activity using process ID, activity ID and data,
+the activity found should be same
+as Consumer activity for which consumer route is activated. If we give any
+other activity say DummyAct then in consumer route it will find the DummyAct activity,
+which won't be useful and no action will be taken on that found activity. In this case,
+the consumer activity will remain in hibernated state.
<h3>Correlate by activity instance OID</h3>