-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fatal exception with malformed MessageCenter.log4j.properties file #84
Comments
Stack trace from a batch run:
|
Possible source location of error in batch: Line 85 in 200de2e
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the MessageCenter.log4j.properties file in the project root is out of date or malformed in some way, the runtime will throw an exception. This can happen with the GUI runtime and in batch. We should perform input validation on the MessageCenter.log4j.properties file and use a default configuration if missing, and throw a warning instead.
The MessageCenter.log4j.properties can be out of data from a Repast 1.x model or user-edited incorrectly, so we should account for multiple paths that can corrupt the file.
The text was updated successfully, but these errors were encountered: