One thing on the sandbox net package: XML-based appenders (UDPAppender/MulticastAppender), don't handle the case where the xml-ized event size is > buffer size..the receivers (actually the xmldecoders) correctly deal with this issue, but I had to kick the buffer size up to temporarily get around this problem for some Jboss-generated events that I wanted to see in Chainsaw V2.
Should be a simple fix (tear the event up into buffer-size pieces and send in order) but I haven't had time.. -----Original Message----- From: Mark Womack [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 17, 2003 2:06 PM To: 'Log4J Developers List' Subject: RE: Receivers & Chainsaw Paul, We need to do a review of all the o.a.log4j.net changes. I think we should coordinate an "official" review so we can start to move the changes into the core. A threshold setting on receivers has been suggested previously. I'll see about adding it later today. If you want to look at it before then, please have no hesitation about checking a modified version into the sandbox. I'm starting to think that checking modified versions of the core classes into the sandbox is a nice way to explore changes and allow others to comment and make changes. So, I was going to check my modified version there anyway. We could add a specific "pause" functionality for plugins. I haven't thought that through completely though. Just stopping and re-starting the plugin wouldn't be sufficient? BTW, I think your idea for the receiver dialog box is most excellent. -Mark > -----Original Message----- > From: Paul Smith [mailto:[EMAIL PROTECTED] > Sent: Monday, June 16, 2003 9:20 PM > To: Log4j-Dev (E-mail) > Subject: Receivers & Chainsaw > > > Hi Mark & Ceki(& everyone else), > > I've started checking some mods to SocketReceiver into the > sandbox. Would > anyone mind taking a peek at what I've done, and provide any feedback? > > What I'm attempting to do is provide a dialog box for > Chainsaw that shows > all the Receivers in a little hierarchy, and show each > Receiver with any > children, if they have any. e.g. for a Socket Receiver, show all the > currently connected socket details with IP/hostname & port. > (you can see > this by starting up chainsaw and choosing the View->Show > Receivers... menu > item. ) > > I'd then like the user to be able to start/stop a specific > plugin via the > GUI, and either disconnect, or "pause" a Net-based receiver. > Perhaps by > setting some threshold for a Receiver? Could we have a Threshold on a > receiver too, just like an Appender? This could be in > addition (but just > prior) to passing it through the localLogger's own threshold. > > This pause option would be particularly handy, because > currently Chainsaw > only has a pause that is very late in the event reception > cycle (just about > as late as you can get), be nice to cut all that work off at > the knees as > early as possible and tell a specific Receiver, or even > SocketNode to just > "forgetaboutit", and then resume when you are interested in > monitoring the > events. > > cheers, > > Paul Smith > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
