[jira] [Comment Edited] (CODEC-228) URLCodec.decode does not throw DecoderException with invalid UTF-8
[
https://issues.apache.org/jira/browse/CODEC-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15950240#comment-15950240
]
Andrew Gaul edited comment on CODEC-228 at 7/10/17 5:50 AM:
Agree that this is logical behavior if {{URLCodec}} wants to mimic Java
{{URLDecoder}}. However I want a validator to catch issues like this:
https://github.com/andrewgaul/s3proxy/issues/201
Is this outside the scope of Commons Codec? Could you add an optional strict
parsing mode?
was (Author: gaul):
Agree that this is logical behavior is {{URLCodec}} wants to mimic Java
{{URLDecoder}}. However I want a validator to catch issues like this:
https://github.com/andrewgaul/s3proxy/issues/201
Is this outside the scope of Commons Codec? Could you add an optional strict
parsing mode?
> URLCodec.decode does not throw DecoderException with invalid UTF-8
> --
>
> Key: CODEC-228
> URL: https://issues.apache.org/jira/browse/CODEC-228
> Project: Commons Codec
> Issue Type: Bug
>Affects Versions: 1.10
>Reporter: Andrew Gaul
>
> I expect the following to throw {{DecoderException}}:
> {code:java}
> new URLCodec().decode("%AE%8A-", "UTF-8");
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CLI-276) Adjust access-modifier of checkRequiredOptions() to protected
[ https://issues.apache.org/jira/browse/CLI-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079775#comment-16079775 ] Jason Dillon commented on CLI-276: -- Any idea when 1.5 might be out with this fix? > Adjust access-modifier of checkRequiredOptions() to protected > - > > Key: CLI-276 > URL: https://issues.apache.org/jira/browse/CLI-276 > Project: Commons CLI > Issue Type: Improvement > Components: CLI-1.x >Affects Versions: 1.4 >Reporter: Jason Dillon > Fix For: 1.5 > > > ... for parity with GnuParser, PosixParser and Parser impls to allow > sub-class a bit more control. > I have a use-case in which needs to defer the required-options check, which > is doable with GnuParser and PosixParser, but the new DefaultParser doesn't > allow this due to a private access-modifier on checkRequiredOptions(). > https://github.com/apache/commons-cli/pull/11 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (DAEMON-370) Move attributions from @author in Javadocs to POM
[ https://issues.apache.org/jira/browse/DAEMON-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved DAEMON-370. - Resolution: Fixed Fix Version/s: 1.1 Closes #2. Please verify and close. > Move attributions from @author in Javadocs to POM > - > > Key: DAEMON-370 > URL: https://issues.apache.org/jira/browse/DAEMON-370 > Project: Commons Daemon > Issue Type: Task >Reporter: Amey Jadiye > Fix For: 1.1 > > > SSIA. @authors should be moved to the POM. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (DAEMON-370) Move attributions from @author in Javadocs to POM
[ https://issues.apache.org/jira/browse/DAEMON-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated DAEMON-370: Summary: Move attributions from @author in Javadocs to POM (was: Remove all the @author tags as per guidelines.) > Move attributions from @author in Javadocs to POM > - > > Key: DAEMON-370 > URL: https://issues.apache.org/jira/browse/DAEMON-370 > Project: Commons Daemon > Issue Type: Task >Reporter: Amey Jadiye > > SSIA. @authors should be moved to the POM. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (DAEMON-370) Remove all the @author tags as per guidelines.
[ https://issues.apache.org/jira/browse/DAEMON-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated DAEMON-370: Description: SSIA. @authors should be moved to the POM. (was: SSIA) > Remove all the @author tags as per guidelines. > -- > > Key: DAEMON-370 > URL: https://issues.apache.org/jira/browse/DAEMON-370 > Project: Commons Daemon > Issue Type: Task >Reporter: Amey Jadiye > > SSIA. @authors should be moved to the POM. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DAEMON-370) Remove all the @author tags as per guidelines.
[ https://issues.apache.org/jira/browse/DAEMON-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079713#comment-16079713 ] Amey Jadiye commented on DAEMON-370: actually I found Pier In ASF member list so places him in developers while Nick is in contributors section. I think we are good with it now. > Remove all the @author tags as per guidelines. > -- > > Key: DAEMON-370 > URL: https://issues.apache.org/jira/browse/DAEMON-370 > Project: Commons Daemon > Issue Type: Task >Reporter: Amey Jadiye > > SSIA -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DAEMON-370) Remove all the @author tags as per guidelines.
[ https://issues.apache.org/jira/browse/DAEMON-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079712#comment-16079712 ] Gary Gregory commented on DAEMON-370: - I think contributor is better. Does anyone else have an opinion? > Remove all the @author tags as per guidelines. > -- > > Key: DAEMON-370 > URL: https://issues.apache.org/jira/browse/DAEMON-370 > Project: Commons Daemon > Issue Type: Task >Reporter: Amey Jadiye > > SSIA -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DAEMON-370) Remove all the @author tags as per guidelines.
[ https://issues.apache.org/jira/browse/DAEMON-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079695#comment-16079695 ] Amey Jadiye commented on DAEMON-370: [~garydgregory], never mind, moved them to developer section, plz take look at PR https://github.com/apache/commons-daemon/pull/2 > Remove all the @author tags as per guidelines. > -- > > Key: DAEMON-370 > URL: https://issues.apache.org/jira/browse/DAEMON-370 > Project: Commons Daemon > Issue Type: Task >Reporter: Amey Jadiye > > SSIA -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (DAEMON-370) Remove all the @author tags as per guidelines.
[ https://issues.apache.org/jira/browse/DAEMON-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079694#comment-16079694 ] Gary Gregory edited comment on DAEMON-370 at 7/9/17 7:11 PM: - My best guess based on https://people.apache.org/committer-index.html would be to put both as contributors since neither are listed as Commons committers -- even though the distinction between Commons committer and Apache committer is only ceremonial at this point. was (Author: garydgregory): My best guess based on https://people.apache.org/committer-index.html would be to put both as contributors since neither as Commons committers -- even though the distinction between Commons committer and Apache committer is only ceremonial at this point. > Remove all the @author tags as per guidelines. > -- > > Key: DAEMON-370 > URL: https://issues.apache.org/jira/browse/DAEMON-370 > Project: Commons Daemon > Issue Type: Task >Reporter: Amey Jadiye > > SSIA -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DAEMON-370) Remove all the @author tags as per guidelines.
[ https://issues.apache.org/jira/browse/DAEMON-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079694#comment-16079694 ] Gary Gregory commented on DAEMON-370: - My best guess based on https://people.apache.org/committer-index.html would be to put both as contributors since neither as Commons committers -- even though the distinction between Commons committer and Apache committer is only ceremonial at this point. > Remove all the @author tags as per guidelines. > -- > > Key: DAEMON-370 > URL: https://issues.apache.org/jira/browse/DAEMON-370 > Project: Commons Daemon > Issue Type: Task >Reporter: Amey Jadiye > > SSIA -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DAEMON-370) Remove all the @author tags as per guidelines.
[
https://issues.apache.org/jira/browse/DAEMON-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079690#comment-16079690
]
Amey Jadiye commented on DAEMON-370:
Hi [~garydgregory],
Almost all authors are present in pom.xml except below two, where should I move
them Developers OR Contributors ?
{code}
@author Pier Fumagalli
@author Nick Griffiths (nicobre...@gmail.com)
{code}
> Remove all the @author tags as per guidelines.
> --
>
> Key: DAEMON-370
> URL: https://issues.apache.org/jira/browse/DAEMON-370
> Project: Commons Daemon
> Issue Type: Task
>Reporter: Amey Jadiye
>
> SSIA
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (DAEMON-370) Remove all the @author tags as per guidelines.
[ https://issues.apache.org/jira/browse/DAEMON-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079688#comment-16079688 ] Gary Gregory commented on DAEMON-370: - @authors should be moved to the POM. > Remove all the @author tags as per guidelines. > -- > > Key: DAEMON-370 > URL: https://issues.apache.org/jira/browse/DAEMON-370 > Project: Commons Daemon > Issue Type: Task >Reporter: Amey Jadiye > > SSIA -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (DAEMON-370) Remove all the @author tags as per guidelines.
Amey Jadiye created DAEMON-370: -- Summary: Remove all the @author tags as per guidelines. Key: DAEMON-370 URL: https://issues.apache.org/jira/browse/DAEMON-370 Project: Commons Daemon Issue Type: Task Reporter: Amey Jadiye SSIA -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (DAEMON-369) Fix and improve general stuff around processes and quality.
Amey Jadiye created DAEMON-369: -- Summary: Fix and improve general stuff around processes and quality. Key: DAEMON-369 URL: https://issues.apache.org/jira/browse/DAEMON-369 Project: Commons Daemon Issue Type: Task Reporter: Amey Jadiye Goal of this JIRA is to improve process of coding, build, release, tests, quality etc ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (NET-641) SubnetUtils.SubnetInfo.isInRange("0.0.0.0") returns incorrect value
pin_ptr created NET-641:
---
Summary: SubnetUtils.SubnetInfo.isInRange("0.0.0.0") returns
incorrect value
Key: NET-641
URL: https://issues.apache.org/jira/browse/NET-641
Project: Commons Net
Issue Type: Bug
Affects Versions: 3.6
Environment: Windows; JDK8; common-net 3.6
Reporter: pin_ptr
Priority: Minor
Code:
import org.apache.commons.net.util.SubnetUtils;
public class A {
public static void main(String[] args) {
System.out.println(new
SubnetUtils("192.168.1.0/30").getInfo().isInRange("0.0.0.0"));
System.out.println(new
SubnetUtils("192.168.1.0/31").getInfo().isInRange("0.0.0.0"));
System.out.println(new
SubnetUtils("192.168.1.0/32").getInfo().isInRange("0.0.0.0"));
}
}
Result:
false
true
true
Expected:
false
false
false
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (DAEMON-367) Windows service fails to start after Windows 10 Creators Update
[ https://issues.apache.org/jira/browse/DAEMON-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079584#comment-16079584 ] Bernd Eckenfels commented on DAEMON-367: Thanks for the feedback. I wonder why the install was partial and produced no error. There might be room for improvement. > Windows service fails to start after Windows 10 Creators Update > --- > > Key: DAEMON-367 > URL: https://issues.apache.org/jira/browse/DAEMON-367 > Project: Commons Daemon > Issue Type: Bug > Components: Procrun >Affects Versions: 1.0.15 > Environment: Windows 10 Home and Pro after Creators Update. Windows > version 10.0.15063 Build 15063 >Reporter: Dave Bennett > Labels: prunsrv, windows10 > > I have been running windows services via prunsrv for quite a long time > without any problem. Since updating my PC (Windows 10 Home) recently with the > Creators Update version of Windows 10 any new service that I install will not > start. Similar services that were installed prior to the update work ok as > before. When I try to start a new service, the system event log contains the > message "The BSS2SRVB2 service terminated with the following service-specific > error: Incorrect function". The service was initially configured with > PR_LOGLEVEL set to "Error" and no log files were created. When I set the > level to "Debug", the following log files were created, > - stderrb2.txt contains, > 2017-06-29 08:45:34 Commons Daemon procrun stderr initialized > - stdoutb2.txt contains, > 2017-06-29 08:45:34 Commons Daemon procrun stdout initialized > - commons-daemon.2017-06-29.log contains, > [2017-06-29 08:45:34] [debug] ( prunsrv.c:1679) [20104] Commons Daemon > procrun log initialized > [2017-06-29 08:45:34] [info] ( prunsrv.c:1683) [20104] Commons Daemon > procrun (1.0.15.0 32-bit) started > [2017-06-29 08:45:34] [info] ( prunsrv.c:1596) [20104] Running 'BSS2SRVB2' > Service... > [2017-06-29 08:45:34] [debug] ( prunsrv.c:1374) [19220] Inside ServiceMain... > [2017-06-29 08:45:34] [debug] ( prunsrv.c:844 ) [19220] reportServiceStatusE: > 2, 0, 3000, 0 > [2017-06-29 08:45:34] [info] ( prunsrv.c:1127) [19220] Starting service... > [2017-06-29 08:45:34] [error] ( prunsrv.c:1190) [19220] Missing service > ImageFile > [2017-06-29 08:45:34] [error] ( prunsrv.c:1536) [19220] ServiceStart returned > 1 > [2017-06-29 08:45:34] [debug] ( prunsrv.c:844 ) [19220] reportServiceStatusE: > 1, 1066, 0, 1 > [2017-06-29 08:45:34] [info] ( prunsrv.c:1598) [20104] Run service finished. > [2017-06-29 08:45:34] [info] ( prunsrv.c:1764) [20104] Commons Daemon > procrun finished > The service processes have been written by myself in Java. > I have also seen the same problem on another PC (Windows 10 Pro) so this > suggests that it is not specific to my PC. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (LANG-1339) Some classes depend on the java.desktop profile
[
https://issues.apache.org/jira/browse/LANG-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079524#comment-16079524
]
ASF GitHub Bot commented on LANG-1339:
--
GitHub user kinow opened a pull request:
https://github.com/apache/commons-lang/pull/275
[WIP] LANG-1339: replace java.beans.PropertyListener by java.util.Observable
For discussion, regarding
[LANG-1339](https://issues.apache.org/jira/browse/LANG-1339) (TL;DR: remove
depedency on java.desktop from [lang], preparing for Java 9). Thought having
some code to discuss would be helpful.
This pull request contains a possible solution, where
java.beans.{PropertyChangeListener,PropertyChangeListener} are replaced by
java.util.{Observer,Observable}.
Users would still have the same feature, but alas binary compatibility
would not be kept. So perhaps this could be in a 4.x release. The other methods
are deprecated in the next 3.x releases, and we remove the dependency to
java.desktop on 4.x, and also offer a Java9 module with no dependency
java.desktop.
Would this be a viable alternative?
Cheers
Bruno
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kinow/commons-lang LANG-1339
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/commons-lang/pull/275.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #275
commit 0ba4ea983b0e2ffdffd102b23921292c3c92d3ac
Author: Bruno P. Kinoshita
Date: 2017-07-09T10:01:06Z
LANG-1339: replace java.beans.PropertyListener by java.util.Observable
> Some classes depend on the java.desktop profile
> ---
>
> Key: LANG-1339
> URL: https://issues.apache.org/jira/browse/LANG-1339
> Project: Commons Lang
> Issue Type: Task
>Reporter: Benedikt Ritter
> Labels: Java9
> Fix For: 3.7
>
>
> Commons Lang currently depends on java.desktop. This seems like an
> unnecessary heavy dependency for a library like Commons Lang. We need to find
> a way to fix this, without breaking bc. For more information see
> https://lists.apache.org/thread.html/8db8ec4aa1bdeae3d471ca4f46a21dc7da1a4c6933e1810238b72283@%3Cdev.commons.apache.org%3E
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[GitHub] commons-lang pull request #275: [WIP] LANG-1339: replace java.beans.Property...
GitHub user kinow opened a pull request:
https://github.com/apache/commons-lang/pull/275
[WIP] LANG-1339: replace java.beans.PropertyListener by java.util.Observable
For discussion, regarding
[LANG-1339](https://issues.apache.org/jira/browse/LANG-1339) (TL;DR: remove
depedency on java.desktop from [lang], preparing for Java 9). Thought having
some code to discuss would be helpful.
This pull request contains a possible solution, where
java.beans.{PropertyChangeListener,PropertyChangeListener} are replaced by
java.util.{Observer,Observable}.
Users would still have the same feature, but alas binary compatibility
would not be kept. So perhaps this could be in a 4.x release. The other methods
are deprecated in the next 3.x releases, and we remove the dependency to
java.desktop on 4.x, and also offer a Java9 module with no dependency
java.desktop.
Would this be a viable alternative?
Cheers
Bruno
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kinow/commons-lang LANG-1339
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/commons-lang/pull/275.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #275
commit 0ba4ea983b0e2ffdffd102b23921292c3c92d3ac
Author: Bruno P. Kinoshita
Date: 2017-07-09T10:01:06Z
LANG-1339: replace java.beans.PropertyListener by java.util.Observable
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
[jira] [Closed] (DAEMON-367) Windows service fails to start after Windows 10 Creators Update
[ https://issues.apache.org/jira/browse/DAEMON-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Bennett closed DAEMON-367. --- > Windows service fails to start after Windows 10 Creators Update > --- > > Key: DAEMON-367 > URL: https://issues.apache.org/jira/browse/DAEMON-367 > Project: Commons Daemon > Issue Type: Bug > Components: Procrun >Affects Versions: 1.0.15 > Environment: Windows 10 Home and Pro after Creators Update. Windows > version 10.0.15063 Build 15063 >Reporter: Dave Bennett > Labels: prunsrv, windows10 > > I have been running windows services via prunsrv for quite a long time > without any problem. Since updating my PC (Windows 10 Home) recently with the > Creators Update version of Windows 10 any new service that I install will not > start. Similar services that were installed prior to the update work ok as > before. When I try to start a new service, the system event log contains the > message "The BSS2SRVB2 service terminated with the following service-specific > error: Incorrect function". The service was initially configured with > PR_LOGLEVEL set to "Error" and no log files were created. When I set the > level to "Debug", the following log files were created, > - stderrb2.txt contains, > 2017-06-29 08:45:34 Commons Daemon procrun stderr initialized > - stdoutb2.txt contains, > 2017-06-29 08:45:34 Commons Daemon procrun stdout initialized > - commons-daemon.2017-06-29.log contains, > [2017-06-29 08:45:34] [debug] ( prunsrv.c:1679) [20104] Commons Daemon > procrun log initialized > [2017-06-29 08:45:34] [info] ( prunsrv.c:1683) [20104] Commons Daemon > procrun (1.0.15.0 32-bit) started > [2017-06-29 08:45:34] [info] ( prunsrv.c:1596) [20104] Running 'BSS2SRVB2' > Service... > [2017-06-29 08:45:34] [debug] ( prunsrv.c:1374) [19220] Inside ServiceMain... > [2017-06-29 08:45:34] [debug] ( prunsrv.c:844 ) [19220] reportServiceStatusE: > 2, 0, 3000, 0 > [2017-06-29 08:45:34] [info] ( prunsrv.c:1127) [19220] Starting service... > [2017-06-29 08:45:34] [error] ( prunsrv.c:1190) [19220] Missing service > ImageFile > [2017-06-29 08:45:34] [error] ( prunsrv.c:1536) [19220] ServiceStart returned > 1 > [2017-06-29 08:45:34] [debug] ( prunsrv.c:844 ) [19220] reportServiceStatusE: > 1, 1066, 0, 1 > [2017-06-29 08:45:34] [info] ( prunsrv.c:1598) [20104] Run service finished. > [2017-06-29 08:45:34] [info] ( prunsrv.c:1764) [20104] Commons Daemon > procrun finished > The service processes have been written by myself in Java. > I have also seen the same problem on another PC (Windows 10 Pro) so this > suggests that it is not specific to my PC. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (DAEMON-367) Windows service fails to start after Windows 10 Creators Update
[ https://issues.apache.org/jira/browse/DAEMON-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Bennett resolved DAEMON-367. - Resolution: Fixed > Windows service fails to start after Windows 10 Creators Update > --- > > Key: DAEMON-367 > URL: https://issues.apache.org/jira/browse/DAEMON-367 > Project: Commons Daemon > Issue Type: Bug > Components: Procrun >Affects Versions: 1.0.15 > Environment: Windows 10 Home and Pro after Creators Update. Windows > version 10.0.15063 Build 15063 >Reporter: Dave Bennett > Labels: prunsrv, windows10 > > I have been running windows services via prunsrv for quite a long time > without any problem. Since updating my PC (Windows 10 Home) recently with the > Creators Update version of Windows 10 any new service that I install will not > start. Similar services that were installed prior to the update work ok as > before. When I try to start a new service, the system event log contains the > message "The BSS2SRVB2 service terminated with the following service-specific > error: Incorrect function". The service was initially configured with > PR_LOGLEVEL set to "Error" and no log files were created. When I set the > level to "Debug", the following log files were created, > - stderrb2.txt contains, > 2017-06-29 08:45:34 Commons Daemon procrun stderr initialized > - stdoutb2.txt contains, > 2017-06-29 08:45:34 Commons Daemon procrun stdout initialized > - commons-daemon.2017-06-29.log contains, > [2017-06-29 08:45:34] [debug] ( prunsrv.c:1679) [20104] Commons Daemon > procrun log initialized > [2017-06-29 08:45:34] [info] ( prunsrv.c:1683) [20104] Commons Daemon > procrun (1.0.15.0 32-bit) started > [2017-06-29 08:45:34] [info] ( prunsrv.c:1596) [20104] Running 'BSS2SRVB2' > Service... > [2017-06-29 08:45:34] [debug] ( prunsrv.c:1374) [19220] Inside ServiceMain... > [2017-06-29 08:45:34] [debug] ( prunsrv.c:844 ) [19220] reportServiceStatusE: > 2, 0, 3000, 0 > [2017-06-29 08:45:34] [info] ( prunsrv.c:1127) [19220] Starting service... > [2017-06-29 08:45:34] [error] ( prunsrv.c:1190) [19220] Missing service > ImageFile > [2017-06-29 08:45:34] [error] ( prunsrv.c:1536) [19220] ServiceStart returned > 1 > [2017-06-29 08:45:34] [debug] ( prunsrv.c:844 ) [19220] reportServiceStatusE: > 1, 1066, 0, 1 > [2017-06-29 08:45:34] [info] ( prunsrv.c:1598) [20104] Run service finished. > [2017-06-29 08:45:34] [info] ( prunsrv.c:1764) [20104] Commons Daemon > procrun finished > The service processes have been written by myself in Java. > I have also seen the same problem on another PC (Windows 10 Pro) so this > suggests that it is not specific to my PC. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DAEMON-367) Windows service fails to start after Windows 10 Creators Update
[ https://issues.apache.org/jira/browse/DAEMON-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16079509#comment-16079509 ] Dave Bennett commented on DAEMON-367: - I found what the problem was, eventually. After performing the windows update, the new service was installed via a command prompt that was NOT in administrator mode. When repeated in admin mode, the service started successfully. Prior to the windows update, I always opened the command prompt via the File Explorer, ie. from the 'Open Command Prompt as Administrator' on the File menu. After the update, the Command Prompt options have disappeared and replaced by the equivalent Powershell options. I used another way to open the Command Prompt (entering 'cmd' in the search box) but I hadn't realised that it wasn't opened in admin mode. Interestingly, if you right-click on the Command Prompt option that shows and select 'Run as Adminitrator' nothing happens. The only way that I found to run the Command Propmpt in admin mode was via CTL+ALT+DEL, select Task Manager, select 'File', select 'run new task', enter 'cmd', tick 'create this task with administrative privileges'. > Windows service fails to start after Windows 10 Creators Update > --- > > Key: DAEMON-367 > URL: https://issues.apache.org/jira/browse/DAEMON-367 > Project: Commons Daemon > Issue Type: Bug > Components: Procrun >Affects Versions: 1.0.15 > Environment: Windows 10 Home and Pro after Creators Update. Windows > version 10.0.15063 Build 15063 >Reporter: Dave Bennett > Labels: prunsrv, windows10 > > I have been running windows services via prunsrv for quite a long time > without any problem. Since updating my PC (Windows 10 Home) recently with the > Creators Update version of Windows 10 any new service that I install will not > start. Similar services that were installed prior to the update work ok as > before. When I try to start a new service, the system event log contains the > message "The BSS2SRVB2 service terminated with the following service-specific > error: Incorrect function". The service was initially configured with > PR_LOGLEVEL set to "Error" and no log files were created. When I set the > level to "Debug", the following log files were created, > - stderrb2.txt contains, > 2017-06-29 08:45:34 Commons Daemon procrun stderr initialized > - stdoutb2.txt contains, > 2017-06-29 08:45:34 Commons Daemon procrun stdout initialized > - commons-daemon.2017-06-29.log contains, > [2017-06-29 08:45:34] [debug] ( prunsrv.c:1679) [20104] Commons Daemon > procrun log initialized > [2017-06-29 08:45:34] [info] ( prunsrv.c:1683) [20104] Commons Daemon > procrun (1.0.15.0 32-bit) started > [2017-06-29 08:45:34] [info] ( prunsrv.c:1596) [20104] Running 'BSS2SRVB2' > Service... > [2017-06-29 08:45:34] [debug] ( prunsrv.c:1374) [19220] Inside ServiceMain... > [2017-06-29 08:45:34] [debug] ( prunsrv.c:844 ) [19220] reportServiceStatusE: > 2, 0, 3000, 0 > [2017-06-29 08:45:34] [info] ( prunsrv.c:1127) [19220] Starting service... > [2017-06-29 08:45:34] [error] ( prunsrv.c:1190) [19220] Missing service > ImageFile > [2017-06-29 08:45:34] [error] ( prunsrv.c:1536) [19220] ServiceStart returned > 1 > [2017-06-29 08:45:34] [debug] ( prunsrv.c:844 ) [19220] reportServiceStatusE: > 1, 1066, 0, 1 > [2017-06-29 08:45:34] [info] ( prunsrv.c:1598) [20104] Run service finished. > [2017-06-29 08:45:34] [info] ( prunsrv.c:1764) [20104] Commons Daemon > procrun finished > The service processes have been written by myself in Java. > I have also seen the same problem on another PC (Windows 10 Pro) so this > suggests that it is not specific to my PC. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
