Edit report at https://bugs.php.net/bug.php?id=68889&edit=1
ID: 68889
Updated by: requinix@php.net
Reported by: loic dot cotonea at sogeti dot com
Summary: Serialization issue on DateTime objects by using PHP
5.4.35-0+deb7u2
-Status: Open
+Status: Feedback
Type: Bug
Package: Reflection related
Operating System: Debian Wheezy
PHP Version: 5.4.36
Block user comment: N
Private report: N
New Comment:
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.
Can anyone reproduce this on a version of PHP still in active support?
Previous Comments:
------------------------------------------------------------------------
[2016-10-19 11:41:41] adam dot conway at carus dot com
Just had this with PHP 5.4.45 on Centos 6.5. From session_start()
------------------------------------------------------------------------
[2015-04-29 11:51:06] intercity at massiveimpact dot ch
In mycase https://github.com/symfony/symfony/issues/3691#issuecomment-9831914
helped me.
I had to add the format to the serialize like so:
public function serialize() {
return \serialize(array(
$this->myDateTimeObj->format('Y-m-d H:i:s'),
------------------------------------------------------------------------
[2015-01-22 14:47:30] loic dot cotonea at sogeti dot com
Description:
------------
On the Debian Wheezy distribution, since the last update of PHP5 to the version 5.4.35-0+deb7u2, the
serialization of DateTime seems to be broken.
The problem occurs periodically and is reproducible with difficulties.
In my test environment, the problem occurs when I want to read data that are stored into the Redis
Server.
Examples:
During the authentication, when the problem occurs, the stack trace is :
[{"message":"Error: Invalid serialization data for DateTime object in
\/var\/www\/XXXX\/front\/vendor\/symfony\/symfony\/src\/Symfony\/Component\/Security\/Core\/Authentication\/Token\/AbstractToken.php
line
163","class":"Symfony\\Component\\Debug\\Exception\\FatalErrorException","trace":[{"namespace":"","short_class":"","class":"","type":"","function":"","file":"\/var\/www\/XXXX\/front\/vendor\/symfony\/symfony\/src\/Symfony\/Component\/Security\/Core\/Authentication\/Token\/AbstractToken.php","line":163,"args":[]}]}]
Another example during data retrieval from cache:
{"message":"Error: Invalid serialization data for DateTime object in
\/var\/www\/XXXX\/front\/src\/XXXX\/APIBundle\/Service\/YYYYService.php line
144","class":"Symfony\\Component\\Debug\\Exception\\FatalErrorException","trace":[{"namespace":"","short_class":"","class":"","type":"","function":"","file":"\/var\/www\/XXXX\/front\/src\/XXXX\/APIBundle\/Service\/YYYYService.php","line":144,"args":[]}]}]
I've found a recent bug report in the EZPublish project that seems to be built on Symfony 2
components: https://jira.ez.no/browse/EZP-23713.
Attached files to this issue are interesting because we have a valid and an invalid DateTime
serialization.
Then I've downgraded my Debian Wheezy PHP5 package to this version : 5.4.4-14+deb7u14 , and the
problem doesn't exists.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=68889&edit=1