Commented: (WAGONFTP-8) ArrayIndexOutOfBoundsException upon deploy

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Commented: (WAGONFTP-8) ArrayIndexOutOfBoundsException upon deploy

JIRA jira@codehaus.org
    [ http://jira.codehaus.org/browse/WAGONFTP-8?page=comments#action_54271 ]

John Wells commented on WAGONFTP-8:
-----------------------------------

The hanging bug has to do with the commons-net ftp client running against a windows ftp server.

This is an age-old problem (I remember working on a problem like this ten or more years ago).

The windows "ls" or "dir" command gives an *approximation* of the size of the file.  However, the actual number of bytes in the file may be different.

What is happening here is that if you do a dir (or ls) from ftp you get the following:

12-23-05 06:17AM 266 maven-metadata.xml

You would think from this that maven-metadata.xml is 266 bytes, right?  *wrong*  maven-metadata is actually 269 bytes long.  Funny, right?

Not.

What happens (I think) is that the ftp input stream reads 266 bytes and then expects an eof.  It doesn't get it, because there are still three bytes to read.  Hence, our program fails.  (You can see the real size by printing out the "inputStream.available()" result, which is 269.

I have not proved this conclusively, but I'm 90% sure this is what causes the hang.  So be happy, wagon-ftp people, looks like the bug is not you.  Now I have to go figure out how to fix the commons-net package.

Sigh...

John Wells (Aziz)
[hidden email]



> ArrayIndexOutOfBoundsException upon deploy
> ------------------------------------------
>
>          Key: WAGONFTP-8
>          URL: http://jira.codehaus.org/browse/WAGONFTP-8
>      Project: wagon-ftp
>         Type: Bug

>  Environment: Win xp, sp2
>     Reporter: Michael Fiedler

>
>
> I am trying to deploy for the first time.  I am using wagon-ftp, 1.0-alpha-4 as an extension for a maven 2 deploy goal.  The repository location (on the host) is new and empty.
> c:\...> .../bin/mvn clean:clean install deploy
> ...
> [INFO] [deploy:deploy]
> [INFO] Retrieving previous build number from M2_repo_ftp
> Uploading: ftp://host/com/company/modules/1.0-SNAPSHOT/modules-1.0-20051202.165702-1.pom
> 4K uploaded
> [INFO] Retrieving previous metadata from M2_repo_ftp
> [INFO] ----------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ----------------------------------------------------------------------------
> [INFO] 0
> [INFO] ----------------------------------------------------------------------------
> [INFO] Trace
> java.lang.ArrayIndexOutOfBoundsException: 0
>         at org.apache.maven.wagon.providers.ftp.FtpWagon.fillInputData(FtpWagon.java:326)
>         at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:68)
>         at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:367)
>         at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:295)
>         at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolveAlways(DefaultRepositoryMetadataManager.java:334)
>         at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.deploy(DefaultRepositoryMetadataManager.java:379)
>         at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:83)
>         at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:138)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:399)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>         at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO] ----------------------------------------------------------------------------

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]