Home >> All >> org >> apache >> log4j >> [ net Javadoc ]

•	org.apache.log4j.net.test.* (4)

• org.apache.log4j.net: Javadoc index of package org.apache.log4j.net.


Package Samples:

• org.apache.log4j.net.test: Package for remote logging.  

Classes:

• SocketHubAppender: Sends org.apache.log4j.spi.LoggingEvent objects to a set of remote log servers, usually a SocketNodes . Acts just like SocketAppender except that instead of connecting to a given remote log server, SocketHubAppender accepts connections from the remote log servers as clients. It can accept more than one connection. When a log event is received, the event is sent to the set of currently connected remote log servers. Implemented this way it does not require any update to the configuration file to send data to another remote log server. The remote log server simply connects to the host and port the ...
• SocketAppender: Sends org.apache.log4j.spi.LoggingEvent objects to a remote a log server, usually a SocketNode . The SocketAppender has the following properties: If sent to a SocketNode , remote logging is non-intrusive as far as the log event is concerned. In other words, the event will be logged with the same time stamp, org.apache.log4j.NDC , location info as if it were logged locally by the client. SocketAppenders do not use a layout. They ship a serialized org.apache.log4j.spi.LoggingEvent object to the server side. Remote logging uses the TCP protocol. Consequently, if the server is reachable, then log events ...
• JMSAppender: A simple appender that publishes events to a JMS Topic. The events are serialized and transmitted as JMS message type javax.jms.ObjectMessage . JMS topics and topic connection factories are administered objects that are retrieved using JNDI messaging which in turn requires the retreival of a JNDI javax.naming.Context . There are two common methods for retrieving a JNDI javax.naming.Context . If a file resource named jndi.properties is available to the JNDI API, it will use the information found therein to retrieve an initial JNDI context. To obtain an initial context, your code will simply call: ...
• SocketServer: A SocketNode based server that uses a different hierarchy for each client. Usage: java org.apache.log4j.net.SocketServer port configFile configDir where port is a part number where the server listens, configFile is a configuration file fed to the org.apache.log4j.PropertyConfigurator and configDir is a path to a directory containing configuration files, possibly one for each client host. The configFile is used to configure the log4j default hierarchy that the SocketServer will use to report on its actions. When a new connection is opened from a previously unknown host, say foo.bar.net , then the ...
• DatagramStringAppender: Use DatagramStringAppender to send log messages to a remote daemon which accepts Datagram (UDP) messages. The benefits of UDP are that the client is guarunteed not to slow down if the network or remote log daemon is slow, and that no permanent TCP connection between client and server exists. The disadvantages are that log messages can be lost if the network or remote daemon are under excessive load. This class builts the final message string before sending the UDP packet, hence the "string" component in the class name. This means that the receiving application can be written in any language. The ...
• TelnetAppender: The TelnetAppender is a log4j appender that specializes in writing to a read-only socket. The output is provided in a telnet-friendly way so that a log can be monitored over TCP/IP. Clients using telnet connect to the socket and receive log data. This is handy for remote monitoring, especially when monitoring a servlet. Here is a list of the available configuration options: Name Requirement Description Sample Value Port optional This parameter determines the port to use for announcing log events. The default port is 23 (telnet). 5875
• SimpleSocketServer: A simple SocketNode based server. Usage: java org.apache.log4j.net.SimpleSocketServer port configFile where port is a part number where the server listens and configFile is a configuration file fed to the org.apache.log4j.PropertyConfigurator or to org.apache.log4j.xml.DOMConfigurator if an XML file.
• SMTPAppender: Send an e-mail when a specific logging event occurs, typically on errors or fatal errors. The number of logging events delivered in this e-mail depend on the value of BufferSize option. The SMTPAppender keeps only the last BufferSize logging events in its cyclic buffer. This keeps memory requirements at a reasonable level while still delivering useful application context.
• SocketNode: Read org.apache.log4j.spi.LoggingEvent objects sent from a remote client using Sockets (TCP). These logging events are logged according to local policy, as if they were generated locally. For example, the socket node might decide to log events to a local file and also resent them to a second socket node.
• JMSSink: A simple application that consumes logging events sent by a JMSAppender .
• DatagramStringWriter: DatagramStringWriter is a wrapper around the java.net.DatagramSocket class so that it behaves like a java.io.Writer.
• SyslogAppender: Use SyslogAppender to send log messages to a remote syslog daemon.
• DefaultEvaluator
• Loop
• SMTPMin
• SocketMin
• SyslogMin

Home | Contact Us | Privacy Policy | Terms of Service