Tomcat log inundated with irrelevant warning messages about "No IdentifiableObjectStore found for class: ... Reportingrate"

Support - Assistance technique
1

Hi
I have recently noticed that the tomcat log is getting filled with irrelevant warning messages of this type:

  • WARN 2018-10-08 22:12:51,086 No IdentifiableObjectStore found for class: class org.hisp.dhis.common.ReportingRate (DefaultIdentifiableObjectManager.java [http-nio-8080-exec-9])

  • WARN 2018-10-08 22:12:51,111 No IdentifiableObjectStore found for class: class org.hisp.dhis.common.ReportingRate (DefaultIdentifiableObjectManager.java [http-nio-8080-exec-9])

  • WARN 2018-10-08 22:12:51,113 No IdentifiableObjectStore found for class: class org.hisp.dhis.common.ReportingRate (DefaultIdentifiableObjectManager.java [http-nio-8080-exec-9])

As far as I can tell, every single favourite invoked on e.g. dashboard generates one of these irrelevant warning messages in the log.

Any idea what could cause this?

Regards

Calle

···

Calle Hedberg

46D Alma Road, 7700 Rosebank, SOUTH AFRICA

Tel/fax (home): +27-21-685-6472

Cell: +27-82-853-5352

Iridium SatPhone: +8816-315-19119

Email: calle.hedberg@gmail.com

Skype: calle_hedberg

1 Like
2

we are facing the same:

* WARN  2019-02-26 16:05:41,162 No IdentifiableObjectStore found for class: class org.hisp.dhis.common.ReportingRate (DefaultIdentifiableObjectManager.java [http-bio-127.0.0.1-8081-exec-4])
* WARN  2019-02-26 16:05:41,175 No IdentifiableObjectStore found for class: class org.hisp.dhis.common.ReportingRate (DefaultIdentifiableObjectManager.java [http-bio-127.0.0.1-8081-exec-4])
* WARN  2019-02-26 16:05:41,188 No IdentifiableObjectStore found for class: class org.hisp.dhis.common.ReportingRate (DefaultIdentifiableObjectManager.java [http-bio-127.0.0.1-8081-exec-4])
* WARN  2019-02-26 16:05:41,202 No IdentifiableObjectStore found for class: class org.hisp.dhis.common.ReportingRate (DefaultIdentifiableObjectManager.java [http-bio-127.0.0.1-8081-exec-4])

Any idea why this is happening and how we can solve it?

1 Like
3

Hi,

this was simply a bit of excessive logging. We have reduced the log level to debug for this statement in recent versions so it will go away once you upgrade.

regards,

Lars

4 Likes