#50378 [Bgs]: msg_receive() blocks next requests to the same URL
ID: 50378
User updated by: dimitri dot ho at gmail dot com
Reported By: dimitri dot ho at gmail dot com
Status: Bogus
Bug Type: Semaphore related
Operating System: Linux
PHP Version: 5.2.11
New Comment:
I forgot a detail. When requesting the second time, you must open it in
a new window or tab. The first request must be blocked (which is an
expected behavior) while you make the second request with the same URL
(which should create another file then block, but it just blocks).
Previous Comments:
------------------------------------------------------------------------
[2009-12-07 18:51:17] jani@php.net
Well, it works fine. Quite likely the issue has nothing to do with
semaphores.
------------------------------------------------------------------------
[2009-12-04 08:49:28] dimitri dot ho at gmail dot com
I meant the script can reproduce the bug, and was not incomplete. It
doesn't work as I expected.
------------------------------------------------------------------------
[2009-12-04 08:20:20] jani@php.net
Exactly, it works like you want so what's the bug here?
------------------------------------------------------------------------
[2009-12-04 07:16:31] dimitri dot ho at gmail dot com
Actually, the script was complete and worked. :)
<?php
file_put_contents("/tmp/" . uniqid('moo') . '.txt', __FILE__);
$queue = msg_get_queue(123456);
msg_receive($queue, 1, $msgType, 1024, $var);
?>
------------------------------------------------------------------------
[2009-12-04 04:42:55] jani@php.net
Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves.
A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external
resources such as databases, etc. If the script requires a
database to demonstrate the issue, please make sure it creates
all necessary tables, stored procedures etc.
Please avoid embedding huge scripts into the report.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/50378
--
Edit this bug report at http://bugs.php.net/?id=50378&edit=1
Thread (7 messages)