Warnings from Liquibase.

[rhe-reliatec]

This concerns libreclinica1.0

After a restart we always get in libreclinica-db.log warnings from LiquibaseEntityResolver. Lots of them.

04/05 12:41:43 [LibreClinica] NEWS INFO   l.e.jvm.JdbcExecutor:42 - SELECT COUNT(*) FROM public.databasechangeloglock 
04/05 12:41:43 [LibreClinica] NEWS INFO   l.e.jvm.JdbcExecutor:42 - SELECT COUNT(*) FROM public.databasechangeloglock 
04/05 12:41:43 [LibreClinica] NEWS INFO   l.e.jvm.JdbcExecutor:42 - SELECT LOCKED FROM public.databasechangeloglock WHERE ID=1 
04/05 12:41:43 [LibreClinica] NEWS INFO   l.l.StandardLockService:42 - Successfully acquired change log lock 
04/05 12:41:45 [LibreClinica] NEWS WARN   l.p.c.x.LiquibaseEntityResolver:32 - Current XML parsers seems to not support EntityResolver2. External entities won't be correctly loaded 
 
... 137 times the same line ...

04/05 12:41:47 [LibreClinica] NEWS INFO   l.e.jvm.JdbcExecutor:42 - SELECT MD5SUM FROM public.databasechangelog WHERE MD5SUM IS NOT NULL LIMIT 1 
04/05 12:41:47 [LibreClinica] NEWS INFO   l.e.jvm.JdbcExecutor:42 - SELECT COUNT(*) FROM public.databasechangelog 
04/05 12:41:47 [LibreClinica] NEWS INFO   l.c.StandardChangeLogHistoryService:42 - Reading from public.databasechangelog 
04/05 12:41:47 [LibreClinica] NEWS INFO   l.e.jvm.JdbcExecutor:42 - SELECT * FROM public.databasechangelog ORDER BY DATEEXECUTED ASC, ORDEREXECUTED ASC 
04/05 12:41:48 [LibreClinica] NEWS INFO   l.l.StandardLockService:42 - Successfully released change log lock 
 

I have no idea what this means and what might happen.

[toskrip]

This warning does not seem to have any direct implication on the system function. It simply says that in classpath loaded XML parser (library) does not support the loading of external DTD files. This has to be understood as inability to use externally defined entities in the database model changesets definitions (will not be loaded correctly). It is kind of good because loading such entities into normally static changeset files could be considered as insecure (and I think it was disabled in newer liquibase anyway). The LC system changesets do not use externally defined entities, that is why I say it has no direct implications. I don't think it is possible to turn off this warning. The origin of the problem will not be in liquibase but in one of XML parsing libraries that the LC depends on. One would need to find of which one is causing the issue and if it is possible to get rid of it.