Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
MIME-Version: 1.0
References: <1464859788409-5783383.post@n5.nabble.com> <CABe1WL_3YWLJog18K8UgJfoOjJc2Jjr65o7+wuVoFgpVgxUc7g@mail.gmail.com>
 <1464865005026-5783388.post@n5.nabble.com> <CABe1WL8oK2ae1Jg3O460wtF+nserUFT8zpB6NEVr5AVrD2ZM1g@mail.gmail.com>
 <HE1PR0101MB19314818E801AD683B8E8D7597590@HE1PR0101MB1931.eurprd01.prod.exchangelabs.com>
In-Reply-To: <HE1PR0101MB19314818E801AD683B8E8D7597590@HE1PR0101MB1931.eurprd01.prod.exchangelabs.com>
From: Pontus Ullgren <ullgren@gmail.com>
Date: Fri, 03 Jun 2016 14:35:25 +0000
Message-ID: <CABe1WL9qCUbCi_Xo6NYYxswAu7mifwVe_tPCLhPXPxi-qsSBqw@mail.gmail.com>
Subject: Re: Problem transfer from SMB to FTP OutMemory Java Heap Space
To: "users@camel.apache.org" <users@camel.apache.org>
Content-Type: multipart/alternative; boundary=001a113f1e0eb7bf43053460a20c
archived-at: Fri, 03 Jun 2016 14:35:41 -0000

--001a113f1e0eb7bf43053460a20c
Content-Type: text/plain; charset=UTF-8

Strange I have run applications where I transfer files up to 300MB without
problems using camel-jcifs.
Feel free to log a jira (
https://camel-extra.atlassian.net/projects/CAMEX/issues) with your findings.

However I do agree that if you use case is such that you can mount the
shares (either on windows or using smbmount on linux) then using the
file:// transport is probably a more stable and tested way to go.
Also if you are running from a Windows machine I do belive using file://
witth a UNC path is also possible. Provided that the user your JVM is
running as has access to the share.

Best regards
Pontus Ullgren


On Fri, 3 Jun 2016 at 15:17 Hans Orbaan <hans.orbaan@docdata.eu> wrote:

> Hi,
>
> You should mount your share and use the file:// component to avoid out of
> memory errors. There is something wrong with camel-jcifs. It will go out of
> memory (threads I guess, not memory, but system resources) will retrieving
> a file.
> This already happens from 5 MB or more we found. Could not really locate
> the issue though.
>
> With kind regards,
>
> Hans Orbaan
>
>
> -----Oorspronkelijk bericht-----
> Van: Pontus Ullgren [mailto:ullgren@gmail.com]
> Verzonden: Friday 3 June 2016 13:15
> Aan: users@camel.apache.org
> Onderwerp: Re: Problem transfer from SMB to FTP OutMemory Java Heap Space
>
> localWorkDirectory is a directory on the server where your camel route run
> (in Fuse as you say),
>
> localWorkDirectory is also supported in camel-jcifs (
> http://camel.apache.org/jcifs.html).
>
>
> // Pontus
>
> On Fri, 3 Jun 2016 at 08:12 Daniel Pompa <pompadaniel@gmail.com> wrote:
>
> > Hi Pontus, sorry Im new in Fuse. The Camel version is 2.12.0
> >
> > how I can defined the heap size to the Java Process?
> >
> > I add localWorkDirectory into the URI, but fail again, this
> > localWorkDirectory is a directory in Fuse or in the smb server? I put
> > in the localWorkDirectory  in smb.
> >
> > I saw localWorkDirectory is just for FTP.
> >
> > Thanks.
> >
> >
> >
> > --
> > View this message in context:
> > http://camel.465427.n5.nabble.com/Problem-transfer-from-SMB-to-FTP-Out
> > Memory-Java-Heap-Space-tp5783383p5783388.html
> > Sent from the Camel - Users mailing list archive at Nabble.com.
> >
>

--001a113f1e0eb7bf43053460a20c--