Re: Logging problem

greghuber-Ij2Ovbx4fFtWk0Htik3J/[email protected]
Newsgroups gmane.comp.java.openjms.user
Message-ID <OF37248505.0C581B3F-ON80256FAC.0039B452-80256FAC.003A1571@ricoh-uk.com>
Hans,

We use the log4j.xml below.  Rolling file appender.

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">

<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/">

   <appender name="STDOUT" class="org.apache.log4j.RollingFileAppender">
      <param name="File" value="/openjms/openjmsConsole.log"/>
      <param name="MaxFileSize" value="150KB"/>
      <param name="MaxBackupIndex" value="3"/>
      <layout class="org.apache.log4j.PatternLayout">
         <param name="ConversionPattern" value="%d{HH:mm:ss.SSS} %-5p [%t] 
- %m\n"/>
      </layout>
   </appender>

   <appender name="openjms" class="org.apache.log4j.RollingFileAppender">
      <param name="File" value="/openjms/openjms.log"/>
      <param name="MaxFileSize" value="150KB"/>
      <param name="MaxBackupIndex" value="3"/>
      <layout class="org.apache.log4j.PatternLayout">
         <param name="ConversionPattern" value="%d{HH:mm:ss.SSS} %-5p [%t] 
- %m\n"/>
      </layout>
   </appender>

   <category name="org.exolab">
      <priority value="WARN"/>
      <appender-ref ref="STDOUT"/>
      <appender-ref ref="openjms"/>
   </category>

</log4j:configuration>

Cheers Greg




[email protected]
Sent by: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
18/02/2005 09:59
Please respond to openjms-user

 
        To:     [email protected]
        cc: 
        Subject:        [openjms-user] Logging problem


Hi,
i have a problem with a log printout that shows up in our application´s 
log. These are the lines that gets printed every 15th second. We have 
tried to change the log4j.properties both in the client jar and the 
log4j.properties in teh server.  We have also tried and used a local 
log4j.properies described in http://openjms.sourceforge.net/faq.html#logging-log4j-client, but none of these methods seem´s to have any effect. We have also tried 
to change the ping frequence in the openjms.xml file in the server. Any 
ideas on how to stop this print out? The log file grows very fast because 
of this.

This is the printout: 

09:10:49 sun.rmi.server.UnicastRef.invoke() FINARE: AWT-EventQueue-0: 
method: public abstract void 
org.exolab.jms.server.rmi.RemoteJmsServerSessionIfc.sendMessage(javax.jms.Message) 
throws javax.jms.JMSException,java.rmi.RemoteException
09:10:49 sun.rmi.server.UnicastRef FINARE: AWT-EventQueue-0: outbound 
call: 
[endpoint:[192.168.1.32:2414](remote),objID:[1b8d6f7:102247bdef6:-8000, 
10]] : 
org.exolab.jms.server.rmi.RmiJmsServerSession_Stub[1b8d6f7:102247bdef6:-8000, 
10]: public abstract void 
org.exolab.jms.server.rmi.RemoteJmsServerSessionIfc.sendMessage(javax.jms.Message) 
throws javax.jms.JMSException,java.rmi.RemoteException
09:10:49 sun.rmi.transport.tcp.TCPChannel.newConnection() FIN: 
AWT-EventQueue-0: reuse connection
09:10:49 sun.rmi.server.UnicastRef.invoke() FINARE: AWT-EventQueue-0: 
opnum = 5824962805738609408
09:10:49 sun.rmi.transport.StreamRemoteCall.<init>() FINARE: 
AWT-EventQueue-0: write remote call header...
09:10:49 sun.rmi.transport.StreamRemoteCall.getOutputStream() FINARE: 
AWT-EventQueue-0: getting output stream
09:10:49 sun.rmi.transport.StreamRemoteCall.getInputStream() FINARE: 
AWT-EventQueue-0: getting input stream
09:10:49 sun.rmi.server.UnicastRef.invoke() FIN: AWT-EventQueue-0: free 
connection (reuse = true)
09:10:49 sun.rmi.transport.tcp.TCPChannel.free() FIN: AWT-EventQueue-0: 
reuse connection

----------------------------------------------------- 
Hans Larsson 
PPM PremiePensionsmyndigheten 
Utvecklingsenheten 
Box 1605 
111 86 Stockholm 
Tel växel : 08 406 50 00 
Tel direkt: 08 406 52 73 
Tel mobil: 0733 406 103 
[email protected] 
www.ppm.nu 
----------------------------------------------------- 
  
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.