[jira] [Updated] (DAEMON-449) Prunsrv fails to stop Open Liberty Windows service
[
https://issues.apache.org/jira/browse/DAEMON-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Blye updated DAEMON-449:
Description:
< *Update* . The reason the stop fails is because the start hasn't finished.
Prunsrv isn't waiting for the start to finish. So in the Windows services
panel, the service appears to be started. If you then click stop, it hangs for
a few minutes and fails to stop. The state at this point in the Windows
services is "Stopping". So you have to manually stop the process. >
When Prunsrv is used to register Open Liberty
([https://openliberty.io|https://openliberty.io/]) as a Windows Service,
stopping the service hangs randomly.
*To recreate the problem:*
1) Download open liberty ~300MB
[https://public.dhe.ibm.com/ibmdl/export/pub/software/openliberty/runtime/release/22.0.0.10/openliberty-22.0.0.10.zip]
Alternatively, you could use just the liberty kernel ~10MB
[https://public.dhe.ibm.com/ibmdl/export/pub/software/openliberty/runtime/release/22.0.0.10/openliberty-kernel-22.0.0.10.zip]
2) md C:\temp\openliberty
unzip openliberty-22.0.0.10.zip into C:\temp\openliberty
3) cd C:\temp\openliberty\wlp\bin
4) Run these two commands to make sure the server runs and to initialize the
environment:
server start
server stop
5) Register liberty as a service (parameter is case sensitive). The
following command is used to invoke prunsrv to register the service using the
default name of defaultServer
server registerWinService
6) Open the windows "services" app (services.msc). Start and stop the
service until the stop hangs. It usually doesn't take more than a couple of
tries.
*Details*
The *server.bat* script registers the service like this:
"C:\temp\openliberty\wlp\bin\tools\win\prunsrv.exe" //IS//defaultServer
--Startup=manual --DisplayName="defaultServer" --Description="Open Liberty"
++DependsOn=Tcpip
--LogPath="C:\temp\openliberty\wlp\usr\servers\defaultServer\logs"
--StdOutput=auto --StdError=auto --StartMode=exe
--StartPath="C:\temp\openliberty\wlp"
--StartImage="C:\temp\openliberty\wlp\bin\server.bat"
++StartParams=start#defaultServer --StopMode=exe
--StopPath="C:\temp\openliberty\wlp" --StopImage="C:\temp\wlp\bin\server.bat"
++StopParams=stop#defaultServer --ServiceUser=LocalSystem
After registering the service you can look at its properties. You will see:
Path to executable:
C:\temp\openliberty\wlp\bin\tools\win\prunsrv.exe //RS//defaultServer
When I (and many of our customers) try to stop the service, it hangs. At that
point, the server, named defaultServer is still up and running. I can send
commands to the server. For instance, I can execute a "server dump" command.
This sends the "dump" command to the server, and the server writes information
to a file. I can also stop the server by executing "server stop". This sends
the "stop" command to the server which causes the server to stop. When the
server stops, the hanging Windows service stops as well.
I have attached a *server.bat* which adds --LogLevel Debug to the prunsrv
commands and also *commons-daemon.2022-09-28.log* which demonstrates the
problem. It shows registering, starting, and stopping the service. Finally, I
uploaded {*}commons-daemon.2022-09-28_afterKillingServer.log{*}, which is a
continuation of the other log file which shows the result of issuing the server
stop command to stop the server.
Thanks for looking at this.
Jim Blye
was:
When Prunsrv is used to register Open Liberty
([https://openliberty.io|https://openliberty.io/]) as a Windows Service,
stopping the service hangs randomly.
*To recreate the problem:*
1) Download open liberty ~300MB
[https://public.dhe.ibm.com/ibmdl/export/pub/software/openliberty/runtime/release/22.0.0.10/openliberty-22.0.0.10.zip]
Alternatively, you could use just the liberty kernel ~10MB
[https://public.dhe.ibm.com/ibmdl/export/pub/software/openliberty/runtime/release/22.0.0.10/openliberty-kernel-22.0.0.10.zip]
2) md C:\temp\openliberty
unzip openliberty-22.0.0.10.zip into C:\temp\openliberty
3) cd C:\temp\openliberty\wlp\bin
4) Run these two commands to make sure the server runs and to initialize the
environment:
server start
server stop
5) Register liberty as a service (parameter is case sensitive). The
following command is used to invoke prunsrv to register the service using the
default name of defaultServer
server registerWinService
6) Open the windows "services" app (services.msc). Start and stop the
service until the stop hangs. It usually doesn't take more than a couple of
tries.
*Details*
The *server.bat* script registers the service like this:
"C:\temp\openliberty\wlp\bin\tools\win\prunsrv.exe" //IS//defaultServer
--Startup=manual --DisplayName="defaultServer"
[jira] [Commented] (VFS-827) CIFS support in Commons VFS
[ https://issues.apache.org/jira/browse/VFS-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17634996#comment-17634996 ] Bernd Eckenfels commented on VFS-827: - I don’t think it is planned to be released in proper, since it depends on a external non-Apache license (LGPL) library which is meanwhile also obsoleted (SMB3 support would require jcifs-ng), Btw there are a few external providers, at least one or two for jCIFS-ng, maybe we should ask authors to donate them? (It won’t change the license situation) > CIFS support in Commons VFS > --- > > Key: VFS-827 > URL: https://issues.apache.org/jira/browse/VFS-827 > Project: Commons VFS > Issue Type: Improvement >Reporter: Sreedhar J >Priority: Major > > I see CIFS file system support is in sandbox state, Any idea, when is > CIFS support would be released? > Also, does CIFS file system has support for SMB 2.0, 2.1 and SMB 3.0 ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [commons-net] sebbASF commented on a diff in pull request #95: NET-707: Process files with spaces in name for OS400
sebbASF commented on code in PR #95:
URL: https://github.com/apache/commons-net/pull/95#discussion_r1024318435
##
src/test/java/org/apache/commons/net/ftp/parser/OS400FTPEntryParserTest.java:
##
@@ -203,6 +203,20 @@ public void testParseFieldsOnFile() throws Exception
df.format(f.getTimestamp().getTime()));
}
+/**
+ * Method testParseFileNameWithSpaces.
+ * Provide a test to show that file which name contains spaces is parsed
correctly.
+ * @throws Exception on error
+ */
+
+public void testParseFileNameWithSpaces() throws Exception
+{
+final FTPFile f = getParser().parseFTPEntry("MYUSER 3
06/12/21 12:00:00 *STMF file with space.txt");
+assertNotNull("Could not parse entry.", f);
+assertTrue("Should have been a file.", f.isFile());
+assertEquals("file with space.txt", f.getName());
Review Comment:
It should be easy enough to handle embedded and trailing spaces.
However leading spaces can only be detected if the filename always starts in
a specific column.
This needs to be determined by experimentation on OS400, or by finding the
appropriate documentation for OS400.
I cannot personally help with that.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Resolved] (JEXL-386) Non-inheritable permissions on interfaces are ignored in an inheritable sandbox
[
https://issues.apache.org/jira/browse/JEXL-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro resolved JEXL-386.
Resolution: Fixed
https://github.com/apache/commons-jexl/commit/535e621d827a68e17e274fa34b6cbd7b24ecdccd
> Non-inheritable permissions on interfaces are ignored in an inheritable
> sandbox
> ---
>
> Key: JEXL-386
> URL: https://issues.apache.org/jira/browse/JEXL-386
> Project: Commons JEXL
> Issue Type: Bug
>Affects Versions: 3.2.1
>Reporter: Song Fuchang
>Assignee: Henri Biestro
>Priority: Minor
> Fix For: 3.3
>
>
> Hello, I found that if I create an inheritable sandbox with:
> {code:java}
> JexlSandbox sandbox = new JexlSandbox(false, true);
> {code}
> and add an non-inheritable permission on an interface:
> {code:java}
> sandbox.permission(SomeInterface.class.getName(), false, true, true, true);
> {code}
> then any object which implemented SomeInterface still gained access to its
> methods.
> Is this normal?
> I have created a PR on [https://github.com/apache/commons-jexl/pull/140]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (JEXL-385) Support disabling fortran-style relational operators syntax
[ https://issues.apache.org/jira/browse/JEXL-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17634930#comment-17634930 ] Henri Biestro commented on JEXL-385: You're absolutely right.. 'in' is gone, don't know why I had it in mind. > Support disabling fortran-style relational operators syntax > > > Key: JEXL-385 > URL: https://issues.apache.org/jira/browse/JEXL-385 > Project: Commons JEXL > Issue Type: Improvement >Affects Versions: 3.2.1 >Reporter: Dmitri Blinov >Assignee: Henri Biestro >Priority: Major > Fix For: 3.3 > > > Introduce JexlFeature to disable 'eq','ne','gt','ge','le','lt' as operators, > treat as plain identifiers > https://github.com/apache/commons-jexl/pull/139 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (VFS-827) CIFS support in Commons VFS
[ https://issues.apache.org/jira/browse/VFS-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17634896#comment-17634896 ] Michael Osipov commented on VFS-827: Though, not worked on VFS, don't expect this to happen. SMB is s very complex protocol and requires a lot of backend resources even to validate against Windows Server. > CIFS support in Commons VFS > --- > > Key: VFS-827 > URL: https://issues.apache.org/jira/browse/VFS-827 > Project: Commons VFS > Issue Type: Improvement >Reporter: Sreedhar J >Priority: Major > > I see CIFS file system support is in sandbox state, Any idea, when is > CIFS support would be released? > Also, does CIFS file system has support for SMB 2.0, 2.1 and SMB 3.0 ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (VFS-827) CIFS support in Commons VFS
[ https://issues.apache.org/jira/browse/VFS-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreedhar J updated VFS-827: --- Issue Type: Improvement (was: Bug) > CIFS support in Commons VFS > --- > > Key: VFS-827 > URL: https://issues.apache.org/jira/browse/VFS-827 > Project: Commons VFS > Issue Type: Improvement >Reporter: Sreedhar J >Priority: Major > > I see CIFS file system support is in sandbox state, Any idea, when is > CIFS support would be released? > Also, does CIFS file system has support for SMB 2.0, 2.1 and SMB 3.0 ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (VFS-827) CIFS support in Commons VFS
Sreedhar J created VFS-827: -- Summary: CIFS support in Commons VFS Key: VFS-827 URL: https://issues.apache.org/jira/browse/VFS-827 Project: Commons VFS Issue Type: Bug Reporter: Sreedhar J I see CIFS file system support is in sandbox state, Any idea, when is CIFS support would be released? Also, does CIFS file system has support for SMB 2.0, 2.1 and SMB 3.0 ? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [commons-io] garydgregory commented on pull request #74: Add new function: byteCountToDisplayRoundedSize
garydgregory commented on PR #74: URL: https://github.com/apache/commons-io/pull/74#issuecomment-1316844945 Hi @RockyMM Go for it ;-) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (IO-373) FileUtils.byteCountToDisplaySize improvement/rounding issues
[ https://issues.apache.org/jira/browse/IO-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17634775#comment-17634775 ] Rade Martinović commented on IO-373: The discussion in the GitHub is leaning towards direction of moving this functionality to CommonsText > FileUtils.byteCountToDisplaySize improvement/rounding issues > > > Key: IO-373 > URL: https://issues.apache.org/jira/browse/IO-373 > Project: Commons IO > Issue Type: Improvement > Components: Utilities >Affects Versions: 2.4 >Reporter: Mark >Priority: Minor > Attachments: byteCountToDisplaySize.patch, > byteCountToHumanReadableGnu.patch > > > Issue IO-226 is not fixed but closed. > ? > Here is my solution that also support a user-defined precision in terms of a > maximum length of the digits part. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [commons-io] RockyMM commented on pull request #74: Add new function: byteCountToDisplayRoundedSize
RockyMM commented on PR #74: URL: https://github.com/apache/commons-io/pull/74#issuecomment-1316788483 Hey @garydgregory, On a second thought, you do have a point. Then I would suggest we move the functionality to CommonsText, and create an issue that will mark all of these methods as `@Deprecated`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-bcel] garydgregory commented on pull request #157: Keep ConstantPool.getConstant(int) backward compatible with v6.5.0
garydgregory commented on PR #157: URL: https://github.com/apache/commons-bcel/pull/157#issuecomment-1316665741 Thanks @KengoTODA The regression found by Xalan is indeed unrelated to this PR. It is now fixed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
