Closed tuanvm closed 8 years ago
Hello, are you busy Joscha? Sorry if you are busy. @joscha I created a sample app there https://github.com/tuanvm/play-authenticate-memcached-exception It's just an exist example in play-authenticate repos, just change default ehcache to memcached. Other providers as facebook are still working fine, just exception with twitter only. Thank you!
Hi @tuanvm - I just relocated from Europe to Australia, so I haven't had any time to look into issues lately - the one thing that comes to mind: memcached is not distributed, right? So if your application runs on more than one node, it can happen that data saved is on one node and the second request (when the user comes back from the oauth flow) is handled by a different node that does not have the data in store.
Hi @joscha , On our current production server, we use a cloud cache, so it's not empty data problem. Even you can run my sample app in single server at localhost, the issue is still remain there. Follow the exception log above
Caused by: java.io.InvalidClassException: com.feth.play.module.pa.providers.oauth1.OAuth1AuthProvider$SerializableRequestToken; no valid constructor
I don't know why it happened? Any idea why i got this exception. Thanks.
Should be fixed in 0.7.1
, 0.6.9
, 0.5.4
and 0.3.6
.
Hi Joscha,
I used memcached instead of Ehcache, and i've got an exception when trying to login with Twitter provider. It might happen with Oauth1 too. Here are the exception log:
Do you have any ideas to fix it? Thanks.