Infosets: Status remain Queued

Sort:
You are not authorized to post a reply.
Author
Messages
Jeroen
Basic Member
Posts: 6
Basic Member

    Hello, this is my first post in this forum, but I haven't been able to find any answers anywhere else.

    We are pretty new to smartnotes, but have been using them for a while now. Lately all the scheduled infosets have been in the "queued" status for a few days, and therefore they will not update.

    The update / process queue status option reveals the queue, but neiter "queue" nor "cancel" will change any status (cancelling one will just give a msgbox  "Set state for xxxx to 4" but no changes occur.

    Is there a way to empty all queues, or restart the scheduler? I have not found this option anywhere in the documentation.

    Any help on this matter will be greatly appreciated, since it happened once before, but then a server reboot fixed it..which is not the case now.

     

    Regards,

    Jeroen.

     

    Jimmy Chiu
    Veteran Member
    Posts: 641
    Veteran Member
      which version of SN you are using and on what platform?
      Jeroen
      Basic Member
      Posts: 6
      Basic Member
        Sorry, needed to mention that ofcourse

        SN: (200811) 9.0.3.1.143
        running on windows 2003 server, with the repository in Sql-server 2005.

        btw: "Schedule administration" shows "No Scheduled Jobs Found", so my first guess
        is that either the scheduler isn't running (We don't know how to address this) or the
        repository has some remainders of jobs clogging up the system.

        Thanks for your thoughts.
        Jeroen.
        Jimmy Chiu
        Veteran Member
        Posts: 641
        Veteran Member
          Any scheduled job in Start> programs > accessories > system tools > scheduled tasks?

          Jeroen
          Basic Member
          Posts: 6
          Basic Member
            There are no jobs in the windows scheduler, so that can't be it.
            Still searching the net on how Quartz scheduler might work.
            mark.cook
            Veteran Member
            Posts: 444
            Veteran Member

              I had this happen once, I recycled my LBI server and that cleared out the error and was able to proceed.

              If you are getting any other error messages post them and I will see if we have run into those as well.

              Jean
              New Member
              Posts: 2
              New Member

                We had this happen twice last month and it is happening right now.  In the prior cases we restarted our Tomcat instances and that cleared it out, although people received multiple emails (all exactly alike) because of all of the requests queued up.  This time restarting Tomcat did not fix the problem. 

                We had a similar problem where we got an AppWorx failure 3 times in one week.  We're still not sure of the cause.

                Jeroen
                Basic Member
                Posts: 6
                Basic Member
                  For what it's worth: we have been able to solve it by stopping and restarting the
                  smart notification application from within Websphere, that seemed to work even when
                  restarting the server itself did not.
                  Pasa
                  Basic Member
                  Posts: 6
                  Basic Member

                    I have been running into this same issue configuring SN, and I usually get SN to clear by restarting Tomcat like many have posted here.

                    Jeroen
                    Basic Member
                    Posts: 6
                    Basic Member
                      The hanging queues happened again from time to time, and restarting Webshpere or the servers itself
                      didn't help.
                      Finally a solution that works for us has been found, I thought I'd share:

                      *Pasting*

                      Smart Notification (LSN): Infosets Remain Queued

                      Article ID:5344254


                      Description:

                      My Smart Notification (LSN) infosets remain at "Queued" status and they no longer update or process. How do I resolve this issue?

                      Resolution:


                      Audience: Lawson Business Intelligence (LBI) System Administrators, DBAs

                      Prerequisites: Familiarity with LSN and LBI administration, familiarity with and access to your Relational Database Management System (RDBMS) for the purpose of running a query directly against the database.



                      If LSN is no longer updating or processing there is likely one or more jobs queued that LSN is unable to process. To resolve this issue, perform the following steps:



                      1. Stop the LSN application in the IBM WebSphere Application Server (WAS) Administrative Console.



                      2. Run the following SQL query against the Smart Notification (LSN) database respository:



                      DELETE FROM ENPBATREE where ENTRYCATEGORY = (select CATEGORYID from ENPCATEGORIES where CATEGORYDESC = 'Queue Repos') and ENTRYPARENT IS NOT NULL



                      3. Start the LSN application in the WAS Administrative Console.



                      This will remove all queued jobs from Smart Notes and allow new jobs to be resubmitted again. Note that all infosets that were previously queued will still display the status of "Queued" until the next successful update

                      Anne-Marie
                      Basic Member
                      Posts: 7
                      Basic Member
                        Recently had the same problem.

                        It was solved when we restarted the IBM websphere service through ControlPanel-Services.

                        You are not authorized to post a reply.