Several questions and some bug reporting on 1.7.0pre0.
Engine
----------
Should a running engine pick automatically pick up on changes to a process definition (such as changes to etc/engine/cron.xml) if it is defined as a <service> in etc/engine/engine-configuration.xml? Is a restart required because I simply change the message string in cron and I'm not seeing that reflected in history.log without engine restart.
Logging
-----------
1. In a previous message, John Mettraux said that
'The HistoryService has its parameters in2. I cannot find any mechanism for controlling pyya-apre logging verbosity. All I can see is that standard error and standard output are redirected to $LOG in bin/pyya-apre.sh (which for some reason, logging is still going to the console). The output has entries like INFO, so presumably this is controllable.
etc/engine/engine-configuration.xml, it's not following log4j
directives, but takes some inspiration from them.'
While I see a service entry for "history", I don't see any parameters for logging granularity. How is granularity specified?
3. My first attempt to control granularity of apre.log doesn't seem to have worked. I'm still getting DEBUG and INFO for [main].
I tried this:
<category name="org.apache.axis">
<priority value="ERROR">
<appender-ref ref="axis-file" />
</category>
<category name="openwfe.org">
<priority value="ERROR">
<appender-ref ref="file" />
</category>
<root>
<priority value="ERROR" />
<appender-ref ref="file" />
</root>
Any suggestions?
It would be nice if the manual/book had an explicit section on logging that covers all logging.
pyya-apre
--------------
I found that the following pyya-apre files probably should be modified.
openwfe/engine/participant.py
DEFAULT_PMAP_FILE = 'etc/engine/participant-map.xml'
bin/pyya-apre.sh (ditto for pyya-apre.bat)
PYTHONPATH=$PYTHONPATH:$ETC/lib
pyya-apre-scripts/ToPdfAgent.py (ditto for EmailNotificationAgent.py)
from openwfe.apre import Agent
thanks,
Tony Bigbee
