Hi Jake, No problem..
I'll change the code to work the way it used to: If there is no remoteHost property, look for a remoteSourceInfo property and set a remoteHost property based on the host portion of remoteSourceInfo. You can then use a PROP.remoteHost tab identifier to route all events from the same host (regardless of port) to a single tab. I'll try and get this to this tonight, but I don't think there will be a WebStart build (grab the trunk and build it). Look for the commit on the dev list. Scott -----Original Message----- From: Jacob Kjome [mailto:[EMAIL PROTECTED] Sent: Mon 12/27/2004 7:41 PM To: Log4J Users List Cc: Subject: RE: Receiver Problem?? BTW, Scott, I tried using the "PROP.log4j.remoteSourceInfo" field identifier and it worked to put different connections to different tabs. However, I found it odd that ever time I restarted Tomcat, a new tab was created for each app using a SocketAppender. I had to right click on the old tabs and choose "Hide" to keep them from building up. Is there a way that the same app can continue to log to the same tab across appserver restarts? Jake At 08:51 AM 12/27/2004 -0800, you wrote: >You can use any of the 'Supported field identifiers' described in the >'Expressions' section of the tutorial as well as any other text you'd like >to include (usually separators between identifiers). > >For example: > >To display events with a common severity on single tab (creating DEBUG, >INFO, WARN etc. tabs), set the tab identifier to LEVEL. > > >-----Original Message----- >From: Shai Simchi [mailto:[EMAIL PROTECTED] >Sent: Mon 12/27/2004 8:08 AM >To: Log4J Users List >Cc: >Subject: RE: Receiver Problem?? >what other oprions can i use in that field ? >is there any document regarding that ? >thanks, >Shai > >-----Original Message----- >From: Scott Deboy [mailto:[EMAIL PROTECTED] >Sent: Thursday, December 23, 2004 7:18 PM >To: Log4J Users List >Subject: RE: Receiver Problem?? > > >I'm sure I caused this once Chainsaw started generating logging events itself. > >Assuming you're using a 1.2.8 socketappender: > >Go to the view menu, show application wide preferences > >On the general tab, set this as the the tab identifier field's value: >PROP.log4j.remoteSourceInfo > >This will route unique remoteSourceInfo entries (every unique connection) to >its own tab. > >I'll see if I can get this fixed. > > >-----Original Message----- >From: Jacob Kjome [mailto:[EMAIL PROTECTED] >Sent: Thu 12/23/2004 9:11 AM >To: Log4J Users List >Cc: >Subject: RE: Receiver Problem?? > >I'm seeing this as well. I happens with the latest update to the Webstart >version of chainsaw. Previous to that I saw separate tabs for >socketappenders coming from different remote hosts. Currently, my one >socket appender is appending to localhost, but there was still used to be a >separate tab for localhost. Now all Chainsaw logging along with my app >logging goes to the "chainsaw-log" tab. > >Jake > >At 01:06 PM 12/23/2004 +0200, you wrote: > >Hi Scott ! > >I am using xml as my configuration file and turning the location infro > >helped me too. > >the thing is all incoming messages are going into the same tab - >"chainsaw-log" > >is there a way to control the tabs - i am using 2 SocketAppender and each > >one is directed to a different port and i need each of these to be in a > >different tab. > >does anyone have an idea on that ? > >thanks, > >Shai > > > >-----Original Message----- > >From: Vance Cochrane [mailto:[EMAIL PROTECTED] > >Sent: Wednesday, December 22, 2004 10:11 PM > >To: Log4J Users List > >Subject: Re: Receiver Problem?? > > > > > >Scott, > >Thanks. that fixed the problem. > >vance > > > > > >On Wed, 22 Dec 2004 11:36:43 -0800, Scott Deboy > ><[EMAIL PROTECTED]> wrote: > >> LocationInfo has been moved to a new package, so Chainsaw can't receive > >events which contain file/line/method information if it's sent by a 1.2.8 > >socketappender. > >> > >> In your appender config, move the SocketAppender to first in the list and > >everything should work fine again (and make sure locationInfo is not true on > >the Socketappender config). > >> > >> FileAppender patterns that display file/line/class etc., modify the > >logging event - adding LocationInfo that's then used by appenders below it > >in the list - so moving SocketAppender to the top at least allows you to > >receive events. > >> > >> > >> -----Original Message----- > >> From: Vance Cochrane [mailto:[EMAIL PROTECTED] > >> Sent: Wed 12/22/2004 11:18 AM > >> To: [email protected] > >> Cc: > >> Subject: Receiver Problem?? > >> Just a quick question. I had chainsaw dutifully logging everything as > >> normal to a SocketAppender on the network.. > >> Then I upgraded chainsaw (to the latest rev) and now I am not > >> receiving any of the messages that I was receiving before. No logging > >> code or any other code changed. Was there any configuration change > >> that I should have made? Thanks. > >> -- > >> Vance > >> > >> --------------------------------------------------------------------- > >> 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] > >> > >> > > > > > >-- > >Vance Cochrane > >Cochrane Consulting, Inc. > >PO Box 854 Belmont, CA 94002 > >Voice: 415-412-3062 > >Fax: 415-651-9364 > >Email: [EMAIL PROTECTED] > >Web: http://www.ecochrane.com > > > >--------------------------------------------------------------------- > >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] > > > > > > >--------------------------------------------------------------------- >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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
