+1
I've wandered through the website and checked the rat report, I don't have
time to pull down the sources and try to build myself.
Great work Stefa.
Scott
On Fri, Oct 7, 2011 at 4:54 AM, Stefan Bodewig wrote:
> On 2011-10-06, Stefan Bodewig wrote:
>
> > Votes, please. This vote will close
[
https://issues.apache.org/jira/browse/LOG4NET-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874276#action_12874276
]
Scott Deboy commented on LOG4NET-259:
-
Generally I would prefer that the l
[
https://issues.apache.org/jira/browse/LOG4NET-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874242#action_12874242
]
Scott Deboy commented on LOG4NET-259:
-
The tab routing mechanism is configurable,
The tab routing mechanism is configurable, see application-wide preferences,
general, 'tab identifier' field.
You can provide any valid Chainsaw identifier or property name (or just a
fixed string, if you want all events to go to the same tab)..
The default value is:
PROP.hostname - PROP.applicat
Another option you may find useful: use a file appender instead of a UDP
appender, and configure Chainsaw to use a LogFilePatternReceiver (which will
parse and tail the log file).
There are two versions of LogFilePatternReceiver - the 'regular' version
(which can process files using file: and http
I'd use something like wireshark on the destination machine to ensure the
machine can see the udp packets on the network. I'd suggest you're seeing a
Windows-specific network firewall issue (Windows is probably blocking UDP
traffic to your machine unless you explicitly allow the box to receive the
g
Room with AV conference:
http://www.comotivsystems.com/ourProduct/images/CollabRmVidConfWeb.jpg
If you're interested, send me your email address and I'll create the
account!
Scott Deboy
Principal Engineer
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR
