Resolution:
Receive Event (and Workflow Service Agent) activities use its GUID for subscribing to
RV.  If there are multiple Receive Event activities with same GUID trying to register to RV, it will lead to RVDQ and behavior will be unpredictable.

As you see in the below logs with the two receive events instances running in dev and int environment, RV heart beat messages from dev and Int  is having same  DQ name "SDMFWMTMRUAU2-UeOS--23j-w/Y", although the receive events is configured to talk to different workflow server.  If the receive events forming DQ then you will see the message loss, i.e receive events doesn't absorb the trigger messages from IC server unless all other instances in the DQ group are stopped.


*************  
"F:\Xoriant\SRs\BWC\1-8ZLXPT\listenCLE.DAT"(11,63):2008-08-04 17:58:01
(2008-08-04 22:58:01.025904000Z):
subject=_RVCMQ.WORKER_STATUS.SDMFWMTMRUAU2-UeOS--23j-w/Y,
reply=_INBOX.CDEFD4A1.6030489358D0172F8C8.4, message={max=1 weight=0
cmsubs={TIBCO.IC.WF_TibIntReg01.TRIGGER.TASK.READY=1
TIBCO.IC.WF_TibIntReg01.NotifyByType.TASK_READY=1
TIBCO.IC.WF_TibIntReg01.NotifyByType.JOB_TASKS_COMPLETE=1
TIBCO.IC.WF_TibIntReg01.TRIGGER.JOB.TASKS_COMPLETE=1}}

"F:\Xoriant\SRs\BWC\1-8ZLXPT\listenCLE.DAT"(126,63):2008-08-04 17:58:09
(2008-08-04 22:58:09.162833000Z):
subject=_RVCMQ.WORKER_STATUS.SDMFWMTMRUAU2-UeOS--23j-w/Y,
reply=_INBOX.CDEFD4A0.262148975C4FEC5F18.4, message={max=1 weight=1
cmsubs={TIBCO.IC.WF_TibDevReg01.TRIGGER.TASK.READY=1
TIBCO.IC.WF_TibDevReg01.NotifyByType.TASK_READY=1
TIBCO.IC.WF_TibDevReg01.NotifyByType.JOB_TASKS_COMPLETE=1
TIBCO.IC.WF_TibDevReg01.TRIGGER.JOB.TASKS_COMPLETE=1}}
*******************

To find out whether the receive events  is forming a DQ with other receive event instances , you can do  a tibrvlisten on the subject  "_RVCMQ.WORKER_STATUS.>" for a minute. Every member in the DQ group willbe sending status message on the subject "_RVCMQ.WORKER_STATUS.&ltDQ Name>" in a 10 sec interval. From this you can find out how many are grouped in a single DQ group.


SOLUTION: To address this, precaution has to be taken to avoid forming of RVDQ. You can follow either one of the below approach to avoid forming DQ

1) you have to use different RV channel by using different RV parameters in the workflow connection in each environment.

or

2) recreate the receive events in the desinger project to have different GUID. You have to delete the  receive event pallete and recreate. This process is tedious if you have lot of environments. For every environment you have to recreate the receive events.

we recommend approach 1) to keep it simple.

Receive Events forming DQ when you run multiple instances