Skip to Content
Technical Articles
Author's profile photo Frederic Carius

Enhanced: Alerting for stuck messages on the Adapter Engine

Introduction

With the blog post Alerting for stuck messages on the Adapter Engine a feature to alert on messages that appear to be no longer processed has been provided. This functionality has later been included in the standard coding.

In certain situations this alert mechanism may not be sufficient or more specifically procude false alarms as it does not allow to filter on message status.

Download & Deployment:

Use the following link to download the enhanced version:

Download EAR

The ear-File then needs to be deployed to your system. Make sure that these changes are tested on a non-production system before using it in your production environment.

After deployment  you can find the new application via NetWeaver Administrator -> Operations -> Systems -> Start&Stop -> Java Applications. The application list should have a new entry with name “pi.alertstuckmsgv2” and vendor “cust.sap.com”. Please verify that it is started without errors.

 

Scheduling the Job

Scheduling and configuring the job can be done via NetWeaver Administrator -> Operations -> Jobs -> Java Scheduler. Here you can find the new job template in tab “Job Definitions”. It should list a new job type with name “AlertStuckMessagesJobv2” and application “cust.sap.com/pi.alertstuckmsgv2”.

 

For details about scheduling refer to the original blog post:

https://blogs.sap.com/2016/04/13/alerting-for-stuck-messages/

The difference in scheduling which supports the new enhancement is the parameter “StuckMessageStatusList” which can be populated with comma-separated status values. The mentioned status values are those which are taken into account for alerting. Messages having another status will not be alerted.

The default value (list) is: TBDL,DLNG,HOLD

All other parameters from the original version and the provided information in the blog post is still valid.

 

Summary

This blog post and its provided alerting application allows you to filter for “stuck messages” to be alerted on by message processing status. It heavily builds on already available functionality published in other / earlier blog posts and available in SAP NetWeaver Process Orchestration standard functionality.

 

Assigned Tags

      11 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Pavan G
      Pavan G

      Hi Frederic,

      Thanks for the detailed blog.

      I have followed the blog and set up configurations in my PI Dev system.

      I made messages to get stuck to test it. But the alerts are not triggered.

      Can you please let me know if I am missing something?

      Regards,

      Pavan

      Author's profile photo Frederic Carius
      Frederic Carius
      Blog Post Author

      Hi Pavan,

      i guess the most obvious question is whether the consumer ALERT-TO-MAIL is configured which means that you have a Mail Consumer job polling the JMS queue:

      https://help.sap.com/viewer/bdfc9b7d99b544d8bbda40546b70967a/7.5.14/en-US/504ddc6fa9554b9ab340976c97587042.html

      If you want to enable more traces set this location to DEBUG: com.sap.pi.alertstuckmsg.job

       

      Best regards,

      Frederic

      Author's profile photo Pavan G
      Pavan G

      Hi Frederic,

      Thanks for the Response.

      Yes, ALERT-TO-MAIL is configured.

      The issue has been resolved now, upon connecting with my Basis team.

      One more query: Is there any way to receive alerts for the messages stuck in Waiting status?

      Best Regards,

      Pavan

      Author's profile photo Frederic Carius
      Frederic Carius
      Blog Post Author

      Hi Pavan,

      messages in WAITING status will be retried automatically - means they will go into TBDL status after the time between retries.

      Cheers,

      Frederic

      Author's profile photo Pavan G
      Pavan G

      Hi Frederic,

      Thanks a lot for the insights.

      Best Regards,

      Pavan

      Author's profile photo T. van Rooijen
      T. van Rooijen

      Hi Frederic,

      I was just looking into this for a customer of mine.
      What is strange is that in the original AlertStuckMessagesJob (PO 7.5) I only see the parameter "Additional" .

      I would have at least expected some of the other parameters.

      Also where does this EAR come from? Is it mentioned in a SAP note?
      I may not be able to convince my customer to install an EAR which I picked up from Google drive if I cannot show them that it is a regular software deployment.

       

      Kind regards,

      Tom

       

      Author's profile photo Vaishali Rani
      Vaishali Rani

      Hi Frederic,

      Do you know why we see just  the parameter "Additional"  for standard AlertStuckMessagesJob (PO 7.5) . Also I have the ALERT-TO-MAIL configured. But how do I use it in this job, since no parameter.

       

      Regards,

      Vaishali

      Author's profile photo Frederic Carius
      Frederic Carius
      Blog Post Author

      Hi Vaishali,

      never seen or had this problem before. It may be a UI / rendering issue - have you tried a different browser, clearing cache and this usual stuff? There should be quite a few parameters. The only other thing i can recommend is to re-deploy and see whether that helps.

      Best regards,

      Frederic

      Author's profile photo Vaishali Rani
      Vaishali Rani

      Thankyou, Frederic for the quick response, I will try to redeploy and post the response.

       

      Regards,

      Vaishali

      Author's profile photo Rudra Singh
      Rudra Singh

      Hi Frederic,

      We are getting below error while finishing the Task.

       

      The task was not added due to:An exception has ocurred while persisting state of task 6112898f67ff11eea029000026502e56 Please analyse the stack trace and/or send it to SAP Support center.

       

      Could you please let me know if we need to make any adjustment in the code.

       

      Thank you,

      Author's profile photo Frederic Carius
      Frederic Carius
      Blog Post Author

      Please check the defaultTrace for exceptions ... You might have to raise an incident for "a custom job" which is failing in case the problem is not directly originating from the job.

      Frederic