6 Replies Latest reply on Mar 23, 2003 7:50 PM by liu peng

    MDB miss messages on DurableSubscription

    liu peng Newbie

      I am a newbie.I have a question about Odd durable subscription behavior.
      I have a application as below:
      1. An application client that calls an session bean.
      2. This session bean publishes several messages to a topic.
      3. A message-driven bean that receives and processes the messages,using a durable topic subscriber and a message selector .

      Now I can run this program.but this message-driven bean always miss some messages that Published by session bean. I had already config this message-driven bean as a
      Durable Subscriber.
      some times STDOUT looks like this:
      invalid console appender config detected, console stream is looping
      Can you tell me Why? Thank you very much!!!

      Comment:I use Jboss3.0.6 and connectionFactory JNDI is java:/JmsXA.

        • 1. Re: MDB miss messages on DurableSubscription
          Adrian Brock Master

          Have you changed the log4j configuration?
          Check your deployment for a log4j.xml or log4j.properties

          It sounds like it is trying to display something
          (possibly an error) but it cannot because the
          configuration is incorrect.

          Regards,
          Adrian

          • 2. Re: MDB miss messages on DurableSubscription
            liu peng Newbie

            Thanks for your remind!

            I don't know how to change my log4j.xml.
            Can you tell me?

            My log4j.xml file show as below :

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

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

            <!-- $Id: log4j.xml,v 1.5.2.6 2002/09/27 22:29:24 patriot1burke 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

            -->



            <!-- A size based file rolling appender










            -->

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






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





            <!-- ====================== -->
            <!-- More Appender examples -->
            <!-- ====================== -->

            <!-- Buffer events and log them asynchronously

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

            -->

            <!-- EMail events to an administrator











            -->

            <!-- Syslog events





            -->

            <!-- Log events to JMS (requires a topic to be created)




            -->


            <!-- ================ -->
            <!-- 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.
            If you use replace the log4j 1.2 jar with a 1.1.3 jar you will need to
            change this from XLevel to XPriority.






            -->

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


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


            <!-- Clustering logging -->
            <!-- Uncomment the following to redirect the org.javagroups and
            org.jboss.ha categories to a cluster.log file.













            <appender-ref ref="CLUSTER"/>



            <appender-ref ref="CLUSTER"/>

            -->

            </log4j:configuration>

            ##########################################################

            My JBOSS3.0.6 System INFO show as below:

            ##########################################################

            12:30:00,290 INFO [Server] JBoss (MX MicroKernel) [3.0.6 (CVSTag=JBoss_3_0_6 Da
            te=200301260037)] Started in 0m:25s:270ms
            12:30:43,240 INFO [STDOUT] In PublisherBean() (constructor)
            12:30:43,240 INFO [STDOUT] In PublisherBean.ejbCreate()
            12:30:43,350 INFO [STDOUT] PUBLISHER: Setting message text to: Item 0: Business

            12:30:44,390 INFO [STDOUT] PUBLISHER: Setting message text to: Item 1: Opinion
            12:30:44,390 INFO [STDOUT] PUBLISHER: Setting message text to: Item 2: Opinion
            12:30:44,450 INFO [STDOUT] PUBLISHER: Setting message text to: Item 3: Living/A
            rts
            12:30:44,500 INFO [STDOUT] PUBLISHER: Setting message text to: Item 4: Nation/W
            orld
            12:30:44,500 INFO [STDOUT] PUBLISHER: Setting message text to: Item 5: Nation/W
            orld
            12:30:44,560 INFO [STDOUT] PUBLISHER: Setting message text to: Item 6: Sports
            12:30:44,610 INFO [STDOUT] PUBLISHER: Setting message text to: Item 7: Metro/Re
            gion
            12:30:44,610 INFO [STDOUT] PUBLISHER: Setting message text to: Item 8: Metro/Re
            gion
            12:30:44,670 INFO [STDOUT] PUBLISHER: Setting message text to: Item 9: Living/A
            rts
            12:30:44,720 INFO [STDOUT] PUBLISHER: Setting message text to: Item 10: Living/
            Arts
            12:30:44,780 INFO [STDOUT] PUBLISHER: Setting message text to: Item 11: Opinion

            12:30:44,780 INFO [STDOUT] PUBLISHER: Setting message text to: Item 12: Opinion

            12:30:44,830 INFO [STDOUT] PUBLISHER: Setting message text to: Item 13: Nation/
            World
            12:30:44,890 INFO [STDOUT] PUBLISHER: Setting message text to: Item 14: Metro/R
            egion
            12:30:44,890 INFO [STDOUT] PUBLISHER: Setting message text to: Item 15: Metro/R
            egion
            12:30:44,940 INFO [STDOUT] PUBLISHER: Setting message text to: Item 16: Nation/
            World
            12:30:45,000 INFO [STDOUT] PUBLISHER: Setting message text to: Item 17: Nation/
            World
            12:30:45,160 INFO [STDOUT] In MessageBean.MessageBean()
            12:30:45,160 INFO [STDOUT] In MessageBean.setMessageDrivenContext()
            ERROR: invalid console appender config detected, console stream is looping
            12:30:45,220 INFO [STDOUT] In MessageBean.MessageBean()
            12:30:45,330 INFO [STDOUT] In MessageBean.setMessageDrivenContext()
            12:30:45,330 INFO [STDOUT] In MessageBean.ejbCreate()
            12:30:45,380 INFO [STDOUT] MESSAGE BEAN: Message received: Item 11: Opinion

            ##########################################################


            Many Thanks! All the best wishes to you !

            • 3. Re: MDB miss messages on DurableSubscription
              Adrian Brock Master

              This looks like the default log4j.xml from
              server/default/conf. The most likely reason for an
              the message is because you tried to reconfigure
              the consol appender so it loops.

              Try lookining in server/default/log/server.log
              for the same messages.

              Regards,
              Adrian

              • 4. Re: MDB miss messages on DurableSubscription
                liu peng Newbie

                Yes! you are right.
                I found that same messages in the server.log.
                What should I do for receive the all the messages published from PublisherBean ?

                Waiting for your reply!
                Thanks a lot!

                • 5. Re: MDB miss messages on DurableSubscription
                  Adrian Brock Master

                  You mean you got
                  ERROR: invalid console appender config detected, console stream is looping
                  in server.log?

                  I don't know what it is wrong with your log4j config.

                  Try removing the console appender temporarily
                  from log4j.xml in server/default/conf

                  Maybe this will give a clue?

                  Regards,
                  Adrian

                  • 6. Re: MDB miss messages on DurableSubscription
                    liu peng Newbie

                    I think I had already get some practises from you.
                    Thanks for your help!