This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 258791 - java.io.IOException: CreateProcess error=193, %1 nie jest prawid?ow? aplikacj? systemu Win32
Summary: java.io.IOException: CreateProcess error=193, %1 nie jest prawid?ow? aplikacj...
Status: STARTED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WildFly (show other bugs)
Version: 8.2
Hardware: All All
: P3 normal (vote)
Assignee: ehsavoie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-12 13:27 UTC by cezariusz
Modified: 2016-06-09 10:33 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 220828

Attachments
stacktrace (1.12 KB, text/plain)
2016-04-12 13:27 UTC, cezariusz 		Details
stacktrace (1.13 KB, text/plain)
2016-04-12 13:29 UTC, cezariusz 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description cezariusz 2016-04-12 13:27:12 UTC 
This issue was reported manually by cezariusz.
It already has 5 duplicates 


Build: NetBeans IDE Dev (Build 201604120001)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.60-b23, Java(TM) SE Runtime Environment, 1.8.0_60-b27
OS: Windows 8.1

User Comments:
cezariusz: Starting Tomcat

nonono: ?????????????????WildFly??????????????????????????

samyomar82: when I tried to run wildfly 10 for the first time.

cezariusz: Starting WildFly

jizel: Trying to start Wildfly AS 9.0.1. Exception during start.

Working on Win7, CLI Wildfly standolane working just fine.




Stacktrace: 
java.io.IOException: CreateProcess error=193, %1 nie jest prawid?ow? aplikacj? systemu Win32
   at java.lang.ProcessImpl.create(ProcessImpl.java:0)
   at java.lang.ProcessImpl.<init>(ProcessImpl.java:386)
   at java.lang.ProcessImpl.start(ProcessImpl.java:137)
   at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
   at org.openide.execution.NbProcessDescriptor.exec(NbProcessDescriptor.java:202)
   at org.netbeans.modules.javaee.wildfly.ide.WildflyStartRunnable.createProcess(WildflyStartRunnable.java:363)
Comment 1 cezariusz 2016-04-12 13:27:14 UTC 
Created attachment 159232 [details]
stacktrace
Comment 2 cezariusz 2016-04-12 13:29:54 UTC 
Created attachment 159233 [details]
stacktrace

WildFly 10
Comment 3 ehsavoie 2016-04-12 14:21:14 UTC 
This is due to some limitations on your OS configuration that won't allow the PowerShell scripts to be run since those aren't signed.
Comment 4 cezariusz 2016-04-12 14:28:40 UTC 
What is the advantage of running it through the PowerShell script instead of bat script? Or at least give me an option.
Comment 5 ehsavoie 2016-04-12 14:36:19 UTC 
we are using the bat script which calls the powershell script
Comment 6 cezariusz 2016-04-19 09:43:35 UTC 
(In reply to ehsavoie from comment #5)
> we are using the bat script which calls the powershell script

So what am I supposed to do to make it work?
Comment 7 ehsavoie 2016-04-19 11:18:56 UTC 
This is a Windows permission issue it seems.
I'm afraid I can help you there, maybe you can start the server manually, the plugin should be able to connect to it.
Comment 8 jizel 2016-04-19 11:24:01 UTC 
This is not an issue for me anymore in later NetBeans builds. I am using nightly build 201603240001 on several Windows machines and Wildfly is starting neatly. Killing it doesn't work though...
Comment 9 jizel 2016-04-19 11:24:52 UTC 
But I certainly haven't changed any Windows permissions or anything..
Comment 10 cezariusz 2016-04-19 11:27:59 UTC 
(In reply to jizel from comment #8)
> This is not an issue for me anymore in later NetBeans builds. I am using
> nightly build 201603240001 on several Windows machines and Wildfly is
> starting neatly. Killing it doesn't work though...

I'm using 201604120001 and it is an issue for me.

(In reply to ehsavoie from comment #7)
> maybe you can start the server manually,

Of course I can, using both standalone.bat and standalone.ps1, but that's not a solution, it's a workaround.
Comment 11 ehsavoie 2016-06-09 10:33:12 UTC 
Could you please try some nightly build starting on the 10th of June as I may have fixed this ?