Hi Tim,

The Beehive NetUI Logger class leverages commons-logging to create loggers
for NetUI messages. You could configure your logging such that the
PageFlowRequestProcessor is logged at a warning or error level and leave the
rest of your app at info level logging.

The internal default logger for NetUI uses log4j. You could add a
WEB-INF/classes/log4j.xml file to your NetUI web app that has an entry
specific for the PageFlowRequestProcessor. Something like...

 <category name="org.apache.beehive.netui.pageflow.PageFlowRequestProcessor
">
   <priority value="warn"/>
   <appender-ref ref="BEEHIVE_CONSOLE_LOG"/>
 </category>

...where "BEEHIVE_CONSOLE_LOG" is the desired appender you define.


You can also open a request in JIRA to change the log level of the shared
flow message you identified from info to debug or trace.

https://issues.apache.org/jira/browse/BEEHIVE


On a side note, it would be great to hear about what you're doing with AJAX
and NetUI integration. Based on posts to this list in the past about AJAX,
some of the other beehive users and devs might be interested in what you're
doing. What framework are you using on the client?

Kind regards,
Carlin

On 7/10/06, Seears, Tim B <[EMAIL PROTECTED]> wrote:

Hi,

I've been using Beehive on the Sun Java App Server 8.1 for a while now
but there's something which is increasingly causing me a problem, and I
couldn't find any answer in the docs/faq/tutorials.

Beehive seems to produce a lot of unnecessary log entries, and now I'm
making extensive use of AJAX to commnicate to the client behind the
scenes, the log is filling up with too much unwanted information.  The
main culprit is log lines like:
[#|2006-07-10T14:38:25.401+0100|INFO|sun-appserver-pe8.1_01|org.apache.b
eehive.netui.pageflow.PageFlowRequestProcessor|_ThreadID=17;|Attempting
to instantiate SharedFlowControllers for request
/MAGDA/plot/viewJobStatus.do|#]

The "attempting to instantiate SharedFlowControllers" log info message
appears on every request, for every action, (not just the first time
after a restart) and I'm not even using any shared flow controllers!
Since some of my AJAX xml requests are called every 1 second in the
background, for every user logged in, this is a lot of log entries!

Is there a way to disable these non-error log messages in beehive, or
turn it down to a quieter level?  I don't want to disable the INFO log
level on the server because it is required for other things.  Surely the
above kind of message should be logged as FINE?

Thanks,
Tim



Reply via email to