It resolves to another dictionary custom class which contain a property called "_SIGNATURE" which may have or not a string value according to the instance of the class. The string is the signature of the package (here it's ADAM) which is flagged in the registry during the installation.
Yes, everyone has read on all custom classes and object of the dictionary.
1 of 1 people found this helpful
There’s some debug we could try to enable.
In the log4j.properties for your deployment add:
and wait a couple min for it to get picked up, then run the compliance job again and see if this puts anything useful into the logs ?
I did as you said and modified log4j.properties file to implement debug for compliance.
I ran my compliance job and here is the capture from appserver.log.
I see a very long SQL qeury and nothing happens after.
Failed_compliance_job.log 452.6 K
I see this message over and over in your log:
[Job-Execution-1] [DEBUG] [BLAdmin:BLAdmins:] [Compliance] Unable to find String resource: enum_data_type_legal_value.--2003322.0.display_name in com.bladelogic.model.util.CoreDatamessages
java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key enum_data_type_legal_value.--2003322.0.display_name
My guess is this has something to do with the string value you're using. Either it doesn't exist or it's not recognizing the value has String.
In our Communities I searched for "enum_data_type_legal_value" and found this explanation:
"All that message means is that a string value it was looking for is not in a properties file (which is a normal occurance)."
it's possible that the job is having an issue expanding the smart component group that is being used as a target. can you try creating a simple smart component group like (NAME contains blah) and see if you can target such a group ?
the next step will be to run the job and grab a sql profiler log from the database.