Yeah, the filename opens perfectly in a browser. I've tried it both with a
patternlayout and with the xmllayout, the xmllayout never says Connected in
zero conf. Right now I'm using a complete copy and paste of the config
file you put in SO.
I do see a receiver listed, and I can right click to tell it I'd like to
see trace, but that's all I can get it to do. Restarting the receiver
doesn't seem to do anything. Double clicking does nothing.
--M@
On Fri, May 10, 2013 at 2:07 PM, Scott Deboy <scott.de...@gmail.com> wrote:
> When Chainsaw starts you don't need to give it a config, as the config
> will be generated once the advertisement is discovered.
>
> If you have a row in ZeroConf with your appender name, that's great.
>
> Maybe the advertiseURI in your log4j appender configuration is wrong?
> Copy and paste that into a browser to see if it opens your log file.
> If not, you need to put in the right URI for your log file and restart
> the app..and maybe Chainsaw..not sure if updates to advertisements
> work - haven't tried it.
>
> Also, are you using a patternlayout? You need to
> (VFSLogFilePatternReceiver doesn't support XMLLayout).
>
> You should see a receiver defined in the receiver window...if it's not
> showing anything it's because the advertiseURI you provided wasn't
> quite right.
>
> On 5/10/13, M@ <matthew.dun...@gmail.com> wrote:
> > Right, I followed you, I'm using it in my app, what I meant was when
> > Chainsaw starts it asks me if I want to open a log4j config file so I
> > select the one the app is using and click Ok. I hadn't notice this
> before
> > because my window was too small, but at the status bar at the bottom it
> > tells me the result of that was {}.
> >
> > Good call, I did have the jmdns line commented out in the classpath from
> > last night's debugging, so that's back in, and now zeroconf is much
> closer
> > to working. The only remaining problem is that although the zeroconf tab
> > says Connected no tab has popped up. Double clicking the row toggles it
> > between Connected ant Not Connected, but I can't see any of the messages
> > that should be streaming in. Giving the receiver a level doesn't seem to
> > fix it either. Any idea what the problem is?
> >
> > Also it seems that one of the restarts has fixed the horizontal resizing
> > issue I'd been seeing.
> >
> > --M@
> >
> > On Fri, May 10, 2013 at 1:13 PM, Scott Deboy <scott.de...@gmail.com>
> wrote:
> >
> >> So a couple of things - the config I posted was a Log4j2 config to use
> >> on the appender side. Make sure your app is using that appender
> >> configuration.
> >>
> >> This allows Chainsaw to begin parsing and tailing your log file
> >> without you having to tell Chainsaw about the fileappender
> >> configuration.
> >>
> >> Once you have started your app that is using the appender
> >> configuration I provided, just open the 'zeroconf' tab in Chainsaw.
> >> You should see a row with your appender's name (assuming you added
> >> jmdns to the classpath for the app using the fileappender
> >> configuration).
> >>
> >> You can click 'autoconnect' if you'd like to always start Chainsaw
> >> with this configuration if it is available. Next, just double-click
> >> on the row and Chainsaw will start parsing and tailing your log file
> >> - assuming the advertised URL your used in your file appender
> >> configuration is accessible by Chainsaw (looks like you are working
> >> locally with Chainsaw and your fileappender, so file:// paths will
> >> work fine).
> >>
> >> On 5/10/13, M@ <matthew.dun...@gmail.com> wrote:
> >> > Thanks for the quick response! I pulled down your custom build and
> >> > it's
> >> > definitely fixed some things (notably the "please load a config file"
> >> intro
> >> > screen), but I'm still not getting it.
> >> >
> >> > I pointed chainsaw at the config file you posted on SO but it didn't
> >> > seem
> >> > to cause chainsaw to do anything (no recievers defined, zeroconf still
> >> did
> >> > nothing). After that I tried opening the log file but it wouldn't
> >> > open.
> >> > When I switched the logging format back to XMLLayout chainsaw could
> >> > manually open it, but it still didn't tail. Could the not tailing be
> >> > related to the XML format? Is there a more tail-friendly format that
> >> will
> >> > open?
> >> >
> >> > On an unrelated note, in the new version the horizontal resizing (of
> >> > the
> >> > recievers pane and the pane on the other side) seems to be broken,
> it's
> >> not
> >> > really a problem, just a heads up.
> >> >
> >> > --M@
> >> >
> >> > On Fri, May 10, 2013 at 11:48 AM, Scott Deboy <scott.de...@gmail.com>
> >> > wrote:
> >> >
> >> >> Thanks for posting to the dev list!
> >> >>
> >> >> I've commented on your stackoverflow post. There were a few issues.
> >> >>
> >> >> - Stale docs (sorry)
> >> >> - No support in Chainsaw V2 for Log4j2 socketappenders yet
> >> >> - Chainsaw wasn't setting up a 'tailing' log file receiver
> >> >> configuration for the advertised fileappender
> >> >>
> >> >> Those are all fixed, and I commented on the stackoverflow post.
> >> >>
> >> >> Thanks much!
> >> >>
> >> >>
> >> >>
> >> >> On 5/10/13, M@ <matthew.dun...@gmail.com> wrote:
> >> >> > Hi all, I'm trying to get a basic hello world log message to stream
> >> >> > from
> >> >> > log4j2 (beta 5, the binary release as of yesterday) to chainsaw v2
> >> >> > (also
> >> >> > the binary release as of yesterday). None of my guesses as to what
> >> >> > to
> >> >> > put
> >> >> > into log4j2.xml have proven fruitful. I'm also asking this question
> >> >> > on
> >> >> > stack overflow (
> >> >> >
> >> >>
> >>
> http://stackoverflow.com/questions/16474939/log4j2-to-chainsaw-hello-world-not-working-what-am-i-doing-wrong
> >> >> )
> >> >> > if you'd like to get some goodness points in exchange for the
> answer
> >> >> > (otherwise I'll copy whatever I get working to there and keep the
> >> >> goodness
> >> >> > points for myself).
> >> >> >
> >> >> > My config file is posted in the SO question, but I'd be just as
> >> >> > happy
> >> >> > scrapping the whole thing and pasting in something that ought to
> >> >> > work,
> >> >> > whichever is easier. Thanks for your help!
> >> >> >
> >> >> > --M@
> >> >> >
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
> >> >> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
> >> >>
> >> >>
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
> >> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
> For additional commands, e-mail: log4j-dev-h...@logging.apache.org
>
>
