search

vaseems / xmemcached

Automatically exported from code.google.com/p/xmemcached
Apache License 2.0
0 stars 0 forks source link

Set method with large than 30 days exp parameter #242

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. put a cache using set method with large than 30 days exp parameter (for 
example, 3*30*24*60*60).
2. get the cache with the key - the value is null.

What is the expected output? What do you see instead?
According to the memcached wiki 
-http://code.google.com/p/memcached/wiki/NewProgramming#Expiration - 
Expiration times can be set from 0, meaning "never expire", to 30 days. Any 
time higher than 30 days is interpreted as a unix timestamp date.
The exp parameter should be convert to unix timestamp date when it large than 
30 days.

What version of the product are you using? On what operating system?
Version of xmemcached - 1.3.8
Version of memcached - 1.4.13
Operation system - Linux 3.2.0-31-generic #50-Ubuntu SMP Fri Sep 7 16:16:45 UTC 
2012 x86_64 x86_64 x86_64 GNU/Linux

Original issue reported on code.google.com by tiedangy...@gmail.com on 20 Dec 2012 at 11:38

GoogleCodeExporter commented 9 years ago 
You should convert it by yourself:

3*30*24*60*60 + System. currentTimeMillis();

Original comment by killme2...@gmail.com on 8 Jan 2013 at 11:48