我知道這是舊的,但是,您使用的是哪個版本的grails?從grails 2.3遷移到grails 2.5後,我遇到了同樣的問題。
經過一段相當痛苦的調查,我發現這個問題是運行新的分叉模式下性能測試時,容易從BuildConfig.groovy刪除這些選項來解決:
grails.project.fork = [
// configure settings for compilation JVM, note that if you alter the Groovy version forked compilation is required
//compile: [maxMemory: 256, minMemory: 64, debug: false, maxPerm: 256, daemon:true],
// configure settings for the test-app JVM, uses the daemon by default
test: false,
// configure settings for the run-app JVM
run: [maxMemory: 1536, minMemory: 512, debug: false, maxPerm: 1024, forkReserve:false],
// configure settings for the run-war JVM
war: [maxMemory: 1536, minMemory: 512, debug: false, maxPerm: 1024, forkReserve:false],
// configure settings for the Console UI JVM
console: [maxMemory: 1536, minMemory: 64, debug: false, maxPerm: 1024]
]
問候。
感謝您的回答,Ian – malc 2014-08-28 15:43:47