Hi, We have a listener node(Receive Message) node in our process model whi

siddharthg521 over 11 years ago

Hi,
We have a listener node(Receive Message) node in our process model which listens for the message once the process starts and is active throughout .
We have another process model (a standalone process) which contains send message node.
Now, according to our use case the message is sent from this process model(standalone process model) to all the instances of the above process model which has a listener node in it once or twice in 15 days or so.
Currently lets say, there are 200 instances running to which the message is sent from the process model consisting of send message node. As time goes,number of instances will keep increasing as a result of which number of instances to which message needs to be sent will also increase.
Hence, our concern is whether or not it will put any load on execution engines or not? Are sending messages to multiple instances in bulk at the same time are reliable? Is there any probability that few instances will r...

Discussion posts and replies are publicly visible

Parents

0 shelzle over 11 years ago

The first case I created some form of a messaging queue where for each message a process is started which sends the message and waits for a acknowledge message from the receiving process. But: The message is sent only if the process instance itself is the longest running one.

Second case: Access custom message properties with the "property" or "index" function.

In short: Any messages that have not arrived had their cause in the infrastructure or in modelling.

Does this help you?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 shelzle over 11 years ago

The first case I created some form of a messaging queue where for each message a process is started which sends the message and waits for a acknowledge message from the receiving process. But: The message is sent only if the process instance itself is the longest running one.

Second case: Access custom message properties with the "property" or "index" function.

In short: Any messages that have not arrived had their cause in the infrastructure or in modelling.

Does this help you?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data