Connect 1.2.2 Release Notes

Connect 1.2.2 Release Notes
Version 1.2.2
Platform Windows, Mac
Feb 28 2008
  • Windows Vista install improvements for Connect.
  • False transfer timeout conditions when transferring huge sets of small files (or resuming such transfers).
  • SSH keep alive sent in all products to avoid ssh timeouts by firewalls for long running transfers.
  • Various memory leak fixes / crashes in Aspera Central - affects many file transfers in Connect and long running uses of the web services API.
  • Better error handling throughout, including of non fatal errors.
  • Fixes of resume problems for special cases.
  • Various UDP timeout conditions for transfers where some or all files are already at the destination.
  • Connect crashes on transfer of a huge number of small files.
  • ascp crashes on machines with certain modified Windows TCP stack.
  • File resume bug on Windows.
  • Stall without error when network disconnected during transfer.
  • Upgrade installation fails to update Connect.
  • Incorrect error reported if transfer attempts to use a target directory that does not exist.
  • Aspera central fails to report a failed ssh connection.
  • Improved logging in asperacentral.
  • Default network preferences in Connect raised to 45 Mbps.
  • Terminating ascp causes receiver to block.
  • ascp does not exit properly and locks port 33001 if checksumming when signaled.
  • Short network interruption causes transfer to fail.
  • ascp fails to timeout properly in some cases when the network is interrupted for 60 seconds or more.
  • Various improvements in error handling when the target directory does not exist.
  • Incorrect 'Done' report in Connect in some cases of trasnfer error.
  • No resume option in Connect when the transfer fails on ssh authentication.
  • Connect overwrites SCP license file when scp is installed on the machine.
  • ascp hangs on Mac (in case of network disruption).
  • On pause, Elapsed time does not stop.
  • Connect process leaks socket handles in transfers of large numbers of small files.
  • scp.aspera (fasp1) can not find the license on Mac OS X.
  • The ".aspx" metadata file syntax is made configurable configurable.
  • Aspera central init.d 'stop' daemon method does not work when a database adaptor is bad.
  • Sending rate abnormally "large" at tiny rates.
  • Connect should display download file target name opposed to source name.
  • No rate on cmd line = no rate in FASPMGR session message.
  • ascp man page lacks documentation of the -i public/private key option.
  • Directory modification times are not preserved correctly when transferring with the -p / preserve timestamp option.
  • Transfer timeout on the remote end incorrectly reported as success, and causes receiver to delete .aspx file, and transfer can no longer be resumed.
  • Sender side abort misreported in remote log as success.
  • Checksum fails on win32 with ERROR_NO_SYSTEM_RESOURCES for ultra-large files.
  • Win 2000 K installer ; SCP client attampts user console install.
  • ascp fails (errno=88) with some SSH servers, e.g. Tactia.
  • PathMTU setting not propagated in Connect.
  • fasp sender doesn't handle optimally EWOULDBLOCK errors.
  • add aspera.conf option to disable fasp receiver file cache and set max cache size.
  • asperacentral leaves zombies.
  • No FASP timeout if no UDP traffic and no work.
  • New Connect logo/icon graphic for Mac OS X.
  • Webplugin connect download link redirects indefinitely.
  • Mac OS Connect version number is incorrect. Change in info.plist.
  • aspera web must not use bandwidth detection by default.
  • pMTU size error is not discovered correctly.
  • aspx file not deleted after successful transfer of files with utf characters.
  • db_logger - session completion query should always set the stopped_at time.
  • ascp prepost called twice on Session Stop.
  • License key allows expiration times by the day.
  • asperacentral --version check crashes on mac-ppc and mac-intel gives 'Bus error'.
  • Connect fails to save preferences due to race condition.
  • +72 minor issues.
Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk