PHP prompt PHP class x has no unserializer solution_PHP tutorial

When we use PHP caching technology, the prompt PHP class x has no unserializer will appear. Let’s introduce the solution to this problem.

PHP has been released to the stable version 5.3.8, so I am planning to upgrade PHP on the company's production server from 5.2.17 to 5.3.8. When debugging on the test server, I discovered a strange problem:

After installing the dual PHP environment, the code that originally ran normally in 5.2.17 reported an error, prompting PHP class x has no unserializer, but the same set of code used 5.3.8 on the same server without any problems. Google it I found that there was no useful information. It seemed that I had encountered an unpopular problem, so I started to debug and check step by step. I found that the error was reported in the part where memcache was used to fetch data. When fetching the data cached in memcache, it prompted that my class was not Deserialization function, but there is no problem when this line of code runs on 5.3.8.

Since the only clue is this deserialization prompt, I searched for official PHP serialization information, and first found the introduction to the serialization interface Serializable. Here I noticed that the interface has an unserializ method, this It is an excuse to call when deserializing a class. At the same time, PHP's memcache extension will serialize PHP data objects when they are stored in memcache. Is it a problem that the object I use does not implement the Serializable interface? I traced the code and found that the class I stored in memcache inherited from the Array_Object class, so I went to the official Array_Object introduction page and found that it was indeed the case,

As shown above, Array_Object has implemented the Serializable interface since 5.3.0, but it has not been implemented in 5.2. At this point, the cause of this problem is clear. The analysis is as follows:
The program runs under two versions of PHP but uses the same memcache buffer pool. The first one I tested was version 5.3.8, so what was stored was the Array_Object object of PHP5.3. This object can be serialized and reversed normally under 5.3. Serialization, then I visited the program running under PHP5.2. This is because there is already a cache object in memcache, so what 5.2 reads is the Array_Object object serialized in 5.3, but in 5.2 there is no Array_Object If you implement the Serializable interface, an error will occur during deserialization, which is why PHP class x has no unserializer is prompted.

The solution to this problem is very simple. Use a different cache pool for each program to avoid data pollution and version compatibility issues.

http://www.bkjia.com/PHPjc/632184.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/632184.htmlTechArticleWhen we use php caching technology, a prompt will appear. PHP class x has no unserializer. Let’s introduce this issue. method. PHP has reached the stable version 5.3.8, so...