php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #60646 Recursive request with same session fails
Submitted: 2012-01-03 19:10 UTC Modified: 2013-06-29 14:30 UTC
Votes:4
Avg. Score:3.8 ± 0.8
Reproduced:3 of 3 (100.0%)
Same Version:2 (66.7%)
Same OS:2 (66.7%)
From: lgandras at gmail dot com Assigned:
Status: Not a bug Package: Session related
PHP Version: 5.3.8 OS: Centos 5.4
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: lgandras at gmail dot com
New email:
PHP Version: OS:

 

 [2012-01-03 19:10 UTC] lgandras at gmail dot com 
Description:
------------
Hi,

When a request issues another request to same domain sending the same cookie (e.g. Cookie: PHPSESSID=f2e6bd70963b37243d6be566a6d3adc1). The inner request timeouts throwing a "Warning: Unknown: Error occured while closing statement in Unknown on line 0" occurs.

I suspect this has to do with the fact that the session file is being locked. If the documentation says it somewhere, at least the error thrown should be more specific.

Expected result:
----------------
Dont'know, but if error, a detailed one.

Actual result:
--------------
Warning: Unknown: Error occured while closing statement in Unknown on line 0

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2012-05-05 21:33 UTC] scampbell525 at gmail dot com 
PHP version 5.3.10
This is not an issue on my localhost using WAMP, but when migrated to a LAMP stack on the web host, it becomes an issue.
 [2013-03-19 10:55 UTC] cnam dot cdel at free dot fr 
I got the same problem with Lamp / PHP Version 5.3.3-7+squeeze14
 [2013-06-27 21:25 UTC] arpad@php.net
-Status: Open +Status: Feedback
 [2013-06-27 21:25 UTC] arpad@php.net 
Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php for *NIX and
http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32

Once you have generated a backtrace, please submit it to this bug
report and change the status back to "Open". Thank you for helping
us make PHP better.
 [2013-06-27 21:26 UTC] arpad@php.net 
Er, clicked the wrong option..
 [2013-06-27 21:26 UTC] arpad@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.
 [2013-06-29 14:30 UTC] johannes@php.net
-Status: Feedback +Status: Not a bug
 [2013-06-29 14:30 UTC] johannes@php.net 
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php

When starting a session it is being locked to prevent concurrent access and loosing state. My suggestion is to use another mechanism to transfer the required data. If you really want parallel access you can use session_write_close() and lateron session-start() again.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Tue Apr 30 02:01:31 2024 UTC