20 Replies Latest reply on Feb 26, 2016 10:47 AM by jlebourhis RSS
    tnayyar Creator

    Tomcat Restart

    I have come across a scenerio multiple times,where my application get stuck or stops responding and restarting Apache Tomcat resolves that.

     

    -Why we need to restart tomcat always to overcome this issue?

     

    -What are the possible reasons of application failure or zero response while in a production environment?

     

    -Are there any resolutions for this problem and to avoid force restart of Tomcat server in a production environment?

     

     

    Please provide your valuable feedback/Inputs.

     

     

     

    Thanks in advance!

      • Re: Tomcat Restart
        James Penney Explorer

        Hi Tarun,

         

        It could be a whole host of different things - Do you see any exceptions in the catalina logs?


        James

        Cryptosoft Ltd

        • Re: Tomcat Restart
          qn Communicator

          Can you monitor the memory and the cpu usage of tomcat ? Are there some scripts which consume a lot of resources or which block other script ?

           

          By the way, I wonder how ThingWork manages the concurrent threads.

          • Re: Tomcat Restart
            jlebourhis Explorer

            Hello,

             

            I know it is a bit old but i wa wondering if you managed to do anything about your problem ?

            I had the same problem and it was ALWAYS because I was loading too much data. For instance, if you fill an Infotable with 10 000 rows of data, Thingworx will just crash.

            And this problem is even more present with the Neo4J version.

              • Re: Tomcat Restart
                qn Communicator

                Hi,

                 

                Do you give Tomcat more memory than the maximum memory of your machine/VM ? It's declared in "setenv.sh", "Xmx...". If the memory is allocated correctly, the processing will take time but ThingWorx won't crash.

                  • Re: Tomcat Restart
                    jlebourhis Explorer

                    no, that is what i thought at first...

                    But after some researches, it seems that Neo4J is causing troubles with big loads of data.

                      • Re: Tomcat Restart
                        qn Communicator

                        Maybe there's something you can try with Stream / ValueStream processor settings like Max Queue Size, Max Wait Time...

                          • Re: Tomcat Restart
                            jlebourhis Explorer

                            We cannot use them in our case

                            Anyway, as we know where it comes from, we're not running into this problem anymore since we have implemented some pagination to avoid this (ideed, it is not usefull for end users to wait more than 10mn to have displayed data )

                            My answer to this thread was, at first, to give another piece of answer to Tarun Nayyar.

                            But thank you for your thoughts QD N, much appreciated