1. the simple one: ./configure --disable-log4j does the right thing but gives the output "log4j enabled" anyway. A simple copy-and-paste-error in the configure script.
2. the harder one: log4j tries to connect to localhost:4448 whether it's disabled or not. As nothing listens on that port on my machine the programs using log4j hang here (i.e. introspect and the tests)
Jan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
bug 1 is fixed, but bug 2 is not reproducible here. val1_server starts normally if chainsaw is waiting or not. If the problem still exists, please give me more information about your environment in the bug tracker.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I have two problems with the buitlin log4j.
1. the simple one: ./configure --disable-log4j does the right thing but gives the output "log4j enabled" anyway. A simple copy-and-paste-error in the configure script.
2. the harder one: log4j tries to connect to localhost:4448 whether it's disabled or not. As nothing listens on that port on my machine the programs using log4j hang here (i.e. introspect and the tests)
Jan
bug 1 is fixed, but bug 2 is not reproducible here. val1_server starts normally if chainsaw is waiting or not. If the problem still exists, please give me more information about your environment in the bug tracker.
if log4j is NOT disabled, try running "make distclean" in your build directory to start from scratch.