Transferring a large file

Hi,
I have to transfer a huge file. I am zipping the file and passing the byteArray. but the problem is the size. I am not able to transfer file of size 2-3 MB.
how do I split the file or send it in small parts.

thank you for the reply but FileInputStream is not serializable i guess. I tried it.
let me give a clear picture of what i am trying to do.
i have to transfer a file from client to server. I am doin this using RMI.
so i will call the remote method by passing the byteArray.
for this i need to split the file. be it FileInputStream or byteArray.
So how do i do it. how do i split the large file.
do i have to use some buffer and keep appending to it.
if you can give an example or sample code it will be great.
hope u can help me out
thanks

Similar Messages

  • Remote Desktop Connection Drops when opening a large file or Transferring a large file

    I am running a Dell R720 Windows 2008 R2 Server. When I open a Large PDF or transfer a large file to the server, the server drops the remote desktop connection. I do not see any errors and no events are reported. I can access the server via
    iDRAC 7 enterprise and the server is still up and functioning properly; however, the remote desktop connection can only be restored after the server is rebooted. I have read the following article below do not see any conflicts.
    http://support.microsoft.com/kb/2477133/en-us
     That said, the issue happens when:
    1. opening a large PDF
    2. Using a UNC path to transfer a large file
    3. Using Hyper-V to import a .VHD (another large file)
    Any help is appreciated - Thanks in advance

    Hi,
    Thank you for posting in Windows Server Forum.
    Does this issue facing for single user or multiple users?
    Have you tried on other system? IS it, facing same issue.
    From description it seems network issue, please check whether there is any drop for network connection or it works on low bandwidth. You need to see there is no loss from bandwidth perspective. There are other certain reason which can drop the connection or
    performance as remote desktop works on many different points. 
    For try you can autotune disable and check with following command.
    netsh interface tcp set global autotuning=disabled
    To renable follow beneath command
    netsh interface tcp set global autotuninglevel=normal
    When you are remote desktop to the remote server, please set the connection speed accordingly to optimize performance and might it will resolve your case of dropping connection.
    More information.
    Announcing the Remote Desktop Protocol Performance Improvements in Windows Server 2008 R2 and Windows 7 white paper
    http://blogs.msdn.com/b/rds/archive/2010/02/05/announcing-the-remote-desktop-protocol-performance-improvements-in-windows-server-2008-r2-and-windows-7-white-paper.aspx
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • Need help with email transfers of large files WRT160nl

    This is a new router for my home based business network. I am using Windows XP, Vonage, cable, a Dell power connect 2708 to expand ports and the WRT160nl router. Two issues: the most important is that I can no longer email large pdf files (contracts for instance) without breaking them into 6 to 7 Mg size files. Even 10mg files will not go. My previous Linksys wireless router (since 2003) never had this problem. Any ideas? I should also mention that I scan the files before trying to upload via email to clients.
    Also, at least once a day I have to restart my desktop (wireless) because the connection to our server (where all our files are stored) has dropped. I can access the internet and email.  Any ideas?
    Many thanks

    Open the setup page of the router and change the MTU size to 1365. Save the settings.
    Go to Wireless tab and click on Advanced wireless settings sub tab. Change the Beacon Interval to 75, RTS and fragmentation threshold to 2306. Save the settings and power cycle the router. See if that makes any difference.
    Make sure that firmware on your router is upgraded.

  • TimeCapsule (and AirPort extreme too) hangs on large file transfers

    Greetings,
    I got a following problem. I had install AirPort connected to my router with copper and extend network with TimeCapsule. TimeCapsule have two USB drives attached, AirPort - one USB. When I am transferring a large file, in a magnitude 2-3Gb or multiple simultaneous transfers of smaller files to/from those USB drives, depending on which drive I am using the AirPort or TimeCapsule get crashed. For plain user it is looks like as of sudden, data transfer stops, led in a front keeps green, and I can not reconnect to the drives. If I powercycle TC or AES everything get back to normal. Are there anyone else experiencing the same issues and if yes, what would be solution ?
    Thank you.

    I think we have tried almost every combination of disabling Large Send Offload, TCP offload, IP SEC Offloading, VMQ and Receive Side Scaling possible - in the various places there are - although I will be quite honest - as there are 3 places to do this
    for each Server (the related physical and virtual NICs on the HV Server, and also the NIC in the VM) it is possible we may have missed an iteration...
    During our testing we have noticed that the symptoms of the problem gets worse the higher the transfer speed is. For example if you transfer to the VM from a desktop with a 100Mbs NIC, there will be subtle lag and a transfer speed of say 10 or so KBs ,
    if you use a device with a 1Gbs NIC, you on average achieve 50-70 KBs transfer speeds and the higher the number, the worse the GUI / Server locks up (although the transfer completes just fine).
    We also tried throttling the bandwidth via the 2012 GUI - to see if that helped, but none of the changes we made seemed to work, and we did not have time to try the powershell way of doing this.
    We did replace one of the VM's NIC with a legacy one as part of our testing today, and now data transfers to the VM from a PC with a 1Gbs NIC run slower at around 30-35 KBs and the are no noticeable GUI freezes, although during the large transfer
    it looks like 1 in every 30-40 packets is dropped in a continual ping that runs during the transfer period.
    We have done a lot of cable replacing today (out of diligence) but there seems to be no noticeable issue. We also tried and older NC380T dual port NIC we had available and used the standard driver Windows offered instead of an HP one, but the problem
    was identical no matter which NIC we used.

  • Large file copy fails through 4240 sensor

    Customer attempts to copy a large file from a server in an IPS protected vlan to a host in an IPS un-protected vlan and the copy fails if file is greater than about 2Gbytes in size. If the server is moved to the un-protected vlan the copy succeeds. There are no events on the IPS suggesting any blocking or other actions.

    The CPU does occasionly peak at 100% when transferring a large file but the copy often fails when the CPU is significantly lower. I know a 4240 has 300Mbit/s throughput but as I understood it traffic would still be serviced but would bypass the inspection process if exceeded, maybe a transition from inspection to non inspection causes the copy to fail like a tcp reset, I may try a sniffer.
    I do have TAC involved but like to try and utilise the knowledge of other expert users like yourself to try and rectify issues. Thanks for your help. If you have any other comments please let me know, I will certainly post my findings if you are interested.

  • Slow large file transfer speed with LaCie 1T firewire 800 drives

    I am transferring two large files (201gb and 95gb) from one LaCie 1T firewire external drives to another one (using separate connections to a PCI Express firewire 800 card in my Quad G5. The transfer time is incredibly slow – over for hours for the 201gb file and over 2 hours for the 95gb file.
    Does anyone have any ideas why this is so slow or what I might try to speed up the transfer rates?
    Thank you.
    G5 Quad 2.5 8GB DDR2 SDRAM two SATA 400GB   Mac OS X (10.4.5)  

    You posted this in the Powerbook discussion forum. You may want to post it in the Power Mac G5 area, located at http://discussions.apple.com/category.jspa?categoryID=108

  • Large file copy fails

    trying to move a 60GB folder from a NAS to a local USB drive, and regardless of how many times it try to do this it fails within the first few minutes.
    I'm on a managed Ciscso Gigabit Ethernet switch in a commercial building and I have hundreds of users having no problems with OS 10.6, Windows XP and Windows 7 but my Yosemite system is not able to do this unless I boot into my OS 10.6. partition.
    Reconfig of the switch is not a viable option, I can't change things on a switch that would jeopardize hundreds of users to fix one thing on a mac testing the legitimacy of OS 10.10 in  a corporate setting.

    The CPU does occasionly peak at 100% when transferring a large file but the copy often fails when the CPU is significantly lower. I know a 4240 has 300Mbit/s throughput but as I understood it traffic would still be serviced but would bypass the inspection process if exceeded, maybe a transition from inspection to non inspection causes the copy to fail like a tcp reset, I may try a sniffer.
    I do have TAC involved but like to try and utilise the knowledge of other expert users like yourself to try and rectify issues. Thanks for your help. If you have any other comments please let me know, I will certainly post my findings if you are interested.

  • WRT110 router - FTP problem - Timeouts on large files

    When I upload files via FTP and if the transfer of a file takes more then 3 minutes,
    then my FTP programs doesn't jump to the next file to upload when the previous one has been just finished.
    The problem occurs only if I connect to the internet behind the wrt110 router.
    I have tried FileZilla, FTPRush and FlashFXP FTP softwares to upload via FTP.
    At FileZilla sending keep-alives doesn't help,
    only it works at FlashFXP, but I have a trial version.
    At FIleZilla's site I can read this:
    http://wiki.filezilla-project.org/Network_Configuration#Timeouts_on_large_files
    Timeouts on large files
    If you can transfer small files without any issues,
    but transfers of larger files end with a timeout,
    a broken router and/or firewall exists
    between the client and the server and is causing a problem.
    As mentioned above,  
    FTP uses two TCP connections:
    a control connection to submit commands and receive replies,
    and a data connection for actual file transfers.
    It is the nature of FTP that during a transfer the control connection stays completely idle.
    The TCP specifications do not set a limit on the amount of time a connection can stay idle.
    Unless explicitly closed, a connection is assumed to remain alive indefinitely.
    However, many routers and firewalls automatically close idle connections after a certain period of time.  
    Worse, they often don't notify the user, but just silently drop the connection.
    For FTP, this means that during a long transfer
    the control connection can get dropped because it is detected as idle, but neither client nor server are notified.
    So when all data has been transferred, the server assumes the control connection is alive
    and it sends the transfer confirmation reply.
    Likewise, the client thinks the control connection is alive and it waits for the reply from the server.
    But since the control connection got dropped without notification,
    the reply never arrives and eventually the connection will timeout.
    In an attempt to solve this problem,
    the TCP specifications include a way to send keep-alive packets on otherwise idle TCP connections,
    to tell all involved parties that the connection is still alive and needed.
    However, the TCP specifications also make it very clear that these keep-alive packets should not be sent more often than once every two hours. Therefore, with added tolerance for network latency, connections can stay idle for up to 2 hours and 4 minutes.
    However, many routers and firewalls drop connections that have been idle for less than 2 hours and 4 minutes. This violates the TCP specifications (RFC 5382 makes this especially clear). In other words, all routers and firewalls that are dropping idle connections too early cannot be used for long FTP transfers. Unfortunately manufacturers of consumer-grade router and firewall vendors do not care about specifications ... all they care about is getting your money (and only deliver barely working lowest quality junk).
    To solve this problem, you need to uninstall affected firewalls and replace faulty routers with better-quality ones.

    When I upload files via FTP and if the transfer of a file takes more then 3 minutes,
    then my FTP programs doesn't jump to the next file to upload when the previous one has been just finished.
    The problem occurs only if I connect to the internet behind the wrt110 router.
    I have tried FileZilla, FTPRush and FlashFXP FTP softwares to upload via FTP.
    At FileZilla sending keep-alives doesn't help,
    only it works at FlashFXP, but I have a trial version.
    At FIleZilla's site I can read this:
    http://wiki.filezilla-project.org/Network_Configuration#Timeouts_on_large_files
    Timeouts on large files
    If you can transfer small files without any issues,
    but transfers of larger files end with a timeout,
    a broken router and/or firewall exists
    between the client and the server and is causing a problem.
    As mentioned above,  
    FTP uses two TCP connections:
    a control connection to submit commands and receive replies,
    and a data connection for actual file transfers.
    It is the nature of FTP that during a transfer the control connection stays completely idle.
    The TCP specifications do not set a limit on the amount of time a connection can stay idle.
    Unless explicitly closed, a connection is assumed to remain alive indefinitely.
    However, many routers and firewalls automatically close idle connections after a certain period of time.  
    Worse, they often don't notify the user, but just silently drop the connection.
    For FTP, this means that during a long transfer
    the control connection can get dropped because it is detected as idle, but neither client nor server are notified.
    So when all data has been transferred, the server assumes the control connection is alive
    and it sends the transfer confirmation reply.
    Likewise, the client thinks the control connection is alive and it waits for the reply from the server.
    But since the control connection got dropped without notification,
    the reply never arrives and eventually the connection will timeout.
    In an attempt to solve this problem,
    the TCP specifications include a way to send keep-alive packets on otherwise idle TCP connections,
    to tell all involved parties that the connection is still alive and needed.
    However, the TCP specifications also make it very clear that these keep-alive packets should not be sent more often than once every two hours. Therefore, with added tolerance for network latency, connections can stay idle for up to 2 hours and 4 minutes.
    However, many routers and firewalls drop connections that have been idle for less than 2 hours and 4 minutes. This violates the TCP specifications (RFC 5382 makes this especially clear). In other words, all routers and firewalls that are dropping idle connections too early cannot be used for long FTP transfers. Unfortunately manufacturers of consumer-grade router and firewall vendors do not care about specifications ... all they care about is getting your money (and only deliver barely working lowest quality junk).
    To solve this problem, you need to uninstall affected firewalls and replace faulty routers with better-quality ones.

  • USB key ejecting itself when transferring large files

    I have a LG 16G USB key formatted in MacOS extended (journaled), I've been encountering a particular issue when I try to transfer files taken on another computer and copying them from the key to my Macbook pro ( OSX 10.6.2). after it start transferring it ejects itself with the "the disk was not ejected properly" message, then reappears right away in the finder...
    the problem doesn't present itself when I copy a file from my macbook pro to the key, and then try transferring it back to my computer. and I've tried this with both small files (under 200mb) and large files (over 4G).
    I've also noticed the transfer rate is very slow when this happens.
    so far the problem only presents itself when I transfer files from one of the MacPro's in my university's studios, but since I work a lot on these machine, this is becoming quite a problem. I don't have the complete specs of these machines, they all run on Leopard, probably 10.5.something. not SL... perhaps that's the problem?
    I've seen similar post on the forum concerning this issue with TimeMachine backup drives, suggesting it had something to do with the sleep preferences, however I've tried all the potential solutions from these post and the problem persists.
    So far the only solution I've found has been to transfer the files to my girlfriend's macbook (running on tiger), and then transferring the files in target mode from her computer to mine... quite inconvenient...
    I have a feeling this might be due to the formatting of my key, I have a 2G USB key formatted in MS-DOS (FAT32) and have had no problems with it so far. The reason I formatted in Mac OS extended is simple, I work in the video field and with HD I find myself often moving around single files larger then 4GB, which I've come to understand isn't possible in FAT 32.
    I'd like to know how to resolve this, and especially like to know if it is indeed a format issue, since I'm soon going to acquire a new external hard drive for the sole purpose of storing my increasing large media files and would like to know how to format it.

    Hi,
    I have an external USB Card reader (indeed - two different readers), which have the same problems with self-ejecting disks. Every transfer of data from SD card from my camera is the pain now. There is many different themes related to the self-"the disk was not ejected properly" situation, but no working solution now.

  • Privileges problem when transferring large files

    This just happened, and I don't know what changed. I cannot transfer large files from my Macbook Pro to my MacPro desktop, neither on the network nor by a USB hard drive. I get the infamous "You do not have sufficient privileges" message. The files start copying, and after about 1gb or so, the message pops up. Small files no problem, there's no restriction on those. It does not matter which disk I am trying to copy it to.
    I thought it was just a problem with iMovie files and folders (these get big fast), but it seems to be an issue with any large file. I have repaired permissions on both disks, I have made sure that the unlock key is unlocked and that all the boxes are checked "Read & Write".
    And this problem just arose today. Nothing has changed, so far as I know.

    I assume I am always logged in as administrator because I have never logged in as anything else. It also does not matter from what folder, or even disk drive, I am trying to transfer from. If the file is above a certain size, it stops transferring and I get the error.
    What interests me is not that I immediately get the "insufficient privileges" error when I try and transfer a forbidden folder or file. I've seen that. This happens after about a gig of data has transferred over already, then that error pops up.

  • WAP4410N stops responding on large file transfers

    Also experience this issue, latest firmware (7/17/2010 version).  Definately related to large file transfers.  Or, viewing videos (e.g. youtube) over RDP.
    Only power cycle gets responsiveness back.  Laptops remain connected, but with "Limited Connectivity".

    There's a limit of 10MB for a single RTMP message in LCDS, you're probably running into this but you're supposed to get a "TCMessageTooLargeException" when you go over 10MB. I think there might be a bug around bubbling this exception but either way, I think you should try to chop your file in 10MB chunks when using RTMP.

  • Transferring large files from my mac to pc

    Hi guys, i'm trying to transfer a large file from my mac to my pc. Its over 7GB and my mac doesnt have a DL dvd burner so that's out of the question. I've tried transferring it over the network however the eta is 2 days which is a little too long. I've tried putting the file on my external HD but when its formatted into mac os extended my laptop does not recognise it and when the drive is formated in ms dos (fat) i am unable to put the file on to the drive (error code 0)
    I've run out of ideas what to do so was hoping someone on here could help
    Thanks

    Hi and welcome to Discussions,
    have a look at this little Windows program http://hem.bredband.net/catacombae/hfsx.html
    It enables Windows to read from HFS-formatted (OSX) harddisks.
    Might be the easiest and cheapest solution, as others are not free.
    MacDrive would be another option, but is not free (but has more features).
    Regards
    Stefan

  • Itunes with 10.3x not transferring large files to external hard drive

    I have been unable to transfer any large files, basically anything over over two artists or so from old external hard drive for my old windows xp computer to my new external hard drive (both iomega and western digital have been tried) without the transfer cutting out and popping up a message to effect of itunes can not copy or add file to folder...something like that. am i missing something that i need to be doing? ive got about 33,000 items, and the thought of doing them 10-15 at a time really isn't something i want to do. But as of this point, i can't find a way to simply xfer the whole itunes library from the old external to the new one. Thanks for any help.

    You can transfer purchased content ONLY! Unfortunately, you have no choice as to what gets transferred. Here are some work arounds
    1. Delete off iPod Touch/iPhone/iPod then transfer
    2. Transfer all content then delete from computer

  • Transferring Time Machine File to larger hard drive

    I have a time machine backup on a 250 G hard drive and would like to transfer that file to a 1 T hard drive. When I connect both hard drives to the MacBook Pro and try to transfer the very large file from one drive to the other it stops part way and hangs up. I think it tries to put the whole file on the MacBook Pro and there isn't enough space. Is there a special copy program that can handle a file this large?

    see if this user tip helps: http://web.me.com/pondini/Time_Machine/18.html.
    JGG

  • WiFi breaks when transferring large file over LAN

    Hi guys,My WiFi mostly behaves itself, however if I try to transfer a large file (The last one was ~1GB) over the LAN (standard SMB file copy), WiFi drops out. It gets roughly 30MB through before connectivity is lost.The WiFi continues to show as connected, but I cannot even ping my router.Only disconecting and reconnecting WiFi re-establishes the connection.Any idea what's up? (My router is the black 'home hub' style. I can't find any version information in it's admin panel.) (And before someone asks, no I'm not telling you the contents of the file as it isn't relevant. With the greatest of respect, if you just ask unrelated questions to pry, please don't waste everyones time.)

    Didn't think of that, thanks. Great workaround.I'm going to call Sky, see if they have any firmware updates or other solution. Surely they wouldn't leave such a big knows issue unfixed. I'll report back with what they say. Edit:Just got off the phone from Sky technical support.This issue was first reported Nov/Dec 2014.The chap I spoke to does not know of a fix, or whether a fix is being worked on, or if a fix will ever be worked on.He has not way of contacting the development team to find out any of this information.He said firmware updates are pushed out to routers every now and again. He does not know when this is going to happen and does not have a way to notify about firmware updates installed on my router. (This terrifies me. Sky have a backdoor into my router and can install any code they wish, without even telling me what they changed/installed). There is no way to turn these auto-updates off either. Here's a key thing he did say though:He said he was not at liberty to provide my ADSL credentials, but if I chose to extract them from the router and install my own router instead, they would not have any problem with that.When I told him that this was against their TOS and they could terminate my contract for doing this, he went silent and just said "errr..." Allowing Sky, their subcontractors and anyone else they choose to install any code they wish to my router whenever they please and have free open access to my entire LAN is a total deal breaker for me. That router is getting unplugged today and I'm putting a new router on the credit card. I told tech support this. I said if they have a problem with that, let's go the legal route. I literally have a recorded call where they give me permission to install my own router. 

Maybe you are looking for