The first process is IJ IDE itself, the second process is gradle daemon. So as a workaround, I've been just using the command line and using jettyRun, but it'd be really nice to run from the ps aux | grep java | grep -v grepĪhi 12882 47.5 6.5 3347180 522180 ? Sl 23:16 1:20 /usr/lib/jvm/java-8-oracle/bin/java -Xms128m -Xmx750m -XX:MaxPermSize=350m -XX:ReservedCodeCacheSize=96m -ea -Dsun.io.useCanonCaches=false 4Stack=true -Djsse.enableSNIExtension=false -XX:+UseCodeCacheFlushing -XX:+UseConcMarkSweepGC -XX:SoftRefLRUPolicyMSPerMB=50 eSystemAAFontSettings=lcd -Djb.vmOptionsFile=/home/ahi/devtools/idea/bin/idea64.vmoptions -Xbootclasspath/a:/home/ahi/devtools/idea/bin/./lib/boot.jar =IdeaIC13 =6 27.0 6.8 3508324 546388 ? Sl 23:17 0:40 /usr/lib/jvm/java-8-oracle/bin/java -XX:MaxPermSize=256m -XX:+HeapDumpOnOutOfMemoryError -Xmx1024m -Dfile.encoding=UTF-8 untry=US -Duser.language=en -Duser.variant -cp /home/ahi/.gvm/gradle/2.1/lib/gradle-launcher-2.1.jar .bootstrap.GradleDaemon 2.1 /home/ahi/.gradle/daemon 10800000 f1d075c4-9bd0-4c35-b4d7-bb35282607bc -XX:MaxPermSize=256m -XX:+HeapDumpOnOutOfMemoryError -Xmx1024m -Dfile.encoding=UTF-8 untry=US -Duser.language=en -Duser.variant I basically have to manually kill the process by doing a CTRL-ALT-DELETE. But clicking JettyStop fails by giving me a "Connection refused: connect" error. If I click jettyStart, I get a ": Address already in use: JVM_Bind" error. If I click jetty stop, it only kills one of the processes, but not the other, even if I click jettyStop twice. The annoying part is that if I accidentally click "jettyStart" while jetty is already running in IntelliJ, it fails, but it leaves the program is some kind of inconsistent state. Which is fine, but odd that this doesn't happen if I just use the command line.
When starting jettyStart using the gradle plugin on IntelliJ and then doing a jettyStop, if I click CTRL-ALT-DELETE and look at the running processes in Windows, the process is still hanging around. Thanks, I've tried using the jettyStart & jettyStop, but I've noticed a strange behavior though.
0 kommentar(er)
