Running eclipse Jetty 9 with Gradle - jetty
Help running Jetty 9 with Gradle
I have seen references to run Jetty on how-to-run-jetty-7-with-specified-war-with-groovy-gradle and setting_up_embedded_jetty_8_and_spring_mvc_with_maven
But I want to run the new Eclipse Jetty 9 in Gradle.
I tried this:
task jetty8Run(type: JavaExec, dependsOn: assemble) {
main = "org.eclipse.jetty.server.Server"
args = ["--port", 8080, "--stop-port", 9876, "--stop-key", 'shutterdown', war.archivePath]
classpath configurations.jetty8
}
I am using this as the dependencies:
jettyEclipse "org.eclipse.jetty:jetty-server:$jetty9Version"
jettyEclipse "org.eclipse.jetty:jetty-servlet:$jetty9Version"
jettyEclipse "org.eclipse.jetty:jetty-webapp:$jetty9Version"
jettyEclipse "org.eclipse.jetty:jetty-servlets:$jetty9Version"
jettyEclipse "org.eclipse.jetty:jetty-jsp:$jetty9Version"
jettyEclipse "javax.servlet:jstl:1.2"
in my gradle.properties:
jetty9Version: 9.0.0.M0
But when I run, I get the following message
An attempt to initialize for well behaving parent process finished.
Here is the full debug stack trace:
14:22:16.699 [INFO] [org.gradle.process.internal.DefaultExecHandle] Starting process 'command 'C:\usr\bin\Java\jdk1.7\bin\java.exe''. Working directory: C:\usr\git_workspaces\oxygen\code_wash Command: C:\usr\bin\Java\jdk1.7\bin\java.exe -Dfile.encoding=windows-1252 -cp C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.mortbay.jetty\jetty-runner\8.1.5.v20120716\jar\2f8a590e1dcdf75e40cabfc0803c3712b7f04360\jetty-runner-8.1.5.v20120716.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty\jetty-server\9.0.0.M0\jar\7c6ea0dc0230fba0fe0e2a37490558477b9833c6\jetty-server-9.0.0.M0.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty\jetty-servlet\9.0.0.M0\jar\5bfecce207651c0f7861255061df32204e1f4ba0\jetty-servlet-9.0.0.M0.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty\jetty-webapp\9.0.0.M0\jar\b67fc43d6949e1bf66eb479fba3a9b335fa9dd0e\jetty-webapp-9.0.0.M0.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty\jetty-servlets\9.0.0.M0\jar\1cb5a7222ebec54e5c5b089d5c757ec6ac6506a0\jetty-servlets-9.0.0.M0.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty\jetty-jsp\9.0.0.M0\jar\5120a9a20405a286d158825257d50812d63493d4\jetty-jsp-9.0.0.M0.jar;C:\Users\mknuts6173c\.m2\repository\javax\servlet\jstl\1.2\jstl-1.2.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.mortbay.jetty\servlet-api\3.0.pre4\jar\d5611e63cefe84a858bb46a4cb1249dcb7ddb830\servlet-api-3.0.pre4.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty.orbit\javax.servlet\3.0.0.v201112011016\orbit\aaaa85845fb5c59da00193f06b8e5278d8bf3f8\javax.servlet-3.0.0.v201112011016.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty.orbit\javax.servlet.jsp\2.2.0.v201112011158\orbit\80b4ffe7c26ee97313bea2ddda5835fd38812ee4\javax.servlet.jsp-2.2.0.v201112011158.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty.orbit\org.apache.jasper.glassfish\2.2.2.v201112011158\orbit\3945afe6a042228a92da320aec3fa1bc1308183b\org.apache.jasper.glassfish-2.2.2.v201112011158.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty.orbit\javax.servlet.jsp.jstl\1.2.0.v201105211821\orbit\db594f1c8fc00d536f6d135bd7f8a9a99a6b8eea\javax.servlet.jsp.jstl-1.2.0.v201105211821.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty.orbit\javax.el\2.2.0.v201108011116\orbit\ec8944c11833d84b0283a5afbad0fafb264f86a9\javax.el-2.2.0.v201108011116.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty.orbit\com.sun.el\2.2.0.v201108011116\orbit\15f7774c3fa514835a371f47c152317704ea411a\com.sun.el-2.2.0.v201108011116.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty.orbit\org.eclipse.jdt.core\3.7.1\orbit\5b79bfee0852ca685e33cab74496fa3400271b5b\org.eclipse.jdt.core-3.7.1.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty\jetty-continuation\9.0.0.M0\jar\3031a06840cee834b640ae3d145044fb07aebdc4\jetty-continuation-9.0.0.M0.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty\jetty-util\9.0.0.M0\jar\7149f92459b45f91b5a0487a5edc300764392ee7\jetty-util-9.0.0.M0.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty\jetty-io\9.0.0.M0\jar\8dcc24862d1832e0035f893e227d38b656ecef49\jetty-io-9.0.0.M0.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty\jetty-http\9.0.0.M0\jar\c0a5dc125b94ebc049f60f66b5ce8b17a0d9d917\jetty-http-9.0.0.M0.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty\jetty-security\9.0.0.M0\jar\b18d3938499c88109283007657e4d89ffcc8aff3\jetty-security-9.0.0.M0.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty\jetty-xml\9.0.0.M0\jar\5421375311559e23bc77d1e65624f13406018467\jetty-xml-9.0.0.M0.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty.orbit\javax.activation\1.1.0.v201105071233\orbit\b394a9fbf664ca835452b3ced452710bcf79fd81\javax.activation-1.1.0.v201105071233.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty.orbit\javax.mail.glassfish\1.4.1.v201005082020\orbit\b707c39fc080529c4a9ffc1df4eac58421133aaf\javax.mail.glassfish-1.4.1.v201005082020.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty\jetty-jndi\8.1.5.v20120716\jar\f0c40a2e62bf4b78a8c3a34cd8c0a8250b8321c0\jetty-jndi-8.1.5.v20120716.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty.orbit\javax.transaction\1.1.1.v201105210645\orbit\68e61aa115bbff4e1e2ae4b16feb27d9f805eb6\javax.transaction-1.1.1.v201105210645.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty\jetty-plus\8.1.5.v20120716\jar\d901ed553709d53b2fa72ade6a06f8bef82f29f5\jetty-plus-8.1.5.v20120716.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty.orbit\javax.annotation\1.1.0.v201108011116\orbit\964b4bd5e4f40d6497fd302e2e66c4a4257138b3\javax.annotation-1.1.0.v201108011116.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty.orbit\org.objectweb.asm\3.1.0.v200803061910\orbit\bf952ae43613f460f11ce5f8727cc9e4a7f8d33d\org.objectweb.asm-3.1.0.v200803061910.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty\jetty-annotations\8.1.5.v20120716\jar\aee87dde17b6d6fe18a3bab3f3fc4ae40356ae94\jetty-annotations-8.1.5.v20120716.jar;C:\Users\mknuts6173c\.gradle\caches\artifacts-14\filestore\org.eclipse.jetty.orbit\org.apache.taglibs.standard.glassfish\1.2.0.v201112081803\orbit\2c4baa72af1d3aae3a1e029d4f8ca07498dabbe0\org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar org.eclipse.jetty.server.Server --port 8080 --stop-port 9876 --stop-key shutterdown C:\usr\git_workspaces\oxygen\code_wash\target\libs\code_wash.war
14:22:16.706 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Environment for process 'command 'C:\usr\bin\Java\jdk1.7\bin\java.exe'': {TERM=cygwin, USERPROFILE=C:\Users\mknuts6173c, HISTFILE=C:\usr\configs\scripts/.bash_history, LS_OPTS=--color=auto, JAVA_HOME=C:\usr\bin\Java\jdk1.7, HSTART_HOME=C:\usr\bin\utils\Hstart_4.1-bin, PROGRAMDATA=C:\ProgramData, PROGRAMPATH=C:\usr\bin\CONSOLES\Git, JAVA7_HOME=C:\usr\bin\Java\jdk1.7, GNUPGHOME=c:/Users/mknuts6173c/.gnupg, COMMONPROGRAMFILES=C:\Program Files\Common Files, USR_HOME=C:\usr, PWD=c:/usr/git_workspaces/oxygen/code_wash, JRUBY_HOME=C:\usr\bin\SDK\jruby\jruby-1.6.8, PROCESSOR_REVISION=2a07, LS_OPTIONS=--color=auto, USERDOMAIN=CABLE, GREP_COLOR=7, ALLUSERSPROFILE=C:\ProgramData, PROGRAMW6432=C:\Program Files, JAVA6_HOME=C:\usr\bin\Java\jdk1.6, !::=::\, CONFIGS_HOME=C:\usr\configs, INPUTRC=C:/usr/bin/CONSOLES/Git/etc/inputrc, SESSIONNAME=Console, M2_REPO=C:\usr\repository, PLINK_PROTOCOL=ssh, IDEA_JDK=C:\usr\bin\Java\jdk1.7, HISTSIZE=100, EDITOR=~/AppData/Roaming/GitPad/GitPad.exe, TMP=C:/Users/MKNUTS~1/AppData/Local/Temp, SCALA_HOME=C:\usr\bin\SDK\scala, PSMODULEPATH=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\, LOGONSERVER=\\PAOAKADDCCB02, PATH=/c/Users/mknuts6173c/bin:.:/usr/local/bin:/mingw/bin:/bin:/usr/bin:/c/usr/bin/Java/jdk1.7/bin:/c/usr/bin/SDK/jruby/jruby-1.6.8/bin:/c/usr/bin/SDK/jruby/jruby-1.6.8/lib/ruby/gems/1.8/gems:/c/usr/bin/SDK/gradle/bin:/c/usr/bin/groovy-1.8.6/bin:/c/usr/bin/SDK/maven/bin:/c/usr/bin/SDK/ant/bin:/c/usr/bin/SDK/scala/bin:/c/usr/bin/mobile/android-sdk-windows/platform-tools/:/c/usr/bin/mobile/android-sdk-windows/tools/:/c/usr/bin/CONSOLES/ansicon/x86:/c/usr/bin/utils/Hstart_4.1-bin:/c/usr/configs/scripts:/c/usr/configs/scripts/shell:/c/usr/configs/scripts/cmd:/c/Program Files/Dell/DW WLAN Card:/c/Program Files (x86)/RSA SecurID Token Common:/c/Windows/system32:/c/Windows:/c/Windows/System32/Wbem:/c/Program Files/TortoiseSVN/bin:.:/c/Program Files/TortoiseSVN/bin:/c/Program Files (x86)/Graphviz 2.28/bin
:/usr/bin/MOBILE/android-sdk-windows/platform-tools, SHELL_HOME=C:\usr\configs\scripts\shell, GRADLE_HOME=C:\usr\bin\SDK\gradle, PROMPT=$P$G, COMMONPROGRAMW6432=C:\Program Files\Common Files, PROCESSOR_LEVEL=6, LESS=-FRSX, LOCALAPPDATA=C:\Users\mknuts6173c\AppData\Local, SCRIPTS_HOME=C:\usr\configs\scripts, COMPUTERNAME=PAGWKL-D5CDBS1, ANSICON_HOME=C:\usr\bin\CONSOLES\ansicon\x86, CORP_PATH=C:\Program Files\Dell\DW WLAN Card;C:\Program Files (x86)\RSA SecurID Token Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\TortoiseSVN\bin;, LSCOLORS=gxBxhxDxfxhxhxhxhxcxcx, USERNAME=MKnuts6173c, HISTFILESIZE=100, WINDIR=C:\Windows, APPDATA=C:\Users\mknuts6173c\AppData\Roaming, USERDNSDOMAIN=CABLE.COMCAST.COM, PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC, SHLVL=1, MAVEN_HOME=C:\usr\bin\SDK\maven, PROGRAMFILES(X86)=C:\Program Files (x86), CMD_HOME=C:\usr\configs\scripts\cmd, JREBEL_HOME=C:\usr\bin\SERVERS\jrebel, GROOVY_HOME=C:\usr\bin\groovy-1.8.6, DELLCLIENTSYSTEMUPDATEPATH=C:\Program Files (x86)\Dell\ClientSystemUpdate\, TEMP=C:/Users/MKNUTS~1/AppData/Local/Temp, PROMPT_COMMAND=history -n; history -w; history -c; history -r; lastcmd; , HOMEDRIVE=C:, JAVA_OPTS=-ea -Xmx512m -XX:MaxPermSize=512m -Dd2.config.location=file:///C:/xivr/d2/override.properties, TERM_DRIVE=c:/, SYSTEMDRIVE=C:, LOGNAME=MKnuts6173c, =C:=C:\usr\git_workspaces\xivr, JRUBY_GEMS=C:\usr\bin\SDK\jruby\jruby-1.6.8\lib\ruby\gems\1.8\gems, COMMONPROGRAMFILES(X86)=C:\Program Files (x86)\Common Files, PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 42 Stepping 7, GenuineIntel, OLDPWD=c:/usr/bin/SDK/gradle, SHELL=C:/usr/bin/CONSOLES/Git/bin/bash, MAKE_MODE=unix, GLASSFISH_HOME=C:\usr\bin\SERVERS\glassfish3, PROCESSOR_ARCHITECTURE=AMD64, JMETER_HOME=C:\usr\bin\TESTING\apache-jmeter-2.7, OS=MINGW, FP_NO_HOST_CHECK=NO, HOMEPATH=\Users\mknuts6173c, COMSPEC=C:\Windows\system32\cmd.exe, MSYSTEM=MINGW32, ANT_HOME=C:\usr\bin\SDK\ant, GRADLE_OPTS=-Xmx1024M -XX:MaxPermSize=512m, PROGRAMFILES=C:\Program Files, HISTCONTROL=ignoredups:erasedups, HOME=c:/Users/mknuts6173c, CYGWIN_HOME=C:\usr\bin\CONSOLES\cygwin, NUMBER_OF_PROCESSORS=4, SYSTEMROOT=C:\Windows, PUBLIC=C:\Users\Public, ANDROID_HOME=C:\usr\bin\mobile\android-sdk-windows, LESSCHARSET=utf-8}
14:22:16.722 [DEBUG] [org.gradle.internal.nativeplatform.jna.WindowsHandlesManipulator] Invalid parameter attempting to uninherit stream - child process may remain attached.
14:22:16.732 [DEBUG] [org.gradle.internal.nativeplatform.jna.WindowsHandlesManipulator] Invalid parameter attempting to uninherit stream - child process may remain attached.
14:22:16.737 [DEBUG] [org.gradle.internal.nativeplatform.jna.WindowsHandlesManipulator] Invalid parameter attempting to uninherit stream - child process may remain attached.
14:22:16.744 [INFO] [org.gradle.process.internal.ProcessParentingInitializer] An attempt to initialize for well behaving parent process finished.
14:22:16.750 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: STARTING
14:22:16.758 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Waiting until process started: command 'C:\usr\bin\Java\jdk1.7\bin\java.exe'.
14:22:16.768 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: STARTED
14:22:16.778 [INFO] [org.gradle.process.internal.DefaultExecHandle] Successfully started process 'command 'C:\usr\bin\Java\jdk1.7\bin\java.exe''
14:22:16.778 [DEBUG] [org.gradle.process.internal.ExecHandleRunner] waiting until streams are handled...
14:22:16.987 [ERROR] [system.err] 8.y.z-SNAPSHOT
14:22:16.999 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: SUCCEEDED
14:22:17.008 [INFO] [org.gradle.process.internal.DefaultExecHandle] Process 'command 'C:\usr\bin\Java\jdk1.7\bin\java.exe'' finished with exit value 0 (state: SUCCEEDED)
14:22:17.016 [DEBUG] [org.gradle.logging.internal.DefaultLoggingConfigurer] Finished configuring with level: DEBUG, configurers: [org.gradle.logging.internal.OutputEventRenderer#1398c0b5, org.gradle.logging.internal.logback.LogbackLoggingConfigurer#1193b520, org.gradle.logging.internal.JavaUtilLoggingConfigurer#785850e3]
14:22:17.023 [DEBUG] [org.gradle.logging.internal.DefaultLoggingConfigurer] Finished configuring with level: DEBUG, configurers: [org.gradle.logging.internal.OutputEventRenderer#1398c0b5, org.gradle.logging.internal.logback.LogbackLoggingConfigurer#1193b520, org.gradle.logging.internal.JavaUtilLoggingConfigurer#785850e3]
14:22:17.031 [DEBUG] [org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter] Finished executing task ':jetty8Run'
14:22:17.036 [DEBUG] [org.gradle.execution.taskgraph.DefaultTaskGraphExecuter] Timing: Executing the DAG took 1 mins 17.814 secs
14:22:17.044 [LIFECYCLE] [org.gradle.BuildResultLogger]
14:22:17.051 [LIFECYCLE] [org.gradle.BuildResultLogger] BUILD SUCCESSFUL
14:22:17.062 [LIFECYCLE] [org.gradle.BuildResultLogger]
14:22:17.069 [LIFECYCLE] [org.gradle.BuildResultLogger] Total time: 1 mins 22.869 secs
14:22:17.083 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on no_buildscript class cache for build file 'C:\usr\git_workspaces\oxygen\code_wash\build.gradle' (C:\Users\mknuts6173c\.gradle\caches\1.2\scripts\build_6pds00nsngb1qkefk395em9gdo\ProjectScript\no_buildscript).
14:22:17.102 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on buildscript class cache for build file 'C:\usr\git_workspaces\oxygen\code_wash\build.gradle' (C:\Users\mknuts6173c\.gradle\caches\1.2\scripts\build_6pds00nsngb1qkefk395em9gdo\ProjectScript\buildscript).
14:22:17.118 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on no_buildscript class cache for settings file 'C:\usr\git_workspaces\oxygen\code_wash\settings.gradle' (C:\Users\mknuts6173c\.gradle\caches\1.2\scripts\settings_6mc489vb6gkj8h6rl06dj51vmb\SettingsScript\no_buildscript).
14:22:17.131 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on buildscript class cache for settings file 'C:\usr\git_workspaces\oxygen\code_wash\settings.gradle' (C:\Users\mknuts6173c\.gradle\caches\1.2\scripts\settings_6mc489vb6gkj8h6rl06dj51vmb\SettingsScript\buildscript).
14:22:17.153 [DEBUG] [org.gradle.logging.internal.DefaultLoggingConfigurer] Finished configuring with level: DEBUG, configurers: [org.gradle.logging.internal.OutputEventRenderer#1398c0b5, org.gradle.logging.internal.logback.LogbackLoggingConfigurer#1193b520, org.gradle.logging.internal.JavaUtilLoggingConfigurer#785850e3]
Any chance anyone can help with this?
Gretty gradle plugin solves the problem: https://github.com/akhikhl
It supports jetty versions 7, 8 and 9 out of the box.
Disclosure: I am author of Gretty plugin.
I don't have any suggestions specifically for the Gradle JavaExec task, but if you're stuck and want to try an alternative - you could try launching using the Ant task, with appropriate settings for fork/spawn.
you can try this
https://github.com/Khoulaiz/gradle-jetty-eclipse-plugin
it work for me.
Related
AWS Glue job failed with error 'ERROR Client: Application diagnostics message: User application exited with status 1'
I'm recently using AWS Glue job to test to run some spark python codes, I kicked off a run yesterday and it succeeded, this morning, without any changes, I kicked off three times and it all failed.
The logs are weird and I don't understand...:
This is copied from the error log:
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
awk: /tmp/parse_yarn_logs.awk:6: warning: escape sequence `\[' treated as plain `['
awk: /tmp/parse_yarn_logs.awk:6: warning: escape sequence `\]' treated as plain `]'
awk: /tmp/parse_yarn_logs.awk:8: warning: escape sequence `\(' treated as plain `('
awk: /tmp/parse_yarn_logs.awk:8: warning: escape sequence `\)' treated as plain `)'
21/03/04 09:56:42 INFO client.RMProxy: Connecting to ResourceManager at ip-xxxxxx.ec2.internal/xxx.xx.xx.x:xxxx
awk: /tmp/parse_yarn_logs.awk:19: (FILENAME=- FNR=1) fatal: Unmatched ( or \(: /.*Unregistering ApplicationMaster with FAILED (diag message: Shutdown hook called before final status was reported.*$/
By looking at the full version logs, I found this bit seem causing the issue:
21/03/04 10:12:08 ERROR Client: Application diagnostics message: User application exited with status 1
Exception in thread "main" org.apache.spark.SparkException: Application application_xxxxxxxx_0001 finished with failed status
at org.apache.spark.deploy.yarn.Client.run(Client.scala:1149)
at org.apache.spark.deploy.yarn.YarnClusterApplication.start(Client.scala:1526)
at org.apache.spark.deploy.SparkSubmit.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:849)
at org.apache.spark.deploy.SparkSubmit.doRunMain$1(SparkSubmit.scala:167)
at org.apache.spark.deploy.SparkSubmit.submit(SparkSubmit.scala:195)
at org.apache.spark.deploy.SparkSubmit.doSubmit(SparkSubmit.scala:86)
at org.apache.spark.deploy.SparkSubmit$$anon$2.doSubmit(SparkSubmit.scala:924)
at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:933)
at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)
21/03/04 10:12:08 INFO ShutdownHookManager: Shutdown hook called
21/03/04 10:12:08 INFO ShutdownHookManager: Deleting directory /tmp/spark-xxxxxxxxxx
21/03/04 10:12:08 INFO ShutdownHookManager: Deleting directory /tmp/spark-xxxxxxxxxx
one of the runs startup time used 10 mins?! Normally it only used a few secs...
Seems like glue is not very stable...and the job is failed or not based on my luck...
Does anyone know what's causing the issue and is there anything I can do to improve its perfomance? Thanks.
The same happens me now on AWS Glue Job. But on my side it happens when I add one new line to the code
device = DeviceDetector('Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.77.34.5 Safari/537.36 QJY/2.0 Philco_PTV24G50SN-VB_DRM HDR DID/C0132bb2240f').parse()
When I close this line the job is ok.
Since it is new Python package in our code (I just added it) I have no idea as it was before. Hope somebody can explain it.
xunit .net core 2.1 basic unit test run inside VS2017 fail with time out
I have build a project from "xUnit Test Project(.Net Core)", the target framework is .Net Core 2.1, once I am trying to run a basic test inside VS 2017 (15.7.4), it fails with the following error after a couple of minutes: Microsoft.VisualStudio.TestPlatform.ObjectModel.TestPlatformException: Failed to negotiate protocol. Wait for response timed out. at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.TestRequestSender.CheckVersionWithTestHost() at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyOperationManager.SetupChannel(IEnumerable`1 sources) at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyExecutionManager.StartTestRun(TestRunCriteria testRunCriteria, ITestRunEventsHandler eventHandler) I have tried with dotnet test command also but still getting the same error. I guess it is something related to my proxy setting as I my computer is inside my corporate network which is protected by a proxy. EDIT: I have just realized that once I add reference to SUT project, it will cause the issue, but how just adding a project reference could cause this?! EDIT2: I have run the tests using the following command: dotnet test --diag:log.txt And can see the following logs in the log file: TpTrace Verbose: 0 : 1316, 6, 2018/06/28, 13:32:47.524, 21212669743, vstest.console.dll, Test Runtime launched TpTrace Verbose: 0 : 1316, 4, 2018/06/28, 13:32:47.533, 21212694192, vstest.console.dll, TestRequestSender.WaitForRequestHandlerConnection: waiting for connection with timeout: 60000 TpTrace Verbose: 0 : 1316, 11, 2018/06/28, 13:32:48.215, 21214464768, vstest.console.dll, SocketServer.OnClientConnected: Client connected for endPoint: 127.0.0.1:51299, starting MessageLoopAsync: TpTrace Verbose: 0 : 1316, 11, 2018/06/28, 13:32:48.215, 21214465327, vstest.console.dll, TcpClientExtensions.MessageLoopAsync: Polling on remoteEndPoint: 127.0.0.1:51300 localEndPoint: 127.0.0.1:51299
SonarQube C++ build-wrapper produce empty build-wrapper-dump.json
I'm using sonarQube C/C++ on WIN10 machine on a vxworks (arm) cross compile project. After running: build-wrapper-win-x86-64 --out-dir bw_output make MyProject.make Build succeeded, but I get empty build-wrapper-dump.json file. looking at the build-wrapper.log file I see: process created with pid: 25256 image path name: <C:\WindRiver_6.9\gnu\4.3.3-vxworks-6.9\x86-win32\bin\ccarm.exe> command line: <ccarm ...long line... MwInterfaceService.cpp > working directory: <CommonLib\> isWow64: 1 skipping process C:\WindRiver_6.9\gnu\4.3.3-vxworks-6.9\x86-win32\bin\ccarm.exe with pid: 25256 Is there a way to make build-wrapper to fill build-wrapper-dump.json file correctly? thanks, Mr. G
Got a SIGABRT while executing native code - error when running xsp4 on AWS during Cloudformation
I'm getting an error when starting the xsp4 server on an AWS Ubuntu AMI. The error is initialize: mono_thread_create_internal () failed, and then: Got a SIGABRT while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. The same command executes without errors on my own computer. Any idea what the error is - maybe a missing package, some configuration or something like that? Edit: Huh, that's weird, it's working when I log in via ssh and manually run the command. I need to run it during CloudFormation however, and it fails there. Maybe something isn't fully setup yet during CloudFormation, or the user account is different? But on second thought, doesn't CloudFormation run as root? Full log: + xsp4 --port 80 Cloud-init v. 0.7.9 running 'modules:final' at Sun, 22 Oct 2017 17:18:30 +0000. Up 12.78 seconds. Cloud-init v. 0.7.9 finished at Sun, 22 Oct 2017 17:19:27 +0000. Datasource DataSourceEc2. Up 69.50 seconds xsp4 Listening on address: 0.0.0.0 Root directory: /var/www/HelloWebApi Listening on port: 80 (non-secure) Hit Return to stop the server. The server is not started. at Mono.WebServer.ApplicationServer.Stop () in :0 at (wrapper remoting-invoke-with-check) Mono.WebServer.ApplicationServer:Stop () at Mono.WebServer.XSP.Server.DebugMain (System.String[] args, Boolean root, IApplicationHost ext_apphost, Boolean quiet) in :0 initialize: mono_thread_create_internal () failed Stacktrace: at at (wrapper managed-to-native) System.Net.Sockets.Socket.socket_pool_queue (System.Net.Sockets.SocketAsyncCallback,System.Net.Sockets.SocketAsyncResult) at System.Net.Sockets.Socket.QueueSocketAsyncResult (System.Collections.Generic.Queue`1,System.Net.Sockets.SocketAsyncWorker,System.Net.Sockets.SocketAsyncResult) at System.Net.Sockets.Socket.AcceptAsync (System.Net.Sockets.SocketAsyncEventArgs) at Mono.WebServer.ApplicationServer.RunServer () at System.Threading.ThreadHelper.ThreadStart_Context (object) at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool) at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool) at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext,System.Threading.ContextCallback,object) at System.Threading.ThreadHelper.ThreadStart () at (wrapper runtime-invoke) object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) Native stacktrace: /usr/bin/mono() [0x49ff2f] /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390) [0x7f39c549b390] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38) [0x7f39c50f5428] /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a) [0x7f39c50f702a] /usr/bin/mono() [0x630409] /usr/bin/mono() [0x63069c] /usr/bin/mono() [0x63076f] /usr/bin/mono() [0x58e6e5] [0x4044ec36] Debug info from gdb: ================================================================= Got a SIGABRT while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. =================================================================
If it works after SSH and not directly they most probably it is a TTY missing issue. If your server requires TTY then it won't start this way As you mentioned in your response that xsp4 waits for enter key to exit and take --nonstop if you don't want the behavior, then you should use that arg. It will make sure the TTY is not required. In case if a executable actually still requires TTY then you can look at the script command. Which does allocate a TTY and execute the command. See below for more details http://man7.org/linux/man-pages/man1/script.1.html
karma:unit fails with tmp browserify errors
I'm having the following issue and I'm the only developer in a team of 6 experiencing this issue. When I run the following command: $ grunt unit (Task: clean:reports install_custom_coverage karma:unit), I receive the following result: ... DEBUG [web-server]: serving: C:\Dev\life-web_components\node_modules\karma\static/context.html PhantomJS 1.9.8 (Windows 7) ERROR TEST RUN WAS CANCELLED because this file contains some errors: C:/cygwin/tmp/2cfb2e9479b44a59f6d3c57d366bd5b4.browserify IE 8.0.0 (Windows 7) ERROR TEST RUN WAS CANCELLED because this file contains some errors: C:/cygwin/tmp/2cfb2e9479b44a59f6d3c57d366bd5b4.browserify Chrome 41.0.2272 (Windows 7) ERROR TEST RUN WAS CANCELLED because this file contains some errors: C:/cygwin/tmp/2cfb2e9479b44a59f6d3c57d366bd5b4.browserify DEBUG [karma]: Run complete, exiting. DEBUG [launcher]: Disconnecting all browsers DEBUG [framework.browserify]: cleaning up DEBUG [launcher]: Process PhantomJS exited with code 0 DEBUG [temp-dir]: Cleaning temp dir C:\cygwin\tmp\karma-34162292 DEBUG [launcher]: Process Chrome exited with code 0 DEBUG [temp-dir]: Cleaning temp dir C:\cygwin\tmp\karma-61774528 DEBUG [reporter.junit]: JUnit results written to "C:/Dev/life-web_components/reports/unit_tests.xml". DEBUG [launcher]: Killed extra IE process 6528 DEBUG [launcher]: Process IE exited with code 0 DEBUG [temp-dir]: Cleaning temp dir C:\cygwin\tmp\karma-94332604 Warning: Task "karma:unit" failed. Use --force to continue. Aborted due to warnings. I've tried a range of suggestions, restarting CMDER, restarting machine, deleting node_modules, reinstalling global node modules, set autoWatch to false and various other attempts with no luck. As I'm the only developer in the team experiencing the issue, it appears to be environment related.
It turned out to be a component in our repo that required npm install within the directory to install it's dependencies.