This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 202280 - File cannot be saved
Summary: File cannot be saved
Status: RESOLVED DUPLICATE of bug 174443
Alias: None
Product: php
Classification: Unclassified
Component: FTP Support (show other bugs)
Version: 7.1
Hardware: PC Linux
: P3 normal (vote)
Assignee: Tomas Mysik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-19 07:43 UTC by Tomas Mysik
Modified: 2011-09-20 08:58 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
netbeans nightly log, save/upload with new keep alive issue (34.67 KB, text/x-log)
2011-09-19 22:21 UTC, ramzih
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Mysik 2011-09-19 07:43:28 UTC
From issue #187836, comment #30:

Hi,

I'm reopening this one as I came across the same issue as described in Comment
#21 with the exception that I first have a keep alive transfer timeout error
dialog alert and then whenever I try to save a file ( upload on save ) the
second dialog inviting to disable the feature shows up.

The issue was reproduced on two different desktop machines with two different
server machines.

**Scenario 1**

Desktop machine :
Ubuntu Natty desktop 64 with netbeans Build 201109140600

Server machine :
Fresh Ubuntu Lucid server 64 on vmware virtual machine with vanilla virtualmin
install ( LAMP environment with a default virtual server created
http://software.virtualmin.com/gpl/scripts/install.sh )
FTP Server installed is proftpd 1.3.2c-1ubuntu0.1
With default config file :

TimeoutNoTransfer               600
TimeoutStalled                  600
TimeoutIdle                     1200

**Scenario 2**

Desktop machine :
Ubuntu Maverick desktop 64 with netbeans Build 201109140600/201109170600

Server machine :
Fresh Ubuntu Lucid server 64 on kvm virtual machine with vanilla virtualmin
install ( LAMP environment with a default virtual server created
http://software.virtualmin.com/gpl/scripts/install.sh )
FTP Server installed is proftpd 1.3.2c-1ubuntu0.1
With default config file :

TimeoutNoTransfer               600
TimeoutStalled                  600
TimeoutIdle                     1200


In both scenarios, desktop and server machines are in the same lan subnet and
no firewall between them.

The issue is still there when :

Using Passive/Active mode
Enabling/Disabling preserve permission option
Enabling/Disabling temporary upload option
Increasing/Decreasing ftp timeouts in netbeans
Increasing/Decreasing ftp timeouts in proftpd config file ( make eventually the
keep alive error a bit longer to show up if increasing the timeouts but it's
still there )

There's no issue with the stable 7.0.1 netbeans release.

Haven't tested another FTP server or an SFTP one though
Comment 1 Tomas Mysik 2011-09-19 07:57:42 UTC
We need your IDE log [1], please reopen this issue and attach it (do NOT copy & paste, please) once this problem happens to you.

Meanwhile - Lado, could you please try to reproduce this issue? Thanks a lot.

Thanks.
[1] View > IDE Log
Comment 2 ramzih 2011-09-19 22:21:46 UTC
Created attachment 110884 [details]
netbeans nightly log, save/upload with new keep alive issue
Comment 3 ramzih 2011-09-19 22:26:17 UTC
Comment on attachment 110884 [details]
netbeans nightly log, save/upload with new keep alive issue

Hi,

Here you go. The log is that of nebeans scenario 1.

Starting netbeans
Saving file (uploads fine)
Waiting 10 mn ( transfer timeout is set to 600s )
Keep alive error shows up without using netbeans
Second dialog box inviting to disable the upload on save feature shows up every time there's an attempt to save a file.
Comment 4 Tomas Mysik 2011-09-20 08:51:09 UTC
Thanks for the attachments, will look at it.
Comment 5 Tomas Mysik 2011-09-20 08:58:01 UTC
The problem is:

> Error while disconnecting

and

> Cannot log out from server ftp.workspace.lan.

This is a duplicate of issue #174443. Just navigate to your server setting and make sure that "Ignore disconnect errors" is checked.

Thanks for reporting.

*** This bug has been marked as a duplicate of bug 174443 ***