I couldn't find the license anywhere... So, it'd be nice if it could be added to the code with a LICENSE.txt (I'd like to use it in PyDev: http://pydev.org, so, it'd be nice it if was an EPL-compatible license).

Hi @segrey . This is a follow-up to our discussion about the component ownership before the new year. I am ready to proceed with this topic.

Just to provide some context, I still need to re-setup the Windows development environment to do a release with MVS 14.0 tools version. I will likely be able to do it in few weeks when I get a new laptop (migrating from Mac to Windows). I hope to have a bit more time to maintain this component and the release environment, but it will be great to work together on this component.

Invoking mvn clean removes the target/ directory but not the native components. It should somehow invoke build.cmd clean in a similar fashion to how the normal build invokes build.cmd build.

Greetings.

I am getting an exception from winp (v1.25, bundled with Jenkins LTS 2.73.3), specifically from Native.java, line 144.

I believe it is coming from the getJarFile() method. There is an if-statement on line 166 that returns null if the url doesn't start with jar: or wsjar:.

In my case the url starts with zip: so it is failing the test & coming up null.

Does this need a code fix or is there something I can do on my end to workaround the issue?

Dec 01, 2017 3:58:35 PM org.jvnet.winp.Native loadByUrl
WARNING: Failed to load DLL from static location
java.lang.RuntimeException: Failed to locate JAR file by URL zip:C:/[[[path redacted]]]/servers/AdminServer/tmp/_WL_user/Jenkins_LTS_2.73.3/frocxk/war/WEB-INF/lib/winp-1.25.jar!/winp.x64.dll
at org.jvnet.winp.Native.extractToStaticLocation(Native.java:144)
at org.jvnet.winp.Native.loadByUrl(Native.java:129)
at org.jvnet.winp.Native.load(Native.java:99)
at org.jvnet.winp.Native.(Native.java:70)
at org.jvnet.winp.WinProcess.enableDebugPrivilege(WinProcess.java:226)
at hudson.util.ProcessTree$Windows.(ProcessTree.java:555)
at hudson.util.ProcessTree.get(ProcessTree.java:350)
at hudson.Launcher$LocalLauncher.kill(Launcher.java:949)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:502)
at hudson.model.Run.execute(Run.java:1737)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:421)

Currently, sendctrlc.exe is spawned in winp.cpp.
Is it possible to use java.lang.ProcessBuilder to spawn sendctrlc.exe and, thus, simplify code?
If no, it'd be great to write a comment in code explaining decision.

When winp.folder.preferred property is being used actually parent of such folder is used.

as per #69 (review) the Jenkinsci org is willing to take ownership of this repository.

Would you be willing to request a support issue with Github to transfer the ownership of this repository please.

@oleg-nenashev

Now that #116 has landed, the next step is to enable JEP-229 CD for this repository, using GitHub Actions (as is standard for CD in the Jenkins project). The CD work should largely follow https://www.jenkins.io/doc/developer/publishing/releasing-cd/ but may be slightly more involved in that it needs to run on a Windows 2019 system in GitHub Actions rather than a Linux system in GitHub Actions (as the instructions currently describe).

The standard process used in Jenkins is to run CD after CI has passed, skipping the tests in CD. Since this CD build is more complicated, and since the test suite runs in milliseconds, it may be desirable to also run the tests again during CD.

One complication is that CD needs to sign the binaries after building them but before putting them in the JAR. The signing should take place as described here with some commands like:

WinSDK/bin/signtool sign /f path-to-certificate.pfx /p PASSWORD /t http://timestamp.digicert.com native\x64\Release\winp.dll
WinSDK/bin/signtool sign /f path-to-certificate.pfx /p PASSWORD /t http://timestamp.digicert.com native\x64\Release\winp.x64.dll

It may be necessary to engage with the Jenkins infrastructure team for access to a certificate. The password for the certificate can be stored by a GitHub administrator as a secret in the "Actions secrets and variables" configuration for this repository, where it may be consumed by the CD (but not CI!) build.

According to the code, the getCmdLineAndEnvVars() command is unreliable on newer modern OS versions.

The last ReadProcessMemory command may fail:

	// Checking the read size is more likely to result in success than checking the BOOL that is
	// returned by ReadProcessMemory, on newer versions of Windows. That said, neither approach
	// is particularly reliable past Vista. This approach differs from checking the BOOL in that
	// it will succeed for partial reads that read _some_ data, where the other approach fails.

There are many usages of the command in WinP itself and in the dependent codebase like Jenkins ( JENKINS-30782). Example of the log in Jenkins:

The error that I get is ERROR: Build step failed with exception
org.jvnet.winp.WinpException: Failed to read environment variable table error=299 at .\envvar-cmdline.cpp:201
at org.jvnet.winp.Native.getCmdLineAndEnvVars(Native Method)
at org.jvnet.winp.WinProcess.parseCmdLineAndEnvVars(WinProcess.java:126)
at org.jvnet.winp.WinProcess.getCommandLine(WinProcess.java:102)
at org.jvnet.winp.WinProcess.killRecursively(WinProcess.java:66)
at hudson.util.ProcessTree$Windows$1.killRecursively(ProcessTree.java:425)
at hudson.util.ProcessTree.killAll(ProcessTree.java:141)
at hudson.Proc$LocalProc.destroy(Proc.java:379)
at hudson.Proc$LocalProc.join(Proc.java:352)
at hudson.Launcher$ProcStarter.join(Launcher.java:389)
at hudson.tasks.Ant.perform(Ant.java:217)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
at hudson.model.Build$BuildExecution.build(Build.java:205)
at hudson.model.Build$BuildExecution.doRun(Build.java:162)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:408

Proposals:

• Fix the failing ReadProcessMemory operation if possible
• Reduce the scope of the EnvVars usage, provide API for retrieving the CMD Line only
• It won't help Jenkins, which terminates processes by using EnvVars filters (e.g. by BUILD_NUMBER env. var)

According to the winp-1.23 release experience, it makes sense to push changes to GitHub only when the release process uploads the package to Sonatype Staging Area and pushes the documentation to the gh-pages branch

Windows 8.1 Pro 64-bit

Windows Defender | About

Antimalware Client Version: 4.7.205.0
Engine Version: 1.1.11701.0
Antivirus definition: 1.199.2816.0
Antispyware definition: 1.199.2816.0
Network Inspection System Engine Version: 2.1.11502.0
Network Inspection System Definition Version: 114.3.0.0

http://windows.microsoft.com/en-us/windows/using-defender#1TC=windows-8

Downloading https://github.com/kohsuke/winp/archive/winp-1.23.zip using Chrome 43.0.2357.124 results in

winp-winp-1.23.zip Anti-virus software detected a virus.
https://codeload.github.com/kohsuke/winp/zip/winp-1.23

Seems several GitHub permissions are missing on my account.

• mvn:release step was able to create an empty version (seems to be OK)
• the tag has been also added => commit & push operations work well
• winp-1.23 snapshot is also available on Maven Central
• I was able to commit to gh-pages directly ( db20e0c )
• Seems https://github.com/kohsuke/wagon-gitsite somehow takes a wrong Git installation or ignores GIT_SSH variable

[INFO] [INFO] --- maven-site-plugin:3.3:deploy (default-deploy) @ winp ---
[INFO] [INFO] Parent project loaded from repository: org.kohsuke:pom:pom:10
[INFO] scm:git:ssh://github.com/kohsuke/winp.git/ - Session: Opened
[INFO] [INFO] Pushing /remote/ru20home1/nenashev/Documents/jenkins/libs/winp/target/checkout/target/site
[INFO] [INFO]    >>> to scm:git:ssh://github.com/kohsuke/winp.git/./
[INFO] Uploading: ./ to scm:git:ssh://github.com/kohsuke/winp.git/
[INFO]
[INFO] [INFO] Executing: /bin/sh -c cd /remote/ru20home1/nenashev/Documents/jenkins/libs/winp/target/checkout/. && git ls-files
[INFO] [INFO] Working directory: /remote/ru20home1/nenashev/Documents/jenkins/libs/winp/target/checkout/.
[INFO] [INFO] Executing: /bin/sh -c cd /tmp/wagon-scm324908943.checkout && git init
[INFO] [INFO] Working directory: /tmp/wagon-scm324908943.checkout
[INFO] [INFO] Executing: /bin/sh -c cd /tmp/wagon-scm324908943.checkout && git remote add origin ssh://github.com/kohsuke/winp.git
[INFO] [INFO] Working directory: /tmp/wagon-scm324908943.checkout
[INFO] [INFO] Executing: /bin/sh -c cd /tmp/wagon-scm324908943.checkout && git pull origin refs/heads/gh-pages
[INFO] [INFO] Working directory: /tmp/wagon-scm324908943.checkout
[INFO]  Transfer error: org.apache.maven.scm.ScmException: Unable to commit file. The git-pull command failed. Permission denied (publickey).
[INFO] fatal: The remote end hung up unexpectedly
[INFO]
[INFO] scm:git:ssh://github.com/kohsuke/winp.git/ - Session: Disconnecting
[INFO] scm:git:ssh://github.com/kohsuke/winp.git/ - Session: Disconnected
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] BUILD FAILURE
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Total time: 55.243 s
[INFO] [INFO] Finished at: 2015-02-17T08:45:39+03:00
[INFO] [INFO] Final Memory: 39M/367M
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.3:deploy (default-deploy) on project winp: Error uploading site: Error checking out: Unable to commit file. The git-pull command failed. Permission denied (publickey).
[INFO] [ERROR] fatal: The remote end hung up unexpectedly
[INFO] [ERROR] -> [Help 1]
[INFO] [ERROR]
[INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[INFO] [ERROR]
[INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:08 min
[INFO] Finished at: 2015-02-17T08:45:40+03:00
[INFO] Final Memory: 11M/233M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.3.2:perform (default-cli) on project winp: Maven execution failed, exit code: '1' -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

When a process is started without console window, executing org.jvnet.winp.WinProcess#sendCtrlC leads to running sendctrlc.exe with a new console visible window. Even though sendctrlc.exe is a short-living process, the console window flickering is noticeable.

To reproduce the issue, please see myapp.zip.
It's a simple Java Swing application running new WinProcess(123).sendCtrlC() on button click.

1. Unzip the project and optionally rebuild it.
2. Run the app with run.cmd. Or start it manually, just ensure you're using javaw.exe instead of java.exe to start the process without console window.
3. A window with a single button will appear:
   
4. Click it and a console window will appear and hide.

The build.cmd flow for WinP on Windows does not require pushing binaries to GitHub though it may be required if @kohsuke needs non-Windows machine to spin releases. The approach needs to be investigated.

In the latter case maybe it is possible to stage native binaries in AppVeyor/NuGet and then just download them for the release purpose. Not good since it requires untested rebuild of the WinP JAR

Jenkins background:

The current Jenkins version uses "winp" to recursively terminate Windows processes. Such approach works well, but ProcessKiller extensions cannot be invoked for the entire process tree on Windows, so their behavior differs from Linux.

I propose to replace getChildren() and getParent() method stubs by working implementations using additional methods in the native part.

My use-case:

• Terminate Cygwin processes using https://wiki.jenkins-ci.org/display/JENKINS/Cygwin+Process+Killer+Plugin

https://issues.jenkins-ci.org/browse/JENKINS-20289

Hello,

If winp.jar is located in unc path (with write access) the following exception can occur :

16 2011 15:26:49 org.jvnet.winp.Native load
WARNING: Failed to write winp.dll
java.io.FileNotFoundException: \Optimus\TestWinp1.16\lib\winp.dll (Cannot find the file specified)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.(Unknown Source)
at java.io.FileOutputStream.(Unknown Source)
at org.jvnet.winp.Native.load(Native.java:81)
at org.jvnet.winp.Native.(Native.java:52)
at org.jvnet.winp.WinProcess.(WinProcess.java:41)
at Test.main(Test.java:112)
Exception in thread "main" java.lang.UnsatisfiedLinkError: Expecting an absolute path of the library: \Optimus\TestWinp1.16\lib\winp.dll
at java.lang.Runtime.load0(Unknown Source)
at java.lang.System.load(Unknown Source)
at org.jvnet.winp.Native.loadDll(Native.java:158)
at org.jvnet.winp.Native.load(Native.java:90)
at org.jvnet.winp.Native.(Native.java:52)
at org.jvnet.winp.WinProcess.(WinProcess.java:41)
at Test.main(Test.java:112)

Changes to fix it, in org/jvnet/winp/Native.java (form winp1.5)

64,65c64,65
was:

if(filePortion.startsWith("/"))
filePortion = "/"+filePortion;

should be:
if(filePortion.startsWith("//"))
filePortion = filePortion.substring(2);

69c69
was:
if(!dllFile.exists()/* || jarFile.lastModified()>dllFile.lastModified()*/) {

should be:
if(!dllFile.exists() || jarFile.lastModified()>dllFile.lastModified()) {

Thank you

The way that winp's killRecursive works means that occasionally, the tree it tries to walk hits an old process whose parent exited before them, but had the same process id as one of the processes in the tree we are trying to kill (The PPID of these children is not cleared or reset when the parent exits).

This means that random processes die and on a windows VM, it can BSOD the entire VM.

Face with the problem where DLL winp.x64 cannot load on ARM machine
Tried using OpenJDK 17.0.0, OpenJDK 16.0.2 on tosh have error:
WARNING: Failed to load DLL from static location
java.lang.UnsatisfiedLinkError: C:\jenkins\remoting\jarCache\44\winp.x64.BFFE30B3B50581290B1866EF8D48C609.dll: Can't load AMD 64-bit .dll on a ARM 64-bit platform

To not warn user about launching an application from an "unknown publisher".

Native class doesn't try to load DLL via temp location and class loading just fails with java.lang.UnsatisfiedLinkError exception "Native Library %homepath%.jenkins\cache\jars\2C\winp.x64.C29A3A9FA89660FAA034AABD3B4E3E20.dll already loaded in another classloader".
Although there is a code for this purpose, it cannot be reached due to uncought exception.

Particularly it is a root cause of https://issues.jenkins-ci.org/browse/JENKINS-20913

The following issue describes a problem still present in winp due to a failure to merge the pull request correctly: winp sometimes kills random processes when using killRecursive

Specifically this pull request was not correctly merged: #8

A simple check would seem to indicate the commit was merged:

$ git tag --contains 27a1f7ca64f4dfa0f243dfc834e671ffc3c0b8b9
1.23-beta
winp-1.17
winp-1.18
winp-1.19
winp-1.20
winp-1.21
winp-1.22
winp-1.23

However the merge (b859526) actually reverted the change during the merge. Note that native/winp.cpp is listed as a conflict. It would appear a merge strategy "ours" was used to resolve the conflict, hence discarding the change.

We encountered this problem only recently because we have been using the 1.17-atlassian1 release of winp (found here https://github.com/bturner/winp/tree/winp-1.17-atlassian1), which does include a fix for the issue, for a long time. We recently upgraded to the 1.19 release from the primary winp repository and have been seeing this problem since.

Sometimes winp is killing all processes on the machine.
It happens with different windows version.
For more details see https://youtrack.jetbrains.com/issue/IDEA-131748

The getCmdLineAndEnvVars function seems to be incompatible with 32bit windows os.

We currently have a jenkins server that runs on a x64 windows machine.
This machine starts a java process on a jenkins slave that is running on a 32bit windows machine.

The process on the 32bit machine cannot be killed. The getCmdLineAndEnvVars checks if the process is wow64, which it is not according to the msdn documentation:

A pointer to a value that is set to TRUE if the process is running under WOW64. If the process is running under 32-bit Windows, the value is set to FALSE. If the process is a 64-bit application running under 64-bit Windows, the value is also set to FALSE.

This means the iswow64 check will always fail, causing an error. This also means the process will never get cleaned.

The check should also look for PROCESSOR_ARCHITECTURE_INTEL and not just wow64

Sometimes return new WinProcess(myProcess).sendCtrlC(); fails with with the following exception:

java.lang.NoClassDefFoundError: Could not initialize class org.jvnet.winp.Native
	at org.jvnet.winp.WinProcess.<init>(WinProcess.java:46)
	at com.intellij.execution.process.KillableProcessHandler.destroyProcessGracefully(KillableProcessHandler.java:168)
	at com.intellij.execution.process.KillableProcessHandler.doDestroyProcess(KillableProcessHandler.java:143)
	at com.intellij.execution.process.KillableProcessHandler.destroyProcessImpl(KillableProcessHandler.java:127)
	at com.intellij.execution.process.ProcessHandler$1.run(ProcessHandler.java:100)
	at com.intellij.execution.process.ProcessHandler$TasksRunner.execute(ProcessHandler.java:256)
	at com.intellij.execution.process.ProcessHandler.destroyProcess(ProcessHandler.java:95)
	at com.intellij.execution.ui.RunContentManagerImpl$CloseListener.closeQuery(RunContentManagerImpl.java:696)
	at com.intellij.execution.ui.RunContentManagerImpl$CloseListener.contentRemoveQuery(RunContentManagerImpl.java:649)
	at com.intellij.ui.content.impl.ContentManagerImpl.fireContentRemoveQuery(ContentManagerImpl.java:561)
	at com.intellij.ui.content.impl.ContentManagerImpl.removeContent(ContentManagerImpl.java:201)
	at com.intellij.ui.content.impl.ContentManagerImpl.removeContent(ContentManagerImpl.java:166)
	at com.intellij.openapi.wm.impl.content.ContentTabLabel$1.lambda$getAction$0(ContentTabLabel.java:69)
	at com.intellij.openapi.wm.impl.content.ContentTabLabel$2.execute(ContentTabLabel.java:134)
	at com.intellij.util.ui.BaseButtonBehavior$MyMouseListener.execute(BaseButtonBehavior.java:173)
	at com.intellij.util.ui.BaseButtonBehavior$MyMouseListener.mouseReleased(BaseButtonBehavior.java:156)
	at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:289)
	at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:289)
	at java.awt.Component.processMouseEvent(Component.java:6548)
	at javax.swing.JComponent.processMouseEvent(JComponent.java:3325)
	at java.awt.Component.processEvent(Component.java:6313)
	at java.awt.Container.processEvent(Container.java:2237)
	at java.awt.Component.dispatchEventImpl(Component.java:4903)
	at java.awt.Container.dispatchEventImpl(Container.java:2295)
	at java.awt.Component.dispatchEvent(Component.java:4725)
	at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4889)
	at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4526)
	at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4467)
	at java.awt.Container.dispatchEventImpl(Container.java:2281)
	at java.awt.Window.dispatchEventImpl(Window.java:2746)
	at java.awt.Component.dispatchEvent(Component.java:4725)
	at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:764)
	at java.awt.EventQueue.access$500(EventQueue.java:98)
	at java.awt.EventQueue$3.run(EventQueue.java:715)
	at java.awt.EventQueue$3.run(EventQueue.java:709)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:90)
	at java.awt.EventQueue$4.run(EventQueue.java:737)
	at java.awt.EventQueue$4.run(EventQueue.java:735)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
	at java.awt.EventQueue.dispatchEvent(EventQueue.java:734)
	at com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.java:718)
	at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:663)
	at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:366)
	at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
	at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
	at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

The exception was received automatically from a WebStorm instance. It's also known that OS is Windows 10.
Unfortunately, there is no "caused by" linked exception making it impossible to figure out the cause.
Is it possible to enhance thrown exception?

Hi,

I'm trying to get the commandline of a WinProcess constructed via pid and got following exception:

org.jvnet.winp.WinpException: Failed to read environment variable table error=299 at .\envvar-cmdline.cpp:114
at org.jvnet.winp.Native.getCmdLineAndEnvVars(Native Method)
at org.jvnet.winp.WinProcess.parseCmdLineAndEnvVars(WinProcess.java:114)
at org.jvnet.winp.WinProcess.getCommandLine(WinProcess.java:90)
at de.heuboe.csb.manage.uz.stdImpl.StdUZSystemMonitor.restart(StdUZSystemMonitor.java:297)
at de.heuboe.csb.manage.uz.stdImpl.StdUZManagerImpl.init(StdUZManagerImpl.java:84)
at de.heuboe.csb.manage.uz.stdImpl.StdUZFactory.init(StdUZFactory.java:33)
at de.heuboe.csb.manage.uz.stdImpl.StdUZFactory.(StdUZFactory.java:26)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:126)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:105)
at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:278)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:993)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:897)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:291)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:288)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:190)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:574)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
at org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:139)
at org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:93)
at de.heuboe.csb.manage.manager.CorbaServiceTestRunner.main(CorbaServiceTestRunner.java:19)

System is: Windows 7/x64 Professional.

Thx

Milraun

'Java_org_jvnet_winp_Native_isCriticalProcess' is available in the library API as WinProcess#isCritical() . This method will return error if the user lacks the PROCESS_TERMINATE permission. But this permission is actually not required to query the process info.

Likely it was a copy-paste error from the KillProcess() method

upstream of JENKINS-67681

The overhead in obtaining the process environemnt variables is too great resulting in a single no-op build on windows taking 700+ms just to enumerate all the processes looking for something to kill.

More info: winsw/winsw#56

Windows 8.1 Pro

When running manually:

When running via Java API:

Exception in thread "main" org.jvnet.winp.WinpException: External Ctrl+C execution failed for process pid=1160. Ctrl+C process exited with code -1073741515: Failed to attach to the console (see the AttachConsole WinAPI call). error=0 at winp.cpp:59
	at org.jvnet.winp.Native.sendCtrlC(Native Method)
	at org.jvnet.winp.Native.sendCtrlC(Native.java:90)
	at org.jvnet.winp.WinProcess.sendCtrlC(WinProcess.java:93)
	at example.Main.main(Main.java:29)

See example project to reproduce: stop-child-process.zip.

Where is the source for the dlls? Should it be included in this repository?