Unknown Error on Catalina File

Dear All,

This morning my instance could not find any dataset, data element, etc. Looking at its’ log file i notice the following errors:

[tomcat-http-7])

  • WARN 2018-01-20 02:50:05,501 No IdentifiableObjectStore found for class: class org.hisp.dhis.dataelement.DataElement (DefaultIdentifiableObjectManager.java [tomcat-http-7])
  • WARN 2018-01-20 02:50:05,501 No IdentifiableObjectStore found for class: class org.hisp.dhis.dataelement.DataElementOperand (DefaultIdentifiableObjectManager.java [tomcat-http-7])
  • WARN 2018-01-20 02:50:05,501 No IdentifiableObjectStore found for class: class org.hisp.dhis.common.ReportingRate (DefaultIdentifiableObjectManager.java [tomcat-http-7])
  • WARN 2018-01-20 02:50:05,503 No IdentifiableObjectStore found for class: class org.hisp.dhis.dataset.DataSet (DefaultIdentifiableObjectManager.java [tomcat-http-7])
  • WARN 2018-01-20 02:50:10,112 No IdentifiableObjectStore found for class: class org.hisp.dhis.dataelement.DataElement

Please can someone explain these errors?

···

Regards,

Gerald

1 Like

Did you get around this Gerald? Facing a similar error, only with categories and category combos.

  • WARN 2019-07-10 16:56:22,270 No IdentifiableObjectStore found for class: class org.hisp.dhis.dataelement.DataElementCategoryCombo (DefaultIdentifiableObjectManager.java [catalina-exec-12])
  • WARN 2019-07-10 16:56:22,271 No IdentifiableObjectStore found for class: class org.hisp.dhis.dataelement.DataElementCategory (DefaultIdentifiableObjectManager.java [catalina-exec-12])

1 Like

Hi @haroon and @Gerald_Thomas,

These warnings are harmless, and could potentially even be removed, no need to worry.

The issue you are having @haroon is not related to these error messages, but potentially something else. It’s hard to deduct from your screenshot what might be the issue, but I would guess you are trying to open a URL that is pointing to a DataElementCategory that does not exist.

If you think this is not right, and the data element category should in fact exist, try accessing it through the api using the UID mentioned in the error message in your screenshot. If it return a message of not found, it means it is not found in the database. In that case it should actually not exist at all.

1 Like

I reinstalled our instance with a different build revision and restored the database, this is when we started experiencing the issue of categories not being accessible. Changed it to the orginal build revision and this seemed to have solved the issue.

1 Like