Hi
Look, these are 4 tables associated with the problem:
select * from maximo.maxprop where propname = 'mxe.logging.disableLoggingPropFile';
select * from maximo.maxpropvalue where propname = 'mxe.logging.disableLoggingPropFile';
select * from maximo.maxlogger;
select * from maximo.maxlogappender;
You should be query the tables to see if you can detect any erroneous data.
The problem seems to occur in the loadSettingsFromDB method of the MXLoggerFactory class
(java.lang.StringIndexOutOfBoundsException: begin 0, end -1, length 8
at java.lang.String.substring(String.java:2744)
at psdi.util.logging.MXLoggerFactory.loadSettingsFromDB(MXLoggerFactory.java:457)
This method attempts to load logging configurations from the database and fails when manipulating a string (possibly attempting to split a string into components).
Regards!