[jira] Created: (NET-331) AS400 file timestamp format is wrong

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (NET-331) AS400 file timestamp format is wrong

ASF GitHub Bot (Jira)
AS400 file timestamp format is wrong
------------------------------------

                 Key: NET-331
                 URL: https://issues.apache.org/jira/browse/NET-331
             Project: Commons Net
          Issue Type: Bug
          Components: FTP
    Affects Versions: 2.0
         Environment: AS400
            Reporter: Jim Urban


There is a bug in org.apache.commons.net.ftp.parser.OS400FTPEntryParser.java.  The variable "private static final String DEFAULT_DATE_FORMAT" needs to be changed from "yy/MM/dd HH:mm:ss"; //01/11/09 12:30:24 to "MM/dd/yy HH:mm:ss"; //01/15/08 14:21:38 to work correctly.  I have tested this on our companies AS400 and it solved the problem we were having.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (NET-331) AS400 file timestamp format is wrong

ASF GitHub Bot (Jira)

    [ https://issues.apache.org/jira/browse/NET-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891634#action_12891634 ]

Sebb commented on NET-331:
--------------------------

What is the location of the server? Is it in Europe, or the US?

Seems to me that if the format is changed, it may stop working for systems with a different default date format.

It seems to me that both old and new formats will need to be supported.

I don't know if it is possible to determine the date format using standard FTP commands, so it may be necessary to provide two different parsers, or at least allow the parser to be configured with the appropriate format.



> AS400 file timestamp format is wrong
> ------------------------------------
>
>                 Key: NET-331
>                 URL: https://issues.apache.org/jira/browse/NET-331
>             Project: Commons Net
>          Issue Type: Bug
>          Components: FTP
>    Affects Versions: 2.0
>         Environment: AS400
>            Reporter: Jim Urban
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> There is a bug in org.apache.commons.net.ftp.parser.OS400FTPEntryParser.java.  The variable "private static final String DEFAULT_DATE_FORMAT" needs to be changed from "yy/MM/dd HH:mm:ss"; //01/11/09 12:30:24 to "MM/dd/yy HH:mm:ss"; //01/15/08 14:21:38 to work correctly.  I have tested this on our companies AS400 and it solved the problem we were having.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (NET-331) AS400 file timestamp format is wrong

ASF GitHub Bot (Jira)
In reply to this post by ASF GitHub Bot (Jira)

    [ https://issues.apache.org/jira/browse/NET-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891740#action_12891740 ]

Jim Urban commented on NET-331:
-------------------------------

The server I tested with is in the U.S.  I do not have access to a server in Europe to test against.  Allowing the parser to be configured would probably be the best option if in fact the default date format is different between the U.S. and Europe.

> AS400 file timestamp format is wrong
> ------------------------------------
>
>                 Key: NET-331
>                 URL: https://issues.apache.org/jira/browse/NET-331
>             Project: Commons Net
>          Issue Type: Bug
>          Components: FTP
>    Affects Versions: 2.0
>         Environment: AS400
>            Reporter: Jim Urban
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> There is a bug in org.apache.commons.net.ftp.parser.OS400FTPEntryParser.java.  The variable "private static final String DEFAULT_DATE_FORMAT" needs to be changed from "yy/MM/dd HH:mm:ss"; //01/11/09 12:30:24 to "MM/dd/yy HH:mm:ss"; //01/15/08 14:21:38 to work correctly.  I have tested this on our companies AS400 and it solved the problem we were having.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.