Hallo Expert..

Recently I found several warning messages as follows :

INFO  01 Mar 2015 09:06:16 org.displaytag.properties.TableProperties  - LocaleResolver initialized to org.joget.apps.app.web.LocalLocaleResolver. 
Mar 01, 2015 9:11:52 AM org.apache.jasper.compiler.TldLocationsCache tldScanJar
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup  time and JSP compilation time.
INFO  01 Mar 2015 09:06:16 org.displaytag.properties.TableProperties  - LocaleResolver initialized to org.joget.apps.app.web.LocalLocaleResolver. 
Mar 01, 2015 9:11:52 AM org.apache.jasper.compiler.TldLocationsCache tldScanJar 
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup  time and JSP compilation time.

Question :

These messages appear before & after upgrading to Joget Enterprises 4.0.14 - build 1792, what should i do regarding this TLD thing ?

Thank you..

.0.14 - build

  • No labels

8 Comments

  1. The main problem is i need to wait for a minute long to get user log in for the first time. 

    And another minute for inputting one form with ajax sub form.  

    Any advise, thank you in advance..

    1. Try to also shut down the server, delete off the extracted "jw" folder in your webapps folder. After you upgraded to v4, there may be uneeded jars in the (already existed - created by v3 or earlier versions) old "jw" folder to try to eliminate the messages.

      Anyway, that's unlikely to be the cause of slowdown, try to check using Monitoring using VisualVM first then let us know hows the parameters are like.

      Cheers.

      1. Based on VisualVM, it said :

        -XX:MaxPermSize=256m
        -Xmx1024M
        -Dcom.sun.management.jmxremote=true
        -Dcom.sun.management.jmxremote.port=9090
        -Dcom.sun.management.jmxremote.ssl=false
        -Dcom.sun.management.jmxremote.authenticate=false
        -Djava.rmi.server.hostname=127.0.0.1
        -Dwflow.home=./wflow/
        -Djava.util.logging.config.file=.\apache-tomcat-7.0.52\conf\logging.properties
        -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
        -Djava.endorsed.dirs=.\apache-tomcat-7.0.52\endorsed
        -Dcatalina.base=.\apache-tomcat-7.0.52
        -Dcatalina.home=.\apache-tomcat-7.0.52
        -Djava.io.tmpdir=.\apache-tomcat-7.0.52\temp

        with snapshot as follow :

        Thank you for your kind reply,

        Regards.

        1. Hi there,

          The graphs looks normal to me. And its unusual for you to experience these. Can you supply us with your log files to inspect? A thread dump at the time of incident would be great as well to examine what's running.

          Thanks.

          1. The probem solved, Joget is the best ;)

            1. Hey there,

              Good to hear that you have resolved your problem. We would appreciate if you can share with us on what you have done to fix your issue. Thanks.

              Have a good day.

              1. After identifying slow queries in MySQL by enabling the slow query log & found the problem+solution : disabling "Show Number of Rows In Menu"  ...

                1. Hey there,

                  Oh I see. Great!

                  If you still want to have the row count in your userview you can probably add some indexes to the affected tables so that the row count query would run fast too in the future.

                  Thanks for sharing.