With the latest developer snapshot from http://people.apache.org/~sdeboy

See the 'Welcome' tab in Chainsaw, and click 'View example Receiver
Configuration' toolbar button.

Copy and paste that to a file, and remove all of the plugin entries except for:

 <plugin name="XMLSocketReceiver"
class="org.apache.log4j.net.XMLSocketReceiver">
      <param name="decoder" value="org.apache.log4j.xml.UtilLoggingXMLDecoder"/>
      <param name="Port" value="2222"/>
   </plugin>

And modify that port to match what you need, and save as
chainsaw-config-util-logging-socket.xml or something like that.

Then, in Chainsaw, select File, Load Chainsaw configuration, use a
Chainsaw config file, open file, browse to that
chainsaw-config-util-logging-socket.xml file, and click ok.

You should start seeing your events show up in the UI.

Scott

On 5/16/16, Ray Tayek <rta...@ca.rr.com> wrote:
> hi,  please excuse me if this is the wrong place to post, but i am new
> to log4j and chainsaw.
>
> i posted this question
> <http://stackoverflow.com/questions/37239400/apache-chainsaw-v2-gets-bind-exception-or-connection-lost-invalid-stream-he>,
>
> but have no results yet.
>
> jigsaw seems kinda dead, is this what people still use to monitor logs
> from socket handlers or should i look at something more recent?
>
> any pointers will be appreciated.
>
> thanks
>
> --
> Honesty is a very expensive gift. So, don't expect it from cheap people -
> Warren Buffett
> http://tayek.com/
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org

Reply via email to