[jira] [Commented] (NET-493) FTPClient: Slow data transfer rate if __bufferSize != 0
[
https://issues.apache.org/jira/browse/NET-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13546731#comment-13546731
]
Erik Wramner commented on NET-493:
--
No, we have only observed that the application transfers files with FTP much
faster (seconds/minutes rather than hours) with 3.1 than with 3.2. The
application code is unchanged. It doesn't set the buffer size, using the
default. Files are sent with client.storeFile(fileName, inputStream). We can't
experiment in production, this is an important system, but if I can find time I
will try to run some tests. Not sure how easy it is to reproduce in the test
environment, though.
FTPClient: Slow data transfer rate if __bufferSize != 0
---
Key: NET-493
URL: https://issues.apache.org/jira/browse/NET-493
Project: Commons Net
Issue Type: Bug
Components: FTP
Affects Versions: 3.2
Environment: Windows 7 32bit / Windows XP 32bit
Reporter: Mico Micic
Labels: ftpclient
Attachments: screenshot-1.jpg, screenshot-2.jpg
The patch applied in [NET-465|https://issues.apache.org/jira/browse/NET-465]
causes a very slow data transfer rate. The line {code}850:
socket.setSendBufferSize(__bufferSize){code} in
{code}_openDataConnection_{code} sets the buffer size to 1024 by default.
With this size I had a very bad transfer rate on windows 7 and XP. The
wireshark log shows that each FTP-DATA packet is exactly 1024 bytes long and
has to be acknowledged on the TCP layer before the next one is sent. I don't
know why, but when I set the buffer size to 0 (FTPClient.setBufferSize) the
transfer rate is fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (VFS-442) Add an HDFS FileSystem Provider
[ https://issues.apache.org/jira/browse/VFS-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13546863#comment-13546863 ] Gary Gregory commented on VFS-442: -- Do you have any further documentation, like usage tips or anything else that may help users avoid searching for answers? Add an HDFS FileSystem Provider --- Key: VFS-442 URL: https://issues.apache.org/jira/browse/VFS-442 Project: Commons VFS Issue Type: New Feature Affects Versions: 2.0 Reporter: Dave Marion Assignee: Gary Gregory Priority: Minor Labels: accumulo, hdfs Attachments: vfs-422-3.diff, VFS-442-1.patch, VFS-442-2.patch, VFS-442-4.patch, VFS-442-5.patch, VFS-442-6.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DAEMON-274) procrun ignores shutdown
[ https://issues.apache.org/jira/browse/DAEMON-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13546882#comment-13546882 ] Mladen Turk commented on DAEMON-274: Yeah, I intend to start the RM process by the end of this week. procrun ignores shutdown Key: DAEMON-274 URL: https://issues.apache.org/jira/browse/DAEMON-274 Project: Commons Daemon Issue Type: Bug Components: Procrun Affects Versions: 1.0.10 Environment: Windows OS Reporter: Hsehdar Assignee: Mladen Turk Labels: procrun Procrun does not gracefully shut down when OS shut down occurs. Operating system kills the service started. Service started using procrun is with state IGNORES_SHUTDOWN. What was expected? Procrun service registered to be ACCEPTS_SHUTDOWN such that procrun shuts down gracefully within the time allocated by OS. It would be great if this becomes command line parameter. It will be a bonus :) Author requests assignee to change this issue details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (LANG-866) StringEscapeUtils.escapeHTML() does not escape ~ ` @ # $ % ^ * ( ) _ - + = | ; : . , ? } { ] [
vcr created LANG-866:
Summary: StringEscapeUtils.escapeHTML() does not escape ~ ` @ # $
% ^ * ( ) _ - + = | ; : . , ? } { ] [
Key: LANG-866
URL: https://issues.apache.org/jira/browse/LANG-866
Project: Commons Lang
Issue Type: Bug
Components: lang.*
Environment: java
Reporter: vcr
Fix For: 2.4
i am trying to encoding the charecter's (~ ` @ # $ % ^ * ( ) _ - + = | ; : .
, ? } { ] [ ) but when i execute the below its giving the same out put rather
ascii values.
String str = ~ ` @ # $ % ^ * ( ) _ - + = | ; : . , ? } { ] [ ;
str = StringEscapeUtils.escapeJava(str);
Expected out: should encode the charecters to ascii values.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (LANG-866) StringEscapeUtils.escapeHTML() does not escape ~ ` @ # $ % ^ * ( ) _ - + = | ; : . , ? } { ] [
[
https://issues.apache.org/jira/browse/LANG-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
vcr updated LANG-866:
-
Description:
i am trying to encoding the charecter's (~ ` @ # $ % ^ * ( ) _ - + = | ; : .
, ? } { ] [ ) but when i execute the below its giving the same out put rather
ascii values.
String str = ~ ` @ # $ % ^ * ( ) _ - + = | ; : . , ? } { ] [ ;
str = StringEscapeUtils.escapeJava(str);
Expected output: should encode the charecters to ascii values.
was:
i am trying to encoding the charecter's (~ ` @ # $ % ^ * ( ) _ - + = | ; : .
, ? } { ] [ ) but when i execute the below its giving the same out put rather
ascii values.
String str = ~ ` @ # $ % ^ * ( ) _ - + = | ; : . , ? } { ] [ ;
str = StringEscapeUtils.escapeJava(str);
Expected out: should encode the charecters to ascii values.
StringEscapeUtils.escapeHTML() does not escape ~ ` @ # $ % ^ * ( ) _ - + =
| ; : . , ? } { ] [
--
Key: LANG-866
URL: https://issues.apache.org/jira/browse/LANG-866
Project: Commons Lang
Issue Type: Bug
Components: lang.*
Environment: java
Reporter: vcr
Fix For: 2.4
i am trying to encoding the charecter's (~ ` @ # $ % ^ * ( ) _ - + = | ; :
. , ? } { ] [ ) but when i execute the below its giving the same out put
rather ascii values.
String str = ~ ` @ # $ % ^ * ( ) _ - + = | ; : . , ? } { ] [ ;
str = StringEscapeUtils.escapeJava(str);
Expected output: should encode the charecters to ascii values.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (COMPRESS-210) handle zip extra field 0x5455 - Extended Timestamp
[
https://issues.apache.org/jira/browse/COMPRESS-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julius Davies updated COMPRESS-210:
---
Description:
From Info Zip's zip-3.0 source archive (proginfo/extrafld.txt):
{noformat}
-Extended Timestamp Extra Field:
==
The following is the layout of the extended-timestamp extra block.
(Last Revision 19970118)
Local-header version:
Value SizeDescription
- ---
(time) 0x5455Short tag for this extra block type (UT)
TSize Short total data size for this block
Flags Byteinfo bits
(ModTime) Longtime of last modification (UTC/GMT)
(AcTime) Longtime of last access (UTC/GMT)
(CrTime) Longtime of original creation (UTC/GMT)
Central-header version:
Value SizeDescription
- ---
(time) 0x5455Short tag for this extra block type (UT)
TSize Short total data size for this block
Flags Byteinfo bits (refers to local header!)
(ModTime) Longtime of last modification (UTC/GMT)
The central-header extra field contains the modification time only,
or no timestamp at all. TSize is used to flag its presence or
absence. But note:
{noformat}
was:
From Info Zip's zip-3.0 source archive (proginfo/extrafld.txt):
-Extended Timestamp Extra Field:
==
The following is the layout of the extended-timestamp extra block.
(Last Revision 19970118)
Local-header version:
Value SizeDescription
- ---
(time) 0x5455Short tag for this extra block type (UT)
TSize Short total data size for this block
Flags Byteinfo bits
(ModTime) Longtime of last modification (UTC/GMT)
(AcTime) Longtime of last access (UTC/GMT)
(CrTime) Longtime of original creation (UTC/GMT)
Central-header version:
Value SizeDescription
- ---
(time) 0x5455Short tag for this extra block type (UT)
TSize Short total data size for this block
Flags Byteinfo bits (refers to local header!)
(ModTime) Longtime of last modification (UTC/GMT)
The central-header extra field contains the modification time only,
or no timestamp at all. TSize is used to flag its presence or
absence. But note:
handle zip extra field 0x5455 - Extended Timestamp
--
Key: COMPRESS-210
URL: https://issues.apache.org/jira/browse/COMPRESS-210
Project: Commons Compress
Issue Type: Improvement
Components: Archivers
Reporter: Julius Davies
Priority: Minor
From Info Zip's zip-3.0 source archive (proginfo/extrafld.txt):
{noformat}
-Extended Timestamp Extra Field:
==
The following is the layout of the extended-timestamp extra block.
(Last Revision 19970118)
Local-header version:
Value SizeDescription
- ---
(time) 0x5455Short tag for this extra block type (UT)
TSize Short total data size for this block
Flags Byteinfo bits
(ModTime) Longtime of last modification (UTC/GMT)
(AcTime) Longtime of last access (UTC/GMT)
(CrTime) Longtime of original creation (UTC/GMT)
Central-header version:
Value SizeDescription
- ---
(time) 0x5455Short tag for this extra block type (UT)
TSize Short total data size for this block
Flags Byteinfo bits (refers to local header!)
(ModTime) Longtime of last modification (UTC/GMT)
The central-header extra field contains the modification time only,
or no timestamp at all. TSize is used to flag its presence or
absence. But note:
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
[jira] [Updated] (COMPRESS-210) handle zip extra field 0x5455 - Extended Timestamp
[
https://issues.apache.org/jira/browse/COMPRESS-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julius Davies updated COMPRESS-210:
---
Description:
From Info Zip's zip-3.0 source archive (proginfo/extrafld.txt):
-Extended Timestamp Extra Field:
==
The following is the layout of the extended-timestamp extra block.
(Last Revision 19970118)
{noformat}
Local-header version:
Value SizeDescription
- ---
(time) 0x5455Short tag for this extra block type (UT)
TSize Short total data size for this block
Flags Byteinfo bits
(ModTime) Longtime of last modification (UTC/GMT)
(AcTime) Longtime of last access (UTC/GMT)
(CrTime) Longtime of original creation (UTC/GMT)
Central-header version:
Value SizeDescription
- ---
(time) 0x5455Short tag for this extra block type (UT)
TSize Short total data size for this block
Flags Byteinfo bits (refers to local header!)
(ModTime) Longtime of last modification (UTC/GMT)
{noformat}
The central-header extra field contains the modification time only,
or no timestamp at all. TSize is used to flag its presence or
absence. But note:
was:
From Info Zip's zip-3.0 source archive (proginfo/extrafld.txt):
{noformat}
-Extended Timestamp Extra Field:
==
The following is the layout of the extended-timestamp extra block.
(Last Revision 19970118)
Local-header version:
Value SizeDescription
- ---
(time) 0x5455Short tag for this extra block type (UT)
TSize Short total data size for this block
Flags Byteinfo bits
(ModTime) Longtime of last modification (UTC/GMT)
(AcTime) Longtime of last access (UTC/GMT)
(CrTime) Longtime of original creation (UTC/GMT)
Central-header version:
Value SizeDescription
- ---
(time) 0x5455Short tag for this extra block type (UT)
TSize Short total data size for this block
Flags Byteinfo bits (refers to local header!)
(ModTime) Longtime of last modification (UTC/GMT)
The central-header extra field contains the modification time only,
or no timestamp at all. TSize is used to flag its presence or
absence. But note:
{noformat}
handle zip extra field 0x5455 - Extended Timestamp
--
Key: COMPRESS-210
URL: https://issues.apache.org/jira/browse/COMPRESS-210
Project: Commons Compress
Issue Type: Improvement
Components: Archivers
Reporter: Julius Davies
Priority: Minor
From Info Zip's zip-3.0 source archive (proginfo/extrafld.txt):
-Extended Timestamp Extra Field:
==
The following is the layout of the extended-timestamp extra block.
(Last Revision 19970118)
{noformat}
Local-header version:
Value SizeDescription
- ---
(time) 0x5455Short tag for this extra block type (UT)
TSize Short total data size for this block
Flags Byteinfo bits
(ModTime) Longtime of last modification (UTC/GMT)
(AcTime) Longtime of last access (UTC/GMT)
(CrTime) Longtime of original creation (UTC/GMT)
Central-header version:
Value SizeDescription
- ---
(time) 0x5455Short tag for this extra block type (UT)
TSize Short total data size for this block
Flags Byteinfo bits (refers to local header!)
(ModTime) Longtime of last modification (UTC/GMT)
{noformat}
The central-header extra field contains the modification time only,
or no timestamp at all. TSize is used to flag its presence or
absence. But note:
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more
[jira] [Commented] (LANG-866) StringEscapeUtils.escapeHTML() does not escape ~ ` @ # $ % ^ * ( ) _ - + = | ; : . , ? } { ] [
[
https://issues.apache.org/jira/browse/LANG-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13547185#comment-13547185
]
Sebb commented on LANG-866:
---
The title refers to escapeHTML(), but the description is for escapeJava() -
which is it?
StringEscapeUtils.escapeHTML() does not escape ~ ` @ # $ % ^ * ( ) _ - + =
| ; : . , ? } { ] [
--
Key: LANG-866
URL: https://issues.apache.org/jira/browse/LANG-866
Project: Commons Lang
Issue Type: Bug
Components: lang.*
Environment: java
Reporter: vcr
Fix For: 2.4
i am trying to encoding the charecter's (~ ` @ # $ % ^ * ( ) _ - + = | ; :
. , ? } { ] [ ) but when i execute the below its giving the same out put
rather ascii values.
String str = ~ ` @ # $ % ^ * ( ) _ - + = | ; : . , ? } { ] [ ;
str = StringEscapeUtils.escapeJava(str);
Expected output: should encode the charecters to ascii values.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (COMPRESS-210) handle zip extra field 0x5455 - Extended Timestamp
[
https://issues.apache.org/jira/browse/COMPRESS-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julius Davies updated COMPRESS-210:
---
Attachment: COMPRESS-210.patch
Here is what I'm about to commit!
handle zip extra field 0x5455 - Extended Timestamp
--
Key: COMPRESS-210
URL: https://issues.apache.org/jira/browse/COMPRESS-210
Project: Commons Compress
Issue Type: Improvement
Components: Archivers
Reporter: Julius Davies
Priority: Minor
Attachments: COMPRESS-210.patch
From Info Zip's zip-3.0 source archive (proginfo/extrafld.txt):
-Extended Timestamp Extra Field:
==
The following is the layout of the extended-timestamp extra block.
(Last Revision 19970118)
{noformat}
Local-header version:
Value SizeDescription
- ---
(time) 0x5455Short tag for this extra block type (UT)
TSize Short total data size for this block
Flags Byteinfo bits
(ModTime) Longtime of last modification (UTC/GMT)
(AcTime) Longtime of last access (UTC/GMT)
(CrTime) Longtime of original creation (UTC/GMT)
Central-header version:
Value SizeDescription
- ---
(time) 0x5455Short tag for this extra block type (UT)
TSize Short total data size for this block
Flags Byteinfo bits (refers to local header!)
(ModTime) Longtime of last modification (UTC/GMT)
{noformat}
The central-header extra field contains the modification time only,
or no timestamp at all. TSize is used to flag its presence or
absence. But note:
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (COMPRESS-210) handle zip extra field 0x5455 - Extended Timestamp
[
https://issues.apache.org/jira/browse/COMPRESS-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julius Davies resolved COMPRESS-210.
Resolution: Implemented
Fix Version/s: 1.5
Assignee: Julius Davies
Implemented! Whew!
Kinda cute how zip time overflows in 2108 (1980 + 127), while these unix time
stamps overflow in 2106 (32 bits of seconds since Jan 1st 1970).
handle zip extra field 0x5455 - Extended Timestamp
--
Key: COMPRESS-210
URL: https://issues.apache.org/jira/browse/COMPRESS-210
Project: Commons Compress
Issue Type: Improvement
Components: Archivers
Reporter: Julius Davies
Assignee: Julius Davies
Priority: Minor
Fix For: 1.5
Attachments: COMPRESS-210.patch
From Info Zip's zip-3.0 source archive (proginfo/extrafld.txt):
-Extended Timestamp Extra Field:
==
The following is the layout of the extended-timestamp extra block.
(Last Revision 19970118)
{noformat}
Local-header version:
Value SizeDescription
- ---
(time) 0x5455Short tag for this extra block type (UT)
TSize Short total data size for this block
Flags Byteinfo bits
(ModTime) Longtime of last modification (UTC/GMT)
(AcTime) Longtime of last access (UTC/GMT)
(CrTime) Longtime of original creation (UTC/GMT)
Central-header version:
Value SizeDescription
- ---
(time) 0x5455Short tag for this extra block type (UT)
TSize Short total data size for this block
Flags Byteinfo bits (refers to local header!)
(ModTime) Longtime of last modification (UTC/GMT)
{noformat}
The central-header extra field contains the modification time only,
or no timestamp at all. TSize is used to flag its presence or
absence. But note:
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COMPRESS-214) better support for unix symlinks
Julius Davies created COMPRESS-214:
--
Summary: better support for unix symlinks
Key: COMPRESS-214
URL: https://issues.apache.org/jira/browse/COMPRESS-214
Project: Commons Compress
Issue Type: Improvement
Components: Archivers
Reporter: Julius Davies
Assignee: Julius Davies
Priority: Minor
Fix For: 1.5
The current API is a little awkward when dealing with symlinks (e.g., those
created using Info-Zip's zip -y).
I propose the following three methods for ZipArchiveEntry:
{noformat}
public boolean isUnixSymlink()
public String getUnixSymlink(ZipFile zf)
public String getUnixSymlink(ZipFile zf, String pathCharset)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (COMPRESS-214) better support for unix symlinks
[
https://issues.apache.org/jira/browse/COMPRESS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julius Davies updated COMPRESS-214:
---
Attachment: COMPRESS-214_tentative.patch
Attached a tentative patch for review. Still working on JUnits.
better support for unix symlinks
Key: COMPRESS-214
URL: https://issues.apache.org/jira/browse/COMPRESS-214
Project: Commons Compress
Issue Type: Improvement
Components: Archivers
Reporter: Julius Davies
Assignee: Julius Davies
Priority: Minor
Fix For: 1.5
Attachments: COMPRESS-214_tentative.patch
The current API is a little awkward when dealing with symlinks (e.g., those
created using Info-Zip's zip -y).
I propose the following three methods for ZipArchiveEntry:
{noformat}
public boolean isUnixSymlink()
public String getUnixSymlink(ZipFile zf)
public String getUnixSymlink(ZipFile zf, String pathCharset)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (VFS-442) Add an HDFS FileSystem Provider
[ https://issues.apache.org/jira/browse/VFS-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13547521#comment-13547521 ] Dave Marion commented on VFS-442: - Internally, getting access to the file in HDFS is pretty simple. The software: 1. extracts the root URI of the file (i.e. hdfs://host:port) 2. Creates a Hadoop configuration object and sets org.apache.hadoop.fs.FileSystem.FS_DEFAULT_NAME_KEY to the root URI. 3. Calls org.apache.hadoop.fs.FileSystem.get(conf) to get a FileSystem implementation The file system could be local or remote, but I think it has only been tested locally at this time. The default security mechanism is documented at [1]. In short, without Kerberos enabled, HDFS will use the user and group permissions of the O/S process that is running the software to determine whether or not the file can be accessed. I have not played with Kerberos at all, so I'm not sure what the changes would be. I would also assume that anyone trying to use this has some knowledge of HDFS. [1] http://hadoop.apache.org/docs/r1.0.4/hdfs_permissions_guide.html Add an HDFS FileSystem Provider --- Key: VFS-442 URL: https://issues.apache.org/jira/browse/VFS-442 Project: Commons VFS Issue Type: New Feature Affects Versions: 2.0 Reporter: Dave Marion Assignee: Gary Gregory Priority: Minor Labels: accumulo, hdfs Attachments: vfs-422-3.diff, VFS-442-1.patch, VFS-442-2.patch, VFS-442-4.patch, VFS-442-5.patch, VFS-442-6.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (VFS-442) Add an HDFS FileSystem Provider
[ https://issues.apache.org/jira/browse/VFS-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved VFS-442. -- Resolution: Fixed Fix Version/s: 2.1 Done for now. Add an HDFS FileSystem Provider --- Key: VFS-442 URL: https://issues.apache.org/jira/browse/VFS-442 Project: Commons VFS Issue Type: New Feature Affects Versions: 2.0 Reporter: Dave Marion Assignee: Gary Gregory Priority: Minor Labels: accumulo, hdfs Fix For: 2.1 Attachments: vfs-422-3.diff, VFS-442-1.patch, VFS-442-2.patch, VFS-442-4.patch, VFS-442-5.patch, VFS-442-6.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
