Re: VFS: Multiple providers registered for URL scheme "file"

[Gary Gregory]

Hello Jenny,

You should not need to call init(). That's likely the cause of the problem.

Gary



On Mon, Jul 31, 2023, 12:30 AM Jenny Kwan  wrote:

> Hi,
>
> I'm getting started with VFS, using version 2.9.0. I'm calling
> `VFS.getManager().init()`, and getting the exception:
>
> org.apache.commons.vfs2.FileSystemException: Multiple providers registered
> for URL scheme "file".
>
> This is the cause of:
>
> org.apache.commons.vfs2.FileSystemException: Could not load VFS
> configuration from
>
> "jar:file:/home//.m2/repository/org/apache/commons/commons-vfs2/2.9.0/commons-vfs2-2.9.0.jar!/org/apache/commons/vfs2/impl/providers.xml".
>
> I checked out the jar and it looks fine; the providers.xml file has the
> single provider for the file scheme, right after the default
> UrlFileProvider.
>
> I happen to be using Clojure with Leiningen. I checked out `lein classpath`
> and there's no duplicate entry for this jar.
>
> What should I be looking for?
>
> Thanks,
> Jenny
>

VFS: Multiple providers registered for URL scheme "file"

[Jenny Kwan]

Hi,

I'm getting started with VFS, using version 2.9.0. I'm calling
`VFS.getManager().init()`, and getting the exception:

org.apache.commons.vfs2.FileSystemException: Multiple providers registered
for URL scheme "file".

This is the cause of:

org.apache.commons.vfs2.FileSystemException: Could not load VFS
configuration from
"jar:file:/home//.m2/repository/org/apache/commons/commons-vfs2/2.9.0/commons-vfs2-2.9.0.jar!/org/apache/commons/vfs2/impl/providers.xml".

I checked out the jar and it looks fine; the providers.xml file has the
single provider for the file scheme, right after the default
UrlFileProvider.

I happen to be using Clojure with Leiningen. I checked out `lein classpath`
and there's no duplicate entry for this jar.

What should I be looking for?

Thanks,
Jenny

Re: [VFS] Status of JSch and SFTP support

[Elric V]

On 2023-04-30 09:55, Jon wrote:

JSch is aging and appears to be abandoned at this point.
Any insight or recommendations would be greatly appreciated.


I've been using mwiede's continuation of jsch for a few years now, with 
success. Their fork can be found on github and in maven central etc: 
https://github.com/mwiede/jsch


-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: [VFS] Status of JSch and SFTP support

[Gary Gregory]

I would not mind seeing if we can replace Jsch with Mina. This should be
transparent to call sites (hopefully). Feel free to provide a PR on GitHub
;-)

Gary

On Sun, Apr 30, 2023, 04:15 Jon  wrote:

> JSch is aging and appears to be abandoned at this point. (One particular
> issue is its lack of support for newer key formats and algorithms). Are
> there any plans to replace it with a different implementation? It looks
> like there is an SFTP implementation under the Apache MINA SSHD project, as
> an example of an alternative. It's also possible to replace the standard
> JSch dependency with a fork (such as github.com/mwiede/jsch), but I'd
> rather stick to something "sanctioned" by VFS contributors.
>
> Any insight or recommendations would be greatly appreciated.
>

[VFS] Status of JSch and SFTP support

[Jon]

JSch is aging and appears to be abandoned at this point. (One particular
issue is its lack of support for newer key formats and algorithms). Are
there any plans to replace it with a different implementation? It looks
like there is an SFTP implementation under the Apache MINA SSHD project, as
an example of an alternative. It's also possible to replace the standard
JSch dependency with a fork (such as github.com/mwiede/jsch), but I'd
rather stick to something "sanctioned" by VFS contributors.

Any insight or recommendations would be greatly appreciated.

RE: [VFS] Question regarding releasing specific VFS2 version - Snapshot build version

[Watroba, Paulina]

Sure, thank you so much for help. 

Thanks and Regards, 
Paulina 

-Original Message-
From: Gary Gregory  
Sent: 12 December 2022 12:49
To: Watroba, Paulina (MBDJ 892) CWR 
Cc: user@commons.apache.org
Subject: Re: [VFS] Question regarding releasing specific VFS2 version - 
Snapshot build version

You can always find the current development version in pom.xml:
https://urldefense.com/v3/__https://github.com/apache/commons-vfs/blob/851ca24430eb19fefb6b9e8a0efd15d4608cc8fb/pom.xml*L32__;Iw!!KXPsTJeyZY4CYP7Aps0!5btFFD9b1WJfwaZmjRBbVE2p0a4OddMdNB4R_7hUte0RGEl9daXmkOlv58GO376KXbHkhgeWMPA85cOTO-Jndv7zZ8DFTMtx$
  

Gary

On Mon, Dec 12, 2022 at 6:35 AM Watroba, Paulina 
 wrote:
>
> Hello Gary / Team
>
>
>
> Thank you for your response.
>
> I hope it will be released soon.
>
>
>
> Could you please advise which version of the snapshot build  for dependency 
> listed below?
>
> 
>
>org.apache.commons
>
>commons-vfs2
>
>${snapshot-build-version}
>
>
>
>
>
> I will appreciate any help.
>
>
>
> Kind Regards,
>
> Paulina Watroba
> CREDIT SUISSE (POLAND) SP. Z O.O.
> Credit Suisse CoE OPS Wroclaw | EDA Data Acquisition - Wroclaw, MBDJ 
> 892 ul. Legnicka 48 | Wroclaw 54-202 | EMEA 
> paulina.watr...@credit-suisse.com | http://www.credit-suisse.com
>
> From: Gary Gregory 
> Sent: Monday, December 5, 2022 12:05 PM
> To: Commons Users List
> Cc: Witkowski, Adam (MBDJ 892) CWR
> Subject: Re: [VFS] Question regarding releasing specific VFS2 version
>
>
>
> Hello Dawid,
>
>
>
> There is no release date planned yet. Maybe within a month or two. In the 
> meantime, feel free to use a snapshot build or the git repository.
>
>
>
> Gary
>
> On Mon, Dec 5, 2022, 04:15 Dembinski, Dawid 
>  wrote:
>
> Hello,
>
> I would like to ask about below PR: Add active port range configuration for 
> FTP client factory by mperever * Pull Request #318 * apache/commons-vfs * 
> GitHub<https://urldefense.com/v3/__https://github.com/apache/commons-vfs/pull/318*pullrequestreview-1143338928__;Iw!!KXPsTJeyZY4CYP7Aps0!5btFFD9b1WJfwaZmjRBbVE2p0a4OddMdNB4R_7hUte0RGEl9daXmkOlv58GO376KXbHkhgeWMPA85cOTO-Jndv7zZ01xa92c$
>   >.
> Is there any estimated date when this will be released?
> I would like to use commons-vfs2 with active port range and this PR should 
> remove main blocker for this case.
>
> Thank you in advance for your response.
>
>
> Best Regards,
> Dawid
>
> Dawid Dembinski
> EDA Data Acquisition - Wroclaw
> CREDIT SUISSE (POLAND) SP. Z O.O.
> Credit Suisse CoE OPS Wroclaw | EDA Data Acquisition - Wroclaw, MBDJ 
> 892 ul. Legnicka 48 | Wroclaw 54-202 | EMEA 
> dawid.dembin...@credit-suisse.com<mailto:Dawid.dembinski@credit-suisse
> .com> | http://www.credit-suisse.com<http://www.credit-suisse.com>
> ==
> = Please access the attached hyperlink for an important 
> electronic communications disclaimer:
> http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
> ==
> =
>
>
> ==
>  Please access the attached hyperlink for an important 
> electronic communications disclaimer:
> http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
> ==
> 

=== 
Please access the attached hyperlink for an important electronic communications 
disclaimer: 
http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html 
=== 

-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

[VFS] Question regarding releasing specific VFS2 version - Snapshot build version

[Watroba, Paulina]

Hello Gary / Team

Thank you for your response.
I hope it will be released soon.

Could you please advise which version of the snapshot build  for dependency 
listed below?

   org.apache.commons
   commons-vfs2
   ${snapshot-build-version}
   

I will appreciate any help.

Kind Regards,
Paulina Watroba
CREDIT SUISSE (POLAND) SP. Z O.O.
Credit Suisse CoE OPS Wroclaw | EDA Data Acquisition - Wroclaw, MBDJ 892
ul. Legnicka 48 | Wroclaw 54-202 | EMEA
paulina.watr...@credit-suisse.com<mailto:paulina.watr...@credit-suisse.com> | 
www.credit-suisse.com<http://www.credit-suisse.com>
From: Gary Gregory mailto:garydgreg...@gmail.com>>
Sent: Monday, December 5, 2022 12:05 PM
To: Commons Users List
Cc: Witkowski, Adam (MBDJ 892) CWR
Subject: Re: [VFS] Question regarding releasing specific VFS2 version

Hello Dawid,

There is no release date planned yet. Maybe within a month or two. In the 
meantime, feel free to use a snapshot build or the git repository.

Gary
On Mon, Dec 5, 2022, 04:15 Dembinski, Dawid 
mailto:dawid.dembin...@credit-suisse.com.invalid>>
 wrote:
Hello,

I would like to ask about below PR: Add active port range configuration for FTP 
client factory by mperever * Pull Request #318 * apache/commons-vfs * 
GitHub<https://github.com/apache/commons-vfs/pull/318#pullrequestreview-1143338928<https://urldefense.com/v3/__https:/github.com/apache/commons-vfs/pull/318*pullrequestreview-1143338928__;Iw!!KXPsTJeyZY4CYP7Aps0!6Ge6c27GUuXb0ftD6KnTJfCEluyhacMbaBI6bX6lK7ns_pADU5CpZFtAqxArTVZdQTP4EedVPlCg-JkCwx15yNaWsUpmpSUh$>>.
Is there any estimated date when this will be released?
I would like to use commons-vfs2 with active port range and this PR should 
remove main blocker for this case.

Thank you in advance for your response.


Best Regards,
Dawid

Dawid Dembinski
EDA Data Acquisition - Wroclaw
CREDIT SUISSE (POLAND) SP. Z O.O.
Credit Suisse CoE OPS Wroclaw | EDA Data Acquisition - Wroclaw, MBDJ 892
ul. Legnicka 48 | Wroclaw 54-202 | EMEA
dawid.dembin...@credit-suisse.com<mailto:dawid.dembin...@credit-suisse.com><mailto:dawid.dembin...@credit-suisse.com<mailto:dawid.dembin...@credit-suisse.com>>
 | 
www.credit-suisse.com<http://www.credit-suisse.com><http://www.credit-suisse.com>
===
Please access the attached hyperlink for an important electronic communications 
disclaimer:
http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
===

=== 
Please access the attached hyperlink for an important electronic communications 
disclaimer: 
http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html 
=== 

Re: [VFS] Question regarding releasing specific VFS2 version - Snapshot build version

[Gary Gregory]

You can always find the current development version in pom.xml:
https://github.com/apache/commons-vfs/blob/851ca24430eb19fefb6b9e8a0efd15d4608cc8fb/pom.xml#L32

Gary

On Mon, Dec 12, 2022 at 6:35 AM Watroba, Paulina
 wrote:
>
> Hello Gary / Team
>
>
>
> Thank you for your response.
>
> I hope it will be released soon.
>
>
>
> Could you please advise which version of the snapshot build  for dependency 
> listed below?
>
> 
>
>org.apache.commons
>
>commons-vfs2
>
>${snapshot-build-version}
>
>
>
>
>
> I will appreciate any help.
>
>
>
> Kind Regards,
>
> Paulina Watroba
> CREDIT SUISSE (POLAND) SP. Z O.O.
> Credit Suisse CoE OPS Wroclaw | EDA Data Acquisition - Wroclaw, MBDJ 892
> ul. Legnicka 48 | Wroclaw 54-202 | EMEA
> paulina.watr...@credit-suisse.com | www.credit-suisse.com
>
> From: Gary Gregory 
> Sent: Monday, December 5, 2022 12:05 PM
> To: Commons Users List
> Cc: Witkowski, Adam (MBDJ 892) CWR
> Subject: Re: [VFS] Question regarding releasing specific VFS2 version
>
>
>
> Hello Dawid,
>
>
>
> There is no release date planned yet. Maybe within a month or two. In the 
> meantime, feel free to use a snapshot build or the git repository.
>
>
>
> Gary
>
> On Mon, Dec 5, 2022, 04:15 Dembinski, Dawid 
>  wrote:
>
> Hello,
>
> I would like to ask about below PR: Add active port range configuration for 
> FTP client factory by mperever * Pull Request #318 * apache/commons-vfs * 
> GitHub<https://github.com/apache/commons-vfs/pull/318#pullrequestreview-1143338928>.
> Is there any estimated date when this will be released?
> I would like to use commons-vfs2 with active port range and this PR should 
> remove main blocker for this case.
>
> Thank you in advance for your response.
>
>
> Best Regards,
> Dawid
>
> Dawid Dembinski
> EDA Data Acquisition - Wroclaw
> CREDIT SUISSE (POLAND) SP. Z O.O.
> Credit Suisse CoE OPS Wroclaw | EDA Data Acquisition - Wroclaw, MBDJ 892
> ul. Legnicka 48 | Wroclaw 54-202 | EMEA
> dawid.dembin...@credit-suisse.com<mailto:dawid.dembin...@credit-suisse.com> | 
> www.credit-suisse.com<http://www.credit-suisse.com>
> ===
> Please access the attached hyperlink for an important electronic 
> communications disclaimer:
> http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
> ===
>
>
> ==
> Please access the attached hyperlink for an important electronic 
> communications disclaimer:
> http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
> ==

-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: [VFS] Question regarding releasing specific VFS2 version

[Gary Gregory]

Hello Dawid,

There is no release date planned yet. Maybe within a month or two. In
the meantime, feel free to use a snapshot build or the git repository.

Gary

On Mon, Dec 5, 2022, 04:15 Dembinski, Dawid
 wrote:

> Hello,
>
> I would like to ask about below PR: Add active port range configuration
> for FTP client factory by mperever * Pull Request #318 * apache/commons-vfs
> * GitHub<
> https://github.com/apache/commons-vfs/pull/318#pullrequestreview-1143338928
> >.
> Is there any estimated date when this will be released?
> I would like to use commons-vfs2 with active port range and this PR should
> remove main blocker for this case.
>
> Thank you in advance for your response.
>
>
> Best Regards,
> Dawid
>
> Dawid Dembinski
> EDA Data Acquisition - Wroclaw
> CREDIT SUISSE (POLAND) SP. Z O.O.
> Credit Suisse CoE OPS Wroclaw | EDA Data Acquisition - Wroclaw, MBDJ 892
> ul. Legnicka 48 | Wroclaw 54-202 | EMEA
> dawid.dembin...@credit-suisse.com<mailto:dawid.dembin...@credit-suisse.com>
> | www.credit-suisse.com<http://www.credit-suisse.com>
> ===
>
> Please access the attached hyperlink for an important electronic
> communications disclaimer:
> http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
> ===
>
>

[VFS] Question regarding releasing specific VFS2 version

[Dembinski, Dawid]

Hello,

I would like to ask about below PR: Add active port range configuration for FTP 
client factory by mperever * Pull Request #318 * apache/commons-vfs * 
GitHub<https://github.com/apache/commons-vfs/pull/318#pullrequestreview-1143338928>.
Is there any estimated date when this will be released?
I would like to use commons-vfs2 with active port range and this PR should 
remove main blocker for this case.

Thank you in advance for your response.


Best Regards,
Dawid

Dawid Dembinski
EDA Data Acquisition - Wroclaw
CREDIT SUISSE (POLAND) SP. Z O.O.
Credit Suisse CoE OPS Wroclaw | EDA Data Acquisition - Wroclaw, MBDJ 892
ul. Legnicka 48 | Wroclaw 54-202 | EMEA
dawid.dembin...@credit-suisse.com<mailto:dawid.dembin...@credit-suisse.com> | 
www.credit-suisse.com<http://www.credit-suisse.com>
=== 
Please access the attached hyperlink for an important electronic communications 
disclaimer: 
http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html 
=== 

Re: [vfs] About hadoop-hdfs-client dependency

[Gary Gregory]

The better solution would be to move this provider to its own Maven module.
Thoughts?

Gary

On Mon, May 16, 2022, 05:26 Xavier Courangon 
wrote:

> Hello,
>
> We are using commons-vfs2 to create files in memory.
> However we are wondering why hadoop-hdfs-client dependency is not optional
> ?
> We don't really need support for HDFS in our case.
> Moreover it brings these additional transitive dependencies (vfs 2.9.0):
>
>- org.apache.hadoop : hadoop-hdfs-client : 3.3.1
>   - com.squareup.okhttp : okhttp : 2.7.5
>  - com.squareup.okio : okio : 1.6.0
>
>
> Can we explicitly exclude  hadoop-hdfs-client dependency without fear of
> side effects ?
> If so, shouldn't this dependency be optional ?
>
> Thanks
>
> Xavier C
>

Re: [vfs] About hadoop-hdfs-client dependency

[Bernd Eckenfels]

Yes, those dependencies can be left out. The optional=True seems to be missing 
for one of the libs. If you get a new manager it will not load the provide if 
it can’t load the dependencies.

If you want you could contribute a jira ticket and a patch. Thanks for 
notifying us.

Gruss
Bernd
--
http://bernd.eckenfels.net

Von: Xavier Courangon 
Gesendet: Monday, May 16, 2022 10:35:18 AM
An: user@commons.apache.org 
Betreff: [vfs] About hadoop-hdfs-client dependency

Hello,

We are using commons-vfs2 to create files in memory.
However we are wondering why hadoop-hdfs-client dependency is not optional ?
We don't really need support for HDFS in our case.
Moreover it brings these additional transitive dependencies (vfs 2.9.0):

   - org.apache.hadoop : hadoop-hdfs-client : 3.3.1
  - com.squareup.okhttp : okhttp : 2.7.5
 - com.squareup.okio : okio : 1.6.0


Can we explicitly exclude  hadoop-hdfs-client dependency without fear of
side effects ?
If so, shouldn't this dependency be optional ?

Thanks

Xavier C

[vfs] About hadoop-hdfs-client dependency

[Xavier Courangon]

Hello,

We are using commons-vfs2 to create files in memory.
However we are wondering why hadoop-hdfs-client dependency is not optional ?
We don't really need support for HDFS in our case.
Moreover it brings these additional transitive dependencies (vfs 2.9.0):

   - org.apache.hadoop : hadoop-hdfs-client : 3.3.1
  - com.squareup.okhttp : okhttp : 2.7.5
 - com.squareup.okio : okio : 1.6.0


Can we explicitly exclude  hadoop-hdfs-client dependency without fear of
side effects ?
If so, shouldn't this dependency be optional ?

Thanks

Xavier C

Re: [VFS] jsch thread hanging while reading from SFTP

[Bernd Eckenfels]

VFS is not very well suited to parallel usage, especially not if the meta data 
operations are relatively slow. One thing you can do (besides checking why the 
particular operation which blocks is slow) is to use multiple instances of the 
filesystems I think. (Won’t work with the default manager as this is a 
singleton).

Gruss
Bernd
--
http://bernd.eckenfels.net

Von: Shekhar B 
Gesendet: Friday, February 25, 2022 6:16:17 PM
An: user@commons.apache.org 
Betreff: [VFS] jsch thread hanging while reading from SFTP

I have noticed slowness in reading data from SFTP server, I have 10
parallel processes running in the different containers which are reading
this data and slowness is usually observed in one or two containers
randomly. I am using commons-vfs to read data from SFTP server and I have
extended SFTP related classes to add some sort logic. I am using centos-7.9
to host my SFTP server. I have noticed the reader thread is in blocked
state and waiting for monitor thread to release lock.

Can someone please guide me on how to fix this issue.


Thread dump:

"Thread-135" #150 prio=5 os_prio=0 tid=0x7f1e3808d800 nid=0x3a2
waiting for monitor entry [0x7f1ea5eed000]
   java.lang.Thread.State: BLOCKED (on object monitor)
at 
org.apache.commons.vfs2.provider.AbstractFileSystem.resolveFile(AbstractFileSystem.java:306)
- waiting to lock <0x0005cedf23f8> (a
org.apache.commons.vfs2.provider.sftp.MySftpFileSystem)
at 
org.apache.commons.vfs2.provider.AbstractFileSystem.resolveFile(AbstractFileSystem.java:301)
at 
org.apache.commons.vfs2.provider.AbstractOriginatingFileProvider.findFile(AbstractOriginatingFileProvider.java:76)
at 
org.apache.commons.vfs2.provider.AbstractOriginatingFileProvider.findFile(AbstractOriginatingFileProvider.java:56)
at 
org.apache.commons.vfs2.impl.DefaultFileSystemManager.resolveFile(DefaultFileSystemManager.java:711)
at 
org.apache.commons.vfs2.impl.DefaultVfsComponentContext.resolveFile(DefaultVfsComponentContext.java:46)
at 
org.apache.commons.vfs2.provider.AbstractLayeredFileProvider.findFile(AbstractLayeredFileProvider.java:54)
at 
org.apache.commons.vfs2.impl.DefaultFileSystemManager.resolveFile(DefaultFileSystemManager.java:711)
at 
org.apache.commons.vfs2.impl.DefaultFileSystemManager.resolveFile(DefaultFileSystemManager.java:677)
at 
org.apache.commons.vfs2.impl.DefaultFileSystemManager.resolveFile(DefaultFileSystemManager.java:632)
at 
com.sqlstream.aspen.namespace.filevfs.FileVFSInputSource$FileReader.run(FileVFSInputSource.java:894)
at java.lang.Thread.run(Thread.java:748)
"Thread-134" #149 daemon prio=1 os_prio=0 tid=0x7f1e381e7800
nid=0x3a1 in Object.wait() [0x7f1ea6af9000]
   java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.io.PipedInputStream.read(PipedInputStream.java:326)
- eliminated <0x0005d821ea90> (a
com.jcraft.jsch.Channel$MyPipedInputStream)
at java.io.PipedInputStream.read(PipedInputStream.java:377)
- locked <0x0005d821ea90> (a
com.jcraft.jsch.Channel$MyPipedInputStream)
at com.jcraft.jsch.ChannelSftp.fill(ChannelSftp.java:2909)
at com.jcraft.jsch.ChannelSftp.header(ChannelSftp.java:2935)
at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1643)
at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1553)
at 
org.apache.commons.vfs2.provider.sftp.MySftpFileObject.doListChildrenResolved(MySftpFileObject.java:376)
at 
org.apache.commons.vfs2.provider.AbstractFileObject.getChildren(AbstractFileObject.java:1081)
- locked <0x0005cedf23f8> (a
org.apache.commons.vfs2.provider.sftp.MySftpFileSystem)
at 
com.sqlstream.aspen.namespace.filevfs.MyFileMonitor$FileMonitorAgent.checkForNewChildren(MyFileMonitor.java:458)
at 
com.sqlstream.aspen.namespace.filevfs.MyFileMonitor$FileMonitorAgent.check(MyFileMonitor.java:543)
at 
com.sqlstream.aspen.namespace.filevfs.MyFileMonitor$FileMonitorAgent.access$200(MyFileMonitor.java:376)
at 
com.sqlstream.aspen.namespace.filevfs.MyFileMonitor.run(MyFileMonitor.java:321)
at java.lang.Thread.run(Thread.java:748)

Re: [VFS] jsch thread hanging while reading from SFTP

[Gary Gregory]

Hi,

Sorry to hear you're have an issue with VFS. I'm not sure how to help. The
usual route for support here is to provide a failing unit test or a whole
standalone project we could debug. Short of that I would start by making
sure you're using the latest versions of everything. Providing a
reproducible bug in a program is key.

Gary

On Fri, Feb 25, 2022, 14:38 Shekhar B  wrote:

> I have noticed slowness in reading data from SFTP server, I have 10
> parallel processes running in the different containers which are reading
> this data and slowness is usually observed in one or two containers
> randomly. I am using commons-vfs to read data from SFTP server and I have
> extended SFTP related classes to add some sort logic. I am using centos-7.9
> to host my SFTP server. I have noticed the reader thread is in blocked
> state and waiting for monitor thread to release lock.
>
> Can someone please guide me on how to fix this issue.
>
>
> Thread dump:
>
> "Thread-135" #150 prio=5 os_prio=0 tid=0x7f1e3808d800 nid=0x3a2
> waiting for monitor entry [0x7f1ea5eed000]
>java.lang.Thread.State: BLOCKED (on object monitor)
> at
> org.apache.commons.vfs2.provider.AbstractFileSystem.resolveFile(AbstractFileSystem.java:306)
> - waiting to lock <0x0005cedf23f8> (a
> org.apache.commons.vfs2.provider.sftp.MySftpFileSystem)
> at
> org.apache.commons.vfs2.provider.AbstractFileSystem.resolveFile(AbstractFileSystem.java:301)
> at
> org.apache.commons.vfs2.provider.AbstractOriginatingFileProvider.findFile(AbstractOriginatingFileProvider.java:76)
> at
> org.apache.commons.vfs2.provider.AbstractOriginatingFileProvider.findFile(AbstractOriginatingFileProvider.java:56)
> at
> org.apache.commons.vfs2.impl.DefaultFileSystemManager.resolveFile(DefaultFileSystemManager.java:711)
> at
> org.apache.commons.vfs2.impl.DefaultVfsComponentContext.resolveFile(DefaultVfsComponentContext.java:46)
> at
> org.apache.commons.vfs2.provider.AbstractLayeredFileProvider.findFile(AbstractLayeredFileProvider.java:54)
> at
> org.apache.commons.vfs2.impl.DefaultFileSystemManager.resolveFile(DefaultFileSystemManager.java:711)
> at
> org.apache.commons.vfs2.impl.DefaultFileSystemManager.resolveFile(DefaultFileSystemManager.java:677)
> at
> org.apache.commons.vfs2.impl.DefaultFileSystemManager.resolveFile(DefaultFileSystemManager.java:632)
> at
> com.sqlstream.aspen.namespace.filevfs.FileVFSInputSource$FileReader.run(FileVFSInputSource.java:894)
> at java.lang.Thread.run(Thread.java:748)
> "Thread-134" #149 daemon prio=1 os_prio=0 tid=0x7f1e381e7800
> nid=0x3a1 in Object.wait() [0x7f1ea6af9000]
>java.lang.Thread.State: TIMED_WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.io.PipedInputStream.read(PipedInputStream.java:326)
> - eliminated <0x0005d821ea90> (a
> com.jcraft.jsch.Channel$MyPipedInputStream)
> at java.io.PipedInputStream.read(PipedInputStream.java:377)
> - locked <0x0005d821ea90> (a
> com.jcraft.jsch.Channel$MyPipedInputStream)
> at com.jcraft.jsch.ChannelSftp.fill(ChannelSftp.java:2909)
> at com.jcraft.jsch.ChannelSftp.header(ChannelSftp.java:2935)
> at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1643)
> at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1553)
> at
> org.apache.commons.vfs2.provider.sftp.MySftpFileObject.doListChildrenResolved(MySftpFileObject.java:376)
> at
> org.apache.commons.vfs2.provider.AbstractFileObject.getChildren(AbstractFileObject.java:1081)
> - locked <0x0005cedf23f8> (a
> org.apache.commons.vfs2.provider.sftp.MySftpFileSystem)
> at
> com.sqlstream.aspen.namespace.filevfs.MyFileMonitor$FileMonitorAgent.checkForNewChildren(MyFileMonitor.java:458)
> at
> com.sqlstream.aspen.namespace.filevfs.MyFileMonitor$FileMonitorAgent.check(MyFileMonitor.java:543)
> at
> com.sqlstream.aspen.namespace.filevfs.MyFileMonitor$FileMonitorAgent.access$200(MyFileMonitor.java:376)
> at
> com.sqlstream.aspen.namespace.filevfs.MyFileMonitor.run(MyFileMonitor.java:321)
> at java.lang.Thread.run(Thread.java:748)
>

[VFS] jsch thread hanging while reading from SFTP

[Shekhar B]

I have noticed slowness in reading data from SFTP server, I have 10
parallel processes running in the different containers which are reading
this data and slowness is usually observed in one or two containers
randomly. I am using commons-vfs to read data from SFTP server and I have
extended SFTP related classes to add some sort logic. I am using centos-7.9
to host my SFTP server. I have noticed the reader thread is in blocked
state and waiting for monitor thread to release lock.

Can someone please guide me on how to fix this issue.


Thread dump:

"Thread-135" #150 prio=5 os_prio=0 tid=0x7f1e3808d800 nid=0x3a2
waiting for monitor entry [0x7f1ea5eed000]
   java.lang.Thread.State: BLOCKED (on object monitor)
at 
org.apache.commons.vfs2.provider.AbstractFileSystem.resolveFile(AbstractFileSystem.java:306)
- waiting to lock <0x0005cedf23f8> (a
org.apache.commons.vfs2.provider.sftp.MySftpFileSystem)
at 
org.apache.commons.vfs2.provider.AbstractFileSystem.resolveFile(AbstractFileSystem.java:301)
at 
org.apache.commons.vfs2.provider.AbstractOriginatingFileProvider.findFile(AbstractOriginatingFileProvider.java:76)
at 
org.apache.commons.vfs2.provider.AbstractOriginatingFileProvider.findFile(AbstractOriginatingFileProvider.java:56)
at 
org.apache.commons.vfs2.impl.DefaultFileSystemManager.resolveFile(DefaultFileSystemManager.java:711)
at 
org.apache.commons.vfs2.impl.DefaultVfsComponentContext.resolveFile(DefaultVfsComponentContext.java:46)
at 
org.apache.commons.vfs2.provider.AbstractLayeredFileProvider.findFile(AbstractLayeredFileProvider.java:54)
at 
org.apache.commons.vfs2.impl.DefaultFileSystemManager.resolveFile(DefaultFileSystemManager.java:711)
at 
org.apache.commons.vfs2.impl.DefaultFileSystemManager.resolveFile(DefaultFileSystemManager.java:677)
at 
org.apache.commons.vfs2.impl.DefaultFileSystemManager.resolveFile(DefaultFileSystemManager.java:632)
at 
com.sqlstream.aspen.namespace.filevfs.FileVFSInputSource$FileReader.run(FileVFSInputSource.java:894)
at java.lang.Thread.run(Thread.java:748)
"Thread-134" #149 daemon prio=1 os_prio=0 tid=0x7f1e381e7800
nid=0x3a1 in Object.wait() [0x7f1ea6af9000]
   java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.io.PipedInputStream.read(PipedInputStream.java:326)
- eliminated <0x0005d821ea90> (a
com.jcraft.jsch.Channel$MyPipedInputStream)
at java.io.PipedInputStream.read(PipedInputStream.java:377)
- locked <0x0005d821ea90> (a
com.jcraft.jsch.Channel$MyPipedInputStream)
at com.jcraft.jsch.ChannelSftp.fill(ChannelSftp.java:2909)
at com.jcraft.jsch.ChannelSftp.header(ChannelSftp.java:2935)
at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1643)
at com.jcraft.jsch.ChannelSftp.ls(ChannelSftp.java:1553)
at 
org.apache.commons.vfs2.provider.sftp.MySftpFileObject.doListChildrenResolved(MySftpFileObject.java:376)
at 
org.apache.commons.vfs2.provider.AbstractFileObject.getChildren(AbstractFileObject.java:1081)
- locked <0x0005cedf23f8> (a
org.apache.commons.vfs2.provider.sftp.MySftpFileSystem)
at 
com.sqlstream.aspen.namespace.filevfs.MyFileMonitor$FileMonitorAgent.checkForNewChildren(MyFileMonitor.java:458)
at 
com.sqlstream.aspen.namespace.filevfs.MyFileMonitor$FileMonitorAgent.check(MyFileMonitor.java:543)
at 
com.sqlstream.aspen.namespace.filevfs.MyFileMonitor$FileMonitorAgent.access$200(MyFileMonitor.java:376)
at 
com.sqlstream.aspen.namespace.filevfs.MyFileMonitor.run(MyFileMonitor.java:321)
at java.lang.Thread.run(Thread.java:748)

[ANNOUNCE] Apache Commons VFS Project 2.9.0

[Gary Gregory]

The Apache Commons VFS Project team is pleased to announce the release
of Apache Commons VFS Project 2.9.0.

Apache Commons VFS is a Virtual File System library.

Maintenance release. Requires Java 8.

Changes in this version include:

Fixed Bugs:
o   Add and use FileOperationProvider.EMPTY_ARRAY. Thanks to
Gary Gregory.
o   VFS.close(): Set `instance` to `null` after closing it;
#163. Thanks to Boris Petrov.
o   Fix closing the files cache after warning that not all
components have been closed; #165. Thanks to Boris Petrov.
o   Fix NPE when closing a stream from a different thread
#167. See also #166. Thanks to Boris Petrov, Gary Gregory, Max
Kellermann.
o VFS-798:  IllegalArgumentException: Bad escape for Chinese
characters in FileObject path #168. Thanks to XenoAmess, Gary Gregory.
o   Minor changes #185. Thanks to Arturo Bernal.
o   Port internal embedded HTTP asynchronous file server used
in tests from from Apache HttpComponents HttpCore/HttpClient 4.x to
5.0.x. Thanks to Gary Gregory.
o   Replace construction of FileInputStream and
FileOutputStream objects with Files NIO APIs. #164. Thanks to Arturo
Bernal.
o   Only use reflection VFS.createFileSystemManager(String) if
the FileSystemManager is not a subclass of AbstractFileSystem. Thanks
to Gary Gregory.
o   Simplify if conditions #170. Thanks to Arturo Bernal.
o   Redundant local variable #171. Thanks to Arturo Bernal.
o VFS-804:  Fix and Refine Javadoc #174. Thanks to Arturo Bernal.
o VFS-784:  SSL Connection failing with http4 provider with squid
proxy nginx combination. Thanks to satish-csi, Michael Osipov, Gary
Gregory.
o   Remove checked exception from method signatures that do
not throw them. This maintains binary compatibility but not source
compatibility.
- 
org.apache.commons.vfs2.impl.DefaultFileSystemConfigBuilder.setUserAuthenticator(FileSystemOptions,
UserAuthenticator)
- 
org.apache.commons.vfs2.impl.DefaultFileSystemManager.setBaseFile(File)
- 
org.apache.commons.vfs2.provider.LayeredFileNameParser.extractRootName(StringBuilder)
- 
org.apache.commons.vfs2.provider.sftp.SftpFileSystemConfigBuilder.setCompression(FileSystemOptions,
String)
- 
org.apache.commons.vfs2.provider.sftp.SftpFileSystemConfigBuilder.setConfigRepository(FileSystemOptions,
ConfigRepository)
- 
org.apache.commons.vfs2.provider.sftp.SftpFileSystemConfigBuilder.setIdentities(FileSystemOptions,
File...)
- 
org.apache.commons.vfs2.provider.sftp.SftpFileSystemConfigBuilder.setIdentityInfo(FileSystemOptions,
IdentityInfo...)
- 
org.apache.commons.vfs2.provider.sftp.SftpFileSystemConfigBuilder.setIdentityProvider(FileSystemOptions,
IdentityProvider...)
- 
org.apache.commons.vfs2.provider.sftp.SftpFileSystemConfigBuilder.setIdentityRepositoryFactory(FileSystemOptions,
IdentityRepositoryFactory)
- 
org.apache.commons.vfs2.provider.sftp.SftpFileSystemConfigBuilder.setKnownHosts(FileSystemOptions,
File)
- 
org.apache.commons.vfs2.provider.local.LocalFile.LocalFile(LocalFileSystem,
String, AbstractFileName)
- org.apache.commons.vfs2.provider.local.LocalFile.doGetType()
- 
org.apache.commons.vfs2.provider.tar.TarFileObject.TarFileObject(AbstractFileName,
TarArchiveEntry, TarFileSystem, boolean)
- 
org.apache.commons.vfs2.provider.tar.TarFileSystem.createTarFileObject(AbstractFileName,
TarArchiveEntry)
- 
org.apache.commons.vfs2.provider.zip.ZipFileObject.ZipFileObject(AbstractFileName,
ZipEntry, ZipFileSystem, boolean)
- 
org.apache.commons.vfs2.provider.http4.Http4FileProvider.createHttpClientContext()
- 
org.apache.commons.vfs2.provider.http5.Http5FileProvider.createHttpClientContext()
- 
org.apache.commons.vfs2.provider.http4.Http4FileObject.getInternalURI()
- 
org.apache.commons.vfs2.provider.http5.Http5FileObject.getInternalURI()
Thanks to Gary Gregory.
o VFS-805:  HTTP seek always exhausts response #186. Thanks to Claus
Stadler, Gary Gregory.
o VFS-805:  SftpFileObject: Add synchronized to methods that read or
write the thread-unsafe instance variable of type
com.jcraft.jsch.SftpATTRS. Thanks to Max Kellermann, Mark Thomas,
Bernd, Gary Gregory.
o VFS-759:  WebDAV providers should loaded only when
commons-vfs2-jackrabbit* jars are available #84 Thanks to Woonsan Ko.
o   Simplify conditions and avoid extra checks #187. Thanks to
Arturo Bernal.
o VFS-803:  Simplify if as some conditions are covered by others #173.
Thanks to Arturo Bernal.

Changes:
o   Bump Log4j 2.14.0 -> 2.14.1. Thanks to Gary Gregory.
o   Bump Maven Surefire from 2.19.1 to 3.0.0-M5. Thanks to Gary Gregory.
o   Bump net.sourceforge.pmd:pmd-* from 6.32.0 to 6.33.0.
o   Bump checkstyle from 8.41 to 8.44 #175. Thanks to
Dependabot, Gary Gregory

RE: Apache Common VFS Version and Java 11

[Vivek Madangeri]

Thanks a lot. 

Regards,
Vivek Madangeri

-Original Message-
From: Bernd Eckenfels  
Sent: Monday, May 17, 2021 11:51 AM
To: Commons Users List 
Subject: Re: Apache Common VFS Version and Java 11

It's not really a question of "last supported" it is the "minimum runtime 
requirement". VFS is compiled with Java 8 and therefore you can't use it 
(easily) with Java 7 or older (depending on the VFS version). All Java after 8 
should work and if there are problems, it's a good idea to report them here.

Gruss
Bernd
--
http://bernd.eckenfels.net

Von: Vivek Madangeri 
Gesendet: Monday, May 17, 2021 4:44:17 PM
An: user@commons.apache.org 
Betreff: Apache Common VFS Version and Java 11


For one of our applications, we use Java 11 and would like to know if Apache 
Commons VFS package is supported with Java 11 When I see the requirements for 
VFS it gives me Java 8 the last supported version.
Appreciate if you can please reply at the earliest convenience.
Thanks in advance!!


Thanks!!

Regards,
Vivek Madangeri



-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: Apache Common VFS Version and Java 11

[Bernd Eckenfels]

It’s not really a question of „last supported“ it is the „minimum runtime 
requirement“. VFS is compiled with Java 8 and therefore you can’t use it 
(easily) with Java 7 or older (depending on the VFS version). All Java after 8 
should work and if there are problems, it’s a good idea to report them here.

Gruss
Bernd
--
http://bernd.eckenfels.net

Von: Vivek Madangeri 
Gesendet: Monday, May 17, 2021 4:44:17 PM
An: user@commons.apache.org 
Betreff: Apache Common VFS Version and Java 11


For one of our applications, we use Java 11 and would like to know if Apache 
Commons VFS package is supported with Java 11
When I see the requirements for VFS it gives me Java 8 the last supported 
version.
Appreciate if you can please reply at the earliest convenience.
Thanks in advance!!


Thanks!!

Regards,
Vivek Madangeri

Apache Common VFS Version and Java 11

[Vivek Madangeri]

For one of our applications, we use Java 11 and would like to know if Apache 
Commons VFS package is supported with Java 11
When I see the requirements for VFS it gives me Java 8 the last supported 
version.
Appreciate if you can please reply at the earliest convenience.
Thanks in advance!!


Thanks!!

Regards,
Vivek Madangeri

Re: Apache Common VFS Version and Java 11

[Gary Gregory]

We build and test with Java 8, 11, 16, and 17-EA on GitHub, where you can
see the current state of things. Personally still use Java 8 mostly, with
some Java 11 testing.

Gary

On Fri, May 14, 2021, 10:45 Vivek Madangeri  wrote:

>
> For one of our applications, we use Java 11 and would like to know if
> Apache Commons VFS package is supported with Java 11
> When I see the requirements for VFS it gives me Java 8 the last supported
> version.
> Appreciate if you can please reply at the earliest convenience.
> Thanks in advance!!
>
>
> Thanks!!
>
> Regards,
> Vivek Madangeri
>
>

Re: Apache Common VFS Version and Java 11

[Bernd Eckenfels]

I have not done formal testing of all features, but we use it in production on 
Java 11.

Gruss
Bernd
--
http://bernd.eckenfels.net

Von: Vivek Madangeri 
Gesendet: Friday, May 14, 2021 3:23:22 PM
An: user@commons.apache.org 
Betreff: Apache Common VFS Version and Java 11


For one of our applications, we use Java 11 and would like to know if Apache 
Commons VFS package is supported with Java 11
When I see the requirements for VFS it gives me Java 8 the last supported 
version.
Appreciate if you can please reply at the earliest convenience.
Thanks in advance!!


Thanks!!

Regards,
Vivek Madangeri

Apache Common VFS Version and Java 11

[Vivek Madangeri]

For one of our applications, we use Java 11 and would like to know if Apache 
Commons VFS package is supported with Java 11
When I see the requirements for VFS it gives me Java 8 the last supported 
version.
Appreciate if you can please reply at the earliest convenience.
Thanks in advance!!


Thanks!!

Regards,
Vivek Madangeri

[ANNOUNCE] Apache Commons VFS Project 2.7.0

[Gary Gregory]

The Apache Commons VFS Project team is pleased to announce the release of
Apache Commons VFS Project 2.7.0.

Apache Commons VFS is a Virtual File System library.

Maintenance release. Requires Java 8.

Changes in this version include:

New features:
o VFS-757:  [SFTP] Configure whether exec detection is enabled #80. Thanks
to ddg-igh.
o   Add proxy config for some HTTP/HTTPS test #108. Thanks to
PeterAlfredLee.
o   Fix some test error when JVM's default language is not US en
#107. Thanks to PeterAlfredLee.
o VFS-787:  Allow users to set proxy schemes like http/https #122. Thanks
to satish bhor.
o VFS-786:  Allow users to set custom keystore types like JCEKS, PKCS12
#121. Thanks to satish bhor.
o VFS-570:  Add HDFS write support #114. Thanks to garpinc, Gary Gregory.
o   Add FileObject.getURI(). Thanks to Gary Gregory.
o   Add FileObject.getPath(). Thanks to Gary Gregory.
o VFS-768:  Update Apache httpclient 4.5.11 to 4.5.13 and httpclient5
5.0-beta7 to 5.0.3. Thanks to ddg-igh, Gary Gregory.
o   Add
org.apache.commons.vfs2.provider.sftp.SftpFileSystemConfigBuilder.isDisableDetectExecChannel(FileSystemOptions)
and setDisableDetectExecChannel(FileSystemOptions, boolean). Thanks to Gary
Gregory.
o   Add
org.apache.commons.vfs2.FileSystemConfigBuilder.toBooleanObject(boolean).
Thanks to Gary Gregory.
o   org.apache.commons.vfs2.provider.VfsComponent now implements
java.io.Closeable. Thanks to Gary Gregory.
o   Modify some code use try-with-resources #138. Thanks to
PeterAlfredLee.

Fixed Bugs:
o VFS-753:  NumberFormatException in SftpFileSystem::getUId. Thanks to John
Webb, Gary Gregory.
o VFS-779:  Possible null pointer dereference in
org.apache.commons.vfs2.impl.DefaultFileReplicator.close() due to return
value of called method. Thanks to Gary Gregory.
o   Modify some loop using stream API #96. Thanks to PeterAlfredLee.
o VFS-780:  SftpFileSystem returns null channel and produce NPE - fix
get… #110. Thanks to Wuchte.
o VFS-788:  [webdav/webdav4] Jackrabbit1 and jackrabbit2 modules getting
same OSGi symbolic name. Thanks to satish bhor.
o VFS-624:  Fix for read() in constructors of LocalFileRandomAccessContent
and RamFileRandomAccessContent #93. Thanks to PeterAlfredLee.
o VFS-769:  Fix .tgz and .tbz2 createFileSystem fails #94 Thanks to
PeterAlfredLee.
o VFS-664:  Fix for file names with exclamation mark can not be read #95.
Thanks to PeterAlfredLee.
o VFS-777:  NoSuchMethodError due to multiple versions of
commons-codec:commons-codec:jar. Thanks to Bing-ok, Gary Gregory.
o   Remove workaround for JDK BUG: 6192331 which was fixed way back
in Java 6: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=6192331
Thanks to Gary Gregory.
o   FileObject.getURL() returns an illegal URL when a it should
escape a space. Thanks to Gary Gregory.
o   Fix test fail caused by lack proxy configuration for machines
behind a proxy #139. Thanks to PeterAlfredLee.

Changes:
o   Update some file from CRLF to LF #141. Thanks to PeterAlfredLee.
o VFS-755:  Update org.apache.httpcomponents:httpclient from 4.5.10 to
4.5.11. Thanks to Gary Gregory.
o VFS-756:  Update org.apache.jackrabbit:jackrabbit-standalone-components
from 2.19.6 to 2.21.3. Thanks to Gary Gregory.
o VFS-754:  Update Apache Commons Compress from 1.19 to 1.20. Thanks to
Gary Gregory.
o   Update tests from Apache Commons Lang 3.9 to 3.11. Thanks to
Gary Gregory.
o   Update tests from Log4j 2.13.0 to 2.13.3. Thanks to Gary
Gregory.
o   Update tests from org.mockito:mockito-core from 3.2.4 to
3.5.13, #131. Thanks to Gary Gregory, Dependabot.
o   Update Apache Commons IO from 2.6 to 2.8.0. Thanks to Gary
Gregory.
o   Update site reports from org.apache.bcel:bcel 6.4.1 to 6.5.0.
Thanks to Gary Gregory.
o   Update actions/checkout from v1 to v2.3.3 #100, #109, #130.
Thanks to Dependabot.
o   Update actions/setup-java from v1.4.0 to v1.4.3 #111, #113,
#133. Thanks to Dependabot.
o   Update commons-parent from 50 to 52. Thanks to Gary Gregory.
o   Update checkstyle from 8.27 to 8.36.2 #123, #132. Thanks to
Dependabot.
o   Update maven-pmd-plugin from 3.12.0 to 3.13.0 #125. Thanks to
Dependabot.
o   Update exec-maven-plugin from 1.6.0 to 3.0.0 #127. Thanks to
Dependabot.
o   Update com.puppycrawl.tools:checkstyle 8.36 -> 8.36.1. Thanks
to Gary Gregory.
o   Update Apache Commons Net from 3.6 to 3.7.2. Thanks to Gary
Gregory.
o   Update JUnit from 4.13 to 4.13.1. Thanks to Gary Gregory.


Historical list of changes:
http://commons.apache.org/proper/commons-vfs/changes-report.html

For complete information on Apache Commons VFS Project, including
instructions on how to submit bug reports,
patches, or suggestions for improvement, see the Apache Apache Commons VFS
Project website:

http://commons.apache.org/proper/commons-vfs/

Download page: h

[vfs] File Monitor for an 'SFTP' file system times out occasionally and fails to recover

[KUMAR Saksham]

Hi,

While using the File Monitor for an 'SFTP' file system, we encounter the 
following error occasionally.


Could not determine the type of file 
"sftp://siq-perf:***@sftp.ggn.in.guavus.com/data/siq05_d/edrflow/edr-flow/0".
 SEVERE [106 2020-06-22 13:41:46.788]: 
org.apache.commons.vfs2.impl.DefaultFileMonitor check Could not determine the 
type of file 
"sftp://siq-perf:***@sftp.ggn.in.guavus.com/data/siq05_d/edrflow/edr-flow/0".
org.apache.commons.vfs2.FileSystemException: Could not determine the type of 
file 
"sftp://siq-perf:***@sftp.ggn.in.guavus.com/data/siq05_d/edrflow/edr-flow/0".
 at 
org.apache.commons.vfs2.provider.AbstractFileObject.getType(AbstractFileObject.java:1390)
 at 
org.apache.commons.vfs2.provider.AbstractFileObject.exists(AbstractFileObject.java:968)
 at 
org.apache.commons.vfs2.impl.DefaultFileMonitor$FileMonitorAgent.check(DefaultFileMonitor.java:496)
 at 
org.apache.commons.vfs2.impl.DefaultFileMonitor$FileMonitorAgent.access$200(DefaultFileMonitor.java:355)
 at 
org.apache.commons.vfs2.impl.DefaultFileMonitor.run(DefaultFileMonitor.java:318)
 at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.commons.vfs2.FileSystemException: Could not connect to 
SFTP server at 
"sftp://siq-perf:***@sftp.ggn.in.guavus.com/".
 at 
org.apache.commons.vfs2.provider.sftp.SftpFileSystem.getChannel(SftpFileSystem.java:159)
 at 
org.apache.commons.vfs2.provider.sftp.SftpFileObject.statSelf(SftpFileObject.java:106)
 at 
org.apache.commons.vfs2.provider.sftp.SftpFileObject.doGetType(SftpFileObject.java:76)
 at 
org.apache.commons.vfs2.provider.AbstractFileObject.getType(AbstractFileObject.java:1384)
 ... 5 more
Caused by: com.jcraft.jsch.JSchException: channel is not opened.
 at com.jcraft.jsch.Channel.sendChannelOpen(Channel.java:765)
 at com.jcraft.jsch.Channel.connect(Channel.java:151)
 at 
org.apache.commons.vfs2.provider.sftp.SftpFileSystem.getChannel(SftpFileSystem.java:133)
 ... 8 more

This error seems to repeat itself (with the File Monitor thread trying to get 
the file type again after timeout) endlessly to no end. However we are able to 
establish a sftp connection to the machine via the cli.

The issue usually arises when a bunch of files are moved onto the machine on 
which the File Monitor thread keeps checking for new files.

Any help with the same will be greatly appreciated.

Regards
Saksham Kumar

Re: [vfs] is there any way to treat a file in a zip-file to a FileObject?

[Xeno Amess]

many thanks!

Bernd Eckenfels  于2020年7月24日周五 下午3:21写道：

> Yes, the VFS providers can be nested and the access is controlled by a
> layered URL, something like zip:file:/dir/1.zip!2.jpg can be resolved into
> a FileObject.
>
> The second example here does the same for entries in a JAR file:
> https://commons.apache.org/proper/commons-vfs/api.html
>
> Gruss
> Bernd
>
>
> --
> http://bernd.eckenfels.net
> 
> Von: Xeno Amess 
> Gesendet: Friday, July 24, 2020 7:51:07 AM
> An: user@commons.apache.org 
> Betreff: [vfs] is there any way to treat a file in a zip-file to a
> FileObject?
>
> As title.
> for example, 2.jpg is in 1.zip, and what I want is a FileObject
> representing 2.jpg, but I don't want to extract it to a virtual file, what
> I want is read/write it directly treating it as a FileObject.
> Is there any ways in doing this?
> If not, should I implement one?
>

Re: [vfs] is there any way to treat a file in a zip-file to a FileObject?

[Bernd Eckenfels]

Yes, the VFS providers can be nested and the access is controlled by a layered 
URL, something like zip:file:/dir/1.zip!2.jpg can be resolved into a FileObject.

The second example here does the same for entries in a JAR file: 
https://commons.apache.org/proper/commons-vfs/api.html

Gruss
Bernd


--
http://bernd.eckenfels.net

Von: Xeno Amess 
Gesendet: Friday, July 24, 2020 7:51:07 AM
An: user@commons.apache.org 
Betreff: [vfs] is there any way to treat a file in a zip-file to a FileObject?

As title.
for example, 2.jpg is in 1.zip, and what I want is a FileObject
representing 2.jpg, but I don't want to extract it to a virtual file, what
I want is read/write it directly treating it as a FileObject.
Is there any ways in doing this?
If not, should I implement one?

[vfs] is there any way to treat a file in a zip-file to a FileObject?

[Xeno Amess]

As title.
for example, 2.jpg is in 1.zip, and what I want is a FileObject
representing 2.jpg, but I don't want to extract it to a virtual file, what
I want is read/write it directly treating it as a FileObject.
Is there any ways in doing this?
If not, should I implement one?

[ANNOUNCEMENT] Apache Commons VFS Project 2.6.0

[Gary Gregory]

The Apache Commons VFS Project team is pleased to announce the release of
Apache Commons VFS Project 2.6.0.

Apache Commons VFS is a Virtual File System library.

New features and bug fix release.

Changes in this version include:

Fixed Bugs:
o   Clean up tests and simplify assertions #76. Thanks to Eitan
Adler.
o VFS-750:  Fix backwards incompatibility in
AbstractFileObject.getInputStream(). Thanks to Boris Petrov, Gary Gregory.
o VFS-751:  Deprecate org.apache.commons.vfs2.FileUtil for
org.apache.commons.vfs2.util.FileObjectUtils. Thanks to Gary Gregory.

Changes:
o   Update JUnit from 4.12 to 4.13. Thanks to Gary Gregory.


Historical list of changes:
http://commons.apache.org/proper/commons-vfs/changes-report.html

For complete information on Apache Commons VFS Project, including
instructions on how to submit bug reports,
patches, or suggestions for improvement, see the Apache Apache Commons VFS
Project website:

http://commons.apache.org/proper/commons-vfs/

Download page: http://commons.apache.org/proper/commons-vfs/download_
vfs.cgi

Gary Gregory
On behalf of the Apache Commons Team.

[ANNOUNCEMENT] Apache Commons VFS 2.5.0

[Gary Gregory]

The Apache Commons VFS team is pleased to announce the release of Apache
Commons VFS Project 2.5.0.

Apache Commons VFS is a Virtual File System library.

New features and bug fix release.

Changes in this version include:

New features:
o VFS-734:  Add functional interface
org.apache.commons.vfs2.function.VfsConsumer. Thanks to Gary Gregory.
o VFS-735:  Add org.apache.commons.vfs2.FileSystemManager.close() via
AutoCloseable. Thanks to Gary Gregory.
o VFS-736:  Add org.apache.commons.vfs2.VFS.reset(). Thanks to Gary Gregory.
o VFS-742:  Add org.apache.commons.vfs2.FileContent.isEmpty(). Thanks to
Gary Gregory.
o VFS-743:  Add
org.apache.commons.vfs2.provider.compressed.CompressedFileFileObject.SIZE_UNDEFINED.
Thanks to Gary Gregory.
o VFS-687:  Add http5 and http5s providers (#74) Thanks to Woonsan Ko, Gary
Gregory.
o VFS-686:  Add webdav4 provider based on the latest Jackrabbit 2.x #52.
Thanks to Woonsan Ko, Gary Gregory.
o VFS-738:  Deprecate org.apache.commons.vfs2.FileChangeEvent.getFile() in
favor of getFileObject(). Thanks to Gary Gregory.

Fixed Bugs:
o VFS-741:  FileObject#getChildren allows listing of files with known
scheme prefix (generalizes VFS-398).
o VFS-726:  getInputStream(int bufferSize) on SftpFileObject effectively
ignores buffer size. Thanks to Cornelius Höfig, Gary Gregory.
o VFS-704:  Some providers wrap their input/output streams twice in a
BufferedInputStream. Thanks to Boris Petrov, Gary Gregory.
o VFS-727:  Prevented creation of singleton file system manager from
providers. Thanks to Michiel Hendriks, Gary Gregory.
o VFS-733:  Parent layer of ZipFileSystem set to null through
OnCallRefreshFileObject and DecoratedFileObject.refresh(). Thanks to Falco,
Gary Gregory, Bruno P. Kinoshita.
o VFS-739:  Changes to parseUri breaks backward compatibility by throwing
NullPointerException in some cases. Thanks to xia0c, Gary Gregory.
o VFS-744:  org.apache.commons.vfs2.FileContent.getByteArray() can throw
NegativeArraySizeException for BZip2 files. Thanks to Gary Gregory.
o VFS-590:  SFTP moveTo operation might fail on permission checks even if
the operation itself might succeed. #75. Thanks to L, Alex Pearce, Gary
Gregory.
o VFS-617:  SFTP isReadable fails if unable to determine group identity.
#75. Thanks to Tim Nickels, Joshua Woods, David Johansson, Bernd Eckenfels,
Len, Nim Lhûg, Vineet Tyagi, Gopal Warawate, Alex Pearce, Gary Gregory.
o VFS-444:  ResourceFileProvider "res://" failed to obtain FileObject from
resolved FileName. Thanks to Walter Eaves, Xavier Dury, Michiel Hendriks,
Gary Gregory.

Changes:
o VFS-737:  Update Hadoop from 3.2.0 to 3.2.1. Thanks to Gary Gregory.
o VFS-728:  Update Apache Commons Compress from 1.18 to 1.19. Thanks to
Gary Gregory.
o VFS-729:  Upgrade Hadoop to 2.7.4 or later; will use current 3.2.0.
Thanks to Michiel Hendriks, Gary Gregory.
o VFS-731:  Update org.apache.httpcomponents:httpclient from 4.5.9 to
4.5.10. Thanks to Gary Gregory.
o VFS-732:  Update org.apache.httpcomponents:httpcore-nio from 4.4.11 to
4.4.12. Thanks to Gary Gregory.
o   Update tests using org.mockito:mockito-core from 3.0.0 to
3.1.0. Thanks to Gary Gregory.
o VFS-749:  Update Apache Commons Parent from 48 to 50. Thanks to Gary
Gregory.

Historical list of changes:
http://commons.apache.org/proper/commons-vfs/changes-report.html

For complete information on Apache Commons VFS Project, including
instructions on how to submit bug reports,
patches, or suggestions for improvement, see the Apache Apache Commons VFS
Project website:

http://commons.apache.org/proper/commons-vfs/

Gary Gregory

Re: commons-vfs-2.4.1 - Question re. usage of VFS.getManager() - SOLVED

[Erwin Hogeweg]

Hi Bernd,

Thanks for your reply. When I tried this again today 

VFS.getManager().getSchemes()

returns the following (impressive) list of schemes:

[zip, par, ftps, res, ftp, sar, war, file, gz, tmp, http4s, ear, ejb3, 
jar, sftp, http4, ram]

and 

VFS.getManager().resolveFile("ftp://ftp.gnu.org/README;, opts);

works as expected. So I don’t know what happened but it looks like I spent a 
lot of time chasing a ghost. Oh well, at least I learned a thing or two.

Thanks for your help anyway.


Erwin




> 
> I think the problem in your case is that the default filesystem manager does 
> not know about the ftp: scheme. The error message is a bit missleading (since 
> a fix done, probably we should file a bug for this).
> 
> The default manager does try to load the FtpProvider and tries to register it 
> with ftp: so I assume loading of the provider failed. Maybe you are missing 
> dependencies like commons-net (see the website for the dependencies per 
> provider).
> 
> For debugging you can print manager.getSchemes() to see the available schemes 
> (providers).
> Gruss
> Bernd
> 
> 
> --
> http://bernd.eckenfels.net
> 
> 
> Von: Erwin Hogeweg 
> Gesendet: Mittwoch, Oktober 30, 2019 3:29 AM
> An: Commons Users List
> Betreff: commons-vfs-2.4.1 - Question re. usage of VFS.getManager()
> 
> All -
> 
> I am trying to set up a VFS but I struggled a while to get past a 
> FileSystemException. After looking at the VFS source code I understood what 
> was going on, and I was able to create a work-around. However, I am not sure 
> that what I hacked together is the right approach so I am looking for some 
> guidance from the experts here…
> 
> This is what I was trying to do:
> 
> FileObject path = VFS.getManager().resolveFile("ftp://ftp.gnu.org/README;, 
> new FileSystemOptions());
> 
> The issue is, or at least appears to be, that the FileSystemManager doesn’t 
> have a baseFile so the resolveFile blows up with this exception:
> 
> org.apache.commons.vfs2.FileSystemException: Could not find file with URI 
> "ftp://ftp.gnu.org/README; because it is a relative path, and no base URI was 
> provided.
> at 
> org.apache.commons.vfs2.FileSystemException.requireNonNull(FileSystemException.java:87)
> 
> I could not find how/where to define that baseFile so I eventually settled on 
> this work-around:
> 
> StandardFileSystemManager fsManager = (StandardFileSystemManager) 
> VFS.getManager(); // YUCK!
> fsManager.setBaseFile(new File("")); // Another YUCK.
> FileObject path = fsManager.resolveFile("ftp://ftp.gnu.org/README;, opts);
> 
> That works, and now I end up with the correct (expected) path. It doesn’t 
> feel right though so any advice would be greatly appreciated.
> 
> 
> Cheers,
> 
> Erwin
> 
> 

Re: commons-vfs-2.4.1 - Question re. usage of VFS.getManager()

[Bernd Eckenfels]

Hello

I think the problem in your case is that the default filesystem manager does 
not know about the ftp: scheme. The error message is a bit missleading (since a 
fix done, probably we should file a bug for this).

The default manager does try to load the FtpProvider and tries to register it 
with ftp: so I assume loading of the provider failed. Maybe you are missing 
dependencies like commons-net (see the website for the dependencies per 
provider).

For debugging you can print manager.getSchemes() to see the available schemes 
(providers).
Gruss
Bernd


--
http://bernd.eckenfels.net


Von: Erwin Hogeweg 
Gesendet: Mittwoch, Oktober 30, 2019 3:29 AM
An: Commons Users List
Betreff: commons-vfs-2.4.1 - Question re. usage of VFS.getManager()

All -

I am trying to set up a VFS but I struggled a while to get past a 
FileSystemException. After looking at the VFS source code I understood what was 
going on, and I was able to create a work-around. However, I am not sure that 
what I hacked together is the right approach so I am looking for some guidance 
from the experts here…

This is what I was trying to do:

FileObject path = VFS.getManager().resolveFile("ftp://ftp.gnu.org/README;, new 
FileSystemOptions());

The issue is, or at least appears to be, that the FileSystemManager doesn’t 
have a baseFile so the resolveFile blows up with this exception:

org.apache.commons.vfs2.FileSystemException: Could not find file with URI 
"ftp://ftp.gnu.org/README; because it is a relative path, and no base URI was 
provided.
at 
org.apache.commons.vfs2.FileSystemException.requireNonNull(FileSystemException.java:87)

I could not find how/where to define that baseFile so I eventually settled on 
this work-around:

StandardFileSystemManager fsManager = (StandardFileSystemManager) 
VFS.getManager(); // YUCK!
fsManager.setBaseFile(new File("")); // Another YUCK.
FileObject path = fsManager.resolveFile("ftp://ftp.gnu.org/README;, opts);

That works, and now I end up with the correct (expected) path. It doesn’t feel 
right though so any advice would be greatly appreciated.


Cheers,

Erwin

commons-vfs-2.4.1 - Question re. usage of VFS.getManager()

[Erwin Hogeweg]

All -

I am trying to set up a VFS but I struggled a while to get past a 
FileSystemException. After looking at the VFS source code I understood what was 
going on, and I was able to create a work-around. However, I am not sure that 
what I hacked together is the right approach so I am looking for some guidance 
from the experts here…

This is what I was trying to do:

FileObject path = VFS.getManager().resolveFile("ftp://ftp.gnu.org/README;, 
new FileSystemOptions());

The issue is, or at least appears to be, that the FileSystemManager doesn’t 
have a baseFile so the resolveFile blows up with this exception:

org.apache.commons.vfs2.FileSystemException: Could not find file with URI 
"ftp://ftp.gnu.org/README; because it is a relative path, and no base URI was 
provided.
at 
org.apache.commons.vfs2.FileSystemException.requireNonNull(FileSystemException.java:87)

I could not find how/where to define that baseFile so I eventually settled on 
this work-around:

   StandardFileSystemManager fsManager = (StandardFileSystemManager) 
VFS.getManager(); // YUCK!
   fsManager.setBaseFile(new File("")); // Another YUCK.
   FileObject path = fsManager.resolveFile("ftp://ftp.gnu.org/README;, opts);

That works, and now I end up with the correct (expected) path. It doesn’t feel 
right though so any advice would be greatly appreciated.


Cheers,

Erwin

[ANNOUNCEMENT] Apache Commons VFS Project 2.4.1

[Gary Gregory]

The Apache Commons VFS Project team is pleased to announce the release of
Apache Commons VFS Project 2.4.1-SNAPSHOT.

Apache Commons VFS is a Virtual File System library.

New features and bug fix release.

Changes in this version include:

Fixed Bugs:
o VFS-725:  [Local]
org.apache.commons.vfs2.FileContent.getLastModifiedTime() is losing
milliseconds (always ends in 000). Thanks to Gary Gregory.
o VFS-724:  FileContent#getByteArray() throws IllegalArgumentException:
Buffer size <= 0 when file size is 0. Thanks to William R, Gary Gregory.
o   Javadoc fixes. Thanks to Gary Gregory.


Historical list of changes:
http://commons.apache.org/proper/commons-vfs/changes-report.html

For complete information on Apache Commons VFS Project, including
instructions on how to submit bug reports,
patches, or suggestions for improvement, see the Apache Apache Commons VFS
Project website:

Visit http://commons.apache.org/proper/commons-vfs/

Download it from
http://commons.apache.org/proper/commons-vfs/download_vfs.cgi

Gary Gregory
On behalf of the Apache Commons Team

[ANNOUNCEMENT] Apache Commons VFS 2.4

[Gary Gregory]

The Apache Commons VFS Project team is pleased to announce the release of
Apache Commons VFS Project 2.4.

Apache Commons VFS is a Virtual File System library.

New features and bug fix release.

Changes in this version include:

New features:
o VFS-690:  Allow to set key exchange algorithm explicitly. GitHub #32.
o VFS-497:  Ported filters from Commons IO #9. Thanks to Michael Schnell.
o VFS-696:  More efficient comparison in FileExtensionSelector #44. Thanks
to Robert DeRose.
o VFS-660:  Expose workaround for connecting to FTP server from different
subnets in PASV mode #35. Thanks to Liu Yubao.
o VFS-699:  Add setting for FTP encoding auto-detection #58. Thanks to
Boris Petrov.
o VFS-706:  Add ability to specify buffer sizes #59. Thanks to Boris Petrov.
o VFS-609:  SFTP provider doesn't support a private key as byte array #60.
Thanks to stevezhuang, Rostislav, Gary Gregory.
o VFS-707:  Update Apache HttpClient from 4.5.7 to 4.5.8. Thanks to Gary
Gregory.
o VFS-712:  Add null-safe
org.apache.commons.vfs2.util.FileObjectUtils.exists(FileObject). Thanks to
Gary Gregory.
o VFS-713:  Add FileObjectUtils.readProperties(FileObject) method to read a
.properties file. Thanks to Gary Gregory.
o VFS-715:  Add org.apache.commons.vfs2.FileContent.getByteArray(). Thanks
to Gary Gregory.
o VFS-719:  Add methods to get the contents of file objects as strings.
Thanks to Gary Gregory.
o VFS-720:  Implement Closeable for RandomAccessContent #66. Thanks to
Boris Petrov.
o VFS-721:  Add support for symbolic links for the local file system and
add FileObject#isSymbolicLink(). Thanks to Gary Gregory.

Fixed Bugs:
o VFS-694:  Fix inability to start the DefaultFileMonitor after it has been
stopped. GitHub PR #55. Thanks to Boris Petrov.
o VFS-696:  SFTP HTTP and SOCKS proxy authentication. GitHub PR #49. Thanks
to rayzzed.
o VFS-707:  [SFTP] SftpFileSystem.executeCommand(String, StringBuilder) can
leak ChannelExec objects. Thanks to Gary Gregory.
o VFS-709:  [SFTP] SftpFileSystem.getGroupsIds() can initialize underlying
data more than once while multithreading. Thanks to Gary Gregory.
o VFS-710:  [SFTP] SftpFileSystem.getUid() can initialize underlying data
more than once while multithreading. Thanks to Gary Gregory.
o VFS-711:  [SFTP] SftpFileSystem can initialize underlying Session more
than once while multithreading. Thanks to Gary Gregory.
o VFS-662:  [SFTP] SftpFileSystem has Thread-safe issue about idleChannel
(#36). Thanks to qxo, Alexey Abashev, Gary Gregory.
o VFS-700:  Some tests fail on Java 11 and above. Thanks to Gary Gregory,
Matthias Krueger.
o VFS-716:  Fix AbstractFileName.getURI returning unencoded #-sign #64.
Thanks to Boris Petrov.
o VFS-698:  SFTP file attributes are fetched multiple times leading to very
slow directory listing; #65. Thanks to David Septimus, Bernd.
o VFS-717:  Update org.apache.httpcomponents:httpclient from 4.5.8 to
4.5.9. Thanks to Gary Gregory.
o VFS-718:  MonitorInputStream should not close the stream in "read" #67.
Thanks to Boris Petrov.

Changes:
o VFS-692:  Update Apache Commons Collections from 4.2 to 4.3. Thanks to
Gary Gregory.
o VFS-693:  Add support for customizing FTP transfer aborted status codes.
GitHub PR #51. Thanks to Boris Petrov, Gary Gregory.
o VFS-702:  Simplify adding files to DefaultFileMonitor #57. Thanks to
Boris Petrov.
o VFS-703:  Update Apache Commons Lang from 3.8.1 to 3.9. Thanks to Gary
Gregory.
o VFS-722:  Update Apache Commons Collections from 4.3 to 4.4. Thanks to
Gary Gregory.
o   Source incompatibility:
org.apache.commons.vfs2.FileFilter.accept(FileSelectInfo) now throws
checked exception FileSystemException.
o   Public API note: The overridden methods getURI() and
getFriendlyURI() in org.apache.commons.vfs2.provider.local.LocalFileName
where removed but are implemented in a superclass.
o   Public API note: The overridden method
org.apache.commons.vfs2.provider.sftp.SftpFileObject#refresh() was removed
but is implemented in a superclass.
o   Public API note: The overridden method
org.apache.commons.vfs2.provider.sftp.SftpFileProvider#init() was removed
but is implemented in a superclass.


Historical list of changes:
http://commons.apache.org/proper/commons-vfs/changes-report.html

For complete information on Apache Commons VFS Project, including
instructions on how to submit bug reports,
patches, or suggestions for improvement, see the Apache Apache Commons VFS
Project website:

Visit http://commons.apache.org/proper/commons-vfs/

Download it from
http://commons.apache.org/proper/commons-vfs/download_vfs.cgi

Gary Gregory
On behalf of Apache Commons

[ANNOUNCE] Apache Commons VFS 2.3

[Gary Gregory]

The Apache Commons VFS Project team is pleased to announce the release of
Apache Commons VFS Project 2.3.

Apache Commons VFS is a Virtual File System library.

New features and bug fix release.

Changes in this version include:

New features:
o VFS-677:  [SFTP] Add support for append mode. Thanks to dingxbcn.
o VFS-673:  [SFTP] Support com.jcraft.jsch.ConfigRepository (~/.ssh/config)
with SftpFileSystemConfigBuilder and flag to load OpenSSHConfig. Thanks to
Oleksandr Lykhonosov.
o VFS-673:  DefaultFileSystemManager should implement AutoCloseable. Thanks
to Daniel Banks.
o VFS-637:  Zip files with legacy encoding and special characters let VFS
crash. Thanks to Gary Gregory.
o VFS-360:  Add HTTP provider based on HttpComponents HttpClient 4. Thanks
to Woonsan Ko.
o VFS-689:
org.apache.commons.vfs2.provider.http.HttpFileObject.getHeadMethod() does
not release connection when an exception is thrown. Thanks to Gary Gregory.

Fixed Bugs:
o VFS-645:  VfsClassLoaderTests and JarProviderTestCase fails on Java 9 and
up.
o VFS-678:  Fix various LGTM.com code review warnings.
o VFS-652:  PatternFileSelector documentation to describe actual matching
against getPath().
o VFS-589:  SFTP moveTo operation hangs if the server does not support SSH
channelExec. Thanks to L, Gary Gregory.
o VFS-655:  OSGI MANIFEST.MF "Import-Package" should be
";resolution:=optional" for Maven "optional" dependencies. Thanks to Arnaud
MERGEY.
o VFS-657:  FileSelector implementations like FileDepthSelector should
throw Exception. Thanks to Elias Putz.
o VFS-614:  MonitorInputStream should not close the stream in read().
Thanks to Boris Petrov, Otto Fowler.
o VFS-667:
org.apache.commons.vfs2.provider.res.ResourceFileProvider.findFile(FileObject,
String, FileSystemOptions) should throw a
org.apache.commons.vfs2.FileSystemException instead of a NPE when the class
loader is null.
o VFS-669:
org.apache.commons.vfs2.util.CombinedResources.loadResources(String) should
not throw an NPE for the system class loader is null.
o VFS-675:  NullPointerException at AbstractFileObject.java:221.
o VFS-674:  Cannot close an FTP input stream without an exception. Thanks
to Boris Petrov, Gary Gregory.
o VFS-294:  NullPointerException in FtpFileObject.getChildFile(). Thanks to
Johannes Scharf.
o VFS-679:  NullPointerException in FtpFileObject.doGetLastModifiedTime().
Thanks to Boris Petrov, Gary Gregory.
o VFS-398:  FtpFileObject.getChildren() fails when a folder contains a file
with a colon in the name. Thanks to Otto Fowler.

Changes:
o VFS-650:  Update Apache Commons Compress from 1.15 to 1.16.1.
o VFS-646:  Update Apache Commons Compress from 1.14 to 1.15.
o VFS-653:  Replace use of deprecated APIs in HDFS provider.
o VFS-666:  Update Apache Commons Collections from 4.1 to 4.2.
o VFS-668:  Throw a NPE with a better message when a class loader is null.
o VFS-671:  Update Apache Commons Compress from 1.16.1 to 1.18.
o VFS-680:  Update from Java 7 to Java 8.
o VFS-681:  VFS.setManager should be synchronized; #43. Thanks to Robert
DeRose.
o VFS-682:  Throw a org.apache.commons.vfs2.FileSystemException instead of
a NullPointerException in
org.apache.commons.vfs2.impl.DefaultFileSystemManager.resolveName(FileName,
String, NameScope).
o VFS-688:  [SFTP] Update jsch from 0.1.54 to 0.1.55.


Historical list of changes:
http://commons.apache.org/proper/commons-vfs/changes-report.html

For complete information on Apache Commons VFS Project, including
instructions on how to submit bug reports,
patches, or suggestions for improvement, see the Apache Apache Commons VFS
Project website:

http://commons.apache.org/proper/commons-vfs/

Download it from
https://commons.apache.org/proper/commons-vfs/download_vfs.cgi

Gary Gregory
On behalf of the Apache Commons Team

[VFS] SFTP + Stream Proxy + ProxyCommand

[Jordi Rodriguez]

We want to download a file from an SFTP using Apache Commons VFS behind a
proxy. Our Java app should connect to the SFTP server through a SOCKS5
proxy. The network team has validate the proxy configuratoin to the sftp
server using this command:

sftp -v -o ProxyCommand='nc -v -x proxyserver:1080 %h %p' the_sftp_host

Regarding this command, we are trying to use a Stream proxy provided by
Apache Commons VFS, as stated in the issue "[SFTP] Stream (e.g. netcat)
proxy for Sftp file system (aka ProxyCommand)" in
https://issues.apache.org/jira/browse/VFS-440).

Using just a SOCKS5 proxy type does not work.

Our code is based on SftpProviderTestCase code provided by
commons.apache.org in
https://commons.apache.org/proper/commons-vfs/commons-vfs2/xref-test/org/apache/commons/vfs2/provider/sftp/test/SftpProviderTestCase.html

The code below works without a proxy. Once we enable the stream proxy, it
always throws an Exception like "Could not connect to SFTP server" without
any further detail.

Java dependencies:

   - commons-vfs-2.1
   - jsch-0.1.53


The commons-vfs Stream proxy requires a user and password for the proxy.
Using the same user and password from the sftp server does not work.

Also, I don't unsderstand if the file URI shoud be rewritten (and how) like
in the SftpProviderTestCase test code or it is just related to the test
case itself.

So, what are we missing to make the stream proxy work?

*Sample Code:*

package es.application.test;

import java.io.InputStream;
import java.net.URI;
import java.net.URISyntaxException;

import org.apache.commons.io.IOUtils;
import org.apache.commons.lang.StringUtils;
import org.apache.commons.lang.exception.ExceptionUtils;
import org.apache.commons.vfs2.FileObject;
import org.apache.commons.vfs2.FileSystemOptions;
import org.apache.commons.vfs2.impl.DefaultFileSystemManager;
import org.apache.commons.vfs2.provider.sftp.SftpFileSystemConfigBuilder;
import org.apache.commons.vfs2.provider.sftp.TrustEveryoneUserInfo;

import es.application.common.util.Utils;

/**
 *
 * This code is based on
https://commons.apache.org/proper/commons-vfs/commons-vfs2/xref-test/org/apache/commons/vfs2/provider/sftp/test/SftpProviderTestCase.html
 *
 * Apache Commons VFS allows ProxyCommand as per
https://issues.apache.org/jira/browse/VFS-440
 *
 *
 *
 */
public class ReadFromSftp {

private String host = "sftp_host";
private String user = "sftp_user";
private String password = "sftp_password";
private String remoteDir = "/";
private String sftpileName = "the_file.xml";

private int proxyPort=1080;
private String proxyHost="localhost";
private String proxyCommand;
private boolean useProxy = true;


public  String readFromSFTP() {

  proxyPort=1080;
  proxyHost="proxyserver";
  useProxy = true;
  proxyCommand ="nc -X 5 -x proxyserver:1080 "+this.host+ " 22";

String fileContent = StringUtils.EMPTY;

if (StringUtils.isNotBlank(host)) {
//FileSystemManager fsManager = null;
DefaultFileSystemManager fsManager = null;
FileSystemOptions opts = null;
FileObject[] remoteFiles = null;
String filePath = StringUtils.EMPTY;

try {

filePath = "sftp://; +host + remoteDir;
/**
 *  Not using fsManager = VFS.getManager();
*/
fsManager = new DefaultFileSystemManager();

fsManager.addProvider("sftp", new
org.apache.commons.vfs2.provider.sftp.SftpFileProvider());
fsManager.init();


//Not using UserAuthenticator auth = new
StaticUserAuthenticator(null, this.user, this.password);
opts = new FileSystemOptions();


/**
 * Not using any of these configurations
 *

DefaultFileSystemConfigBuilder.getInstance().setUserAuthenticator(opts,
auth);

DefaultFileSystemConfigBuilder.getInstance().setRootURI(opts, filePath);
//
FtpFileSystemConfigBuilder.getInstance().setUserDirIsRoot(opts, true);
 */


final SftpFileSystemConfigBuilder builder =
SftpFileSystemConfigBuilder.getInstance();
builder.setStrictHostKeyChecking(opts, "no");
builder.setUserInfo(opts, new TrustEveryoneUserInfo());
builder.setTimeout(opts, 2);
//TODO: Do we need this?
//builder.setIdentityRepositoryFactory(fileSystemOptions,
new TestIdentityRepositoryFactory());


FileSystemOptions proxy_opts =
(FileSystemOptions)opts.clone();

if (this.useProxy) {
System.out.println("PROXY enabled");
builder.setProxyHost(opts, this.proxyHost);
   

[vfs] Support for Kerberos Authentication with HDFS on VFS

[Jacobsen, Jane]

Hi,

I am an engineer at T-Mobile. I am trying to use VFS for an HDFS File Watcher 
written in Scala. According to the VFS documentation, authentication is not 
supported. I need to use Kerberos authentication in order to connect to a 
T-Mobile HDFS cluster. Is this possible with VFS?

Specifically, I’d like to use the resolveFile method to return a FileObject.

VFS.getManager.resolveFile(hdfsPathString)

Is there any way to use the resolveFile method after authentication with 
Kerberos? If not, is there anything else you can suggest?

Thanks,
Jane Jacobsen

Re: [vfs] Is VFS2 suitable for production use?

[Matt Sicker]

There have been suggestions in the past for a v3, so if you search the
mailing lists, you may find a good place to start.

On Sun, Jul 15, 2018 at 07:15, Gary Gregory  wrote:

> VFS is stable and maintained. Feel free to provide PRs :-)
>
> Gary
>
> On Sun, Jul 15, 2018, 03:00 Jurrie Overgoor  wrote:
>
> > Hello everyone,
> >
> > At the moment, my team is using Apache VFS2 in production. We use it for
> > HTTP(S) and for (S)FTP. However, we are having some problems with this.
> >
> > SFTP is implemented using JSCH. That project now seems abandoned. I had
> > to cook up my own fix for issue JSCH-111 (see
> > https://github.com/Jurrie/jsch-111-bugfix).
> >
> > HTTP(S) is implemented using Apache Httpclient 3.x, which is end of life
> > (see https://hc.apache.org/httpclient-3.x/). Its replacement is Apache
> > HttpComponents, but that is not a plug-and-play direct replacement.
> >
> > That leads me to wonder whether Apache VFS2 is still under active
> > development? Are there any plans to fix the above things? Is it still
> > advised to use Apache VSF2 in production software?
> >
> > With kind regards,
> >
> > Jurrie
> >
> >
> > -
> > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> > For additional commands, e-mail: user-h...@commons.apache.org
> >
> >
>
-- 
Matt Sicker 

Re: [vfs] Is VFS2 suitable for production use?

[Gary Gregory]

VFS is stable and maintained. Feel free to provide PRs :-)

Gary

On Sun, Jul 15, 2018, 03:00 Jurrie Overgoor  wrote:

> Hello everyone,
>
> At the moment, my team is using Apache VFS2 in production. We use it for
> HTTP(S) and for (S)FTP. However, we are having some problems with this.
>
> SFTP is implemented using JSCH. That project now seems abandoned. I had
> to cook up my own fix for issue JSCH-111 (see
> https://github.com/Jurrie/jsch-111-bugfix).
>
> HTTP(S) is implemented using Apache Httpclient 3.x, which is end of life
> (see https://hc.apache.org/httpclient-3.x/). Its replacement is Apache
> HttpComponents, but that is not a plug-and-play direct replacement.
>
> That leads me to wonder whether Apache VFS2 is still under active
> development? Are there any plans to fix the above things? Is it still
> advised to use Apache VSF2 in production software?
>
> With kind regards,
>
> Jurrie
>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>
>

[vfs] Is VFS2 suitable for production use?

[Jurrie Overgoor]

Hello everyone,

At the moment, my team is using Apache VFS2 in production. We use it for 
HTTP(S) and for (S)FTP. However, we are having some problems with this.


SFTP is implemented using JSCH. That project now seems abandoned. I had 
to cook up my own fix for issue JSCH-111 (see 
https://github.com/Jurrie/jsch-111-bugfix).


HTTP(S) is implemented using Apache Httpclient 3.x, which is end of life 
(see https://hc.apache.org/httpclient-3.x/). Its replacement is Apache 
HttpComponents, but that is not a plug-and-play direct replacement.


That leads me to wonder whether Apache VFS2 is still under active 
development? Are there any plans to fix the above things? Is it still 
advised to use Apache VSF2 in production software?


With kind regards,

Jurrie


-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Commons VFS 2.2, SFTP, and ProxyCommand

[Scott Dudley]

Can someone direct me to a code fragment or example of how to proxy an SFTP 
connection through an SSH host.  I'm able to do the following via shell:

sftp -o "ProxyCommand=ssh -e none user1@host1 exec /bin/nc %h %p 2>/dev/null" 
user2@host2/path


The following was my initial, failed attempt:



            FileSystemManager fsm = VFS.getManager();

            FileSystemOptions opts = new FileSystemOptions();
            StaticUserAuthenticator auth = new StaticUserAuthenticator(null, 
"user2", "password2");
            
DefaultFileSystemConfigBuilder.getInstance().setUserAuthenticator(opts, auth);
            
            SftpFileSystemConfigBuilder builder = 
SftpFileSystemConfigBuilder.getInstance();
            builder.setProxyHost(opts, "host1");
            builder.setProxyUser(opts, "user1");
            builder.setProxyPassword(opts, "password1");
            
            FileObject fo = 
fsm.resolveFile("sftp://user2:password2@host2/path;, opts);


Thanks.
--
This message is for the designated recipient(s) only and may contain 
privileged, proprietary, and/or confidential information.
If you have received it in error, please notify the sender immediately and 
delete the original. Any other use of the email by you is prohibited. 
Any views or opinions expressed are solely those of the author and do not 
necessarily represent those of MDSL. 
--

[vfs] Zip files and relative paths

[Nick Cross]

Hi,

I am processing a number of potentially large nested archive files (such 
as zips/jars etc). I appear to have hit [1] as one of the zips contains 
a nested path. Simplifying the test down to a trivial zip as per that 
jira issue does show the problem - it simply throws an exception and 
stops processing. However, I would like to continue processing the zip 
file, perhaps logging the offending archive entry.


Using version 2.2, is there any way of overriding the default 
ZipFileSystem so I can provide a patched implementation of init() so I 
can avoid this issue?


Thanks

Nick


[1] https://issues.apache.org/jira/browse/VFS-219

-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

[ANNOUNCEMENT] Apache Commons VFS 2.2 Released

[Gary Gregory]

The Apache Commons team is pleased to announce the release of Commons VFS
2.2.

Commons VFS provides a single API for accessing various different file
systems. It presents a uniform view of the files from various different
sources, such as the files on local disk, on an HTTP server, or inside a
Zip archive.

Details of the changes and bug fixes in this release can be found in the
release notes:
  http://www.apache.org/dist/commons/vfs/RELEASE-NOTES.txt

For information on Commons VFS please visit the VFS website:
  http://commons.apache.org/vfs/

Commons VFS can be downloaded from the following page:
 http://commons.apache.org/vfs/download_vfs.cgi

Allow 24 hours for the mirrors to catch up.

Gary Gregory
on behalf of the Apache Commons community

Re: [VFS] How to override a FileContent / FileContentInfo provider for an existing filesystem?

[Gary Gregory]

I'm curious at what Ralph thinks. You could consider providing a PR to add
the feature to make the class pluggable and see how much code that
touches...

Gary

On Mon, Sep 25, 2017 at 10:23 AM, Carl Eric Codere <
cecod...@yahoo.ca.invalid> wrote:

> Greetings, Thanks for your quick reply!  Yes, you are
> correct.  I would like to have a way to change the provider, I would
> subclass the implementation that you have and use that as content and
> contentInfo provider. Otherwise, if its not the case, currently i need to
> reimplement everything, right?
>
> Best regards,Carl
>
>   From: Gary Gregory <garydgreg...@gmail.com>
>  To: Commons Users List <user@commons.apache.org>; Carl Eric Codere <
> cecod...@yahoo.ca>
>  Sent: Monday, September 25, 2017 5:07 PM
>  Subject: Re: [VFS] How to override a FileContent / FileContentInfo
> provider for an existing filesystem?
>
> Hi Carl,
>
> Do you mean org.apache.commons.vfs2.impl.DefaultFileContentInfo
> and org.apache.commons.vfs2.impl.FileContentInfo?
>
> Ralph, do have issue as to make this pluggable?
>
> Gary
>
> On Mon, Sep 25, 2017 at 8:31 AM, Carl Eric Codere
> <cecod...@yahoo.ca.invalid
> > wrote:
>
> > Greetings,I am interested in using the VFS library for
> one
> > of my projects, as it has almost everything I need, but i have some
> > questions on it though.
> > My use case is as follows:* For the local file system, I use DESCRIPT.ION
> > files to store attributes of files and directories, so I would need to
> > override some methods of DefaultFileInfo() , mainly all the attribute
> > related functions. How can I set my own FileInfo provider? I did not find
> > any API in the interfaces to do this, maybe, i missed something.
> > * The same is true of FileContent, how can I set my own FileContentInfo
> > provider in FileContent ? I would probably use a feature of JDK 1.6 (the
> > FileTypeMap class) to override the default implementation.
> >
> > Finally an unrelated question, why you do not use the DataSource
> interface
> > in FileObject available in JDK 1.6, is it because of Android
> compatibility
> > issues?
> > Thanks in advance for your help,Carl
> >
> >
> >
> >
> >
> >
>
>
>

Re: [VFS] How to override a FileContent / FileContentInfo provider for an existing filesystem?

[Carl Eric Codere]

Greetings,
 Yes, I was talking about javax.activation.DataSource, which 
seems to be consistent with what you are doing, but it does not seem to have 
available in Android i think, so it could be an issue, also same for 
FileTypeMap, thanks for the clarification.
Best regards,Carl

  From: Gary Gregory <garydgreg...@gmail.com>
 To: Commons Users List <user@commons.apache.org>; Carl Eric Codere 
<cecod...@yahoo.ca> 
 Sent: Monday, September 25, 2017 5:10 PM
 Subject: Re: [VFS] How to override a FileContent / FileContentInfo provider 
for an existing filesystem?
   
Hi Carl,

WRT DataSource, this is a JDBC interface, which does not seem appropriate
for a file system. Or do you mean javax.activation.DataSource. Apache
Commons VFS was started a long time ago and not adapted to newer JREs in
this area (obviously.)

Gary


On Mon, Sep 25, 2017 at 8:31 AM, Carl Eric Codere <cecod...@yahoo.ca.invalid
> wrote:

> Greetings,                I am interested in using the VFS library for one
> of my projects, as it has almost everything I need, but i have some
> questions on it though.
> My use case is as follows:* For the local file system, I use DESCRIPT.ION
> files to store attributes of files and directories, so I would need to
> override some methods of DefaultFileInfo() , mainly all the attribute
> related functions. How can I set my own FileInfo provider? I did not find
> any API in the interfaces to do this, maybe, i missed something.
> * The same is true of FileContent, how can I set my own FileContentInfo
> provider in FileContent ? I would probably use a feature of JDK 1.6 (the
> FileTypeMap class) to override the default implementation.
>
> Finally an unrelated question, why you do not use the DataSource interface
> in FileObject available in JDK 1.6, is it because of Android compatibility
> issues?
> Thanks in advance for your help,Carl
>
>
>
>
>
>


   

Re: [VFS] How to override a FileContent / FileContentInfo provider for an existing filesystem?

[Carl Eric Codere]

Greetings,             Thanks for your quick reply!  Yes, you are correct.  I 
would like to have a way to change the provider, I would subclass the 
implementation that you have and use that as content and contentInfo provider. 
Otherwise, if its not the case, currently i need to reimplement everything, 
right?
               
    Best regards,Carl

  From: Gary Gregory <garydgreg...@gmail.com>
 To: Commons Users List <user@commons.apache.org>; Carl Eric Codere 
<cecod...@yahoo.ca> 
 Sent: Monday, September 25, 2017 5:07 PM
 Subject: Re: [VFS] How to override a FileContent / FileContentInfo provider 
for an existing filesystem?
   
Hi Carl,

Do you mean org.apache.commons.vfs2.impl.DefaultFileContentInfo
and org.apache.commons.vfs2.impl.FileContentInfo?

Ralph, do have issue as to make this pluggable?

Gary

On Mon, Sep 25, 2017 at 8:31 AM, Carl Eric Codere <cecod...@yahoo.ca.invalid
> wrote:

> Greetings,                I am interested in using the VFS library for one
> of my projects, as it has almost everything I need, but i have some
> questions on it though.
> My use case is as follows:* For the local file system, I use DESCRIPT.ION
> files to store attributes of files and directories, so I would need to
> override some methods of DefaultFileInfo() , mainly all the attribute
> related functions. How can I set my own FileInfo provider? I did not find
> any API in the interfaces to do this, maybe, i missed something.
> * The same is true of FileContent, how can I set my own FileContentInfo
> provider in FileContent ? I would probably use a feature of JDK 1.6 (the
> FileTypeMap class) to override the default implementation.
>
> Finally an unrelated question, why you do not use the DataSource interface
> in FileObject available in JDK 1.6, is it because of Android compatibility
> issues?
> Thanks in advance for your help,Carl
>
>
>
>
>
>


   

Re: [VFS] How to override a FileContent / FileContentInfo provider for an existing filesystem?

[Gary Gregory]

Hi Carl,

WRT DataSource, this is a JDBC interface, which does not seem appropriate
for a file system. Or do you mean javax.activation.DataSource. Apache
Commons VFS was started a long time ago and not adapted to newer JREs in
this area (obviously.)

Gary


On Mon, Sep 25, 2017 at 8:31 AM, Carl Eric Codere <cecod...@yahoo.ca.invalid
> wrote:

> Greetings,I am interested in using the VFS library for one
> of my projects, as it has almost everything I need, but i have some
> questions on it though.
> My use case is as follows:* For the local file system, I use DESCRIPT.ION
> files to store attributes of files and directories, so I would need to
> override some methods of DefaultFileInfo() , mainly all the attribute
> related functions. How can I set my own FileInfo provider? I did not find
> any API in the interfaces to do this, maybe, i missed something.
> * The same is true of FileContent, how can I set my own FileContentInfo
> provider in FileContent ? I would probably use a feature of JDK 1.6 (the
> FileTypeMap class) to override the default implementation.
>
> Finally an unrelated question, why you do not use the DataSource interface
> in FileObject available in JDK 1.6, is it because of Android compatibility
> issues?
> Thanks in advance for your help,Carl
>
>
>
>
>
>

Re: [VFS] How to override a FileContent / FileContentInfo provider for an existing filesystem?

[Gary Gregory]

Hi Carl,

Do you mean org.apache.commons.vfs2.impl.DefaultFileContentInfo
and org.apache.commons.vfs2.impl.FileContentInfo?

Ralph, do have issue as to make this pluggable?

Gary

On Mon, Sep 25, 2017 at 8:31 AM, Carl Eric Codere <cecod...@yahoo.ca.invalid
> wrote:

> Greetings,I am interested in using the VFS library for one
> of my projects, as it has almost everything I need, but i have some
> questions on it though.
> My use case is as follows:* For the local file system, I use DESCRIPT.ION
> files to store attributes of files and directories, so I would need to
> override some methods of DefaultFileInfo() , mainly all the attribute
> related functions. How can I set my own FileInfo provider? I did not find
> any API in the interfaces to do this, maybe, i missed something.
> * The same is true of FileContent, how can I set my own FileContentInfo
> provider in FileContent ? I would probably use a feature of JDK 1.6 (the
> FileTypeMap class) to override the default implementation.
>
> Finally an unrelated question, why you do not use the DataSource interface
> in FileObject available in JDK 1.6, is it because of Android compatibility
> issues?
> Thanks in advance for your help,Carl
>
>
>
>
>
>

[VFS] How to override a FileContent / FileContentInfo provider for an existing filesystem?

[Carl Eric Codere]

Greetings,    I am interested in using the VFS library for one of 
my projects, as it has almost everything I need, but i have some questions on 
it though.
My use case is as follows:* For the local file system, I use DESCRIPT.ION files 
to store attributes of files and directories, so I would need to override some 
methods of DefaultFileInfo() , mainly all the attribute related functions. How 
can I set my own FileInfo provider? I did not find any API in the interfaces to 
do this, maybe, i missed something.
* The same is true of FileContent, how can I set my own FileContentInfo 
provider in FileContent ? I would probably use a feature of JDK 1.6 (the 
FileTypeMap class) to override the default implementation.

Finally an unrelated question, why you do not use the DataSource interface in 
FileObject available in JDK 1.6, is it because of Android compatibility issues?
Thanks in advance for your help,Carl




 

Re: [vfs] FileSystemException: Could not determine if file ... is writeable with v2.1

[billharrelson]

as expected, destination FileObject instance .isWriteable()() throws
FileSystemException as well.



--
View this message in context: 
http://apache-commons.680414.n4.nabble.com/vfs-FileSystemException-Could-not-determine-if-file-is-writeable-with-v2-1-tp4682060p4694105.html
Sent from the Commons - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: [vfs] FileSystemException: Could not determine if file ... is writeable with v2.1

[billharrelson]

I have tried forcing the JSch version back to 0.1.48 - no difference.  Still
get the error.  Any more suggestions?  Thanks.



--
View this message in context: 
http://apache-commons.680414.n4.nabble.com/vfs-FileSystemException-Could-not-determine-if-file-is-writeable-with-v2-1-tp4682060p4694102.html
Sent from the Commons - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: VFS stats

[Gary Gregory]

Great feature request. Would you create a Jira?

Gary

On Mon, Oct 3, 2016 at 5:15 AM, FLORENT Philippe <
philippe.flor...@edenred.com> wrote:

> Hello,
>
> Using common VFS, sftp, when I use copyFrom, I would like to have some
> stats on the file transfer
> Is it possible ? it's to give the user some feedback about the transfer
> speed
>
> thanks
>



-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

VFS stats

[FLORENT Philippe]

Hello,

Using common VFS, sftp, when I use copyFrom, I would like to have some stats on 
the file transfer
Is it possible ? it's to give the user some feedback about the transfer speed

thanks

Re: [vfs]Issue creating HttpClient timeout

[Bernd Eckenfels]

Hello,

I am not sure I understand how the configuration of HTTPClient with
HttpConnectionManagerParams works. Especially not what the 

* ConnectionManager set methods must be called after the host & port
* and proxy host & port are set in the HostConfiguration.

comment means. But I guess since you have problems with missing
timeouts, the way it is currently done does not work.

Can you please open a JIRA for this problem?

https://issues.apache.org/jira/browse/VFS

If you want you can also attach your patch. I hope somebody who is more
familier with Apache HttpClient can comment on it.

Gruss
Bernd



 Am Mon, 25 Jul 2016
12:04:48 -0700 schrieb Feiyi Xiang <feiyixi...@eharmony.com.INVALID>:

> Hi,
> 
> My name is Ben and recently we met an issue that the thread got stuck
> during the http connection using HttpClient. And It showed that the
> connection timeout was set to 0, which was not what we set. let me
> briefly show here how we are using VFS2: Create a FileSystemOptions
> with timeout set:
> 
> final FileSystemOptions fso = new FileSystemOptions();
> final HttpFileSystemConfigBuilder httpBuilder =
> HttpFileSystemConfigBuilder.getInstance();
> httpBuilder.setConnectionTimeout(fso, connectionTimeout);
> httpBuilder.setSoTimeout(fso, soTimeout);
> 
> Create a FileObject using FileSystemManager:
> 
> vfs2FileManager.resolveFile(fileLocation, fso);
> 
> Finally get the input stream using DefaultFileContent:
> 
> final InputStream instr = fileObject.getInputStream();
> 
> We noticed that in executeMethod() of HttpMethodDirector, line 153,
> it is setting the connection timeout using client's params. However,
> in HttpClientFactory, it's setting fileSystemOptions in
> connectionMgrParams, and the HttpClient's params would not have this
> value. So we did the following to make it work: In package
> org.apache.commons.vfs2.provider.http, HttpClientFactory, added line
> 148 and 149:
> client.getParams().setConnectionManagerTimeout(connectionMgrParams.getConnectionTimeout());
> client.getParams().setSoTimeout(connectionMgrParams.getSoTimeout());
> Please let me know your thought about this and if there is a patch
> needed, or is there something we are missing or doing wrong ?
> 
> Thanks!
> 
> Ben
> 
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

[vfs]Issue creating HttpClient timeout

[Feiyi Xiang]

Hi,

My name is Ben and recently we met an issue that the thread got stuck during 
the http connection using HttpClient. And It showed that the connection timeout 
was set to 0, which was not what we set.
let me briefly show here how we are using VFS2:
Create a FileSystemOptions with timeout set:

final FileSystemOptions fso = new FileSystemOptions();
final HttpFileSystemConfigBuilder httpBuilder = 
HttpFileSystemConfigBuilder.getInstance();
httpBuilder.setConnectionTimeout(fso, connectionTimeout);
httpBuilder.setSoTimeout(fso, soTimeout);

Create a FileObject using FileSystemManager:

vfs2FileManager.resolveFile(fileLocation, fso);

Finally get the input stream using DefaultFileContent:

final InputStream instr = fileObject.getInputStream();

We noticed that in executeMethod() of HttpMethodDirector, line 153, it is 
setting the connection timeout using client's params. However,
in HttpClientFactory, it's setting fileSystemOptions in connectionMgrParams, 
and the HttpClient's params would not have this value.
So we did the following to make it work:
In package org.apache.commons.vfs2.provider.http, HttpClientFactory, added line 
148 and 149:
client.getParams().setConnectionManagerTimeout(connectionMgrParams.getConnectionTimeout());
client.getParams().setSoTimeout(connectionMgrParams.getSoTimeout());
Please let me know your thought about this and if there is a patch needed, or 
is there something we are missing or doing wrong ?

Thanks!

Ben

-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

[VFS] jcifs in sandbox (was: Commons VFS2)

[Bernd]

Hello Chritopher,

(forwarding your request to the aproperiate mailing list)


I think it was never part of main distribution (outside of the sandbox). It
cannot be released as it has a non-ASL-license (LGPL) compatible jcifs
dependency (AFAIK). So it cannot be expected to be released in an official
ASF distribution.



Gruss

Bernd





*From:* Christopher Stasiak [mailto:christopher.stas...@gmail.com]
*Sent:* Monday, June 27, 2016 2:30 PM
*To:* e...@apache.org
*Subject:* Commons VFS2



Hi,

I would like to ask you a question about commons-vfs2. Why SMB provider was
moved to sandbox ? Is there a plan to release it as part of a main library ?

BR

Chris

Re: [vfs] Why does the MonitorInputStream close the stream in read?

[Boris Petrov]

Hi,

I've created an issue:

https://issues.apache.org/jira/browse/VFS-614

I hope it gets resolved soon and a new version is released as it is
quite horrible. :)

Thanks,

Boris


On 06/13/2016 10:20 PM, Bernd Eckenfels wrote:
> Hello Boris,
>
> I was not looking into the code, but from your description this sounds
> like something I would classify as a bug.
>
> Can you open a VFS issue for it please. Ideally with a reproducer unit
> test (w/o tika dependency).
>
> As a workaround I can imagine Tika has a markable wrapper already, so
> it can check for "(stream.markSupported() && !stream instanceof
> MonitorInputStream)...?
>
> Gruss
> Bernd
>
>  Am Mon, 13 Jun 2016 18:40:24
> +0300 schrieb Boris Petrov <bo...@profuzdigital.com>:
>
>> I am using Apache Tika to detect file types. Somewhere in the code it
>> does:
>>
>> if (stream.markSupported())
>>
>> Which returns "true" for a MonitorInputStream. Then it does:
>>
>> stream.mark(...);
>> try {
>> ... read(stream);
>> } finally {
>> stream.reset();
>> }
>>
>> Which should not be an issue as it already asked whether marking is
>> supported. However, due to "read" of MonitorInputStream closing the
>> stream, "reset" throws a "java.io.IOException: Stream closed". This is
>> obviously not good. Any ideas what I should do?
>>
>> Thanks!
>>
>>
>> -
>> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
>> For additional commands, e-mail: user-h...@commons.apache.org
>>


-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: [vfs] commons-vfs2-sandbox-2.1 is missing from Maven Central Repository

[Gary Gregory]

Yeah, I think sandbox code is just that, play things not fit for release,
due to licensing or other reasons.

You'd have to build it yourself and then deploy it to your own
repository(ies).

Gary

On Mon, Jun 13, 2016 at 8:39 AM, Boris Petrov 
wrote:

> Hi, I want to include the CIFS provider, however the classes needed are
> in the sandbox jar which is not in Maven Central. Am I missing something
> here?
>
> Thanks!
>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>
>


-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition

JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

[vfs] Why does the MonitorInputStream close the stream in read?

[Boris Petrov]

I am using Apache Tika to detect file types. Somewhere in the code it does:

if (stream.markSupported())

Which returns "true" for a MonitorInputStream. Then it does:

stream.mark(...);
try {
... read(stream);
} finally {
stream.reset();
}

Which should not be an issue as it already asked whether marking is
supported. However, due to "read" of MonitorInputStream closing the
stream, "reset" throws a "java.io.IOException: Stream closed". This is
obviously not good. Any ideas what I should do?

Thanks!


-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

[vfs] commons-vfs2-sandbox-2.1 is missing from Maven Central Repository

[Boris Petrov]

Hi, I want to include the CIFS provider, however the classes needed are
in the sandbox jar which is not in Maven Central. Am I missing something
here?

Thanks!


-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

[ANNOUNCE] Apache Commons VFS 2.1 released

[Josh Elser]

The Apache Commons team is pleased to announce the release of Apache 
Commons VFS 2.1. Apache Commons VFS provides a single API for accessing 
various different file systems. It presents a uniform view of the files 
from various different sources, such as the files on local disk, on an 
HTTP server, or inside a Zip archive.


Details of the changes and bug fixes in this release can be found in
the release notes:

http://www.apache.org/dist/commons/vfs/RELEASE_NOTES.txt

This release is binary compatible with 2.0, users are encouraged to 
upgrade at their earliest convenience.


For information on Commons VFS please visit the VFS website:
http://commons.apache.org/vfs/

Commons VFS can be downloaded from the following page:
http://commons.apache.org/vfs/download_vfs.cgi

- The Apache Commons community

-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: commons vfs next release - ?

[Gary Gregory]

There is a VOTE in progress for 2.1. Please check the dev ML for details.

Gary

On Sun, May 15, 2016 at 10:50 AM, Dmitry Goldenberg <
dgoldenberg...@gmail.com> wrote:

> Hi,
>
> Apologies if this is posted somewhere already. What is the current roadmap
> for the release of commons vfs2 version 2.1?  Is there a specific target
> date when it'll become available on Maven Central?
>
> Is the HDFS provider in a completed state? It appears that the write to
> HDFS capability is there. Just curious if this is complete.
>
> Thanks.
>



-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition

JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

commons vfs next release - ?

[Dmitry Goldenberg]

Hi,

Apologies if this is posted somewhere already. What is the current roadmap
for the release of commons vfs2 version 2.1?  Is there a specific target
date when it'll become available on Maven Central?

Is the HDFS provider in a completed state? It appears that the write to
HDFS capability is there. Just curious if this is complete.

Thanks.

Re: [vfs] FileSystemException: Could not determine if file ... is writeable with v2.1

[Ryan Pugatch]

> Do you have a full stack trace of that error? I dont think writeability
> is checked by default on login.
> 
> Gruss
> Bernd
> 
> -- 
> http://bernd.eckenfels.net
> 
> -Original Message-
> From: Ryan Pugatch <r...@lp0.org>
> To: user@commons.apache.org
> Sent: Di., 19 Jan. 2016 23:04
> Subject: [vfs] FileSystemException: Could not determine if file ... is
> writeable with v2.1
> 
> Hi all,
> 
> I am working with a third party developed application.  In their new
> version, they have moved from vfs 2.0 to 2.1-snapshot.
> 
> Since making that change, we are having trouble making sftp connections.
>  We receive the following error:
> 
> org.apache.commons.vfs2.FileSystemException: Could not determine if file
> "sftp://username:***@some.site.com:/; is writeable.
> 
> Since I control that sftp site, I watched the logs and see that our app
> is able to log in, cwd, and get a directory listing.  We have the same
> issue when trying to drop to other sftp sites.  We do not have this
> issue when we used vfs 2.0.
> 
> Is anyone aware of any changes within vfs that could cause this change
> in behavior between 2.0 and 2.1-snapshot?
> 
> 
> Thanks,
> 
> Ryan
> 
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
> 
> 
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
> 

-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: [vfs] FileSystemException: Could not determine if file ... is writeable with v2.1

[Schalk Cronjé]

Disconnecting from some.site port 

Thanks,

Ryan



On Tue, Jan 19, 2016, at 06:10 PM, e...@zusammenkunft.net wrote:

Hello,

Do you have a full stack trace of that error? I dont think writeability
is checked by default on login.

Gruss
Bernd

--
http://bernd.eckenfels.net

-Original Message-
From: Ryan Pugatch <r...@lp0.org>
To: user@commons.apache.org
Sent: Di., 19 Jan. 2016 23:04
Subject: [vfs] FileSystemException: Could not determine if file ... is
writeable with v2.1

Hi all,

I am working with a third party developed application.  In their new
version, they have moved from vfs 2.0 to 2.1-snapshot.

Since making that change, we are having trouble making sftp connections.
  We receive the following error:

org.apache.commons.vfs2.FileSystemException: Could not determine if file
"sftp://username:***@some.site.com:/; is writeable.

Since I control that sftp site, I watched the logs and see that our app
is able to log in, cwd, and get a directory listing.  We have the same
issue when trying to drop to other sftp sites.  We do not have this
issue when we used vfs 2.0.

Is anyone aware of any changes within vfs that could cause this change
in behavior between 2.0 and 2.1-snapshot?


Thanks,

Ryan

-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org


-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org


-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org




--
Schalk W. Cronjé
Twitter / Ello / Toeter : @ysb33r


-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

[vfs] FileSystemException: Could not determine if file ... is writeable with v2.1

[Ryan Pugatch]

Hi all,

I am working with a third party developed application.  In their new
version, they have moved from vfs 2.0 to 2.1-snapshot.

Since making that change, we are having trouble making sftp connections.
 We receive the following error:

org.apache.commons.vfs2.FileSystemException: Could not determine if file
"sftp://username:***@some.site.com:/; is writeable.

Since I control that sftp site, I watched the logs and see that our app
is able to log in, cwd, and get a directory listing.  We have the same
issue when trying to drop to other sftp sites.  We do not have this
issue when we used vfs 2.0.

Is anyone aware of any changes within vfs that could cause this change
in behavior between 2.0 and 2.1-snapshot?


Thanks,

Ryan

-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: [vfs] FileSystemException: Could not determine if file ... is writeable with v2.1

[Ryan Pugatch]

> Do you have a full stack trace of that error? I dont think writeability
> is checked by default on login.
> 
> Gruss
> Bernd
> 
> -- 
> http://bernd.eckenfels.net
> 
> -Original Message-
> From: Ryan Pugatch <r...@lp0.org>
> To: user@commons.apache.org
> Sent: Di., 19 Jan. 2016 23:04
> Subject: [vfs] FileSystemException: Could not determine if file ... is
> writeable with v2.1
> 
> Hi all,
> 
> I am working with a third party developed application.  In their new
> version, they have moved from vfs 2.0 to 2.1-snapshot.
> 
> Since making that change, we are having trouble making sftp connections.
>  We receive the following error:
> 
> org.apache.commons.vfs2.FileSystemException: Could not determine if file
> "sftp://username:***@some.site.com:/; is writeable.
> 
> Since I control that sftp site, I watched the logs and see that our app
> is able to log in, cwd, and get a directory listing.  We have the same
> issue when trying to drop to other sftp sites.  We do not have this
> issue when we used vfs 2.0.
> 
> Is anyone aware of any changes within vfs that could cause this change
> in behavior between 2.0 and 2.1-snapshot?
> 
> 
> Thanks,
> 
> Ryan
> 
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
> 
> 
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
> 

-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: [vfs] FileSystemException: Could not determine if file ... is writeable with v2.1

[ecki]

Hello,

Do you have a full stack trace of that error? I dont think writeability is 
checked by default on login.

Gruss
Bernd

-- 
http://bernd.eckenfels.net

-Original Message-
From: Ryan Pugatch <r...@lp0.org>
To: user@commons.apache.org
Sent: Di., 19 Jan. 2016 23:04
Subject: [vfs] FileSystemException: Could not determine if file ... is 
writeable with v2.1

Hi all,

I am working with a third party developed application.  In their new
version, they have moved from vfs 2.0 to 2.1-snapshot.

Since making that change, we are having trouble making sftp connections.
 We receive the following error:

org.apache.commons.vfs2.FileSystemException: Could not determine if file
"sftp://username:***@some.site.com:/; is writeable.

Since I control that sftp site, I watched the logs and see that our app
is able to log in, cwd, and get a directory listing.  We have the same
issue when trying to drop to other sftp sites.  We do not have this
issue when we used vfs 2.0.

Is anyone aware of any changes within vfs that could cause this change
in behavior between 2.0 and 2.1-snapshot?


Thanks,

Ryan

-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org


-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

VFS - JSCH - Preferred Authentication - gssapi-with-mic

[Derek Visch]

We updated to jre8 from jre6 a while back, and had an issue with the
Kerberos Login and Kerberos Password prompt, basically we're providing the
password for an SFTP site, but we get a Kerberos Login prompt which causes
the program to wait for user input (Hitting enter manually twice allows the
program to run properly)

We are using commons-vfs2-2.0 and jsch .1.53

After some digging I found
http://stackoverflow.com/questions/10881981/sftp-connection-through-java-asking-for-weird-authentication
and
https://bz.apache.org/bugzilla/show_bug.cgi?id=53437

But I didn't find anything that talked about VFS2 at all so I thought I'd
at least post this here to help the next poor person who runs into this
problem, and also ask if this has already been fixed, or if maybe I"m just
doing something wrong.

Note that the default preferred authentication options for JSCH are
"gssapi-with-mic,publickey,keyboard-interactive,password"


local = VFS.getManager().toFileObject(new File(args.local_file))
FileSystemOptions opts = new FileSystemOptions();
SftpFileSystemConfigBuilder.getInstance().setPreferredAuthentications(opts,
"publickey,keyboard-interactive,password"); //Needed this in order to fix a
Kerberos Login / Password issue with the upgrade from jre6 to jre8
remote = VFS.getManager().resolveFile(buildFtpUrl(args), opts);

The code above works, what we had before was
local = VFS.getManager().toFileObject(new File(args.local_file))
remote = VFS.getManager().resolveFile(buildFtpUrl(args),  new
FileSystemOptions());

Is there something else I could do here to not have to override the default
authentication options, I'd think that if we provided a username and
password we would skip the Kerberos authentication piece.

Thanks
 - Derek

Re: VFS - JSCH - Preferred Authentication - gssapi-with-mic

[ecki]

Hm, I would not like to change the default jsch settings (if default filesystem 
options are specified) if not needed. Can you maybe ask this question the jsch 
folks whats the reason for that default and why it is not sensitive to 
user/password settings.

-- 
http://bernd.eckenfels.net

-Original Message-
From: Derek Visch <dvi...@leveldata.com>
To: user@commons.apache.org
Sent: Do., 10 Dez. 2015 14:30
Subject: VFS - JSCH - Preferred Authentication - gssapi-with-mic

We updated to jre8 from jre6 a while back, and had an issue with the
Kerberos Login and Kerberos Password prompt, basically we're providing the
password for an SFTP site, but we get a Kerberos Login prompt which causes
the program to wait for user input (Hitting enter manually twice allows the
program to run properly)

We are using commons-vfs2-2.0 and jsch .1.53

After some digging I found
http://stackoverflow.com/questions/10881981/sftp-connection-through-java-asking-for-weird-authentication
and
https://bz.apache.org/bugzilla/show_bug.cgi?id=53437

But I didn't find anything that talked about VFS2 at all so I thought I'd
at least post this here to help the next poor person who runs into this
problem, and also ask if this has already been fixed, or if maybe I"m just
doing something wrong.

Note that the default preferred authentication options for JSCH are
"gssapi-with-mic,publickey,keyboard-interactive,password"


local = VFS.getManager().toFileObject(new File(args.local_file))
FileSystemOptions opts = new FileSystemOptions();
SftpFileSystemConfigBuilder.getInstance().setPreferredAuthentications(opts,
"publickey,keyboard-interactive,password"); //Needed this in order to fix a
Kerberos Login / Password issue with the upgrade from jre6 to jre8
remote = VFS.getManager().resolveFile(buildFtpUrl(args), opts);

The code above works, what we had before was
local = VFS.getManager().toFileObject(new File(args.local_file))
remote = VFS.getManager().resolveFile(buildFtpUrl(args),  new
FileSystemOptions());

Is there something else I could do here to not have to override the default
authentication options, I'd think that if we provided a username and
password we would skip the Kerberos authentication piece.

Thanks
 - Derek

-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: VFS - JSCH - Preferred Authentication - gssapi-with-mic

[Schalk Cronjé]

YEah, that one is a pain. We got bitten by it in the past as well.

Setting System.in = null usually solves the problem, but  you might need 
need stdin for other purposes.




On 10/12/2015 15:30, Derek Visch wrote:

We updated to jre8 from jre6 a while back, and had an issue with the
Kerberos Login and Kerberos Password prompt, basically we're providing the
password for an SFTP site, but we get a Kerberos Login prompt which causes
the program to wait for user input (Hitting enter manually twice allows the
program to run properly)

We are using commons-vfs2-2.0 and jsch .1.53

After some digging I found
http://stackoverflow.com/questions/10881981/sftp-connection-through-java-asking-for-weird-authentication
and
https://bz.apache.org/bugzilla/show_bug.cgi?id=53437

But I didn't find anything that talked about VFS2 at all so I thought I'd
at least post this here to help the next poor person who runs into this
problem, and also ask if this has already been fixed, or if maybe I"m just
doing something wrong.

Note that the default preferred authentication options for JSCH are
"gssapi-with-mic,publickey,keyboard-interactive,password"


local = VFS.getManager().toFileObject(new File(args.local_file))
FileSystemOptions opts = new FileSystemOptions();
SftpFileSystemConfigBuilder.getInstance().setPreferredAuthentications(opts,
"publickey,keyboard-interactive,password"); //Needed this in order to fix a
Kerberos Login / Password issue with the upgrade from jre6 to jre8
remote = VFS.getManager().resolveFile(buildFtpUrl(args), opts);

The code above works, what we had before was
local = VFS.getManager().toFileObject(new File(args.local_file))
remote = VFS.getManager().resolveFile(buildFtpUrl(args),  new
FileSystemOptions());

Is there something else I could do here to not have to override the default
authentication options, I'd think that if we provided a username and
password we would skip the Kerberos authentication piece.

Thanks
  - Derek




--
Schalk W. Cronjé
Twitter / Ello / Toeter : @ysb33r


-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: [vfs] New Properties for FtpFileSystemConfigBuilder

[ecki]

Hello,

Yes it would be good if you can open a Jira bug. You can then either attach 
your patch as a file attachment or add an URL to the GitHub pull request.

I dont think there will be any point release like 2.0.1 but the next target 
version is 2.1 (based on the current trunk). This is supposed to be more or 
less drop-in compatible (unfortunatelly there arenquite a few changes in the 
long time since the last release so I expect some problems.)

If you use VFS2 somewhere already it would be very helpfull if you actually try 
to replace it with 2.1-SNAPSHOT and report all problems you encountered with 
this step.

I am fine with both variants, a string range is less API clutter but more 
complicated parsing, a typed min/max property is most likely much simpler to 
implement.

Gruss
Bernd

-- 
http://bernd.eckenfels.net

-Original Message-
From: Roger Membreno <roger.membr...@celigo.com>
To: Bernd Eckenfels <e...@zusammenkunft.net>
Cc: user@commons.apache.org, d...@commons.apache.org
Sent: Mi., 09 Dez. 2015 23:02
Subject: Re: [vfs] New Properties for FtpFileSystemConfigBuilder

Hi Bernd,

I wanted to touch base and ask what are my next steps--should I enter a
feature request on the Commons VFS JIRA board?  Also, my app is using
Commons VFS 2.0, so I was hoping to make the fix there and port it to 2.1.
Will there be any more releases in the 2.0 branch?

On Mon, Dec 7, 2015 at 2:16 PM, Roger Membreno <roger.membr...@celigo.com>
wrote:

> Hi Bernd,
>
> For now I was using a max and min property so I could pass int values
> directly from my adaptor layer to VFS.  What do you recommend?  A string
> range's only issue that I can see is parsing, but something simple could
> work.
>
> On Mon, Dec 7, 2015 at 1:54 PM, Bernd Eckenfels <e...@zusammenkunft.net>
> wrote:
>
>> Hello Roger,
>>
>> sounds useful to me. Do you plan to parse a string range ("1-100") or
>> define a min and max property?
>>
>> Gruss
>> Bernd
>>
>>  Am Mon, 7 Dec 2015 13:26:35 -0800
>> schrieb Roger Membreno <roger.membr...@celigo.com>:
>>
>> > Hello Apache Community, how are you doing?
>> >
>> > We use Commons VFS in our FTP connection projects, and for a recent
>> > project we only able to connect to our FTP site when using Passive
>> > mode.  If we used Active mode we could login to the FTP site but all
>> > files in the directory did not exist and could not be accessed.
>> >
>> > Since our server is behind a firewall with NAT translation we
>> > determined that the data connection could not be established even if
>> > we opened up some ports on the firewall.  We were able to connect to
>> > the FTP site using a stanadalone FTPClient by setting the following
>> > properties to match our NAT security settings:
>> > setReportActiveExternalIPAddress()
>> > client.setActivePortRange()
>> >
>> > With these properties set the PORT command issued by our client to
>> > the FTP site will create a valid data connection.  What I'd like to
>> > do is submit a change via GitHub that does the following:
>> > 1. Add "reportActiveExternalIPAddress" and "activePortRange"
>> > properties to the class
>> > org.apache.commons.vfs2.provider.ftp.FtpFileSystemConfigBuilder 2.
>> > Ehance createConnection in
>> > org.apache.commons.vfs2.provider.ftp.FtpClientFactory to read these
>> > new FtpFileSystemConfigBuilder properties from the config instance
>> > and set them on the FTPClient.
>> >
>> > Let me know if you have any questions.  If you think this is a good
>> > change I'll make a new issue in JIRA for this enhancement.  I also
>> > think that these changes could help resolve VFS-201 (
>> > https://issues.apache.org/jira/browse/VFS-201)
>> >
>>
>>
>
>
> --
> -Thanks,
> Roger
>
>
> *Roger Membreno *| Senior Software Engineer
> Celigo, Inc
>
> O 650.579.0210 x101
> F 650.240.0143
> E roger.membr...@celigo.com
> W www.celigo.comFollow Us <http://celigo.com/blog/>
> <http://www.linkedin.com/company/celigo-inc>
> <https://plus.google.com/101644332205934540197/posts>
> <https://twitter.com/celigoinc>  <http://www.youtube.com/user/CeligoInc>
>
>
>
>
>
>


-- 
-Thanks,
Roger


*Roger Membreno *| Senior Software Engineer
Celigo, Inc

O 650.579.0210 x101
F 650.240.0143
E roger.membr...@celigo.com
W www.celigo.comFollow Us <http://celigo.com/blog/>
<http://www.linkedin.com/company/celigo-inc>
<https://plus.google.com/101644332205934540197/posts>
<https://twitter.com/celigoinc>  <http://www.youtube.com/user/CeligoInc>

-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

[vfs] When will be the next release 2.1?

[Spico Florin]

Hi!
  I would like to know when will be the next release.

I would like to use the watching folders changes feature provided by vfs,
in an OSGI context. With the current version is hard to achieve this.

I look forward for your answers.
  Regards,
 Florin

[vfs] New Properties for FtpFileSystemConfigBuilder

[Roger Membreno]

Hello Apache Community, how are you doing?

We use Commons VFS in our FTP connection projects, and for a recent project
we only able to connect to our FTP site when using Passive mode.  If we
used Active mode we could login to the FTP site but all files in the
directory did not exist and could not be accessed.

Since our server is behind a firewall with NAT translation we determined
that the data connection could not be established even if we opened up some
ports on the firewall.  We were able to connect to the FTP site using a
stanadalone FTPClient by setting the following properties to match our NAT
security settings:
setReportActiveExternalIPAddress()
client.setActivePortRange()

With these properties set the PORT command issued by our client to the FTP
site will create a valid data connection.  What I'd like to do is submit a
change via GitHub that does the following:
1. Add "reportActiveExternalIPAddress" and "activePortRange" properties to
the class org.apache.commons.vfs2.provider.ftp.FtpFileSystemConfigBuilder
2. Ehance createConnection in
org.apache.commons.vfs2.provider.ftp.FtpClientFactory to read these new
FtpFileSystemConfigBuilder properties from the config instance and set them
on the FTPClient.

Let me know if you have any questions.  If you think this is a good change
I'll make a new issue in JIRA for this enhancement.  I also think that
these changes could help resolve VFS-201 (
https://issues.apache.org/jira/browse/VFS-201)

-- 
-Thanks,
Roger


*Roger Membreno *| Senior Software Engineer
Celigo, Inc

O 650.579.0210 x101
F 650.240.0143
E roger.membr...@celigo.com
W www.celigo.comFollow Us <http://celigo.com/blog/>
<http://www.linkedin.com/company/celigo-inc>
<https://plus.google.com/101644332205934540197/posts>
<https://twitter.com/celigoinc>  <http://www.youtube.com/user/CeligoInc>

Re: [vfs] New Properties for FtpFileSystemConfigBuilder

[Bernd Eckenfels]

Hello Roger,

sounds useful to me. Do you plan to parse a string range ("1-100") or
define a min and max property?

Gruss
Bernd

 Am Mon, 7 Dec 2015 13:26:35 -0800
schrieb Roger Membreno <roger.membr...@celigo.com>:

> Hello Apache Community, how are you doing?
> 
> We use Commons VFS in our FTP connection projects, and for a recent
> project we only able to connect to our FTP site when using Passive
> mode.  If we used Active mode we could login to the FTP site but all
> files in the directory did not exist and could not be accessed.
> 
> Since our server is behind a firewall with NAT translation we
> determined that the data connection could not be established even if
> we opened up some ports on the firewall.  We were able to connect to
> the FTP site using a stanadalone FTPClient by setting the following
> properties to match our NAT security settings:
> setReportActiveExternalIPAddress()
> client.setActivePortRange()
> 
> With these properties set the PORT command issued by our client to
> the FTP site will create a valid data connection.  What I'd like to
> do is submit a change via GitHub that does the following:
> 1. Add "reportActiveExternalIPAddress" and "activePortRange"
> properties to the class
> org.apache.commons.vfs2.provider.ftp.FtpFileSystemConfigBuilder 2.
> Ehance createConnection in
> org.apache.commons.vfs2.provider.ftp.FtpClientFactory to read these
> new FtpFileSystemConfigBuilder properties from the config instance
> and set them on the FTPClient.
> 
> Let me know if you have any questions.  If you think this is a good
> change I'll make a new issue in JIRA for this enhancement.  I also
> think that these changes could help resolve VFS-201 (
> https://issues.apache.org/jira/browse/VFS-201)
> 


-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: [vfs] New Properties for FtpFileSystemConfigBuilder

[Roger Membreno]

Hi Bernd,

For now I was using a max and min property so I could pass int values
directly from my adaptor layer to VFS.  What do you recommend?  A string
range's only issue that I can see is parsing, but something simple could
work.

On Mon, Dec 7, 2015 at 1:54 PM, Bernd Eckenfels <e...@zusammenkunft.net>
wrote:

> Hello Roger,
>
> sounds useful to me. Do you plan to parse a string range ("1-100") or
> define a min and max property?
>
> Gruss
> Bernd
>
>  Am Mon, 7 Dec 2015 13:26:35 -0800
> schrieb Roger Membreno <roger.membr...@celigo.com>:
>
> > Hello Apache Community, how are you doing?
> >
> > We use Commons VFS in our FTP connection projects, and for a recent
> > project we only able to connect to our FTP site when using Passive
> > mode.  If we used Active mode we could login to the FTP site but all
> > files in the directory did not exist and could not be accessed.
> >
> > Since our server is behind a firewall with NAT translation we
> > determined that the data connection could not be established even if
> > we opened up some ports on the firewall.  We were able to connect to
> > the FTP site using a stanadalone FTPClient by setting the following
> > properties to match our NAT security settings:
> > setReportActiveExternalIPAddress()
> > client.setActivePortRange()
> >
> > With these properties set the PORT command issued by our client to
> > the FTP site will create a valid data connection.  What I'd like to
> > do is submit a change via GitHub that does the following:
> > 1. Add "reportActiveExternalIPAddress" and "activePortRange"
> > properties to the class
> > org.apache.commons.vfs2.provider.ftp.FtpFileSystemConfigBuilder 2.
> > Ehance createConnection in
> > org.apache.commons.vfs2.provider.ftp.FtpClientFactory to read these
> > new FtpFileSystemConfigBuilder properties from the config instance
> > and set them on the FTPClient.
> >
> > Let me know if you have any questions.  If you think this is a good
> > change I'll make a new issue in JIRA for this enhancement.  I also
> > think that these changes could help resolve VFS-201 (
> > https://issues.apache.org/jira/browse/VFS-201)
> >
>
>


-- 
-Thanks,
Roger


*Roger Membreno *| Senior Software Engineer
Celigo, Inc

O 650.579.0210 x101
F 650.240.0143
E roger.membr...@celigo.com
W www.celigo.comFollow Us <http://celigo.com/blog/>
<http://www.linkedin.com/company/celigo-inc>
<https://plus.google.com/101644332205934540197/posts>
<https://twitter.com/celigoinc>  <http://www.youtube.com/user/CeligoInc>

Re: [vfs] HDFS provider

[Gary Gregory]

HDFS support was added after 2.0. You'll need to checkout the sources and
build a 2.1 snapshot.

Gary

On Mon, Jun 1, 2015 at 6:56 AM, Sergio Hernández srg46...@gmail.com wrote:

 Hi,

 I'm trying to use VFSJFileChooser to browse the Hadoop Distributed
 Filesystem of my cluster.

 According to documentation, HDFS is supported in read-only mode but when i
 download the apache-commons-vfs library hdfs provider is not included.

 How I can solve this?

 Thanks in advance

 Sergio




-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
http://www.manning.com/bauer3/
JUnit in Action, Second Edition http://www.manning.com/tahchiev/
Spring Batch in Action http://www.manning.com/templier/
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

[vfs] HDFS provider

[Sergio Hernández]

Hi,

I'm trying to use VFSJFileChooser to browse the Hadoop Distributed
Filesystem of my cluster.

According to documentation, HDFS is supported in read-only mode but when i
download the apache-commons-vfs library hdfs provider is not included.

How I can solve this?

Thanks in advance

Sergio

Re: [VFS] Could the HDFS connector work with MapR systems?

[Ted Dunning]

The NFS mount trick allows all of the files to appear via the local://*
file system.

Otherwise, it is true that the wire protocol for MapR FS is different from
HDFS.  In fact, the wire protocol for different versions of HDFS are
different as well.

But what is standard is how different implementations of a Hadoop
compatible file system are plugged into the file space.  That should work
for any reasonable application if you have the right jars in your search
path.

One possibility where this would break would be if the client code assumes,
for instance, that all file paths must have a server address.  Otherwise,
well-behaved HDFS client applications should work.  The null host name
exception sounds like there is a format exception going on.

Can I see the some test code and stack traces somewhere?






On Tue, May 26, 2015 at 4:32 PM, Roger Whitcomb roger.whitc...@actian.com
wrote:

 So, I'm pretty sure (now) that it DOESN'T work.  There are comments here:
 http://answers.mapr.com/questions/9224/apache-hadoop-client-connecting-to-namenode.html
 and here:
 http://doc.mapr.com/display/MapR/Accessing+MapR-FS+in+Java+Applications
 plus the connector here:  https://github.com/pentaho/pentaho-hdfs-vfs
 that all point to special MapR code being needed, and the standard HDFS
 client protocols not working.  Plus all my testing seemed to confirm this.

 We have figured out a workaround for our configuration, though (we're
 basically requiring an NFS mount of the MapR file system, so we can just
 browse the MapR files as native).

 Thanks,
 ~Roger

 -Original Message-
 From: Gary Gregory [mailto:garydgreg...@gmail.com]
 Sent: Tuesday, May 26, 2015 3:48 PM
 To: Commons Users List
 Subject: RE: [VFS] Could the HDFS connector work with MapR systems?

 I've not seen VFS used in this configuration before. You could try
 updating to the current HDFS jar files.
 Gary

  Original message 
 From: Roger Whitcomb roger.whitc...@actian.com
 Date: 05/26/2015  10:39  (GMT-08:00)
 To: Commons Users List user@commons.apache.org
 Subject: [VFS] Could the HDFS connector work with MapR systems?

 Hi all,
 I'm using Commons VFS 2.1 along with the HDFS connector
 and everything is working brilliantly ... until, that is, trying to access
 HDFS on a MapR system.  Then I get things like null host name exceptions
 and the like.  So, anyone have any idea whether the HDFS connector even
 COULD work against MapR?  And if not, anyone tried to build a MapR
 connector to Commons VFS 2.1?

 Thanks in advance,
 ~Roger Whitcomb

RE: [VFS] Could the HDFS connector work with MapR systems?

[Gary Gregory]

I've not seen VFS used in this configuration before. You could try updating to 
the current HDFS jar files.
Gary 

 Original message 
From: Roger Whitcomb roger.whitc...@actian.com 
Date: 05/26/2015  10:39  (GMT-08:00) 
To: Commons Users List user@commons.apache.org 
Subject: [VFS] Could the HDFS connector work with MapR systems? 

Hi all,
    I'm using Commons VFS 2.1 along with the HDFS connector and 
everything is working brilliantly ... until, that is, trying to access HDFS on 
a MapR system.  Then I get things like null host name exceptions and the like.  
So, anyone have any idea whether the HDFS connector even COULD work against 
MapR?  And if not, anyone tried to build a MapR connector to Commons VFS 2.1?

Thanks in advance,
~Roger Whitcomb

RE: [VFS] Could the HDFS connector work with MapR systems?

[Roger Whitcomb]

So, I'm pretty sure (now) that it DOESN'T work.  There are comments here:  
http://answers.mapr.com/questions/9224/apache-hadoop-client-connecting-to-namenode.html
 and here:  
http://doc.mapr.com/display/MapR/Accessing+MapR-FS+in+Java+Applications plus 
the connector here:  https://github.com/pentaho/pentaho-hdfs-vfs 
that all point to special MapR code being needed, and the standard HDFS client 
protocols not working.  Plus all my testing seemed to confirm this.

We have figured out a workaround for our configuration, though (we're basically 
requiring an NFS mount of the MapR file system, so we can just browse the MapR 
files as native).

Thanks,
~Roger

-Original Message-
From: Gary Gregory [mailto:garydgreg...@gmail.com] 
Sent: Tuesday, May 26, 2015 3:48 PM
To: Commons Users List
Subject: RE: [VFS] Could the HDFS connector work with MapR systems?

I've not seen VFS used in this configuration before. You could try updating to 
the current HDFS jar files.
Gary 

 Original message 
From: Roger Whitcomb roger.whitc...@actian.com 
Date: 05/26/2015  10:39  (GMT-08:00) 
To: Commons Users List user@commons.apache.org 
Subject: [VFS] Could the HDFS connector work with MapR systems? 

Hi all,
    I'm using Commons VFS 2.1 along with the HDFS connector and 
everything is working brilliantly ... until, that is, trying to access HDFS on 
a MapR system.  Then I get things like null host name exceptions and the like.  
So, anyone have any idea whether the HDFS connector even COULD work against 
MapR?  And if not, anyone tried to build a MapR connector to Commons VFS 2.1?

Thanks in advance,
~Roger Whitcomb

[VFS] Could the HDFS connector work with MapR systems?

[Roger Whitcomb]

Hi all,
I'm using Commons VFS 2.1 along with the HDFS connector and 
everything is working brilliantly ... until, that is, trying to access HDFS on 
a MapR system.  Then I get things like null host name exceptions and the like.  
So, anyone have any idea whether the HDFS connector even COULD work against 
MapR?  And if not, anyone tried to build a MapR connector to Commons VFS 2.1?

Thanks in advance,
~Roger Whitcomb

Re: [vfs] vsf2.2.0: non-ascii chars in file name are not handled by createFolder()

[Geoff Watters]

Albert
Thanks so much for your suggestion. In my environment, I tried to make 
the changes you suggested, however the


   *org.apache.commons.net.ftp.FtpClient*

class in my environment does not support *setAutodetectUTF8(boolean)*.

Instead, I changed my version of *FtpClientFactory *so that 
*setControlEncoding()* is invoked before the connection is made, see 
green block below.


   76   FTPFileEntryParserFactory myFactory =
   77
   
FtpFileSystemConfigBuilder.getInstance().getEntryParserFactory(fileSystemOptions);
   78if (myFactory != null)
   79{
   80client.setParserFactory(myFactory);
   81}
   82
   83try
   84{
   85String controlEncoding =
   
FtpFileSystemConfigBuilder.getInstance().getControlEncoding(fileSystemOptions);
   86if (controlEncoding != null)
   87{
   88 client.setControlEncoding(controlEncoding);
   89}
   90client.connect(hostname, port);
   91
   92int reply = client.getReplyCode();

After building *commons-vfs2-2.0.jar*, the above change allowed my 
testcase to pass and I was able to see the correct file names on my 
target system.


I note that the javadoc for FtpClient.setAutodetectUTF8() 
https://commons.apache.org/proper/commons-net/apidocs/org/apache/commons/net/ftp/FTPClient.html#setAutodetectUTF8%28boolean%29 
does mention that it should be /invoked before a connection is 
established/. Perhaps the same is true 
fororg.apache.commons.net.ftp.Ftp.setControlEncoding() 
https://commons.apache.org/proper/commons-net/apidocs/org/apache/commons/net/ftp/FTP.html#setControlEncoding%28java.lang.String%29.


Thanks
Geoff

On 09/04/2015 21:05, Albert Briner wrote:

Geoff,

Nicely put together test case. I was able to reproduce your outcome closely 
(different FTP server).

What made it work for me was the following change to the VFS source:

Index: FtpClientFactory.java
===
--- FtpClientFactory.java   (revision 1535203)
+++ FtpClientFactory.java   (working copy)
@@ -150,7 +150,11 @@
  {
  client.setControlEncoding(controlEncoding);
  }
-
+else
+{
+client.setAutodetectUTF8(true);
+}
+
  client.connect(hostname, port);
  
  final int reply = client.getReplyCode();



… and then not specify any encoding in the test code. I don't know whether this 
is the right thing to do in general, but it made all your test cases succeed 
for me.

Albert


On 16/03/2015 11:07, Geoff Watters wrote:

All

I am using*commons-vfs2-2.0.jar* and am running into problems when
file names contain non-ascii characters. According to
https://issues.apache.org/jira/browse/VFS-305 this has been
fixed/shipped in 2.0. In my environment I am able to create such file
names when using ftp on the command-line (Red Hat Enterprise Linux
Server release 5.8 (Tikanga)).

When I execute the following sample code, I get the output shown below.

public class FtpTest {
 public static void main(String[] args) throws FileSystemException
 {
 String host=hhh;
 String user = uuu;
 String password = ppp;
 String destDir = /tmp;
 FileSystemOptions opts = new FileSystemOptions();
FtpFileSystemConfigBuilder.getInstance().setControlEncoding(opts,
UTF-8);

 DefaultFileSystemManager manager = new
DefaultFileSystemManager();
 manager.addProvider(ftp, new FtpFileProvider());
 manager.init();

 String root=ftp://+user+:+password+@+host+destDir;
 // Specify a number of directories that should be created
under destDir
 String[] lRoots = new String[4];
 lRoots[0]= root+/ftpDebug;
 lRoots[1]= root+/ftp\u7684Debug;  // insert a non-ascii char
 lRoots[2]= root+/ftp\u7685Debug;  // insert a different
non-ascii char
 lRoots[3]= root+/ftp\u7684Debug;  // insert the same
non-ascii char

 // Verify the ControlEncoding
 System.out.println(ControlEncoding is
+FtpFileSystemConfigBuilder.getInstance().getControlEncoding(opts));

 int dirCount=0;
 for (String lRoot: lRoots) {
 System.out.println(dirCount+) Process directory
[+lRoot+]);
 FileObject newDir = manager.resolveFile(lRoot, opts);
 if (!newDir.exists()) {
 try {
 System.out.println(dirCount+) +lRoot+ ::Dir
Does Not Exist so Create It );
 newDir.createFolder();
 if (newDir.exists())
 System.out.println(dirCount+) +lRoot+
::Creation Successful );
 else
 System.out.println(dirCount+) +lRoot+
::Creation Fails

[vfs] vsf2.2.0: non-ascii chars in file name are not handled by createFolder()

[Albert Briner]

Geoff,

Nicely put together test case. I was able to reproduce your outcome closely 
(different FTP server).

What made it work for me was the following change to the VFS source:

Index: FtpClientFactory.java
===
--- FtpClientFactory.java   (revision 1535203)
+++ FtpClientFactory.java   (working copy)
@@ -150,7 +150,11 @@
 {
 client.setControlEncoding(controlEncoding);
 }
-
+else
+{
+client.setAutodetectUTF8(true);
+}
+
 client.connect(hostname, port);
 
 final int reply = client.getReplyCode();


… and then not specify any encoding in the test code. I don't know whether this 
is the right thing to do in general, but it made all your test cases succeed 
for me.

Albert


On 16/03/2015 11:07, Geoff Watters wrote:
 All

 I am using*commons-vfs2-2.0.jar* and am running into problems when 
 file names contain non-ascii characters. According to 
 https://issues.apache.org/jira/browse/VFS-305 this has been 
 fixed/shipped in 2.0. In my environment I am able to create such file 
 names when using ftp on the command-line (Red Hat Enterprise Linux 
 Server release 5.8 (Tikanga)).

 When I execute the following sample code, I get the output shown below.

 public class FtpTest {
 public static void main(String[] args) throws FileSystemException
 {
 String host=hhh;
 String user = uuu;
 String password = ppp;
 String destDir = /tmp;
 FileSystemOptions opts = new FileSystemOptions();
 FtpFileSystemConfigBuilder.getInstance().setControlEncoding(opts, 
 UTF-8);

 DefaultFileSystemManager manager = new 
 DefaultFileSystemManager();
 manager.addProvider(ftp, new FtpFileProvider());
 manager.init();

 String root=ftp://+user+:+password+@+host+destDir;
 // Specify a number of directories that should be created 
 under destDir
 String[] lRoots = new String[4];
 lRoots[0]= root+/ftpDebug;
 lRoots[1]= root+/ftp\u7684Debug;  // insert a non-ascii char
 lRoots[2]= root+/ftp\u7685Debug;  // insert a different 
 non-ascii char
 lRoots[3]= root+/ftp\u7684Debug;  // insert the same 
 non-ascii char

 // Verify the ControlEncoding
 System.out.println(ControlEncoding is 
 +FtpFileSystemConfigBuilder.getInstance().getControlEncoding(opts));

 int dirCount=0;
 for (String lRoot: lRoots) {
 System.out.println(dirCount+) Process directory 
 [+lRoot+]);
 FileObject newDir = manager.resolveFile(lRoot, opts);
 if (!newDir.exists()) {
 try {
 System.out.println(dirCount+) +lRoot+ ::Dir 
 Does Not Exist so Create It );
 newDir.createFolder();
 if (newDir.exists())
 System.out.println(dirCount+) +lRoot+ 
 ::Creation Successful );
 else
 System.out.println(dirCount+) +lRoot+ 
 ::Creation Fails );
 }
 catch (Exception ex) {
 System.out.println(dirCount+) +lRoot +  raised 
 +ex);
 }
 }
 else
 System.out.println(dirCount+) +lRoot+ ::Dir Already 
 Exists );
 dirCount++;
 }
 }
 }

 The output from running the above is:-

 ControlEncoding is UTF-8
 0) Process directory [ftp://uuu:ppp@hhh/tmp/ftpDebug]
 0) ftp://uuu:ppp@hhh/tmp/ftpDebug ::Dir Does Not Exist so Create It
 0) ftp://uuu:ppp@hhh/tmp/ftpDebug ::Creation Successful
 1) Process directory [ftp://uuu:ppp@hhh/tmp/ftpªDebug]
 1) ftp://uuu:ppp@hhh/tmp/ftpªDebug ::Dir Does Not Exist so Create It
 1) ftp://uuu:ppp@hhh/tmp/ftpªDebug ::Creation Successful
 2) Process directory [ftp://uuu:ppp@hhh/tmp/ftp%Gçš…%@Debug]
 2) ftp://uuu:ppp@hhh/tmp/ftp%Gçš…%@Debug ::Dir Does Not Exist so 
 Create It
 2) ftp://uuu:ppp@hhh/tmp/ftp%Gçš…%@Debug raised 
 org.apache.commons.vfs2.FileSystemException: Could not create 
 folder ftp://uuu:***@hhh/tmp/ftp%Gçš…%@Debug.
 3) Process directory [ftp://uuu:ppp@hhh/tmp/ftpªDebug]
 3) ftp://uuu:ppp@hhh/tmp/ftpªDebug ::Dir Does Not Exist so Create It
 3) ftp://uuu:ppp@hhh/tmp/ftpªDebug raised 
 org.apache.commons.vfs2.FileSystemException: Could not create folder 
 ftp://uuu:***@hhh/tmp/ftpªDebug;.

 After step 1) I see a directory called*/tmp/ftp?Debug*.
 I think this is causing the subsequent creation problem in step 2) and 
 step 3).
 When a directory such as *ftp\u7684Debug* does exist, then 
 *exists*() returns the correct result of true, but *createFolder*() 
 creates a directory with name *ftp?Debug*.

 Thanks in advance
 Geoff






-
To unsubscribe, e-mail

Re: [vfs] FileSystemException: Could not load VFS configuration

[Helge Waastad]

Hi,
and thanks for answering.

I figured it out.

It was a classloader issue.
so by setting classloader on STandardFilesystemMAnager I got it working.

br hw


on., 25.03.2015 kl. 22.17 +0100, skrev Bernd Eckenfels:

 Am Wed, 25 Mar 2015 17:48:03 +0100
 schrieb Helge Waastad he...@waastad.org:
 
  If I bundle the commons-vfs2 (2.1-SNAPSHOT/2.0) with the rar I get
  then exception:
  FileSystemException: Could not load VFS configuration from
  jar:file:/home/helge/Skrivebord/jca-parent/acme-war/target/apache-tomee/apps/acme-ra-1.0-SNAPSHOT/commons-vfs2-2.1-SNAPSHOT.jar!/org/apache/commons/vfs2/impl/providers.xml
 
 Is this JAR and with the resource existing or not?
 
  If I add vfs2-commons to tomee/lib and provided in my rar, then its
  working OK.
  
  Is this how it's supposed to work?
 
 The default configuration mechanism resolves providers.xml via the
 classloader of the StandardFileSystemManager class. It retrieves the
 URL for that resource and loads it.
 
 You might want to overwrite the init() method or somple create the
 DefaultFileSystemManager and configure it yourself.
 
 (I am not entirely sure why it does not work in your scenario).
 
 Gruss
 Bernd
 
 -
 To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
 For additional commands, e-mail: user-h...@commons.apache.org
 

Resend: [vfs] vsf2.2.0: non-ascii chars in file name are not handled by createFolder()

[Geoff Watters]

Is anyone else able to use non-ascii chars in filenames when using VFS 
2.2.0?


As indicated below, the created file has a ? in the resultant name 
rather than the original non-ascii character.


Thanks


On 16/03/2015 11:07, Geoff Watters wrote:

All

I am using*commons-vfs2-2.0.jar* and am running into problems when 
file names contain non-ascii characters. According to 
https://issues.apache.org/jira/browse/VFS-305 this has been 
fixed/shipped in 2.0. In my environment I am able to create such file 
names when using ftp on the command-line (Red Hat Enterprise Linux 
Server release 5.8 (Tikanga)).


When I execute the following sample code, I get the output shown below.

public class FtpTest {
public static void main(String[] args) throws FileSystemException
{
String host=hhh;
String user = uuu;
String password = ppp;
String destDir = /tmp;
FileSystemOptions opts = new FileSystemOptions();
FtpFileSystemConfigBuilder.getInstance().setControlEncoding(opts, 
UTF-8);


DefaultFileSystemManager manager = new 
DefaultFileSystemManager();

manager.addProvider(ftp, new FtpFileProvider());
manager.init();

String root=ftp://+user+:+password+@+host+destDir;
// Specify a number of directories that should be created 
under destDir

String[] lRoots = new String[4];
lRoots[0]= root+/ftpDebug;
lRoots[1]= root+/ftp\u7684Debug;  // insert a non-ascii char
lRoots[2]= root+/ftp\u7685Debug;  // insert a different 
non-ascii char
lRoots[3]= root+/ftp\u7684Debug;  // insert the same 
non-ascii char


// Verify the ControlEncoding
System.out.println(ControlEncoding is 
+FtpFileSystemConfigBuilder.getInstance().getControlEncoding(opts));


int dirCount=0;
for (String lRoot: lRoots) {
System.out.println(dirCount+) Process directory 
[+lRoot+]);

FileObject newDir = manager.resolveFile(lRoot, opts);
if (!newDir.exists()) {
try {
System.out.println(dirCount+) +lRoot+ ::Dir 
Does Not Exist so Create It );

newDir.createFolder();
if (newDir.exists())
System.out.println(dirCount+) +lRoot+ 
::Creation Successful );

else
System.out.println(dirCount+) +lRoot+ 
::Creation Fails );

}
catch (Exception ex) {
System.out.println(dirCount+) +lRoot +  raised 
+ex);

}
}
else
System.out.println(dirCount+) +lRoot+ ::Dir Already 
Exists );

dirCount++;
}
}
}

The output from running the above is:-

ControlEncoding is UTF-8
0) Process directory [ftp://uuu:ppp@hhh/tmp/ftpDebug]
0) ftp://uuu:ppp@hhh/tmp/ftpDebug ::Dir Does Not Exist so Create It
0) ftp://uuu:ppp@hhh/tmp/ftpDebug ::Creation Successful
1) Process directory [ftp://uuu:ppp@hhh/tmp/ftpªDebug]
1) ftp://uuu:ppp@hhh/tmp/ftpªDebug ::Dir Does Not Exist so Create It
1) ftp://uuu:ppp@hhh/tmp/ftpªDebug ::Creation Successful
2) Process directory [ftp://uuu:ppp@hhh/tmp/ftp%Gçš…%@Debug]
2) ftp://uuu:ppp@hhh/tmp/ftp%Gçš…%@Debug ::Dir Does Not Exist so 
Create It
2) ftp://uuu:ppp@hhh/tmp/ftp%Gçš…%@Debug raised 
org.apache.commons.vfs2.FileSystemException: Could not create 
folder ftp://uuu:***@hhh/tmp/ftp%Gçš…%@Debug.

3) Process directory [ftp://uuu:ppp@hhh/tmp/ftpªDebug]
3) ftp://uuu:ppp@hhh/tmp/ftpªDebug ::Dir Does Not Exist so Create It
3) ftp://uuu:ppp@hhh/tmp/ftpªDebug raised 
org.apache.commons.vfs2.FileSystemException: Could not create folder 
ftp://uuu:***@hhh/tmp/ftpªDebug;.


After step 1) I see a directory called*/tmp/ftp?Debug*.
I think this is causing the subsequent creation problem in step 2) and 
step 3).
When a directory such as *ftp\u7684Debug* does exist, then 
*exists*() returns the correct result of true, but *createFolder*() 
creates a directory with name *ftp?Debug*.


Thanks in advance
Geoff






-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: [vfs] announcing an Azure Blob Storage Provider

[Bernd Eckenfels]

Am Thu, 26 Mar 2015 11:26:26 +0100
schrieb Benedikt Ritter brit...@apache.org:

 We could add a section with 3rd party providers to our website...

There is a related projects in the Wiki:

https://wiki.apache.org/commons/VFS

I have added vfs-azure.

Gruss
Bernd

-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

[vfs] FileSystemException: Could not load VFS configuration

[Helge Waastad]

Hi,
I'm developing a VFS Resource Adapter and testing it out on TomEE
(1.7.1)

If I bundle the commons-vfs2 (2.1-SNAPSHOT/2.0) with the rar I get then
exception:
FileSystemException: Could not load VFS configuration from
jar:file:/home/helge/Skrivebord/jca-parent/acme-war/target/apache-tomee/apps/acme-ra-1.0-SNAPSHOT/commons-vfs2-2.1-SNAPSHOT.jar!/org/apache/commons/vfs2/impl/providers.xml

If I add vfs2-commons to tomee/lib and provided in my rar, then its
working OK.

Is this how it's supposed to work?

PS, the rar has dependencies to a jar having adapter/specs/dependencies
etc.

br hw

Re: [vfs] FileSystemException: Could not load VFS configuration

[Bernd Eckenfels]

Am Wed, 25 Mar 2015 17:48:03 +0100
schrieb Helge Waastad he...@waastad.org:

 If I bundle the commons-vfs2 (2.1-SNAPSHOT/2.0) with the rar I get
 then exception:
 FileSystemException: Could not load VFS configuration from
 jar:file:/home/helge/Skrivebord/jca-parent/acme-war/target/apache-tomee/apps/acme-ra-1.0-SNAPSHOT/commons-vfs2-2.1-SNAPSHOT.jar!/org/apache/commons/vfs2/impl/providers.xml

Is this JAR and with the resource existing or not?

 If I add vfs2-commons to tomee/lib and provided in my rar, then its
 working OK.
 
 Is this how it's supposed to work?

The default configuration mechanism resolves providers.xml via the
classloader of the StandardFileSystemManager class. It retrieves the
URL for that resource and loads it.

You might want to overwrite the init() method or somple create the
DefaultFileSystemManager and configure it yourself.

(I am not entirely sure why it does not work in your scenario).

Gruss
Bernd

-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: [vfs] announcing an Azure Blob Storage Provider

[Gary Gregory]

Cool! I would put the license file in the root though, if you do want to
license the whole project.

G

On Tue, Mar 24, 2015 at 1:49 PM, Kervin Pierre ker...@sludev.com wrote:

 Hi,

 I'd like to briefly announce a VFS Provider I've been looking into
 periodically for the last few weeks.

 https://github.com/kervinpierre/vfs-azure

 Microsoft's SDK can be found at...
 https://github.com/Azure/azure-storage-java

 If anyone uses Azure Storage and would like to help test this, I'd
 appreciate it.  As I'd like to get it to production quality as soon as
 possible.

 Best regards,
 Kervin




-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
http://www.manning.com/bauer3/
JUnit in Action, Second Edition http://www.manning.com/tahchiev/
Spring Batch in Action http://www.manning.com/templier/
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

[vfs] announcing an Azure Blob Storage Provider

[Kervin Pierre]

Hi,

I'd like to briefly announce a VFS Provider I've been looking into
periodically for the last few weeks.

https://github.com/kervinpierre/vfs-azure

Microsoft's SDK can be found at...
https://github.com/Azure/azure-storage-java

If anyone uses Azure Storage and would like to help test this, I'd
appreciate it.  As I'd like to get it to production quality as soon as
possible.

Best regards,
Kervin

[vfs] vsf2.2.0: non-ascii chars in file name are not handled by createFolder()

[Geoff Watters]

All

I am using*commons-vfs2-2.0.jar* and am running into problems when file 
names contain non-ascii characters. According to 
https://issues.apache.org/jira/browse/VFS-305 this has been 
fixed/shipped in 2.0. In my environment I am able to create such file 
names when using ftp on the command-line (Red Hat Enterprise Linux 
Server release 5.8 (Tikanga)).


When I execute the following sample code, I get the output shown below.

public class FtpTest {
public static void main(String[] args) throws FileSystemException
{
String host=hhh;
String user = uuu;
String password = ppp;
String destDir = /tmp;
FileSystemOptions opts = new FileSystemOptions();
FtpFileSystemConfigBuilder.getInstance().setControlEncoding(opts, UTF-8);

DefaultFileSystemManager manager = new DefaultFileSystemManager();
manager.addProvider(ftp, new FtpFileProvider());
manager.init();

String root=ftp://+user+:+password+@+host+destDir;
// Specify a number of directories that should be created under 
destDir

String[] lRoots = new String[4];
lRoots[0]= root+/ftpDebug;
lRoots[1]= root+/ftp\u7684Debug;  // insert a non-ascii char
lRoots[2]= root+/ftp\u7685Debug;  // insert a different 
non-ascii char
lRoots[3]= root+/ftp\u7684Debug;  // insert the same 
non-ascii char


// Verify the ControlEncoding
System.out.println(ControlEncoding is 
+FtpFileSystemConfigBuilder.getInstance().getControlEncoding(opts));


int dirCount=0;
for (String lRoot: lRoots) {
System.out.println(dirCount+) Process directory [+lRoot+]);
FileObject newDir = manager.resolveFile(lRoot, opts);
if (!newDir.exists()) {
try {
System.out.println(dirCount+) +lRoot+ ::Dir Does 
Not Exist so Create It );

newDir.createFolder();
if (newDir.exists())
System.out.println(dirCount+) +lRoot+ 
::Creation Successful );

else
System.out.println(dirCount+) +lRoot+ 
::Creation Fails );

}
catch (Exception ex) {
System.out.println(dirCount+) +lRoot +  raised 
+ex);

}
}
else
System.out.println(dirCount+) +lRoot+ ::Dir Already 
Exists );

dirCount++;
}
}
}

The output from running the above is:-

ControlEncoding is UTF-8
0) Process directory [ftp://uuu:ppp@hhh/tmp/ftpDebug]
0) ftp://uuu:ppp@hhh/tmp/ftpDebug ::Dir Does Not Exist so Create It
0) ftp://uuu:ppp@hhh/tmp/ftpDebug ::Creation Successful
1) Process directory [ftp://uuu:ppp@hhh/tmp/ftpªDebug]
1) ftp://uuu:ppp@hhh/tmp/ftpªDebug ::Dir Does Not Exist so Create It
1) ftp://uuu:ppp@hhh/tmp/ftpªDebug ::Creation Successful
2) Process directory [ftp://uuu:ppp@hhh/tmp/ftp%Gçš…%@Debug]
2) ftp://uuu:ppp@hhh/tmp/ftp%Gçš…%@Debug ::Dir Does Not Exist so Create It
2) ftp://uuu:ppp@hhh/tmp/ftp%Gçš…%@Debug raised 
org.apache.commons.vfs2.FileSystemException: Could not create folder 
ftp://uuu:***@hhh/tmp/ftp%Gçš…%@Debug.

3) Process directory [ftp://uuu:ppp@hhh/tmp/ftpªDebug]
3) ftp://uuu:ppp@hhh/tmp/ftpªDebug ::Dir Does Not Exist so Create It
3) ftp://uuu:ppp@hhh/tmp/ftpªDebug raised 
org.apache.commons.vfs2.FileSystemException: Could not create folder 
ftp://uuu:***@hhh/tmp/ftpªDebug;.


After step 1) I see a directory called*/tmp/ftp?Debug*.
I think this is causing the subsequent creation problem in step 2) and 
step 3).
When a directory such as *ftp\u7684Debug* does exist, then *exists*() 
returns the correct result of true, but *createFolder*() creates a 
directory with name *ftp?Debug*.


Thanks in advance
Geoff

Re: [VFS] weird FileSystemException

[Bernd]

Do you have a logfile with the complete stacktrace? I guess this has a
nested cause pointing to some system resources. If not, it is a good idea
to add exception logging to this location in your app, so we can figure out
next tjme this happens.

Which VFS method was throwi g tnis, is it resolveFile(String)?

Do you always use the same password? Please make sure to send your answers
to the user list, only.

Gruss
Bernd
Am 12.01.2015 13:14 schrieb Israel Malachi isra...@ellipsis.co.il:

 Hi all

 OI got my app running using vfs-2.0 for connecting through SFTP for 48
 hours no problem,
  and the all of a sudden I got Exception saying:

 Could not determine the type of file sftp://appshob:***@host/LOG.log;

 While the app was able to connect the file few minutes earlier
 Restarting the tomcat solved the issue.
 What went wrong?

[VFS] Is is safe to use FileObjects from different FileSystemManagers ?

[Schalk Cronjé]

Hi all,

I have been wondering about this one for a while.

Assume that I have instances of FileSystemManager

  FileSystemManager fsm1
  FileSystemManager fsm2

  FileObject fo1 = fsm1.resolveFile( 'ftp://some-server/file1' )
  FileObject fo2 = fsm2.resolveFile( 'ftp://other-server/file2' )

Is it safe to allow the two FileObjects to co-operate?

  fo1.moveTo(fo2).


--
Schalk W. Cronjé
Twitter / Ello / Toeter : @ysb33r


-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: [vfs] How to properly clear VFS Ram filesystem

[Bernd Eckenfels]

Hello,

there are a number of leak fixes in the trunk (upcoming 2.1), this
might be needed to get the close really purge the cache. Arbi, can you
check and let us know if it works in 2.0 and if not, if 2.1 is fine?

(and yes, I also wonder why we have no .close() on FileSystem :) 

Gruss
Bernd


Am Wed, 24 Dec 2014
17:45:23 +0100 schrieb Martin van den Bemt mll...@mvdb.net:

 FileSystemManager manager = VFS.getManager();
 FileObject root = manager.resolveFile(ram:/);
 manager.closeFileSystem(root.getFileSystem());
 
 should do the trick.

-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

[vfs] How to properly clear VFS Ram filesystem

[Arbi Akhina]

Hi, I'm using VFS2 to construct an in-memory filesystem (uring the ram scheme)
for tests. After each test I've to clean up (destroy all created files and
folders), I'm using the following command:

VFS.getManager().getFilesCache().close();

However this doesn't seem to clear everything! what's the proper way to do
it?

question on stackoverflow
http://stackoverflow.com/questions/27619994/how-to-properly-clear-vfs-ram-filesystem

Re: [vfs] How to properly clear VFS Ram filesystem

[Martin van den Bemt]

FileSystemManager manager = VFS.getManager();
FileObject root = manager.resolveFile(ram:/);
manager.closeFileSystem(root.getFileSystem());

should do the trick.



Mvgr,
Martin

2014-12-24 11:29 GMT+01:00 Arbi Akhina arbi.akh...@gmail.com:
 Hi, I'm using VFS2 to construct an in-memory filesystem (uring the ram scheme)
 for tests. After each test I've to clean up (destroy all created files and
 folders), I'm using the following command:

 VFS.getManager().getFilesCache().close();

 However this doesn't seem to clear everything! what's the proper way to do
 it?

 question on stackoverflow
 http://stackoverflow.com/questions/27619994/how-to-properly-clear-vfs-ram-filesystem

-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

[vfs] Current status?

[Rob Walker]

Commons VFS seems to be useful to help with a number of aspects I'm 
looking at, but I'm concered about it's current development state.


It seems a little dormant in terms of recent development activity and 
fixing, and the web pages have a number of broken links.


Is this still an active and viable project to consider using?

-- Rob


Ascert - Taking systems to the edge
www.ascert.com


-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org

Re: [vfs] Current status?

[Bernd Eckenfels]

Hello,

It hasnt seen much activity but we still are working slowly towards a 2.1 
Version. It is a bit unclear how it fits into newer Java offered FileSystem 
abstractions, but it has still quite a few Providers no other solutions offer.

-- 
http://bernd.eckenfels.net

- Ursprüngliche Nachricht -
Von: Rob Walker r...@ascert.com
Gesendet: ‎01.‎08.‎2014 08:33
An: user@commons.apache.org user@commons.apache.org
Betreff: [vfs] Current status?

Commons VFS seems to be useful to help with a number of aspects I'm 
looking at, but I'm concered about it's current development state.

It seems a little dormant in terms of recent development activity and 
fixing, and the web pages have a number of broken links.

Is this still an active and viable project to consider using?

-- Rob


Ascert - Taking systems to the edge
www.ascert.com


-
To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
For additional commands, e-mail: user-h...@commons.apache.org