Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is under Linux but will maybe useful:</p> <p>If you are running the code within an IDE:</p> <p>ps auwx|grep java</p> <p>-Dgrails.console.class=grails.build.logging.GrailsEclipseConsole -Dosgi.requiredJavaVersion=1.6 <strong>-Xms40m -Xmx768m -XX:MaxPermSize=256m -</strong></p> <p>As you can see the memory settings Xms and Xmx are quite low...</p> <p>In your IDE there should be an INI file:</p> <pre><code>more STS.ini 1 -vm 2 /usr/lib/jvm/java-6-openjdk-amd64/bin/java 3 -startup 4 plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar 5 --launcher.library 6 plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120913-144807 7 -product 8 org.springsource.sts.ide 9 --launcher.defaultAction 10 openFile 11 -vmargs 12 -Dgrails.console.enable.interactive=false 13 -Dgrails.console.enable.terminal=false 14 -Djline.terminal=jline.UnsupportedTerminal 15 -Dgrails.console.class=grails.build.logging.GrailsEclipseConsole 16 -Dosgi.requiredJavaVersion=1.6 17 -Xms40m 18 -Xmx768m 19 -XX:MaxPermSize=256m </code></pre> <p>You can up these value and try restarting your IDE...</p> <p>I would also suggest you run something like nmon before/during and monitor whilst the code is running and monitor disk/cpu/network throughputs.</p> <p>You may find you are hammering your dev box which is causing the issue. </p> <p>If the production is fine I really don't see what the problem is..</p> <p>E2A Ahhh forgot it was under windows so no nmon for windblows but hey not that I tried it - <a href="http://sourceforge.net/projects/jnmonanalyser/" rel="nofollow">http://sourceforge.net/projects/jnmonanalyser/</a></p> <p>E2A again: 1. Enable DataSource.groovy debugging:</p> <pre><code>dataSource { pooled = true driverClassName ="com.mysql.jdbc.Driver" username = "aaa" password = "aaaa" //SQL Logging - refer to Config.groovy at hibernate.sql now logSql=true ... </code></pre> <ol> <li><p>config.groovy - this will stop your app from running if you have issues with lets say records you are trying to add in your BootStrap</p> <p>// Return error when it fails //grails.gorm.failOnError=true</p></li> </ol> <p>Enable log4j and use this or part of it:</p> <pre><code>// log4j configuration log4j { appender.stdout = "org.apache.log4j.ConsoleAppender" appender.'stdout.layout'="org.apache.log4j.PatternLayout" appender.'stdout.layout.ConversionPattern'='[%r] %c{2} %m%n' appender.stacktraceLog = "org.apache.log4j.FileAppender" appender.'stacktraceLog.layout'="org.apache.log4j.PatternLayout" appender.'stacktraceLog.layout.ConversionPattern'='[%r] %c{2} %m%n' appender.'stacktraceLog.File'="stacktrace.log" appender.'stacktraceLog.MaxFileSize'="1MB" rootLogger="error,stdout" logger { grails="error" StackTrace="error,stacktraceLog" org { codehaus.groovy.grails.web.servlet="error" // controllers codehaus.groovy.grails.web.pages="error" // GSP codehaus.groovy.grails.web.sitemesh="error" // layouts codehaus.groovy.grails."web.mapping.filter"="error" // URL mapping codehaus.groovy.grails."web.mapping"="error" // URL mapping codehaus.groovy.grails.commons="info" // core / classloading codehaus.groovy.grails.plugins="error" // plugins codehaus.groovy.grails.orm.hibernate="error" // hibernate integration // Hibernate should be on - if you want to catch sql logs springframework="off" hibernate="on" //hibernate.SQL = 'debug' //hibernate.type = 'trace' //hibernate.SQL = 'info,hibernate' //hibernate.type = 'info,hibernate' //hibernate = 'info,hibernate' //apache.commons.digester.Digester = 'debug,javaclasses' } } additivity.StackTrace=false } </code></pre> <p>try and capture what it is doing, it is also worth running developer tools on your browser whether its firefox of chrome and trying to figure out on what elements it is taking that time - but between the logs and the browser developer tools should lie your answer.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload