Interoperability component which translates our log4cpp events to log4cxx events and sends them to a network/socket appender. More...
#include <Log4cxxAppender.hpp>
Inheritance diagram for Log4cxxAppender:
Public Member Functions | |
| Log4cxxAppender (std::string name) | |
Protected Member Functions | |
| virtual bool | configureHook () |
| virtual void | updateHook () |
| virtual void | cleanupHook () |
Protected Attributes | |
| log4cxx::helpers::Pool | p |
| log4cxx::net::SocketAppender * | socketAppender |
| log4cxx::helpers::InetAddressPtr | address |
| RTT::InputPort< OCL::logging::LoggingEvent > | log_port |
| Port we receive logging events on Initially unconnected. More... | |
| std::string | hostname_prop |
| Name of host to append to. | |
| int | port_prop |
| The port where the logging server runs. | |
| int | maxEventsPerCycle_prop |
| Property to set maximum number of log events to pop per cycle. | |
| int | maxEventsPerCycle |
| Maximum number of log events to pop per cycle. More... | |
Detailed Description
Interoperability component which translates our log4cpp events to log4cxx events and sends them to a network/socket appender.
Definition at line 40 of file Log4cxxAppender.hpp.
Member Data Documentation
|
protected |
Port we receive logging events on Initially unconnected.
The logging service connects appenders.
Definition at line 57 of file Log4cxxAppender.hpp.
|
protected |
Maximum number of log events to pop per cycle.
Defaults to 0.
A value of 0 indicates to not limit the number of events per cycle. With enough event production, this could lead to thread starvation!
Definition at line 78 of file Log4cxxAppender.hpp.
The documentation for this class was generated from the following files:
