bzr ci crashes with TooManyConcurrentRequests after a bzr break-lock

[Rosemary Sumitani]

the command bzr ci has freeze, I kill the cmd.exe and typed command bzr break-lock

bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist.

typed bzr ci
bzr: ERROR: bzrlib.errors.TooManyConcurrentRequests: The medium '<bzrlib.smart.medium.SmartTCPClientMedium object at 0x02ECD430>' has reached its concurrent request limit. Be sure to finish_writing and finish_reading on the currently open request.

Traceback (most recent call last):
  File "bzrlib\commands.pyo", line 907, in exception_to_return_code
  File "bzrlib\commands.pyo", line 1111, in run_bzr
  File "bzrlib\commands.pyo", line 685, in run_argv_aliases
  File "bzrlib\commands.pyo", line 700, in run
  File "bzrlib\cleanup.pyo", line 122, in run_simple
  File "bzrlib\cleanup.pyo", line 156, in _do_with_cleanups
  File "bzrlib\builtins.pyo", line 3190, in run
  File "bzrlib\decorators.pyo", line 194, in write_locked
  File "bzrlib\workingtree_4.pyo", line 197, in commit
  File "bzrlib\decorators.pyo", line 194, in write_locked
  File "bzrlib\mutabletree.pyo", line 225, in commit
  File "bzrlib\commit.pyo", line 264, in commit
  File "bzrlib\cleanup.pyo", line 118, in run
  File "bzrlib\cleanup.pyo", line 156, in _do_with_cleanups
  File "bzrlib\commit.pyo", line 338, in _commit
  File "bzrlib\commit.pyo", line 479, in _check_bound_branch
  File "bzrlib\decorators.pyo", line 140, in read_locked
  File "bzrlib\branch.pyo", line 2463, in get_master_branch
  File "bzrlib\branch.pyo", line 169, in open
  File "bzrlib\bzrdir.pyo", line 863, in open
  File "bzrlib\bzrdir.pyo", line 898, in open_from_transport
  File "bzrlib\bzrdir.pyo", line 2122, in open
  File "bzrlib\bzrdir.pyo", line 3367, in _open
  File "bzrlib\remote.pyo", line 116, in __init__
  File "bzrlib\remote.pyo", line 128, in _probe_bzrdir
  File "bzrlib\remote.pyo", line 135, in _rpc_open_2_1
  File "bzrlib\remote.pyo", line 53, in _call
  File "bzrlib\smart\client.pyo", line 132, in call
  File "bzrlib\smart\client.pyo", line 145, in call_expecting_body
  File "bzrlib\smart\client.pyo", line 90, in _call_and_read_response
  File "bzrlib\smart\client.pyo", line 45, in _send_request
  File "bzrlib\smart\client.pyo", line 115, in _construct_protocol
  File "bzrlib\smart\medium.pyo", line 705, in get_request
  File "bzrlib\smart\medium.pyo", line 918, in __init__
TooManyConcurrentRequests: The medium '<bzrlib.smart.medium.SmartTCPClientMedium object at 0x02ECD430>' has reached its concurrent request limit. Be sure to finish_writing and finish_reading on the currently open request.

bzr 2.2b2 on python 2.5.4 (Windows-Vista-6.1.7600)
arguments: ['bzr', 'ci']
encoding: 'cp1252', fsenc: 'mbcs', lang: None

[Martin Pool (mbp)]

I think this is caused by your connection dropping or being refused:

> bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist.

and then for some reason we give a traceback. I thought we had fixed that already though.

[Andrew Bennetts (spiv)]

Did the "bzr: ERROR: Connection closed: ..." message appear when you did 'bzr break-lock", or when you did "bzr ci", or both times?

This looks quite like a bug that was fixed ages ago (in 2.1.0b2), but you are using bzr 2.2b2 so that shouldn't be it. Hmm!

If you can reproduce it then please run "bzr -Dhpss ci" and then attach the contents of the bzr.log file ("bzr --version" will tell you where to find it").

[Rosemary Sumitani (mayuki-asamiya)]

connection closed appears after 'bzr break-lock' command.

giving more information: we use a server as main branch using version
2.1.1 with Windows 2003.

Server was stuck when I did that command, sometimes the server got stuck and
froze our bzr (when type bzr st or bzr ci).

[]s
On Thu, Jul 1, 2010 at 10:14 PM, Andrew Bennetts <
<email address hidden>> wrote:

> Did the "bzr: ERROR: Connection closed: ..." message appear when you did
> 'bzr break-lock", or when you did "bzr ci", or both times?
>
> This looks quite like a bug that was fixed ages ago (in 2.1.0b2), but
> you are using bzr 2.2b2 so that shouldn't be it. Hmm!
>
> If you can reproduce it then please run "bzr -Dhpss ci" and then attach
> the contents of the bzr.log file ("bzr --version" will tell you where to
> find it").
>
> ** Changed in: bzr
> Importance: Undecided => Medium
>
> ** Changed in: bzr
> Status: New => Confirmed
>
> ** Summary changed:
>
> - bzr ci crashes after a bzr break-lock
> + bzr ci crashes with TooManyConcurrentRequests after a bzr break-lock
>
> --
> bzr ci crashes with TooManyConcurrentRequests after a bzr break-lock
> https://bugs.launchpad.net/bugs/600636
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Bazaar Version Control System: Confirmed
>
> Bug description:
> the command bzr ci has freeze, I kill the cmd.exe and typed command bzr
> break-lock
>
> bzr: ERROR: Connection closed: Unexpected end of message. Please check
> connectivity and permissions, and report a bug if problems persist.
>
> typed bzr ci
> bzr: ERROR: bzrlib.errors.TooManyConcurrentRequests: The medium
> '<bzrlib.smart.medium.SmartTCPClientMedium object at 0x02ECD430>' has
> reached its concurrent request limit. Be sure to finish_writing and
> finish_reading on the currently open request.
>
> Traceback (most recent call last):
> File "bzrlib\commands.pyo", line 907, in exception_to_return_code
> File "bzrlib\commands.pyo", line 1111, in run_bzr
> File "bzrlib\commands.pyo", line 685, in run_argv_aliases
> File "bzrlib\commands.pyo", line 700, in run
> File "bzrlib\cleanup.pyo", line 122, in run_simple
> File "bzrlib\cleanup.pyo", line 156, in _do_with_cleanups
> File "bzrlib\builtins.pyo", line 3190, in run
> File "bzrlib\decorators.pyo", line 194, in write_locked
> File "bzrlib\workingtree_4.pyo", line 197, in commit
> File "bzrlib\decorators.pyo", line 194, in write_locked
> File "bzrlib\mutabletree.pyo", line 225, in commit
> File "bzrlib\commit.pyo", line 264, in commit
> File "bzrlib\cleanup.pyo", line 118, in run
> File "bzrlib\cleanup.pyo", line 156, in _do_with_cleanups
> File "bzrlib\commit.pyo", line 338, in _commit
> File "bzrlib\commit.pyo", line 479, in _check_bound_branch
> File "bzrlib\decorators.pyo", line 140, in read_locked
> File "bzrlib\branch.pyo", line 2463, in get_master_branch
> File "bzrlib\branch.pyo", line 169, in open
> File "bzrlib\bzrdir.pyo", line 863, in open
> File "bzrlib\bzrdir.pyo", line 898, in open_from_transport
> File "bzrlib\bzrdir.pyo", line 2122, in open
> File "bzrlib\bzrdir.pyo", line 3367, in _open
> File "bzrlib\remote.pyo", line 116, in __init__
>...

[Rosemary Sumitani (mayuki-asamiya)]

The server (with 2.1.1) got stuck, but I dunno when or the reason to server
got stuck.

[]s
On Thu, Jul 1, 2010 at 10:07 PM, Martin Pool <email address hidden> wrote:

> I think this is caused by your connection dropping or being refused:
>
> > bzr: ERROR: Connection closed: Unexpected end of message. Please check
> connectivity and permissions, and report a bug if problems persist.
>
> and then for some reason we give a traceback. I thought we had fixed
> that already though.
>
> ** Tags added: hpss
>
> --
> bzr ci crashes after a bzr break-lock
> https://bugs.launchpad.net/bugs/600636
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Bazaar Version Control System: Confirmed
>
> Bug description:
> the command bzr ci has freeze, I kill the cmd.exe and typed command bzr
> break-lock
>
> bzr: ERROR: Connection closed: Unexpected end of message. Please check
> connectivity and permissions, and report a bug if problems persist.
>
> typed bzr ci
> bzr: ERROR: bzrlib.errors.TooManyConcurrentRequests: The medium
> '<bzrlib.smart.medium.SmartTCPClientMedium object at 0x02ECD430>' has
> reached its concurrent request limit. Be sure to finish_writing and
> finish_reading on the currently open request.
>
> Traceback (most recent call last):
> File "bzrlib\commands.pyo", line 907, in exception_to_return_code
> File "bzrlib\commands.pyo", line 1111, in run_bzr
> File "bzrlib\commands.pyo", line 685, in run_argv_aliases
> File "bzrlib\commands.pyo", line 700, in run
> File "bzrlib\cleanup.pyo", line 122, in run_simple
> File "bzrlib\cleanup.pyo", line 156, in _do_with_cleanups
> File "bzrlib\builtins.pyo", line 3190, in run
> File "bzrlib\decorators.pyo", line 194, in write_locked
> File "bzrlib\workingtree_4.pyo", line 197, in commit
> File "bzrlib\decorators.pyo", line 194, in write_locked
> File "bzrlib\mutabletree.pyo", line 225, in commit
> File "bzrlib\commit.pyo", line 264, in commit
> File "bzrlib\cleanup.pyo", line 118, in run
> File "bzrlib\cleanup.pyo", line 156, in _do_with_cleanups
> File "bzrlib\commit.pyo", line 338, in _commit
> File "bzrlib\commit.pyo", line 479, in _check_bound_branch
> File "bzrlib\decorators.pyo", line 140, in read_locked
> File "bzrlib\branch.pyo", line 2463, in get_master_branch
> File "bzrlib\branch.pyo", line 169, in open
> File "bzrlib\bzrdir.pyo", line 863, in open
> File "bzrlib\bzrdir.pyo", line 898, in open_from_transport
> File "bzrlib\bzrdir.pyo", line 2122, in open
> File "bzrlib\bzrdir.pyo", line 3367, in _open
> File "bzrlib\remote.pyo", line 116, in __init__
> File "bzrlib\remote.pyo", line 128, in _probe_bzrdir
> File "bzrlib\remote.pyo", line 135, in _rpc_open_2_1
> File "bzrlib\remote.pyo", line 53, in _call
> File "bzrlib\smart\client.pyo", line 132, in call
> File "bzrlib\smart\client.pyo", line 145, in call_expecting_body
> File "bzrlib\smart\client.pyo", line 90, in _call_and_read_response
> File "bzrlib\smart\client.pyo", line 45, in _send_request
> File "bzrlib\smart\client.pyo", line 115, in _construct_protocol
> File "bzrlib\smart\medium.pyo", line 705, in get_request
> File "bzrlib\smart\medium.pyo", line 918, ...

[Martin Pool (mbp)]

What happens with the server now?

--
Martin

[Martin Pool (mbp)]

To judge from the traceback this is the same as 571064 and there's no specific connection to break-lock.

[Rosemary Sumitani (mayuki-asamiya)]

The server seems stable. Didn't get this problem again. Dunno if have any connection to get server stable, but did an upgrade in client to bzr 2.2b4.