Hi all, Recently when writing the README for the Java Broker I happened to try out various options while starting the broker under various circumstances to make sure I understood the functionality of each directive. And, it seemed that there is a timer that can be configured to refresh the settings specified through log4j.xml. However, during the process of modifying the log4j.xml, if I do make a blunder in xml layout which will cause the xml parser to throw an exception stating that the XML is invalid, the whole log-config watching mechanism comes to a halt.
This can be reproduced by starting the broker as, "./qpid-server -w 2" and editing the log4j.xml found inside ../etc, and replacing "<!DOCTYPE" with "<DOCTYPE". What I would like to know is whether this was intentional or un-intentional, so that if it was un-intentional, I would like to work on a fix for this issue. Your openion is greatly appreciated. Regards, Senaka
