- logback-dev - mailman3.qos.ch

[continuum] BUILD ERROR: Log4j Bridge Module
by John Noreplai 15 Jan '07

15 Jan '07

Online report : http://localhost:8090/continuum/servlet/continuum/target/ProjectBuild.vm/vi… Build statistics: State: Error Previous Build: No previous build. Started at: Mon, 15 Jan 2007 20:17:06 +0100 Finished at: Mon, 15 Jan 2007 20:17:06 +0100 Total time: 0s Build Trigger: Forced Exit code: 0 Building machine hostname: pixie Operating system : Linux(unknown) Java version : 1.5.0_08(Sun Microsystems Inc.) Changes No files changed **************************************************************************** Build Error: **************************************************************************** Provider message: The svn command failed. Command output: ------------------------------------------------------------------------------- svn: PROPFIND request failed on '/repos/logback/trunk/log4j-bridge' svn: PROPFIND of '/repos/logback/trunk/log4j-bridge': Server certificate verification failed: issuer is not trusted (https://svn.qos.ch) -------------------------------------------------------------------------------

1 0

[continuum] BUILD ERROR: Log4j Bridge Module
by John Noreplai 15 Jan '07

15 Jan '07

Online report : http://localhost:8090/continuum/servlet/continuum/target/ProjectBuild.vm/vi… Build statistics: State: Error Previous State: Error Started at: Mon, 15 Jan 2007 20:14:19 +0100 Finished at: Mon, 15 Jan 2007 20:14:19 +0100 Total time: 0s Build Trigger: Forced Exit code: 0 Building machine hostname: pixie Operating system : Linux(unknown) Java version : 1.5.0_08(Sun Microsystems Inc.) Changes No files changed **************************************************************************** Build Error: **************************************************************************** Provider message: The svn command failed. Command output: ------------------------------------------------------------------------------- svn: PROPFIND request failed on '/repos/logback/trunk/log4j-bridge' svn: PROPFIND of '/repos/logback/trunk/log4j-bridge': Server certificate verification failed: issuer is not trusted (https://svn.qos.ch) -------------------------------------------------------------------------------

1 0

svn commit: r1221 - in logback/trunk: logback-examples/src/main/java/chapter4/conf logback-site/src/site/xdocTemplates/manual
by noreply.seb＠qos.ch 15 Jan '07

15 Jan '07

Author: seb Date: Mon Jan 15 20:03:13 2007 New Revision: 1221 Added: logback/trunk/logback-examples/src/main/java/chapter4/conf/logback-JMSQueue.xml logback/trunk/logback-examples/src/main/java/chapter4/conf/logback-JMSTopic.xml Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/appenders.xml Log: Added examples Added: logback/trunk/logback-examples/src/main/java/chapter4/conf/logback-JMSQueue.xml ============================================================================== --- (empty file) +++ logback/trunk/logback-examples/src/main/java/chapter4/conf/logback-JMSQueue.xml Mon Jan 15 20:03:13 2007 @@ -0,0 +1,19 @@ +<configuration> + + <appender name="Queue" + class="ch.qos.logback.classic.net.JMSQueueAppender"> + <InitialContextFactoryName> + org.apache.activemq.jndi.ActiveMQInitialContextFactory + </InitialContextFactoryName> + <ProviderURL>tcp://localhost:61616</ProviderURL> + <QueueConnectionFactoryBindingName> + ConnectionFactory + </QueueConnectionFactoryBindingName> + <QueueBindingName>MyQueue</QueueBindingName> + </appender> + + <root> + <level value="debug" /> + <appender-ref ref="Queue" /> + </root> +</configuration> \ No newline at end of file Added: logback/trunk/logback-examples/src/main/java/chapter4/conf/logback-JMSTopic.xml ============================================================================== --- (empty file) +++ logback/trunk/logback-examples/src/main/java/chapter4/conf/logback-JMSTopic.xml Mon Jan 15 20:03:13 2007 @@ -0,0 +1,19 @@ +<configuration> + + <appender name="Topic" + class="ch.qos.logback.classic.net.JMSTopicAppender"> + <InitialContextFactoryName> + org.apache.activemq.jndi.ActiveMQInitialContextFactory + </InitialContextFactoryName> + <ProviderURL>tcp://localhost:61616</ProviderURL> + <TopicConnectionFactoryBindingName> + ConnectionFactory + </TopicConnectionFactoryBindingName> + <TopicBindingName>MyTopic</TopicBindingName> + </appender> + + <root> + <level value="debug" /> + <appender-ref ref="Topic" /> + </root> +</configuration> \ No newline at end of file Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/appenders.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/manual/appenders.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/manual/appenders.xml Mon Jan 15 20:03:13 2007 @@ -1488,12 +1488,12 @@ publish-and-subscribe and point-to-point queuing. Logback supports the former model with <code>JMSTopicAppender</code> and the latter with <code>JMSQueueAppender</code> Both appenders extend the <code>JMSAppenderBase</code> class and - publish serialized events to a topic or queue specified by the user. - One or more <code>JMSTopicSink</code> or <code>JMSQueueSink</code> applications - can consume these serialized events. + publish serialized events to a topic or queue specified by the user. + One or more <code>JMSTopicSink</code> or <code>JMSQueueSink</code> applications + can register to a JMS server and consume the serialized events. The consumer of JMS appenders generated events need not be only <code>JMSTopicSink</code> or <code>JMSQueueSink</code> applications. Any application or MessageDrivenBean capable of subscribing to the appropriate topic or queue and consuming serialized @@ -1681,7 +1681,42 @@ before calling <code>InitialContext</code> constructor taking a Properties (i.e. Hashtable) parameter. - + + <h4>Comments on JMS appenders</h4> + + + Transmitting a packet of information using JMS is certain to be substantially + slower then sending the same packet using raw TCP sockets. JMS vendors bragging + about the performance of their messaging platform tend to omit this simple fact. + Guaranteed store and forward messaging comes at a hefty price. + In return for increased cost, JMS messaging provides decoupling of + sender and receiver. As long as the JMS provider is reachable, messages + will eventually arrive at destination. + However, what if the JMS server is down or simply unreachable? + + + + According to the JMS specification, producers can mark a message as either + persistent or non-persistent. The persistent delivery mode instructs the JMS provider + to log the message to stable storage as part of the client's send operation, allowing + the message to survive provider crashes. JMS appenders do not set the delivery + mode of messages it produces because according to the JMS specification, + the delivery mode is considered as an administered property. + + + + Once a message reaches the JMS provider, the provider assumes the responsibility + of delivering it to its destination, relieving the client from this chore. + What if the JMS server is unreachable? The JMS API provides an + <code>ExceptionListener</code> interface to deal with this situation. + When the client runtime of the JMS provider detects a lost connection to the JMS server, + it calls the <code>onException()</code> method of the registered + <code>ExceptionListener</code>. Once notified of the problem, client code can attempt + to reestablish the connection. According to the section 4.3.8 of the JMS specification, + the provider should attempt to resolve connection problems prior to notifying the client. + The JMS appenders do not implement the <code>ExceptionListener</code> interface. + + <a name="JMSTopicAppender" /> <h3>JMSTopicAppender</h3> @@ -1799,7 +1834,31 @@ </td> </tr> </table> + + + <code>JMSTopicAppender</code> is rather straightforward to configure: + + Example 4.8: JMSTopicAppender configuration (logback-examples/src/main/java/chapter4/conf/logback-JMSTopic.xml) +<div class="source"><pre><configuration> + + <appender name="Topic" + class="ch.qos.logback.classic.net.JMSTopicAppender"> + <InitialContextFactoryName> + org.apache.activemq.jndi.ActiveMQInitialContextFactory + </InitialContextFactoryName> + <ProviderURL>tcp://localhost:61616</ProviderURL> + <TopicConnectionFactoryBindingName> + ConnectionFactory + </TopicConnectionFactoryBindingName> + <TopicBindingName>MyTopic</TopicBindingName> + </appender> + + <root> + <level value="debug" /> + <appender-ref ref="Topic" /> + </root> +</configuration></pre></div> <a name="JMSQueueAppender" /> <h3>JMSQueueAppender</h3> @@ -1845,16 +1904,30 @@ </tr> </table> - jms comments - - diff topic/queue: client goes off and back online - - - - - - - + + A typical <code>JMSQueueAppender</code> configuration file looks very + similar to that of a <code>JMSTopicAppender</code>. + + Example 4.9: JMSQueueAppender configuration (logback-examples/src/main/java/chapter4/conf/logback-JMSQueue.xml) +<div class="source"><pre><configuration> + + <appender name="Queue" + class="ch.qos.logback.classic.net.JMSQueueAppender"> + <InitialContextFactoryName> + org.apache.activemq.jndi.ActiveMQInitialContextFactory + </InitialContextFactoryName> + <ProviderURL>tcp://localhost:61616</ProviderURL> + <QueueConnectionFactoryBindingName> + ConnectionFactory + </QueueConnectionFactoryBindingName> + <QueueBindingName>MyQueue</QueueBindingName> + </appender> + + <root> + <level value="debug" /> + <appender-ref ref="Queue" /> + </root> +</configuration></pre></div> <a name="SMTPAppender"/> <h3>SMTPAppender</h3> @@ -1985,7 +2058,7 @@ Here is a sample configuration file you can supply to chapter4.mail.Email: -Example 4.8: A sample <code>SMTPAppender</code> configuration (logback-examples/src/main/java/chapter4/mail/mail1.xml) +Example 4.10: A sample <code>SMTPAppender</code> configuration (logback-examples/src/main/java/chapter4/mail/mail1.xml) <div class="source"><pre><configuration> <appender name="EMAIL" class="ch.qos.logback.classic.net.SMTPAppender"> @@ -2071,7 +2144,7 @@ event evaluator whereby every 1024th event triggers an email message. -Example 4.9: A <code>EventEvaluator</code> implementation +Example 4.11: A <code>EventEvaluator</code> implementation that evaluates to <code>true</code> every 1024th event (<a href="../xref/chapter4/mail/CounterBasedEvaluator.html">logback-examples/src/main/java/chapter4/mail/CounterBasedEvaluator.java</a>) <div class="source"><pre>package chapter4.mail; @@ -2122,7 +2195,7 @@ as its event evaluator. -Example 4.10: <code>SMTPAppender</code> with custom +Example 4.12: <code>SMTPAppender</code> with custom <code>Evaluator</code> and buffer size (logback-examples/src/main/java/chapter4/mail/mail3.xml) <div class="source"><pre><configuration> @@ -2420,7 +2493,7 @@ The following configuration file is what one would need. -Example 4.11: <code>DBAppender</code> configuration (logback-examples/src/main/java/chapter4/db/append-toMySQL-with-driverManager.xml) +Example 4.13: <code>DBAppender</code> configuration (logback-examples/src/main/java/chapter4/db/append-toMySQL-with-driverManager.xml) <div class="source"><pre><configuration> <appender name="DB" class="ch.qos.logback.classic.db.DBAppender"> @@ -2499,7 +2572,7 @@ <code>javax.sql.DataSource</code>. -Example 4.12: <code>DBAppender</code> configuration (logback-examples/src/main/java/chapter4/db/append-with-datasource.xml) +Example 4.14: <code>DBAppender</code> configuration (logback-examples/src/main/java/chapter4/db/append-with-datasource.xml) <div class="source"><pre><configuration> <appender name="DB" class="ch.qos.logback.classic.db.DBAppender"> @@ -2611,7 +2684,7 @@ configuration file, logging events are sent to a MySQL database, without any pooling. -Example 4.13: <code>DBAppender</code> configuration without pooling (logback-examples/src/main/java/chapter4/db/append-toMySQL-with-datasource.xml) +Example 4.15: <code>DBAppender</code> configuration without pooling (logback-examples/src/main/java/chapter4/db/append-toMySQL-with-datasource.xml) <div class="source"><pre><configuration> <appender name="DB" class="ch.qos.logback.classic.db.DBAppender"> @@ -2647,7 +2720,7 @@ in the classpath. -Example 4.14: <code>DBAppender</code> configuration with pooling (logback-examples/src/main/java/chapter4/db/append-toMySQL-with-datasource-and-pooling.xml) +Example 4.16: <code>DBAppender</code> configuration with pooling (logback-examples/src/main/java/chapter4/db/append-toMySQL-with-datasource-and-pooling.xml) <div class="source"><pre><configuration> <appender name="DB" class="ch.qos.logback.classic.db.DBAppender"> @@ -2784,7 +2857,7 @@ Here is a sample configuration using a <code>SyslogAppender</code>. -Example 4.15: <code>SyslogAppender</code> configuration (logback-examples/src/main/java/chapter4/conf/logback-syslog.xml) +Example 4.17: <code>SyslogAppender</code> configuration (logback-examples/src/main/java/chapter4/conf/logback-syslog.xml) <div class="source"><pre><configuration> <appender name="SYSLOG" @@ -2849,7 +2922,7 @@ Here is a sample configuration of a <code>SMTPAppender</code> in the access environnement. -Example 4.15: <code>SMTPAppender</code> configuration (logback-examples/src/main/java/chapter4/conf/access/logback-smtp.xml) +Example 4.18: <code>SMTPAppender</code> configuration (logback-examples/src/main/java/chapter4/conf/access/logback-smtp.xml) <div class="source"><pre><appender name="SMTP" class="ch.qos.logback.access.net.SMTPAppender"> <layout class="ch.qos.logback.access.html.HTMLLayout"> @@ -3017,7 +3090,7 @@ Here is a sample configuration that uses <code>DBAppender</code>. - +Example 4.19: DBAppender configuration (logback-examples/src/main/java/chapter4/conf/access/logback-DB.xml) <div class="source"><pre><configuration> <appender name="DB" class="ch.qos.logback.access.db.DBAppender"> @@ -3050,7 +3123,7 @@ thus a few more methods are needed. -Example 4.16: <code>CountingConsoleAppender</code> (logback-examples/src/main/java/chapter4/CountingConsoleAppender.java) +Example 4.20: <code>CountingConsoleAppender</code> (logback-examples/src/main/java/chapter4/CountingConsoleAppender.java) <div class="source"><pre>package chapter4; import ch.qos.logback.core.AppenderBase;

1 0

svn commit: r1220 - logback-demo/src/main/resources
by noreply.seb＠qos.ch 15 Jan '07

15 Jan '07

Author: seb Date: Mon Jan 15 19:20:45 2007 New Revision: 1220 Modified: logback-demo/src/main/resources/logback.xml Log: on going work on demo documentation Modified: logback-demo/src/main/resources/logback.xml ============================================================================== --- logback-demo/src/main/resources/logback.xml (original) +++ logback-demo/src/main/resources/logback.xml Mon Jan 15 19:20:45 2007 @@ -28,19 +28,20 @@ </layout> </appender> -  +  -  <appender name="CYCLIC" class="ch.qos.logback.core.read.CyclicBufferAppender"> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator name="loggingTaskEval"> <expression> - logger.getName().contains("LoggingTask") && + logger.getName().contns("LoggingTask") && message.contains("Howdydy-diddly-ho") && (timeStamp - event.getStartTime()) >= 20000 </expression> @@ -49,7 +50,6 @@ </filter> <MaxSize>512</MaxSize> </appender> - --> <!-- PART III: TurboFilter: MDC value <turboFilter class="ch.qos.logback.classic.turbo.MDCFilter">

1 0

svn commit: r1219 - in logback/trunk: logback-classic/src/main/java/ch/qos/logback/classic/net logback-core/src/main/java/ch/qos/logback/core/net logback-site/src/site/xdocTemplates/manual
by noreply.seb＠qos.ch 15 Jan '07

15 Jan '07

Author: seb Date: Mon Jan 15 18:42:29 2007 New Revision: 1219 Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/net/JMSQueueAppender.java logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/net/JMSQueueSink.java logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/net/JMSTopicAppender.java logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/net/JMSTopicSink.java logback/trunk/logback-core/src/main/java/ch/qos/logback/core/net/JMSAppenderBase.java logback/trunk/logback-site/src/site/xdocTemplates/manual/appenders.xml Log: On going work on JMS*Appender doc Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/net/JMSQueueAppender.java ============================================================================== --- logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/net/JMSQueueAppender.java (original) +++ logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/net/JMSQueueAppender.java Mon Jan 15 18:42:29 2007 @@ -18,78 +18,18 @@ import javax.jms.QueueSession; import javax.jms.Session; import javax.naming.Context; -import javax.naming.InitialContext; import ch.qos.logback.classic.spi.LoggingEvent; +import ch.qos.logback.core.AppenderBase; import ch.qos.logback.core.net.JMSAppenderBase; /** * A simple appender that publishes events to a JMS Queue. The events are * serialized and transmitted as JMS message type {@link * javax.jms.ObjectMessage}. - * - * - * JMS {@link javax.jms.Queue queues} and - * {@link javax.jms.QueueConnectionFactory queue connection factories} are - * administered objects that are retrieved using JNDI messaging which in turn - * requires the retreival of a JNDI {@link Context}. - * * - * There are two common methods for retrieving a JNDI {@link 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: - * - * <pre> - * InitialContext jndiContext = new InitialContext(); - * </pre> - * - * - * Calling the no-argument <code>InitialContext()</code> method will also work - * from within Enterprise Java Beans (EJBs) because it is part of the EJB - * contract for application servers to provide each bean an environment naming - * context (ENC). - * - * - * In the second approach, several predetermined properties are set and these - * properties are passed to the <code>InitialContext</code> contructor to - * connect to the naming service provider. For example, to connect to JBoss - * naming service one would write: - * - * <pre> - * Properties env = new Properties(); - * env.put(Context.INITIAL_CONTEXT_FACTORY, - * "org.jnp.interfaces.NamingContextFactory"); - * env.put(Context.PROVIDER_URL, "jnp://hostname:1099"); - * env.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces"); - * InitialContext jndiContext = new InitialContext(env); - * </pre> - * - * where hostname is the host where the JBoss applicaiton server is - * running. - * - * - * To connect to the the naming service of Weblogic application server one would - * write: - * - * <pre> - * Properties env = new Properties(); - * env.put(Context.INITIAL_CONTEXT_FACTORY, - * "weblogic.jndi.WLInitialContextFactory"); - * env.put(Context.PROVIDER_URL, "t3://localhost:7001"); - * InitialContext jndiContext = new InitialContext(env); - * </pre> - * - * - * Other JMS providers will obviously require different values. - * - * The initial JNDI context can be obtained by calling the no-argument - * <code>InitialContext()</code> method in EJBs. Only clients running in a - * separate JVM need to be concerned about the jndi.properties file - * and calling {@link InitialContext#InitialContext()} or alternatively - * correctly setting the different properties before calling {@link - * InitialContext#InitialContext(java.util.Hashtable)} method. - * + * For more information about this appender, please refer to: + * http://logback.qos.ch/manual/appenders.html#JMSQueueAppender * * @author Ceki Gülcü */ @@ -113,8 +53,8 @@ * Its value will be used to lookup the appropriate * <code>QueueConnectionFactory</code> from the JNDI context. */ - public void setQueueConnectionFactoryBindingName(String tcfBindingName) { - this.qcfBindingName = tcfBindingName; + public void setQueueConnectionFactoryBindingName(String qcfBindingName) { + this.qcfBindingName = qcfBindingName; } /** @@ -216,7 +156,7 @@ } /** - * This method called by {@link AppenderSkeleton#doAppend} method to do most + * This method called by {@link AppenderBase#doAppend} method to do most * of the real appending work. */ public void append(LoggingEvent event) { Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/net/JMSQueueSink.java ============================================================================== --- logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/net/JMSQueueSink.java (original) +++ logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/net/JMSQueueSink.java Mon Jan 15 18:42:29 2007 @@ -45,24 +45,28 @@ private Logger logger = (Logger)LoggerFactory.getLogger(JMSTopicSink.class); static public void main(String[] args) throws Exception { - if (args.length != 2) { + if (args.length < 2) { usage("Wrong number of arguments."); } String qcfBindingName = args[0]; String queueBindingName = args[1]; -// String username = args[2]; -// String password = args[3]; + String username = null; + String password = null; + if (args.length == 4) { + username = args[2]; + password = args[3]; + } LoggerContext loggerContext = (LoggerContext) LoggerFactory .getILoggerFactory(); ContextInitializer.autoConfig(loggerContext); - new JMSQueueSink(qcfBindingName, queueBindingName, null, null); + new JMSQueueSink(qcfBindingName, queueBindingName, username, password); BufferedReader stdin = new BufferedReader(new InputStreamReader(System.in)); // Loop until the word "exit" is typed - System.out.println("Type \"exit\" to quit JMSSink."); + System.out.println("Type \"exit\" to quit JMSQueueSink."); while (true) { String s = stdin.readLine(); if (s.equalsIgnoreCase("exit")) { @@ -89,7 +93,7 @@ System.out.println("Queue found: " + queue.getQueueName()); QueueConnection queueConnection = queueConnectionFactory - .createQueueConnection(); + .createQueueConnection(username, password); System.out.println("Queue Connection created"); QueueSession queueSession = queueConnection.createQueueSession(false, @@ -113,7 +117,8 @@ if (message instanceof ObjectMessage) { ObjectMessage objectMessage = (ObjectMessage) message; event = (LoggingEvent) objectMessage.getObject(); - logger.callAppenders(event); + Logger log = (Logger) LoggerFactory.getLogger(event.getLoggerRemoteView().getName()); + log.callAppenders(event); } else { logger.warn("Received message is of type " + message.getJMSType() + ", was expecting ObjectMessage."); @@ -137,8 +142,8 @@ System.err.println(msg); System.err .println("Usage: java " - + JMSTopicSink.class.getName() - + " QueueConnectionFactoryBindingName QueueBindingName"); + + JMSQueueSink.class.getName() + + " QueueConnectionFactoryBindingName QueueBindingName Username Password"); System.exit(1); } } Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/net/JMSTopicAppender.java ============================================================================== --- logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/net/JMSTopicAppender.java (original) +++ logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/net/JMSTopicAppender.java Mon Jan 15 18:42:29 2007 @@ -18,9 +18,9 @@ import javax.jms.TopicPublisher; import javax.jms.TopicSession; import javax.naming.Context; -import javax.naming.InitialContext; import ch.qos.logback.classic.spi.LoggingEvent; +import ch.qos.logback.core.AppenderBase; import ch.qos.logback.core.net.JMSAppenderBase; /** @@ -28,68 +28,8 @@ * serialized and transmitted as JMS message type {@link * javax.jms.ObjectMessage}. * - * - * JMS {@link javax.jms.Topic topics} and - * {@link javax.jms.TopicConnectionFactory topic connection factories} are - * administered objects that are retrieved using JNDI messaging which in turn - * requires the retreival of a JNDI {@link Context}. - * - * - * There are two common methods for retrieving a JNDI {@link 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: - * - * <pre> - * InitialContext jndiContext = new InitialContext(); - * </pre> - * - * - * Calling the no-argument <code>InitialContext()</code> method will also work - * from within Enterprise Java Beans (EJBs) because it is part of the EJB - * contract for application servers to provide each bean an environment naming - * context (ENC). - * - * - * In the second approach, several predetermined properties are set and these - * properties are passed to the <code>InitialContext</code> contructor to - * connect to the naming service provider. For example, to connect to JBoss - * naming service one would write: - * - * <pre> - * Properties env = new Properties(); - * env.put(Context.INITIAL_CONTEXT_FACTORY, - * "org.jnp.interfaces.NamingContextFactory"); - * env.put(Context.PROVIDER_URL, "jnp://hostname:1099"); - * env.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces"); - * InitialContext jndiContext = new InitialContext(env); - * </pre> - * - * where hostname is the host where the JBoss applicaiton server is - * running. - * - * - * To connect to the the naming service of Weblogic application server one would - * write: - * - * <pre> - * Properties env = new Properties(); - * env.put(Context.INITIAL_CONTEXT_FACTORY, - * "weblogic.jndi.WLInitialContextFactory"); - * env.put(Context.PROVIDER_URL, "t3://localhost:7001"); - * InitialContext jndiContext = new InitialContext(env); - * </pre> - * - * - * Other JMS providers will obviously require different values. - * - * The initial JNDI context can be obtained by calling the no-argument - * <code>InitialContext()</code> method in EJBs. Only clients running in a - * separate JVM need to be concerned about the jndi.properties file - * and calling {@link InitialContext#InitialContext()} or alternatively - * correctly setting the different properties before calling {@link - * InitialContext#InitialContext(java.util.Hashtable)} method. - * + * For more information about this appender, please refer to + * http://logback.qos.ch/manual/appenders.html#JMSTopicAppender * * @author Ceki Gülcü */ @@ -217,7 +157,7 @@ /** - * This method called by {@link AppenderSkeleton#doAppend} method to do most + * This method called by {@link AppenderBase#doAppend} method to do most * of the real appending work. */ public void append(LoggingEvent event) { Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/net/JMSTopicSink.java ============================================================================== --- logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/net/JMSTopicSink.java (original) +++ logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/net/JMSTopicSink.java Mon Jan 15 18:42:29 2007 @@ -45,24 +45,28 @@ private Logger logger = (Logger)LoggerFactory.getLogger(JMSTopicSink.class); static public void main(String[] args) throws Exception { - if (args.length != 2) { + if (args.length < 2) { usage("Wrong number of arguments."); } String tcfBindingName = args[0]; String topicBindingName = args[1]; -// String username = args[2]; -// String password = args[3]; + String username = null; + String password = null; + if (args.length == 4) { + username = args[2]; + password = args[3]; + } LoggerContext loggerContext = (LoggerContext) LoggerFactory .getILoggerFactory(); ContextInitializer.autoConfig(loggerContext); - new JMSTopicSink(tcfBindingName, topicBindingName, null, null); + new JMSTopicSink(tcfBindingName, topicBindingName, username, password); BufferedReader stdin = new BufferedReader(new InputStreamReader(System.in)); // Loop until the word "exit" is typed - System.out.println("Type \"exit\" to quit JMSSink."); + System.out.println("Type \"exit\" to quit JMSTopicSink."); while (true) { String s = stdin.readLine(); if (s.equalsIgnoreCase("exit")) { @@ -89,7 +93,7 @@ System.out.println("Topic found: " + topic.getTopicName()); TopicConnection topicConnection = topicConnectionFactory - .createTopicConnection(); + .createTopicConnection(username, password); System.out.println("Topic Connection created"); TopicSession topicSession = topicConnection.createTopicSession(false, @@ -113,7 +117,8 @@ if (message instanceof ObjectMessage) { ObjectMessage objectMessage = (ObjectMessage) message; event = (LoggingEvent) objectMessage.getObject(); - logger.callAppenders(event); + Logger log = (Logger) LoggerFactory.getLogger(event.getLoggerRemoteView().getName()); + log.callAppenders(event); } else { logger.warn("Received message is of type " + message.getJMSType() + ", was expecting ObjectMessage."); @@ -138,7 +143,7 @@ System.err .println("Usage: java " + JMSTopicSink.class.getName() - + " TopicConnectionFactoryBindingName TopicBindingName"); + + " TopicConnectionFactoryBindingName TopicBindingName Username Password"); System.exit(1); } } Modified: logback/trunk/logback-core/src/main/java/ch/qos/logback/core/net/JMSAppenderBase.java ============================================================================== --- logback/trunk/logback-core/src/main/java/ch/qos/logback/core/net/JMSAppenderBase.java (original) +++ logback/trunk/logback-core/src/main/java/ch/qos/logback/core/net/JMSAppenderBase.java Mon Jan 15 18:42:29 2007 @@ -13,6 +13,9 @@ /** * This class serves as a base class for * JMSTopicAppender and JMSQueueAppender + * + * For more information about this appender, please refer to: + * http://logback.qos.ch/manual/appenders.html#JMSAppenderBase * * @author Ceki Gülcü * @author Sébastien Pennec Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/appenders.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/manual/appenders.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/manual/appenders.xml Mon Jan 15 18:42:29 2007 @@ -1811,10 +1811,39 @@ - It is working in a very similar manner to the <code>JMSTopicAppender</code>. + It works in a very similar manner to the <code>JMSTopicAppender</code>. - queue's own options + + Some options are proper to <code>JMSQueueAppender</code>. They are + listed below. + + + <table> + <tr> + <th>Option Name</th> + <th>Type</th> + <th>Description</th> + </tr> + <tr> + <td>QueueConnectionFactoryBindingName</td> + <td><code>String</code></td> + <td> + + The name of the queue factory. There is no default value for this mandatory option. + + </td> + </tr> + <tr> + <td>QueueBindingName</td> + <td><code>String</code></td> + <td> + + The name of the queue to use. There is no default value for this mandatory option. + + </td> + </tr> + </table> jms comments

1 0

svn commit: r1218 - logback/trunk/logback-site/src/site/xdocTemplates/manual
by noreply.seb＠qos.ch 15 Jan '07

15 Jan '07

Author: seb Date: Mon Jan 15 17:02:57 2007 New Revision: 1218 Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/appenders.xml Log: on going work on the JMS*Appender doc Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/appenders.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/manual/appenders.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/manual/appenders.xml Mon Jan 15 17:02:57 2007 @@ -1463,6 +1463,370 @@ tunnels the events it receives from its clients to a second server. + <a name="JMSAppenderBase" /> + <h3>JMSAppenderBase</h3> + + + The <a href="../xref/ch/qos/logback/core/net/JMSAppenderBase.html"> + <code>JMSAppenderBase</code></a> subclasses conceptually accomplishes + the same task as the <code>SocketAppender</code> but as the name + suggests it is based on the JMS API instead of TCP sockets. + JMS or the Java Message Service API + provides an abstraction for Message-Oriented Middleware (MOM) products. + One of the key architectural concepts in JMS is the decoupling of message + producers and message consumers. Senders do not have to wait for receivers + to handle messages and conversely the receiver consumes messages as they + become available; messages are said to be delivered asynchronously. Just as + importantly, consumers as well as producers can be added or removed at will + to a JMS channel. The set of the message producers and message consumers can + vary independently and transparently over time, with both sets oblivious + to each other. + + + + The JMS specification provides for two types of messaging models, + publish-and-subscribe and point-to-point queuing. Logback supports the former + model with <code>JMSTopicAppender</code> and the latter with <code>JMSQueueAppender</code> + Both appenders extend the <code>JMSAppenderBase</code> class and + publish serialized events to a topic or queue specified by the user. + One or more <code>JMSTopicSink</code> or <code>JMSQueueSink</code> applications + can consume these serialized events. + + + + The consumer of JMS appenders generated events need not be only <code>JMSTopicSink</code> + or <code>JMSQueueSink</code> applications. Any application or MessageDrivenBean + capable of subscribing to the appropriate topic or queue and consuming serialized + logging event messages would be suitable. + Additional consumers could be quickly built based on the <code>JMSTopicSink</code> or + <code>JMSQueueSink</code> model. + + + + Here are <code>JMSAppenderBase</code>'s options: + + + <table> + <tr> + <th>Option Name</th> + <th>Type</th> + <th>Description</th> + </tr> + <tr> + <td>InitialContextFactoryName</td> + <td><code>String</code></td> + <td> + + The class name of the initial JNDI context factory. There is no need + to set this option if you have a properly configured jndi.properties + file or if <code>JMSAppenderBase</code> subclass is running + within an application server. + + + If you set this option, you should + also set the ProviderURL option. + + </td> + </tr> + <tr> + <td>ProviderURL</td> + <td><code>String</code></td> + <td> + + This option specifies configuration information for the + JNDI service provider. The value of the property should contain a + URL string (e.g. ldap://somehost:389). + + + The ProviderURL option is taken into + account only if the InitialContextFactoryName + option is specified. It is ignored otherwise. + + </td> + </tr> + <tr> + <td>URLPkgPrefixes</td> + <td><code>String</code></td> + <td> + + This option contains the list of package prefixes to + use when loading in URL context factories. The value of the + property should be a colon-separated list of package + prefixes for the class name of the URL context factory class. + + + For JBoss the value of this option should be: + org.jboss.naming:org.jnp.interfaces + This option is not needed under Weblogic. + + + This option is taken into account only if the + InitialContextFactoryName + option is specified. It is ignored otherwise. + + </td> + </tr> + <tr> + <td>SecurityPrincipalName</td> + <td><code>String</code></td> + <td> + + The security principal name to use when accessing the JNDI namespace. + This option is usually not required. + + + This option is taken into account only if the + InitialContextFactoryName + option is specified. It is ignored otherwise. + + </td> + </tr> + <tr> + <td> + + SecurityCredentials + + </td> + <td> + <code>String</code> + </td> + <td> + + The security credentials to use when accessing the + JNDI namespace. This option is usually not required. + + + This option is taken into account only if the + + InitialContextFactoryName + + option is specified. It is ignored otherwise. + + </td> + </tr> + <tr> + <td> + + UserName + + </td> + <td> + <code>String</code> + </td> + <td> + + The username to use when creating a topic or queue connection. + + </td> + </tr> + <tr> + <td> + + Password + + </td> + <td> + <code>String</code> + </td> + <td> + + The password to use when creating a topic or queue connection. + + </td> + </tr> + </table> + + + JMS topics, queues and connection factories are administered objects that are obtained + using the JNDI API. This in turn implies the necessity of retrieving a JNDI Context. + There are two common methods for obtaining a JNDI 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, one simply calls: + + +<div class="source"><pre>InitialContext jndiContext = new InitialContext();</pre></div> + + + Calling the no-argument <code>InitialContext()</code> constructor will also work + from within Enterprise Java Beans (EJBs). + Indeed, it is part of the EJB contract for application servers to provide + each enterprise bean an environment naming context (ENC). + + + + In the second approach, several predetermined properties are specified. + These properties are passed to the <code>InitialContext</code> constructor + to connect to the naming service provider. + For example, to connect to an + <a href="http://www.activemq.org/site/home.html"><code>ActiveMQ</code></a> + naming server one would write: + + +<div class="source"><pre>Properties env = new Properties(); +env.put(Context.INITIAL_CONTEXT_FACTORY, "org.apache.activemq.jndi.ActiveMQInitialContextFactory"); +env.put(Context.PROVIDER_URL, "tcp://hostname:61616"); +Context ctx = new InitialContext(env);</pre></div> + + + where hostname is the host where the ActiveMQ server is running. + + + + Other JNDI providers will obviously require different values. + As mentioned previously, the initial JNDI context can be obtained by calling + the no-argument <code>InitialContext()</code> constructor from within EJBs. + Only clients running in a separate JVM need to be concerned about + the jndi.properties file or setting the different properties + before calling <code>InitialContext</code> constructor taking a + Properties (i.e. Hashtable) parameter. + + + <a name="JMSTopicAppender" /> + <h3>JMSTopicAppender</h3> + + + The <a href="../xref/ch/qos/logback/classic/net/JMSTopicAppender.html"> + <code>JMSTopicAppender</code></a> acts as a message producer to a publish and subscribe + Topic. + + + + Its most important method, <code>doAppend()</code> is listed below: + + +<div class="source"><pre>public void append(LoggingEvent event) { + if (!isStarted()) { + return; + } + + try { + ObjectMessage msg = topicSession.createObjectMessage(); + + msg.setObject(event); + topicPublisher.publish(msg); + successiveFailureCount = 0; + } catch (Exception e) { + successiveFailureCount++; + if (successiveFailureCount > SUCCESSIVE_FAILURE_LIMIT) { + stop(); + } + addError("Could not publish message in JMSTopicAppender [" + name + "].", e); + } +}</pre></div> + + + The <code>isStarted()</code> method allows the appender to check whether + prerequisite conditions for its proper functioning, in particular the + availability of a valid and open <code>TopicConnection</code> and a + <code>TopicSession</code>, are fulfilled. If that is not the case, + the append method returns without performing any work. + If the prerequisite conditions are fulfilled, then the method + proceeds to publish the logging event. This is done by obtaining a + <code>javax.jms.ObjectMessage</code> from the <code>TopicSession</code> + and then setting its payload to the logging event received as + the input parameter. Once the payload of the message is set, it is + published. The fact that <code>LoggingEvent</code> is serializable + has its importance, as only Serializable objects can be + transported within an <code>ObjectMessage</code>. + + + + In summary, the <code>JMSTopicAppender</code> broadcasts messages consisting + of a serialized <code>LoggingEvent</code> payload over a user-specified + JMS topic. These events can be processed by a + <a href="../xref/ch/qos/logback/classic/net/JMSTopicSink.html"> + <code>JMSTopicSink</code></a> + or a similar consumer. According to JMS specification, the provider + will asynchronously call the <code>onMessage()</code> of duly registered + and subscribed <code>javax.jms.MessageListener</code> objects. + The <code>onMessage()</code> method in <code>JMSTopicSink</code> + is implemented as follows: + + +<div class="source"><pre>public void onMessage(javax.jms.Message message) { + LoggingEvent event; + try { + if (message instanceof ObjectMessage) { + ObjectMessage objectMessage = (ObjectMessage) message; + event = (LoggingEvent) objectMessage.getObject(); + Logger log = (Logger) LoggerFactory.getLogger(event.getLoggerRemoteView().getName()); + log.callAppenders(event); + } else { + logger.warn("Received message is of type " + message.getJMSType() + + ", was expecting ObjectMessage."); + } + } catch (JMSException jmse) { + logger.error("Exception thrown while processing incoming message.", jmse); + } +}</pre></div> + + + The <code>onMessage()</code> method begins by retrieving the logging event's payload. + It then obtains a Logger with the same name as the logger name of the incoming event. + The event is then logged through this logger as if it were generated locally, + by calling its <code>callAppenders()</code> method. The <code>SocketNode</code> class used by + <code>SimpleSocketServer</code> handles incoming logging events essentially in the same way. + + + + Some options are proper to <code>JMSTopicAppender</code>. They are + listed below. + + + <table> + <tr> + <th>Option Name</th> + <th>Type</th> + <th>Description</th> + </tr> + <tr> + <td>TopicConnectionFactoryBindingName</td> + <td><code>String</code></td> + <td> + + The name of the topic factory. There is no default value for this mandatory option. + + </td> + </tr> + <tr> + <td>TopicBindingName</td> + <td><code>String</code></td> + <td> + + The name of the topic to use. There is no default value for this mandatory option. + + </td> + </tr> + </table> + + + <a name="JMSQueueAppender" /> + <h3>JMSQueueAppender</h3> + + + The <a href="../xref/ch/qos/logback/classic/net/JMSQueueAppender.html"> + <code>JMSQueueAppender</code></a> acts as a message producer to a point-to-point + Queue. + + + + It is working in a very similar manner to the <code>JMSTopicAppender</code>. + + + queue's own options + + jms comments + + diff topic/queue: client goes off and back online + + + + + + + + <a name="SMTPAppender"/> <h3>SMTPAppender</h3>

1 0

[continuum] BUILD ERROR: Log4j Bridge Module
by John Noreplai 15 Jan '07

15 Jan '07

Online report : http://localhost:8090/continuum/servlet/continuum/target/ProjectBuild.vm/vi… Build statistics: State: Error Previous State: Error Started at: Mon, 15 Jan 2007 14:34:09 +0100 Finished at: Mon, 15 Jan 2007 14:34:09 +0100 Total time: 0s Build Trigger: Forced Exit code: 0 Building machine hostname: pixie Operating system : Linux(unknown) Java version : 1.5.0_08(Sun Microsystems Inc.) Changes No files changed **************************************************************************** Build Error: **************************************************************************** Provider message: The svn command failed. Command output: ------------------------------------------------------------------------------- svn: PROPFIND request failed on '/repos/logback/trunk/log4j-bridge' svn: PROPFIND of '/repos/logback/trunk/log4j-bridge': Server certificate verification failed: issuer is not trusted (https://svn.qos.ch) -------------------------------------------------------------------------------

1 0

[continuum] BUILD ERROR: Log4j Bridge Module
by John Noreplai 15 Jan '07

15 Jan '07

Online report : http://localhost:8090/continuum/servlet/continuum/target/ProjectBuild.vm/vi… Build statistics: State: Error Previous State: Error Started at: Mon, 15 Jan 2007 12:40:06 +0100 Finished at: Mon, 15 Jan 2007 12:40:06 +0100 Total time: 0s Build Trigger: Schedule Exit code: 0 Building machine hostname: pixie Operating system : Linux(unknown) Java version : 1.5.0_08(Sun Microsystems Inc.) Changes No files changed **************************************************************************** Build Error: **************************************************************************** Provider message: The svn command failed. Command output: ------------------------------------------------------------------------------- svn: PROPFIND request failed on '/repos/logback/trunk/log4j-bridge' svn: PROPFIND of '/repos/logback/trunk/log4j-bridge': Server certificate verification failed: issuer is not trusted (https://svn.qos.ch) -------------------------------------------------------------------------------

1 0

[continuum] BUILD ERROR: Log4j Bridge Module
by John Noreplai 15 Jan '07

15 Jan '07

Online report : http://localhost:8090/continuum/servlet/continuum/target/ProjectBuild.vm/vi… Build statistics: State: Error Previous State: Error Started at: Mon, 15 Jan 2007 12:20:06 +0100 Finished at: Mon, 15 Jan 2007 12:20:06 +0100 Total time: 0s Build Trigger: Schedule Exit code: 0 Building machine hostname: pixie Operating system : Linux(unknown) Java version : 1.5.0_08(Sun Microsystems Inc.) Changes No files changed **************************************************************************** Build Error: **************************************************************************** Provider message: The svn command failed. Command output: ------------------------------------------------------------------------------- svn: PROPFIND request failed on '/repos/logback/trunk/log4j-bridge' svn: PROPFIND of '/repos/logback/trunk/log4j-bridge': Server certificate verification failed: issuer is not trusted (https://svn.qos.ch) -------------------------------------------------------------------------------

1 0

[continuum] BUILD ERROR: Log4j Bridge Module
by John Noreplai 15 Jan '07

15 Jan '07

Online report : http://localhost:8090/continuum/servlet/continuum/target/ProjectBuild.vm/vi… Build statistics: State: Error Previous State: Error Started at: Mon, 15 Jan 2007 12:19:54 +0100 Finished at: Mon, 15 Jan 2007 12:19:54 +0100 Total time: 0s Build Trigger: Forced Exit code: 0 Building machine hostname: pixie Operating system : Linux(unknown) Java version : 1.5.0_08(Sun Microsystems Inc.) Changes No files changed **************************************************************************** Build Error: **************************************************************************** Provider message: The svn command failed. Command output: ------------------------------------------------------------------------------- svn: PROPFIND request failed on '/repos/logback/trunk/log4j-bridge' svn: PROPFIND of '/repos/logback/trunk/log4j-bridge': Server certificate verification failed: issuer is not trusted (https://svn.qos.ch) -------------------------------------------------------------------------------

1 0