9 Replies Latest reply on Feb 5, 2006 2:36 PM by mcobery

    Pub/Sub persistence

      Can anyone tell me what happens if a TopicPublisher created by a TopicSession with CLIENT_ACKNOWLEDGE continuously publishes a persistent message with an infinite time to live to JBossMQ topic with no maxdepth and without any known subscribers for a few days?

      Will the messages just continue to persist until a subscriber acknowledges them? Or because there are no known subscribers will the message just disappear?

      When a subscriber is finally created for that topic will it have to process all those messages (i.e. acknowledge) in order or will the subscriber just receive the messages from the time after it was created and until is destoyed?

      Thanks.

        • 1. Re: Pub/Sub persistence

          http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossHelp
          Try reading the JMS spec or even the WIKI.

          The answers is:
          Not unless there is a durable subscription.

          • 2. Re: Pub/Sub persistence

            Hi,

            I am not sure what question you are answering with your reply. Are my statements here correct?

            >>Can anyone tell me what happens if a TopicPublisher created by a
            >>TopicSession with CLIENT_ACKNOWLEDGE continuously publishes a
            >>persistent message with an infinite time to live to JBossMQ topic with no
            >>maxdepth and without any known subscribers for a few days?
            >>Will the messages just continue to persist until a subscriber
            >>acknowledges them? Or because there are no known subscribers will
            >>the message just disappear?
            The messages will still persist no matter if there is a client or not. Correct?
            If this is correct, is there a way to create a FIFO like persistence using a null persistence manager? I have tried this approach only to run out of memory due to message softening (the message softening with a null persistence manager uses memory as its internal cache). I would rather have the first messages disappear once the high memory mark of the message cache has been breached.
            If this is not correct, any possibilities why these messages are queuing up?

            >>When a subscriber is finally created for that topic will it have to
            >> process all those messages (i.e. acknowledge) in order or
            >>will the subscriber just receive the messages from the time
            >>after it was created and until is destoyed?
            Only a durable subscriber will need to process all these messages. Correct?

            • 3. Re: Pub/Sub persistence

               

              "mcobery" wrote:

              I am not sure what question you are answering with your reply. Are my statements here correct?


              This one:
              http://wiki.jboss.org/wiki/Wiki.jsp?page=BadPostNoWork


              • 4. Re: Pub/Sub persistence

                Thanks for your help. I understand your frustration and have found similar issue when assisting other people, but I find that it is best to figure out what is the underlying question (everyone has a different approach to questioning) and then answer that underlying question in a less cryptic manner rather than blaming people for lack of effort.

                I have explored JBossMQ on these issues and detailed them in my post. The scenerios presented in my questions are actions that I have taken that do not seem to fix my problem. I am attempting to elminate any doubts.

                Again thank you for the help.

                • 5. Re: Pub/Sub persistence

                  No, your initial question was:


                  Can anyone tell me what happens...


                  To which the correct answers are:
                  * What does the spec say happens?
                  * Suck it and see

                  This is even the first bullet point on the WIKI page.
                  How to get (or not get) guaranteed delivery (messages that survive client and server crashes).

                  => No work on your part.

                  • 6. Re: Pub/Sub persistence

                     

                    "mcobery" wrote:

                    If this is not correct, any possibilities why these messages are queuing up?


                    Use the cunningly entitled "READ THIS FIRST" topic at the top of this forum.

                    That way we get to see (from the log or you posting the code)
                    what is really happening rather than what you think/say is happening.

                    I work from facts not assertions.

                    If you don't want this kind make an effort to make your question answerable
                    (normally I just ignore these posts or move them to the BAD POST forum).
                    http://wiki.jboss.org/wiki/Wiki.jsp?page=BadPostItDoesNotWork

                    • 7. Re: Pub/Sub persistence

                      Again thanks for your help. I know tech support can be difficult sometimes but I think you may need therapy or maybe some time off to deal with your anger.

                      I have one suggestion though in case you do not have time in your vacation bank or money for therapy. Instead of insulting people and wasting your time and my time, you could just ignore the post.

                      Happy early St. Valentine's Day

                      PS I hope I can make your BAD POST forum, you big bad man you!

                      • 8. Re: Pub/Sub persistence

                         

                        "mcobery" wrote:
                        Again thanks for your help. I know tech support can be difficult sometimes but I think you may need therapy or maybe some time off to deal with your anger.


                        Everybody thinks I am angry! If I was angry I would delete your user. ;-)
                        People mistake my directness in trying to teach them how to debug problems
                        for anger!

                        If I said please and thank you, this forum would be fuller than it already is
                        with useless posts.

                        • 9. Re: Pub/Sub persistence

                          No problem. I understand your frustration. I should have put more code up there. Thanks for the help (really). It was a bit cryptic but so were my questions. I thought my last post would lighten things up. Glad to see you have a sense of humor.