How to fix a maxQueueLength error in Tibco?











up vote
0
down vote

favorite












I get this error in TIBCO Administrator Log:




(BW-EXT-LOG-200000 njams: maxQueueLength(=20) is reached.)




My client returns:




Connexion to refused.




Everything returns to normal after restarting the instances, but it takes a few minutes and I get the same error.










share|improve this question




























    up vote
    0
    down vote

    favorite












    I get this error in TIBCO Administrator Log:




    (BW-EXT-LOG-200000 njams: maxQueueLength(=20) is reached.)




    My client returns:




    Connexion to refused.




    Everything returns to normal after restarting the instances, but it takes a few minutes and I get the same error.










    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I get this error in TIBCO Administrator Log:




      (BW-EXT-LOG-200000 njams: maxQueueLength(=20) is reached.)




      My client returns:




      Connexion to refused.




      Everything returns to normal after restarting the instances, but it takes a few minutes and I get the same error.










      share|improve this question















      I get this error in TIBCO Administrator Log:




      (BW-EXT-LOG-200000 njams: maxQueueLength(=20) is reached.)




      My client returns:




      Connexion to refused.




      Everything returns to normal after restarting the instances, but it takes a few minutes and I get the same error.







      tibco tibco-ems tibco-business-works tibco-topic tibco-designer






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 9 at 16:53









      Graham

      3,396123558




      3,396123558










      asked Nov 9 at 15:29









      Hichem

      1




      1
























          2 Answers
          2






          active

          oldest

          votes

















          up vote
          0
          down vote













          Sounds like your maxMsgs property of that queue is set to 20 ? You can check this by connecting with tibemsadmin and show/changing queue properties. For Example:



          tcp://localhost:7222> show queue Q1
          Queue: Q1
          Type: static
          Properties: *prefetch=5,maxMsgs=1000,*store=$sys.nonfailsafe
          JNDI Names: <none>
          Bridges: <none>
          Receivers: 0
          Pending Msgs: 0, (0 persistent)
          Delivered Msgs: 0
          Pending Msgs Size: 0.0 Kb, (0.0 Kb persistent)


          You can change it like this:



            tcp://localhost:7222> setprop queue Q1 maxmsgs=1000





          share|improve this answer




























            up vote
            0
            down vote













            Issue Fixed



            A process remained active so it allocated a space in the memory that it would not release.
            This process contained a requestor for which the timeOut is not configured. it waited endlessly a response from the process containing the receiver which did not respond due to an access issue to an external database.



            Best Regards.






            share|improve this answer





















              Your Answer






              StackExchange.ifUsing("editor", function () {
              StackExchange.using("externalEditor", function () {
              StackExchange.using("snippets", function () {
              StackExchange.snippets.init();
              });
              });
              }, "code-snippets");

              StackExchange.ready(function() {
              var channelOptions = {
              tags: "".split(" "),
              id: "1"
              };
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function() {
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled) {
              StackExchange.using("snippets", function() {
              createEditor();
              });
              }
              else {
              createEditor();
              }
              });

              function createEditor() {
              StackExchange.prepareEditor({
              heartbeatType: 'answer',
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader: {
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              },
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              });


              }
              });














               

              draft saved


              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53228669%2fhow-to-fix-a-maxqueuelength-error-in-tibco%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes








              up vote
              0
              down vote













              Sounds like your maxMsgs property of that queue is set to 20 ? You can check this by connecting with tibemsadmin and show/changing queue properties. For Example:



              tcp://localhost:7222> show queue Q1
              Queue: Q1
              Type: static
              Properties: *prefetch=5,maxMsgs=1000,*store=$sys.nonfailsafe
              JNDI Names: <none>
              Bridges: <none>
              Receivers: 0
              Pending Msgs: 0, (0 persistent)
              Delivered Msgs: 0
              Pending Msgs Size: 0.0 Kb, (0.0 Kb persistent)


              You can change it like this:



                tcp://localhost:7222> setprop queue Q1 maxmsgs=1000





              share|improve this answer

























                up vote
                0
                down vote













                Sounds like your maxMsgs property of that queue is set to 20 ? You can check this by connecting with tibemsadmin and show/changing queue properties. For Example:



                tcp://localhost:7222> show queue Q1
                Queue: Q1
                Type: static
                Properties: *prefetch=5,maxMsgs=1000,*store=$sys.nonfailsafe
                JNDI Names: <none>
                Bridges: <none>
                Receivers: 0
                Pending Msgs: 0, (0 persistent)
                Delivered Msgs: 0
                Pending Msgs Size: 0.0 Kb, (0.0 Kb persistent)


                You can change it like this:



                  tcp://localhost:7222> setprop queue Q1 maxmsgs=1000





                share|improve this answer























                  up vote
                  0
                  down vote










                  up vote
                  0
                  down vote









                  Sounds like your maxMsgs property of that queue is set to 20 ? You can check this by connecting with tibemsadmin and show/changing queue properties. For Example:



                  tcp://localhost:7222> show queue Q1
                  Queue: Q1
                  Type: static
                  Properties: *prefetch=5,maxMsgs=1000,*store=$sys.nonfailsafe
                  JNDI Names: <none>
                  Bridges: <none>
                  Receivers: 0
                  Pending Msgs: 0, (0 persistent)
                  Delivered Msgs: 0
                  Pending Msgs Size: 0.0 Kb, (0.0 Kb persistent)


                  You can change it like this:



                    tcp://localhost:7222> setprop queue Q1 maxmsgs=1000





                  share|improve this answer












                  Sounds like your maxMsgs property of that queue is set to 20 ? You can check this by connecting with tibemsadmin and show/changing queue properties. For Example:



                  tcp://localhost:7222> show queue Q1
                  Queue: Q1
                  Type: static
                  Properties: *prefetch=5,maxMsgs=1000,*store=$sys.nonfailsafe
                  JNDI Names: <none>
                  Bridges: <none>
                  Receivers: 0
                  Pending Msgs: 0, (0 persistent)
                  Delivered Msgs: 0
                  Pending Msgs Size: 0.0 Kb, (0.0 Kb persistent)


                  You can change it like this:



                    tcp://localhost:7222> setprop queue Q1 maxmsgs=1000






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 9 at 17:02









                  Axel Podehl

                  1,5091415




                  1,5091415
























                      up vote
                      0
                      down vote













                      Issue Fixed



                      A process remained active so it allocated a space in the memory that it would not release.
                      This process contained a requestor for which the timeOut is not configured. it waited endlessly a response from the process containing the receiver which did not respond due to an access issue to an external database.



                      Best Regards.






                      share|improve this answer

























                        up vote
                        0
                        down vote













                        Issue Fixed



                        A process remained active so it allocated a space in the memory that it would not release.
                        This process contained a requestor for which the timeOut is not configured. it waited endlessly a response from the process containing the receiver which did not respond due to an access issue to an external database.



                        Best Regards.






                        share|improve this answer























                          up vote
                          0
                          down vote










                          up vote
                          0
                          down vote









                          Issue Fixed



                          A process remained active so it allocated a space in the memory that it would not release.
                          This process contained a requestor for which the timeOut is not configured. it waited endlessly a response from the process containing the receiver which did not respond due to an access issue to an external database.



                          Best Regards.






                          share|improve this answer












                          Issue Fixed



                          A process remained active so it allocated a space in the memory that it would not release.
                          This process contained a requestor for which the timeOut is not configured. it waited endlessly a response from the process containing the receiver which did not respond due to an access issue to an external database.



                          Best Regards.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Nov 14 at 15:59









                          Hichem

                          1




                          1






























                               

                              draft saved


                              draft discarded



















































                               


                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function () {
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53228669%2fhow-to-fix-a-maxqueuelength-error-in-tibco%23new-answer', 'question_page');
                              }
                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              Schultheiß

                              Liste der Kulturdenkmale in Wilsdruff

                              Android Play Services Check