Skip to main content
saahilm4696
saahilm4696
July 25, 2023
Solved

Messaging Event

  • July 25, 2023
  • 5 replies
  • 0 views

Hi,

I have a requirement to send/receive message to process instance. My instance holds 3-4 receive message events a particular receive message will be executed based on the msg.properties.xyz properties. When a particular receive message event continues and the process terminates I am getting a error email from rest of the listeners.

Problem:  This notification is sent for canceled event messages of type Process to Process.

Details:  Canceled consumed message in Message Filter (ERROR:EVAL:@reason=Invalid bean property name 'rejectToRequestor' (valid properties are jmstype;username;eventtype;acceptandallocaterequest;originprocessmodelid;originprocessid;destinationprocessid), bean error code 0) for message sent to persistent id 0003ea7b-4569-8000-4990-7f0000014e7a on named port 'reject To Requestor'. The process itself has not been canceled and may continue to consume events.

Recommended Action:  Check the message listener for correctness. Cleanse the source of the message, if the message itself has caused the failure. For email events, place a spam filter in front of the event listener.

Priority of this problem: Normal Priority

Any idea on what can be done or why is this email coming even after the process is terminated.

Best answer by stefanhelzle0001

I see. And this is exactly what will fail. Accessing a non-existing field in a message using dot-notation creates the error messages you see.

5 replies

stefanhelzle0001
stefanhelzle0001
Brainy
July 25, 2023

I think that the issue is, that this message is consumed by all your listeners. In case a listener tries to access an attribute like "rejectToRequestor", it will create this error message you get.

Do you use dot-notation or index()/property() to fetch values from these messages? Dot-notation will fail if the property does not exist.

And, in case you want the process to stop after consuming the first message, I suggest to configure the end events to terminate the process.

saahilm4696
saahilm4696Author
July 25, 2023

Each listener is looking for a different property using dot notation. For specific tasks we are sending specific property via a send message event. If the property exist we are storing in pv! and using it in this listener process model.

At a time the message will hold specific property.

stefanhelzle0001
stefanhelzle0001Answer
Brainy
July 25, 2023

I see. And this is exactly what will fail. Accessing a non-existing field in a message using dot-notation creates the error messages you see.

    Terms & ConditionsAccessibility statement