Program Notification Issues in DHIS2 version 41.4.2

Support - Assistance technique
1

I upgraded two instances to this version last week. We since noticed that program notifications for the same are an issue. It seems not to be sending program notifications at all, and specifically also when the email to be sent is being stored as a data element

WARN 2025-09-15T15:05:26,814 Notification lost due to: Could not open JPA EntityManager for transaction; nested exception is java.lang.IllegalStateException: EntityManagerFactory is closed (DefaultNotifier.java [pool-4-thread-1]

WARN 2025-09-15T15:09:17,005 Notification lost due to: Could not open JPA EntityManager for transaction; nested exception is java.lang.IllegalStateException: EntityManagerFactory is closed (DefaultNotifier.java [pool-4-thread-1])

How do I handle this?

1 Like
DHIS2 patch release 41.5 is now available
Event program Notification Issues
2

Hi @lillian1n2

Thank you for your post. Would it be possible to continue the update to version 41.5.1? It seems that from version 41.4.2 up to 41.5.1 there were some bug issues that got fixed and were related to notifications: dhis2-releases/releases/2.41/ReleaseNote-2.41.5.md at master · dhis2/dhis2-releases · GitHub

Also, I found tickets that seem similar to the issue you are facing (but they were fixed) so I want to ask if you’re seeing the same issues as described here: Program Stage Notification not sent on 39 & 40 when there are multiple actions defined with Send Message for Program Rule

Thanks!

3

Well to be clear, the two instances were running different versions, and both were upgraded to 2.41.5 and both still have the issue of the data element.

1 - 2.41.1
2 - 2.40.3.2

1 Like
4

Thank you for the info @lillian1n2 ! I have triaged this issue to the team. :folded_hands:

5

Hi again @lillian1n2

As you can see the issue has been triaged and @zubair has created a Jira ticket to look into it (Jira);

however, would you please help identify the actual issue by completing the required info? We need to steps to reproduce this issue in order for the developers to debug. The ticket has three points:

  1. Steps to reproduce
  2. Actual Result
  3. Expected Result

If you can’t provide those then please provide as much details as possible (so that the ticket is not closed for missing info).

Thank you!