You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ftpserver-dev@incubator.apache.org by "Magnus Grimsell (JIRA)" <ji...@apache.org> on 2007/11/02 10:36:51 UTC
[jira] Created: (FTPSERVER-114) File locks when running on IBM:s
JVM
File locks when running on IBM:s JVM
------------------------------------
Key: FTPSERVER-114
URL: https://issues.apache.org/jira/browse/FTPSERVER-114
Project: FtpServer
Issue Type: Bug
Components: Core
Environment: java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build pwi32devifx-20070608 (SR5+IY99712))
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-20070426 (JIT enabled)
J9VM - 20070420_12448_lHdSMR
JIT - 20070419_1806_r8
GC - 200704_19)
JCL - 20070608
Reporter: Magnus Grimsell
The method close on a FileOutputStream originating from a RandomAccessFile behaves differently on SUN:s and IBM:s JVM. SUN:s JVM closes the underlying RandomAccessFile and no locks remains on the file. For IBM:s JVM an explicit close on the RandomAccessFile is necessary to avoid file locks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FTPSERVER-114) File locks when running on IBM:s
JVM
Posted by "Magnus Grimsell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FTPSERVER-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Magnus Grimsell updated FTPSERVER-114:
--------------------------------------
Attachment: raf_close.patch
> File locks when running on IBM:s JVM
> ------------------------------------
>
> Key: FTPSERVER-114
> URL: https://issues.apache.org/jira/browse/FTPSERVER-114
> Project: FtpServer
> Issue Type: Bug
> Components: Core
> Environment: java version "1.5.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build pwi32devifx-20070608 (SR5+IY99712))
> IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-20070426 (JIT enabled)
> J9VM - 20070420_12448_lHdSMR
> JIT - 20070419_1806_r8
> GC - 200704_19)
> JCL - 20070608
> Reporter: Magnus Grimsell
> Attachments: raf_close.patch
>
>
> The method close on a FileOutputStream originating from a RandomAccessFile behaves differently on SUN:s and IBM:s JVM. SUN:s JVM closes the underlying RandomAccessFile and no locks remains on the file. For IBM:s JVM an explicit close on the RandomAccessFile is necessary to avoid file locks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FTPSERVER-114) File locks when running on IBM:s JVM
Posted by "Niklas Gustavsson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FTPSERVER-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Niklas Gustavsson closed FTPSERVER-114.
---------------------------------------
Resolution: Fixed
Fix Version/s: 1.0-M2
Assignee: Niklas Gustavsson
Fixed!
commit -m "IBM JVM requires the RandomAccessFile to be closed (FTPSERVER-114). Patch by Magnus Grimsell, thanks!" C:/home/niklas/workspaces/apache/ftpserver/core/src/java/org/apache/ftpserver/filesystem/NativeFileObject.java
Sending home/niklas/workspaces/apache/ftpserver/core/src/java/org/apache/ftpserver/filesystem/NativeFileObject.java
Transmitting file data ...
Committed revision 591471.
> File locks when running on IBM:s JVM
> ------------------------------------
>
> Key: FTPSERVER-114
> URL: https://issues.apache.org/jira/browse/FTPSERVER-114
> Project: FtpServer
> Issue Type: Bug
> Components: Core
> Environment: java version "1.5.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build pwi32devifx-20070608 (SR5+IY99712))
> IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-20070426 (JIT enabled)
> J9VM - 20070420_12448_lHdSMR
> JIT - 20070419_1806_r8
> GC - 200704_19)
> JCL - 20070608
> Reporter: Magnus Grimsell
> Assignee: Niklas Gustavsson
> Fix For: 1.0-M2
>
> Attachments: raf_close.patch
>
>
> The method close on a FileOutputStream originating from a RandomAccessFile behaves differently on SUN:s and IBM:s JVM. SUN:s JVM closes the underlying RandomAccessFile and no locks remains on the file. For IBM:s JVM an explicit close on the RandomAccessFile is necessary to avoid file locks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.