How do I determine if my Jetty6-service run with administrative rights?
I need to setup Jetty on my XP dev box to run as a service.
http://docs.codehaus.org/display/JETTY/Win32Wrapper
It installs OK and I can see the Jetty6 Service in windows services manager.
But when I try to start it I get this error in the log file:
STATUS | wrapper | 2010/02/26 10:17:10 | Launching a JVM...
INFO | jvm 2 | 2010/02/26 10:17:10 | Error occurred during initialization of VM
INFO | jvm 2 | 2010/02/26 10:17:10 | Too small initial heap for new size specified
ERROR | wrapper | 2010/02/26 10:17:10 | JVM exited while loading the application.
from above link:
Note: The above application (Jetty-Service.exe) must execute with administrator rights otherwise, it fails.
I do have local administrative access to my XP dev box.
And when I run the jetty server as standalone from cmd.exe then it works fine.
(java -jar start.jar etc/jetty.xml)
Does anyone know how to solve this problem / where to look?
/Thanks.
Related
Start udating gcloud:
Your current Cloud SDK version is: 321.0.0
You will be upgraded to version: 322.0.0
┌──────────────────────────────────────────────────┐
│ These components will be updated. │
├──────────────────────────┬────────────┬──────────┤
│ Name │ Version │ Size │
├──────────────────────────┼────────────┼──────────┤
│ Cloud SDK Core Libraries │ 2021.01.05 │ 16.1 MiB │
│ Kuberun │ 0.0.1 │ 20.6 MiB │
└──────────────────────────┴────────────┴──────────┘
I get error:
╠═ Uninstalling: Cloud SDK Core Libraries ═╣
╠════════════════════════════════════════════════════════════╣
╠═ Uninstalling: Kuberun ═╣
ERROR: (gcloud.components.update) Отказано в доступе: [C:\Users\USER_NAME\AppData\Local\Google\ct4j-cloud-sdk\LATEST\google-cloud-sdk.staging\platform\kuberun_licenses\LICENSES.txt]
Ensure you have the permissions to access the file and that the file is not in use.
Env: Win10
i try from IDEA appEngine Plugin.
try from CMD with admin privilegies.
with some error
How to update this ?
Maybe you can disable Kuberun ? I use only appengine
I solved this issue by removing the folder kuberun_licenses from google-cloud-sdk\platform path. Not the one with .staging.
It looks like this is a known issue: https://status.cloud.google.com/incident/support/21001
Here is the workaround provided at that link:
Please run the following commands in a PowerShell window:
$gcloudDir = Get-Command gcloud | Select -ExpandProperty "Source" | Split-Path | Split-Path
attrib -r "$gcloudDir\platform\kuberun_licenses*.*" /s
attrib -r "$gcloudDir\lib\kuberun*.*" /s
attrib -r "$gcloudDir..\google-cloud-sdk.staging\platform\kuberun_licenses*.*" /s
attrib -r "$gcloudDir..\google-cloud-sdk.staging\lib\kuberun*.*" /s
Remove-Item "$gcloudDir..\google-cloud-sdk.staging" -Recurse
If any of the commands fail, proceed with running the remaining
commands.
After running the PowerShell script, run the following in a regular
Command Prompt (not PowerShell):
gcloud components update --version 320.0.0
Please note, after applying this workaround, do not run 'gcloud
components update' as this will re-trigger the issue. Please wait
until the fix is released before updating components.
I find only with full reinstall solution:
exit idea
rename folder C:\Users\Step\AppData\Local\Google\ct4j-cloud-sdk -> _ct4j-cloud-sdk
run idea
start gradle -> downloadCloudSDK
delete folder _ct4j-cloud-sdk
profit
Here is what I did,
On Win10, I went to
C:\Users{your user name}\AppData\Local\Google
removed dir ct4j-cloud-sdk
And ran:
mvn appengine:deploy
This solved the issue for me
For Eclipse,
Exit the Eclipse.
Remove the ct4j-cloud-sdk folder from gCloud installed dir.
Open the Eclipse and Deploy.
In a windows file browser, watch file
C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk.staging\platform\kuberun_licenses\LICENSES.txt
during the gcloud components update process. It will disappear then re-appear. When it does, right click on properties and uncheck Read Only then select Ok, then confirm the administrator pop-up. You must do this quickly or have some way of slowing the update script.
Nothing else worked. This does. Good luck.
New Date. New version. New Google Cloud trouble ... crap...
Your current Cloud SDK version is: 322.0.0
You will be upgraded to version: 323.0.0
| These components will be updated. |
+--------------------------+------------+----------+
| Name | Version | Size |
+--------------------------+------------+----------+
| Cloud SDK Core Libraries | 2021.01.08 | 16.1 MiB |
| Kuberun | 0.0.1 | 20.6 MiB |
| gcloud cli dependencies | 2021.01.08 | 10.7 MiB |
+--------------------------+------------+----------+
gcloud crashed (Error): [('C:\\Users\\USER_NAME\\AppData\\Local\\Google\\ct4j-cloud-sdk\\LATEST\\google-cloud-sdk\\platform\\gsutil\\third_party\\funcsigs\\docs\\index.rst', 'C:\\Users\\USER_NAME\\AppData\\Local\\Google\\ct4j-cloud-sdk\\LATEST\\google-cloud-sdk.staging\\platform\\gsutil\\third_party\\funcsigs\\docs\\index.rst', 'symbolic link privilege not held'), ('C:\\Users\\USER_NAME\\AppData\\Local\\Google\\ct4j-cloud-sdk\\LATEST\\google-cloud-sdk\\platform\\gsutil\\third_party\\mock\\docs\\changelog.txt', 'C:\\Users\\USER_NAME\\AppData\\Local\\Google\\ct4j-cloud-sdk\\LATEST\\google-cloud-sdk.staging\\platform\\gsutil\\third_party\\mock\\docs\\changelog.txt', 'symbolic link privilege not held')]
damn the updates, what to do with it, I lose one day a week with them ...
I am using Fuse 7.7 on Apache Karaf.
I am getting this error
2020-09-28 18:08:57,689 | ERROR | lueprint Extender: 2 | o.a.a.b.c.BlueprintContainerImpl | 51 - org.apache.aries.blueprint.core - 1.10.2 |
Unable to start container for blueprint bundle com.esb.iis-to-rm-vr/1.0.0 due to unresolved dependencies [(&(component=http)(objectClass=org.apache.camel.spi.ComponentResolver))]
java.util.concurrent.TimeoutException: null
I did the below steps. camel-http is not installed.
karaf#root()> features:install camel-http
karaf#root()> features:list | grep camel-http
camel-http4
karaf#root()> list | grep camel-http
67 | Active | 50 | 2.21.0.fuse-770013-redhat-00001 | camel-http-common
255 | Active | 50 | 2.21.0.fuse-770013-redhat-00001 | camel-http4
Please let me know apart from the below step, what are the steps i need to follow to install camel-http.
karaf#root()> features:install camel-http
Be careful that camel-http is only meant to be a producer. You won't be able to do from("http://...") only with him. To be able to do it, you need to add a camel component that will allow your route to bind itself to the karaf's jetty. You can try to install camel-jetty.
Moreover, you're feature:list | grep camel-http seemed to have only returned camel-http4. I'm note sure camel-http feature has been dropped, but you could always install http4 component
Overview:
When I attempt to run VSCode with the instructions given in the contributions page to download all the packages, build the source code, and then run it all on the terminal, an error message pops up saying that I don't have the electron app in the vscode directory. Shouldn't have the electron app been installed when I ran the yarn command to install and build all the dependencies?
Steps to reproduce the bug:
$ yarn //building and installing all dependencies
$ yarn watchd //building vscode
$ ./scripts/code.sh //running vscode
Error Message:
Error launching app
Unable to find Electron app at /home/juan/Desktop/Projects/vscode
Cannot find module '/home/juan/Desktop/Projects/vscode/out/main'. Please verify that the package.json has a valid "main" entry
System Details:
CPUs | Intel(R) Core(TM) i7-6600U CPU # 2.60GHz (4 x 3200)
-- | --
GPU Status | 2d_canvas: unavailable_softwareflash_3d: disabled_softwareflash_stage3d: disabled_softwareflash_stage3d_baseline: disabled_softwaregpu_compositing: disabled_softwaremultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: disabled_offrasterization: disabled_softwareskia_renderer: disabled_off_okvideo_decode: disabled_softwareviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: unavailable_softwarewebgl2: unavailable_software
Load (avg) | 1, 1, 1
Memory (System) | 7.63GB (0.12GB free)
Process Argv | . --no-sandbox
Screen Reader | no
VM | 0%
OS|Ubuntu 18.04 LTS
Extensions:
Extension | Author (truncated) | Version
-- | -- | --
Bookmarks | ale | 11.2.0
vscode-sqlite | ale | 0.8.2
code-gnu-global | aus | 0.2.2
npm-intellisense | chr | 1.3.0
vscode-svgviewer | css | 2.0.0
vscode-markdownlint | Dav | 0.36.0
jshint | dba | 0.10.21
vscode-eslint | dba | 2.1.5
vscode-html-css | ecm | 0.2.3
EditorConfig | Edi | 0.15.1
vscode-npm-script | eg2 | 0.3.12
vscode-firefox-debug | fir | 2.8.0
beautify | Hoo | 1.5.0
vscode-emacs-friendly | lfs | 0.9.0
rainbow-csv | mec | 1.7.0
python | ms- | 2020.5.80290
cpptools | ms- | 0.28.2
debugger-for-chrome | msj | 4.12.8
sqltools | mtx | 0.22.5
material-icon-theme | PKi | 4.1.0
rust | rus | 0.7.8
lc2k | vio | 1.1.1
Here is the bug report I filled in the vscode github page: https://github.com/microsoft/vscode/issues/99537
I got this same error myself when the code did not build correctly.
In your second step you do:
yarn watchd
I tried this command myself, but ran into the same issue that you have stated here. Although the official wiki suggests this as a tip, I would just ignore it.
Instead, do either of these instead (this is what the official wiki originally suggest to do):
Type: Ctrl + Shift + B
Or alternatively use the Command Palette:
Type: Ctrl + Shift + P
Search for the option called: Tasks: Run Build Task and select it.
Once you start the build task you'll see a couple of things:
Firstly, at the bottom of VS Code (on your status line), VS Code will let you know the code is building.
Secondly, The build command will open two terminals:
Task - Build VS Code
Task - Build VS Code Extensions
Watch the output for both of terminals, make sure:
Task - Build VS Code terminal outputs: [some time] Finished compilation ...
and
Task - Build VS Code Extensions terminal outputs: [some time] Finished compilation extensions ...
If not and the build fails, you'll probably get a notification from VS code saying so (You'll probably get the error twice, one for each task):
yarn ... exited with code [some non-zero integer]
A common error that may occur is the ENOSPC error from inotify (also documented well in a medium blog). You'll want to issue this command:
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
Arch users would issue:
echo fs.inotify.max_user_watches=524288 | sudo tee /etc/sysctl.d/40-max-user-watches.conf && sudo sysctl --system
After fixing this, trying to build again should work. Start the build task again and make sure both tasks succeed. (You'll notice that the tasks do not end after they succeed. This is because they will watch for changes you make in the code while developing and automatically recompile for you).
If successful you may finally issue:
./scripts/code.sh
A new instance of VS Code should open called: Code - OSS dev. This is the version of VS Code you just built.
I tried upgrading to GGTS 3.2 on windows7 64bit and java 7.0.21. running on works pc with a proxy config enabled in internet settings
i create a new project in a new workspace. I then try and run the console for the app.
the console fires up and you can use for ~60 seconds. After that the sts ide throws a timeout error and the console is killed
error in log looks like this :
!ENTRY org.grails.ide.eclipse.core 4 0 2013-06-18 22:08:15.103
!MESSAGE Problem executing: console
!STACK 1
org.eclipse.core.runtime.CoreException: The command 'C:\Program Files (x86)\Java\jdk1.7.0_21\bin\javaw.exe (18 Jun 2013 22:06:14)' was terminated because it didn't produce new output for some time.
See details for the output produced so far.
If you think the command simply needed more time, you can increase the time limit in the Grails preferences page.
See menu Windows >> Preferences >> Grails >> Launch
at org.grails.ide.eclipse.core.launch.SynchLaunch$LaunchResult.getCoreException(SynchLaunch.java:168)
at org.grails.ide.eclipse.core.launch.SynchLaunch.synchExec(SynchLaunch.java:57)
at org.grails.ide.eclipse.commands.GrailsExecutor.synchExec(GrailsExecutor.java:131)
at org.grails.ide.eclipse.commands.GrailsCommand.synchExec(GrailsCommand.java:169)
at org.grails.ide.eclipse.ui.internal.inplace.GrailsLaunchUtils$1.run(GrailsLaunchUtils.java:120)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Contains: ------System.out:-----------
| Loading Grails 2.2.1
| Configuring classpath.
| Environment set to development.....
| Packaging Grails application....
| Compiling 1 source files.....
| Packaging Grails application.
| Compiling 1 source files.....
Contains: ------System.err:-----------
Terminating process: Timeout: no new output for 60000 milliseconds
!SUBENTRY 1 org.grails.ide.eclipse.core 4 4 2013-06-18 22:08:15.103
!MESSAGE The command 'C:\Program Files (x86)\Java\jdk1.7.0_21\bin\javaw.exe (18 Jun 2013 22:06:14)' was terminated because it didn't produce new output for some time.
See details for the output produced so far.
If you think the command simply needed more time, you can increase the time limit in the Grails preferences page.
See menu Windows >> Preferences >> Grails >> Launch
!SUBENTRY 2 org.grails.ide.eclipse.core 4 0 2013-06-18 22:08:15.103
!MESSAGE ------System.out:-----------
| Loading Grails 2.2.1
| Configuring classpath.
| Environment set to development.....
| Packaging Grails application....
| Compiling 1 source files.....
| Packaging Grails application.
| Compiling 1 source files.....
!SUBENTRY 2 org.grails.ide.eclipse.core 4 0 2013-06-18 22:08:15.103
!MESSAGE ------System.err:-----------
Terminating process: Timeout: no new output for 60000 milliseconds
There was something like this is the sts/ggts forum which claimed it had been fixed in 3.3m2. and might have been to do with pref>groovy>grails>launch - keep running flag - however i enebaled and diabsled this and it made no difference
i tried installing 3.3m2 and tried the same - new workspace - new project. I run the console, 60 seconds later i get a timeout buty the console stays up - error now reads
| Configuring classpath.
| Environment set to development.....
| Packaging Grails application....
| Compiling 1 source files.....
| Packaging Grails application.
| Compiling 1 source files.....
Contains: ------System.err:-----------
!SUBENTRY 1 org.grails.ide.eclipse.core 4 4 2013-06-18 23:27:11.110
!MESSAGE Command terminated with an exception: java.io.IOException: Cannot run program "jps": CreateProcess error=2, The system cannot find the file specified (see details for partial output)
!STACK 0
java.io.IOException: Cannot run program "jps": CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start(Unknown Source)
at org.grails.ide.eclipse.longrunning.client.GrailsProcessStackTracer.exec(GrailsProcessStackTracer.java:104)
at org.grails.ide.eclipse.longrunning.client.GrailsProcessStackTracer.getGrailsProcessId(GrailsProcessStackTracer.java:72)
at org.grails.ide.eclipse.longrunning.client.GrailsProcessStackTracer.getStackTraces(GrailsProcessStackTracer.java:92)
at org.grails.ide.eclipse.longrunning.client.GrailsClient.executeCommand(GrailsClient.java:381)
at org.grails.ide.eclipse.longrunning.client.GrailsCommandExecution.execute(GrailsCommandExecution.java:85)
at org.grails.ide.eclipse.longrunning.LongRunningProcessGrailsExecutor.synchExec(LongRunningProcessGrailsExecutor.java:82)
at org.grails.ide.eclipse.commands.GrailsCommand.synchExec(GrailsCommand.java:169)
at org.grails.ide.eclipse.ui.internal.inplace.GrailsLaunchUtils$1.run(GrailsLaunchUtils.java:127)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.<init>(Unknown Source)
at java.lang.ProcessImpl.start(Unknown Source)
... 10 more
!SUBENTRY 2 org.grails.ide.eclipse.core 4 0 2013-06-18 23:27:11.110
!MESSAGE ------System.out:-----------
Loading Grails 2.2.2
| Configuring classpath.
| Environment set to development.....
| Packaging Grails application....
| Compiling 1 source files.....
| Packaging Grails application.
| Compiling 1 source files.....
!SUBENTRY 2 org.grails.ide.eclipse.core 4 0 2013-06-18 23:27:11.110
!MESSAGE ------System.err:-----------
Any one else had this and is there a workaround?
The "Execute Grails Command" function wasn't designed to support persistent processes. It worked previously by chance, but no longer does.
The recommended way to execute long-running grails processes in Eclipse/STS/GGTS is to configure an eclipse run configuration to execute the long-running grails commands. (Run -> Run Configurations...)
I have installed apache archiva stand alone in my system.But when i try to start it,itshows the error apache archiva failed to start.My codes are given below
D:\apache-archiva-1.3.5>java -version
java version "1.6.0_10"
Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
Java HotSpot(TM) Client VM (build 11.0-b15, mixed mode, sharing)
D:\apache-archiva-1.3.5>PATH=c:\Windows\system32;C:\Program Files (x86)\Java\jdk
1.6.0_10\bin
D:\apache-archiva-1.3.5>PATH=c:\Windows\system32;C:\Program Files (x86)\Java\jdk
1.6.0_10\bin;D:\apache-archiva-1.3.5\bin
D:\apache-archiva-1.3.5>archiva.bat install
wrapper | Apache Archiva installed.
D:\apache-archiva-1.3.5>archiva.bat start
wrapper | Starting the Apache Archiva service...
wrapper | The Apache Archiva service was launched, but failed to start.
Press any key to continue . . .
Instead of using
C:\apache-archiva-2.2.1\bin>archiva start
if you use console it will work.
C:\apache-archiva-2.2.1\bin>archiva console
wrapper | --> Wrapper Started as Console
wrapper | Launching a JVM...
jvm 1 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
jvm 1 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
jvm 1 |
jvm 1 | 2016-06-05 01:11:49.022:WARN:oejd.ContextDeployer:ContextDeployer is deprecated. Use ContextProvider
jvm 1 | 2016-06-05 01:11:49.022:WARN:oejd.WebAppDeployer:WebAppDeployer is deprecated. Use WebAppProvider
jvm 1 | 2016-06-05 01:11:49.147:INFO:oejs.Server:jetty-8.1.14.v20131031
jvm 1 | 2016-06-05 01:11:49.178:INFO:oejs.NCSARequestLog:Opened C:\apache-archiva-2.2.1\logs\request-20160604.log
jvm 1 | 2016-06-05 01:11:49.225:INFO:oejd.ContextDeployer:Deploy C:\apache-archiva-2.2.1\contexts\archiva.xml -> o.e.j.w.WebAppContext{/,null},C:\apache-archiva-2.2.1/apps/archiva
jvm 1 | 2016-06-05 01:11:53.149:INFO:oejpw.PlusConfiguration:No Transaction manager found - if your webapp requires one, please configure one.
jvm 1 | 2016-06-05 01:11:53.453:INFO:oejw.StandardDescriptorProcessor:NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet
jvm 1 | 2016-06-05 01:11:54.755:INFO:/:Initializing Spring root WebApplicationContext
jvm 1 | Jun 05, 2016 1:12:09 AM org.apache.tomcat.jdbc.pool.ConnectionPool init
jvm 1 | WARNING: maxIdle is larger than maxActive, setting maxIdle to: 20
jvm 1 | 2016-06-05 01:12:25.275:INFO:oejs.AbstractConnector:Started SelectChannelConnector#0.0.0.0:8080