7 Replies Latest reply on Jul 24, 2006 9:02 AM by franco lazzari

    unable to configure logging

    franco lazzari Newbie

      Well, I understand it is my fault, but I am not able to understand how logging works in JbossCache.

      Let's say:

      1) Simple standalone application starting a TreeCache: log4j.xml (the one shipped with JbossCache) is in the classpath.
      Output produced (either with or without -Dlog4j.configuration=log4j.xml parameter):


      [INFO] PropertyConfigurator - -Found existing property editor for org.w3c.dom.Element: org.jboss.util.propertyeditor.ElementEditor@79dc36
      [INFO] PropertyConfigurator - -configure(): attribute size: 13
      [INFO] TreeCache - -setting cluster properties from xml to: UDP(bind_addr=1.6.64.159;ip_mcast=true;ip_ttl=64;loopback=true;mcast_addr=228.1.2.3;mcast_port=48866;mcast_recv_buf_size=80000;mcast_send_buf_size=150000;ucast_recv_buf_size=80000;ucast_send_buf_size=150000):PING(down_thread=false;num_initial_members=3;timeout=2000;up_thread=false):MERGE2(max_interval=20000;min_interval=10000):FD_SOCK:VERIFY_SUSPECT(down_thread=false;timeout=1500;up_thread=false):pbcast.NAKACK(down_thread=false;gc_lag=50;max_xmit_size=8192;retransmit_timeout=600,1200,2400,4800;up_thread=false):UNICAST(down_thread=false;min_threshold=10;timeout=600,1200,2400;window_size=100):pbcast.STABLE(desired_avg_gossip=20000;down_thread=false;up_thread=false):FRAG(down_thread=false;frag_size=8192;up_thread=false):pbcast.GMS(join_retry_timeout=2000;join_timeout=5000;print_local_addr=true;shun=true):pbcast.STATE_TRANSFER(down_thread=true;up_thread=true)
      [INFO] TreeCache - -interceptor chain is:
      class org.jboss.cache.interceptors.CallInterceptor
      class org.jboss.cache.interceptors.LockInterceptor
      class org.jboss.cache.interceptors.UnlockInterceptor
      class org.jboss.cache.interceptors.ReplicationInterceptor
      [INFO] TreeCache - -cache mode is REPL_SYNC
      [INFO] UDP - -sockets will use interface 1.6.64.159
      [INFO] UDP - -socket information:
      local_addr=1.6.64.159:4611, mcast_addr=228.1.2.3:48866, bind_addr=ic2302299.ic.intra.infocamere.it/1.6.64.159, ttl=64
      sock: bound to 1.6.64.159:4611, receive buffer size=80000, send buffer size=150000
      mcast_recv_sock: bound to 1.6.64.159:48866, send buffer size=150000, receive buffer size=80000
      mcast_send_sock: bound to 1.6.64.159:4612, send buffer size=150000, receive buffer size=80000
      [INFO] TreeCache - -viewAccepted(): new members: [1.6.64.159:4611]
      [INFO] TreeCache - -new cache is null (maybe first member in cluster)
      [INFO] TreeCache - -state could not be retrieved (must be first member in group)
      -------------------------------------------------------
      GMS: address is 1.6.64.159:4611
      -------------------------------------------------------

      Then I modify, delete, add entries in log4j.xml: nothing happens. The output remains the same above.


      2) JBossCache used inside Weblogic: nothing is displayed. Only the line:
      -------------------------------------------------------
      GMS: address is 1.6.64.159:4611
      -------------------------------------------------------
      And nothing, related with JBossCache, is present in Weblogic logs.

      Could you kindly post something like a short tutorial on JBosscache logging?

      TIA
      matabo

        • 1. Re: unable to configure logging
          Manik Surtani Master

          Hi,

          We just use bog-standard Log4J. Nothing special, no tricks here. :-)

          Make sure your log4j.xml file is in your classpath, I suppose. That would help. Perhaps WebLogic's class loader cannot find it? Is it in the same package as your application, e.g.,in the same EAR or WAR file?

          Cheers,
          Manik

          • 2. Re: unable to configure logging
            franco lazzari Newbie

            Well. lets' start with the "simple" case:

            This is the source of java stand alone program:

            package cachiamo;
            import org.jboss.cache.*;
            public class Principale {
            public static void main(String[] args) throws Exception {
            TreeCache tree = new TreeCache();
            PropertyConfigurator config = new PropertyConfigurator();
            config.configure(tree, "META-INF/mioreplSync-service.xml");
            tree.setClusterName("pippo");
            tree.startService();
            tree.destroyService();
            }
            }
            __________________________________
            This is log4j.xml contents:

            <?xml version="1.0" encoding="UTF-8"?>
            <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">

            <!-- ===================================================================== -->
            <!-- -->
            <!-- Log4j Configuration -->
            <!-- -->
            <!-- ===================================================================== -->

            <!-- $Id: log4j.xml,v 1.5 2005/06/09 15:54:45 bela Exp $ -->

            <!--
            | For more configuration infromation and examples see the Jakarta Log4j
            | owebsite: http://jakarta.apache.org/log4j
            -->

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

            <!-- ================================= -->
            <!-- Preserve messages in a local file -->
            <!-- ================================= -->

            <!-- A time/date based rolling appender -->




            <!-- Rollover at midnight each day -->
            <param name="DatePattern" value="'.'yyyy-MM-dd"/>

            <!-- Rollover at the top of each hour
            <param name="DatePattern" value="'.'yyyy-MM-dd-HH"/>
            -->



            <!-- The default pattern: Date Priority [Category] Message\n -->


            <!-- The full pattern: Date MS Priority [Category] (Thread:NDC) Message\n

            -->



            <!-- ============================== -->
            <!-- Append messages to the console -->
            <!-- ============================== -->






            <!-- The default pattern: Date Priority [Category] Message\n -->





            <!-- ================ -->
            <!-- Limit categories -->
            <!-- ================ -->

            <!-- Limit JBoss categories to INFO



            -->

            <!-- Increase the priority threshold for the DefaultDS category



            -->

            <!-- Decrease the priority threshold for the org.jboss.varia category



            -->

            <!--
            | An example of enabling the custom TRACE level priority that is used
            | by the JBoss internals to diagnose low level details. This example
            | turns on TRACE level msgs for the org.jboss.ejb.plugins package and its
            | subpackages. This will produce A LOT of logging output.



            -->













            <!-- ======================= -->
            <!-- Setup the Root category -->
            <!-- ======================= -->


            <appender-ref ref="CONSOLE"/>
            <!-- <appender-ref ref="FILE"/>-->


            </log4j:configuration>

            (it is just the log4j.xml shipped with JBosscache distribution)
            ______________________________________


            This is the launch command of the program:

            Q:\remote\jdk\jdk1.3.1_05\bin\java -Dlog4j.configuration=log4j.xml -classpath "C:\JBuilder8\progetti\cache\xml;P:\bea\weblogic700\server\lib\weblogic.jar;C:\JBuilder8\progetti\cache\classes;D:\jbosscachebueo\jdk13\commons-logging.jar;D:\jbosscachebueo\jdk13\concurrent.jar;D:\jbosscachebueo\jdk13\javassist.jar;D:\jbosscachebueo\jdk13\jboss-cache.jar;D:\jbosscachebueo\jdk13\jboss-common.jar;D:\jbosscachebueo\jdk13\jboss-jmx.jar;D:\jbosscachebueo\jdk13\jboss-system.jar;D:\jbosscachebueo\jdk13\jgroups-all.jar;Q:\remote\jdk\jdk1.3.1_05\jre\lib\i18n.jar;Q:\remote\jdk\jdk1.3.1_05\jre\lib\jaws.jar;Q:\remote\jdk\jdk1.3.1_05\jre\lib\rt.jar;Q:\remote\jdk\jdk1.3.1_05\jre\lib\sunrsasign.jar;Q:\remote\jdk\jdk1.3.1_05\lib\dt.jar;Q:\remote\jdk\jdk1.3.1_05\lib\htmlconverter.jar;Q:\remote\jdk\jdk1.3.1_05\lib\tools.jar" cachiamo.Principale

            (Directory C:\JBuilder8\progetti\cache\xml contains file logj4.xml and file META-INF\mioreplSync-service.xml. This directory is, of course, in the classpath.)
            _____________________________________
            The output produced is:

            [INFO] PropertyConfigurator - -Found existing property editor for org.w3c.dom.Element: org.jboss.util.propertyeditor.ElementEditor@5d173
            [INFO] PropertyConfigurator - -configure(): attribute size: 13
            [INFO] TreeCache - -setting cluster properties from xml to: UDP(bind_addr=1.6.64.159;ip_mcast=true;ip_ttl=64;loopback=true;mcast_addr=228.1.2.3;mcast_port=48866;mcast_recv_buf_size=80000;mcast_send_buf_size=150000;ucast_recv_buf_size=80000;ucast_send_buf_size=150000):PING(down_thread=false;num_initial_members=3;timeout=2000;up_thread=false):MERGE2(max_interval=20000;min_interval=10000):FD_SOCK:VERIFY_SUSPECT(down_thread=false;timeout=1500;up_thread=false):pbcast.NAKACK(down_thread=false;gc_lag=50;max_xmit_size=8192;retransmit_timeout=600,1200,2400,4800;up_thread=false):UNICAST(down_thread=false;min_threshold=10;timeout=600,1200,2400;window_size=100):pbcast.STABLE(desired_avg_gossip=20000;down_thread=false;up_thread=false):FRAG(down_thread=false;frag_size=8192;up_thread=false):pbcast.GMS(join_retry_timeout=2000;join_timeout=5000;print_local_addr=true;shun=true):pbcast.STATE_TRANSFER(down_thread=true;up_thread=true)
            [INFO] TreeCache - -interceptor chain is:
            class org.jboss.cache.interceptors.CallInterceptor
            class org.jboss.cache.interceptors.LockInterceptor
            class org.jboss.cache.interceptors.UnlockInterceptor
            class org.jboss.cache.interceptors.ReplicationInterceptor
            [INFO] TreeCache - -cache mode is REPL_SYNC
            [INFO] UDP - -sockets will use interface 1.6.64.159
            [INFO] UDP - -socket information:
            local_addr=1.6.64.159:2625, mcast_addr=228.1.2.3:48866, bind_addr=ic2302299.ic.intra.infocamere.it/1.6.64.159, ttl=64
            sock: bound to 1.6.64.159:2625, receive buffer size=80000, send buffer size=150000
            mcast_recv_sock: bound to 1.6.64.159:48866, send buffer size=150000, receive buffer size=80000
            mcast_send_sock: bound to 1.6.64.159:2626, send buffer size=150000, receive buffer size=80000
            [INFO] TreeCache - -viewAccepted(): new members: [1.6.64.159:2625]
            [INFO] TreeCache - -new cache is null (maybe first member in cluster)
            [INFO] TreeCache - -state could not be retrieved (must be first member in group)
            ______________________________

            Then, I removed the file log4j.xml from directory C:\JBuilder8\progetti\cache\xml. The output produced is:

            [INFO] PropertyConfigurator - -Found existing property editor for org.w3c.dom.Element: org.jboss.util.propertyeditor.ElementEditor@5d173
            [INFO] PropertyConfigurator - -configure(): attribute size: 13
            [INFO] TreeCache - -setting cluster properties from xml to: UDP(bind_addr=1.6.64.159;ip_mcast=true;ip_ttl=64;loopback=true;mcast_addr=228.1.2.3;mcast_port=48866;mcast_recv_buf_size=80000;mcast_send_buf_size=150000;ucast_recv_buf_size=80000;ucast_send_buf_size=150000):PING(down_thread=false;num_initial_members=3;timeout=2000;up_thread=false):MERGE2(max_interval=20000;min_interval=10000):FD_SOCK:VERIFY_SUSPECT(down_thread=false;timeout=1500;up_thread=false):pbcast.NAKACK(down_thread=false;gc_lag=50;max_xmit_size=8192;retransmit_timeout=600,1200,2400,4800;up_thread=false):UNICAST(down_thread=false;min_threshold=10;timeout=600,1200,2400;window_size=100):pbcast.STABLE(desired_avg_gossip=20000;down_thread=false;up_thread=false):FRAG(down_thread=false;frag_size=8192;up_thread=false):pbcast.GMS(join_retry_timeout=2000;join_timeout=5000;print_local_addr=true;shun=true):pbcast.STATE_TRANSFER(down_thread=true;up_thread=true)
            [INFO] TreeCache - -interceptor chain is:
            class org.jboss.cache.interceptors.CallInterceptor
            class org.jboss.cache.interceptors.LockInterceptor
            class org.jboss.cache.interceptors.UnlockInterceptor
            class org.jboss.cache.interceptors.ReplicationInterceptor
            [INFO] TreeCache - -cache mode is REPL_SYNC
            [INFO] UDP - -sockets will use interface 1.6.64.159
            [INFO] UDP - -socket information:
            local_addr=1.6.64.159:2631, mcast_addr=228.1.2.3:48866, bind_addr=ic2302299.ic.intra.infocamere.it/1.6.64.159, ttl=64
            sock: bound to 1.6.64.159:2631, receive buffer size=80000, send buffer size=150000
            mcast_recv_sock: bound to 1.6.64.159:48866, send buffer size=150000, receive buffer size=80000
            mcast_send_sock: bound to 1.6.64.159:2632, send buffer size=150000, receive buffer size=80000
            [INFO] TreeCache - -viewAccepted(): new members: [1.6.64.159:2631]
            [INFO] TreeCache - -new cache is null (maybe first member in cluster)
            [INFO] TreeCache - -state could not be retrieved (must be first member in group)


            (I dont' see any difference.)
            __________________________________


            Then, I modified log4j.xml in this way:

            I modified WARN in the following lines with FATAL









            This is the output after the modification:

            [INFO] PropertyConfigurator - -Found existing property editor for org.w3c.dom.Element: org.jboss.util.propertyeditor.ElementEditor@5d173
            [INFO] PropertyConfigurator - -configure(): attribute size: 13
            [INFO] TreeCache - -setting cluster properties from xml to: UDP(bind_addr=1.6.64.159;ip_mcast=true;ip_ttl=64;loopback=true;mcast_addr=228.1.2.3;mcast_port=48866;mcast_recv_buf_size=80000;mcast_send_buf_size=150000;ucast_recv_buf_size=80000;ucast_send_buf_size=150000):PING(down_thread=false;num_initial_members=3;timeout=2000;up_thread=false):MERGE2(max_interval=20000;min_interval=10000):FD_SOCK:VERIFY_SUSPECT(down_thread=false;timeout=1500;up_thread=false):pbcast.NAKACK(down_thread=false;gc_lag=50;max_xmit_size=8192;retransmit_timeout=600,1200,2400,4800;up_thread=false):UNICAST(down_thread=false;min_threshold=10;timeout=600,1200,2400;window_size=100):pbcast.STABLE(desired_avg_gossip=20000;down_thread=false;up_thread=false):FRAG(down_thread=false;frag_size=8192;up_thread=false):pbcast.GMS(join_retry_timeout=2000;join_timeout=5000;print_local_addr=true;shun=true):pbcast.STATE_TRANSFER(down_thread=true;up_thread=true)
            [INFO] TreeCache - -interceptor chain is:
            class org.jboss.cache.interceptors.CallInterceptor
            class org.jboss.cache.interceptors.LockInterceptor
            class org.jboss.cache.interceptors.UnlockInterceptor
            class org.jboss.cache.interceptors.ReplicationInterceptor
            [INFO] TreeCache - -cache mode is REPL_SYNC
            [INFO] UDP - -sockets will use interface 1.6.64.159
            [INFO] UDP - -socket information:
            local_addr=1.6.64.159:2923, mcast_addr=228.1.2.3:48866, bind_addr=ic2302299.ic.intra.infocamere.it/1.6.64.159, ttl=64
            sock: bound to 1.6.64.159:2923, receive buffer size=80000, send buffer size=150000
            mcast_recv_sock: bound to 1.6.64.159:48866, send buffer size=150000, receive buffer size=80000
            mcast_send_sock: bound to 1.6.64.159:2924, send buffer size=150000, receive buffer size=80000
            [INFO] TreeCache - -viewAccepted(): new members: [1.6.64.159:2923]
            [INFO] TreeCache - -new cache is null (maybe first member in cluster)
            [INFO] TreeCache - -state could not be retrieved (must be first member in group)


            Output doesn't change. I am not able to control the behavior of logging in JBosscache/JGroups.

            regards
            matabo

            • 3. Re: unable to configure logging
              jaikiran pai Master

              Post the contents of your log4j.xml file(Use the Code button above to enclose the contents in a code block). Also, where are you seeing this output? Is it on the console or some log file?

              • 4. Re: unable to configure logging
                franco lazzari Newbie

                 

                <?xml version="1.0" encoding="UTF-8"?>
                <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
                
                <!-- ===================================================================== -->
                <!-- -->
                <!-- Log4j Configuration -->
                <!-- -->
                <!-- ===================================================================== -->
                
                <!-- $Id: log4j.xml,v 1.5 2005/06/09 15:54:45 bela Exp $ -->
                
                <!--
                 | For more configuration infromation and examples see the Jakarta Log4j
                 | owebsite: http://jakarta.apache.org/log4j
                 -->
                
                <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/" debug="false">
                
                 <!-- ================================= -->
                 <!-- Preserve messages in a local file -->
                 <!-- ================================= -->
                
                 <!-- A time/date based rolling appender -->
                 <appender name="FILE" class="org.jboss.logging.appender.DailyRollingFileAppender">
                 <param name="File" value="test.log"/>
                 <param name="Append" value="false"/>
                
                 <!-- Rollover at midnight each day -->
                 <param name="DatePattern" value="'.'yyyy-MM-dd"/>
                
                 <!-- Rollover at the top of each hour
                 <param name="DatePattern" value="'.'yyyy-MM-dd-HH"/>
                 -->
                 <param name="Threshold" value="DEBUG"/>
                
                 <layout class="org.apache.log4j.PatternLayout">
                 <!-- The default pattern: Date Priority [Category] Message\n -->
                 <param name="ConversionPattern" value="%d %-5p [%c] (%t) %m%n"/>
                
                 <!-- The full pattern: Date MS Priority [Category] (Thread:NDC) Message\n
                 <param name="ConversionPattern" value="%d %-5r %-5p [%c] (%t:%x) %m%n"/>
                 -->
                 </layout>
                 </appender>
                
                 <!-- ============================== -->
                 <!-- Append messages to the console -->
                 <!-- ============================== -->
                
                 <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
                 <param name="Threshold" value="FATAL"/>
                 <param name="Target" value="System.out"/>
                
                 <layout class="org.apache.log4j.PatternLayout">
                 <!-- The default pattern: Date Priority [Category] Message\n -->
                 <param name="ConversionPattern" value="%d{ABSOLUTE} %-5p [%c{1}] %m%n"/>
                 </layout>
                 </appender>
                
                
                 <!-- ================ -->
                 <!-- Limit categories -->
                 <!-- ================ -->
                
                 <!-- Limit JBoss categories to INFO
                 <category name="org.jboss">
                 <priority value="INFO" class="org.jboss.logging.XLevel"/>
                 </category>
                 -->
                
                 <!-- Increase the priority threshold for the DefaultDS category
                 <category name="DefaultDS">
                 <priority value="FATAL"/>
                 </category>
                 -->
                
                 <!-- Decrease the priority threshold for the org.jboss.varia category
                 <category name="org.jboss.varia">
                 <priority value="DEBUG"/>
                 </category>
                 -->
                
                 <!--
                 | An example of enabling the custom TRACE level priority that is used
                 | by the JBoss internals to diagnose low level details. This example
                 | turns on TRACE level msgs for the org.jboss.ejb.plugins package and its
                 | subpackages. This will produce A LOT of logging output.
                 <category name="org.jboss.system">
                 <priority value="TRACE" class="org.jboss.logging.XLevel"/>
                 </category>
                 -->
                
                 <category name="org.jboss.cache">
                 <priority value="FATAL" class="org.jboss.logging.XLevel"/>
                 </category>
                
                 <category name="org.jboss.tm">
                 <priority value="DEBUG" class="org.jboss.logging.XLevel"/>
                 </category>
                
                 <category name="org.jgroups">
                 <priority value="FATAL"/>
                 </category>
                
                 <!-- ======================= -->
                 <!-- Setup the Root category -->
                 <!-- ======================= -->
                
                 <root>
                 <appender-ref ref="CONSOLE"/>
                <!-- <appender-ref ref="FILE"/>-->
                 </root>
                
                </log4j:configuration>
                


                The output was catched by redirecting output of stderr (a DOS console) to a file.

                regards
                matabo

                • 5. Re: unable to configure logging
                  jaikiran pai Master

                  1)As per your setting:

                  <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
                   <param name="Threshold" value="FATAL"/>
                   <param name="Target" value="System.out"/>
                  
                   <layout class="org.apache.log4j.PatternLayout">
                   <!-- The default pattern: Date Priority [Category] Message\n -->
                   <param name="ConversionPattern" value="%d{ABSOLUTE} %-5p [%c{1}] %m%n"/>
                   </layout>
                   </appender>


                  The threshold attribute of the console appender has been set to FATAL, which means that anything lesser than this(i.e. debug, info etc...) will NOT be logged to the console.

                  Change it to:

                  <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
                   <param name="Threshold" value="DEBUG"/>
                   <param name="Target" value="System.out"/>
                  
                   <layout class="org.apache.log4j.PatternLayout">
                   <!-- The default pattern: Date Priority [Category] Message\n -->
                   <param name="ConversionPattern" value="%d{ABSOLUTE} %-5p [%c{1}] %m%n"/>
                   </layout>
                   </appender>


                  2) As per your setting:
                  <category name="org.jboss.cache">
                   <priority value="FATAL" class="org.jboss.logging.XLevel"/>
                   </category>


                  Again, anything below FATAL level logged by from the org.jboss.cache package hierarchy will NOT be logged. Change this to

                  <category name="org.jboss.cache">
                   <priority value="DEBUG"/>
                   </category>


                  Same is the case with org.jgroups. Change it to:

                  <category name="org.jgroups">
                   <priority value="DEBUG"/>
                   </category>


                  3)
                  The output was catched by redirecting output of stderr (a DOS console) to a file.


                  As per the above settings, all the logs will be generated to stdout and NOT to stderr. So at all you want to redirect the logs then you should redirect it from stdout






                  • 6. Re: unable to configure logging
                    franco lazzari Newbie

                    I changed log4j.xml as you suggested.

                    Output is:

                    [INFO] PropertyConfigurator - -Found existing property editor for org.w3c.dom.Element: org.jboss.util.propertyeditor.ElementEditor@5d173
                    [INFO] PropertyConfigurator - -configure(): attribute size: 13
                    [INFO] TreeCache - -setting cluster properties from xml to: UDP(bind_addr=1.6.64.159;ip_mcast=true;ip_ttl=64;loopback=true;mcast_addr=228.1.2.3;mcast_port=48866;mcast_recv_buf_size=80000;mcast_send_buf_size=150000;ucast_recv_buf_size=80000;ucast_send_buf_size=150000):PING(down_thread=false;num_initial_members=3;timeout=2000;up_thread=false):MERGE2(max_interval=20000;min_interval=10000):FD_SOCK:VERIFY_SUSPECT(down_thread=false;timeout=1500;up_thread=false):pbcast.NAKACK(down_thread=false;gc_lag=50;max_xmit_size=8192;retransmit_timeout=600,1200,2400,4800;up_thread=false):UNICAST(down_thread=false;min_threshold=10;timeout=600,1200,2400;window_size=100):pbcast.STABLE(desired_avg_gossip=20000;down_thread=false;up_thread=false):FRAG(down_thread=false;frag_size=8192;up_thread=false):pbcast.GMS(join_retry_timeout=2000;join_timeout=5000;print_local_addr=true;shun=true):pbcast.STATE_TRANSFER(down_thread=true;up_thread=true)
                    [INFO] TreeCache - -interceptor chain is:
                    class org.jboss.cache.interceptors.CallInterceptor
                    class org.jboss.cache.interceptors.LockInterceptor
                    class org.jboss.cache.interceptors.UnlockInterceptor
                    class org.jboss.cache.interceptors.ReplicationInterceptor
                    [INFO] TreeCache - -cache mode is REPL_SYNC
                    [INFO] UDP - -sockets will use interface 1.6.64.159
                    [INFO] UDP - -socket information:
                    local_addr=1.6.64.159:4231, mcast_addr=228.1.2.3:48866, bind_addr=ic2302299.ic.intra.infocamere.it/1.6.64.159, ttl=64
                    sock: bound to 1.6.64.159:4231, receive buffer size=80000, send buffer size=150000
                    mcast_recv_sock: bound to 1.6.64.159:48866, send buffer size=150000, receive buffer size=80000
                    mcast_send_sock: bound to 1.6.64.159:4232, send buffer size=150000, receive buffer size=80000
                    [INFO] TreeCache - -viewAccepted(): new members: [1.6.64.159:4231]
                    [INFO] TreeCache - -new cache is null (maybe first member in cluster)
                    [INFO] TreeCache - -state could not be retrieved (must be first member in group)
                    


                    Same as usual.

                    What I am trying to say is that whatever modification I apply to log4j.xml, the output doesn't change.
                    If I delete log4j.xml, the output is always as above.

                    It looks like JBossCache doesn't care about log4j.xml.

                    regards
                    matabo


                    • 7. Re: unable to configure logging
                      franco lazzari Newbie

                      Well, log4j.xml was in my classpath, but log4j.jar wasn't :-)

                      I added it and now I am able to configure logging output from JBossCache in a java stand alone application.

                      Now I'll give a check to WebLogic. log4j.jar is in Weblogic system classpath, but no output is produced.

                      thanks to everybody

                      matabo