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.
Summary: | CVS operations taking LONG time | ||
---|---|---|---|
Product: | versioncontrol | Reporter: | mclaborn <mclaborn> |
Component: | CVS | Assignee: | Ondrej Vrabec <ovrabec> |
Status: | NEW --- | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 8.1 | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
IDE log
stack trace for hung commit |
Description
mclaborn
2015-08-26 21:57:29 UTC
Created attachment 155673 [details]
IDE log
Created attachment 155674 [details]
stack trace for hung commit
After closing NetBeans and restarting, the single commit that was hung up ran successfully in just a couple of seconds. Reassigning for further evaluation. waiting in at java.lang.Thread.sleep(Native Method) at org.netbeans.lib.cvsclient.util.LoggedDataInputStream.read(LoggedDataInputStream.java:210) at org.netbeans.lib.cvsclient.Client.handleResponse(Client.java:579) at org.netbeans.lib.cvsclient.Client.processRequests(Client.java:552) at org.netbeans.lib.cvsclient.command.commit.CommitCommand.execute(CommitCommand.java:322) seems to be expecting server response but none has come. The CVS repository is on a remote server. The CVS root is defined as :ext:mclaborn@servernamehere:/cvs I looked on that remote server and did not see any process with my username that looked like any type of CVS. Any idea what it would/should look like on the CVS repository server for this situation? Seems like the commit operation should time out after a while so that I can try again. As it is now, I have to completely close NetBeans to try a new CVS operation when one hangs up like this. Cancelling the running process in the progress bar does not interrupt it? It does interrupt the stalled commit, but the next commit I try just queues up, it doesn't run. |