After one or two SSJS execution, some exception are thrown and play is not usable anymore

Wakanda-Demos / WakandaDB-Academy

Test Wakanda server-side javascript API with this application demo

http://play.wakanda.org/

15 stars 22 forks source link

After one or two SSJS execution, some exception are thrown and play is not usable anymore #1

Closed AMorgaut closed 11 years ago

AMorgaut commented 11 years ago

Mostly timeouts. It looks like at some point, the server restart at each request

AMorgaut commented 11 years ago

Those did not happen in the first versions, and do not happen locally. We tried reducing some recent changes to identify the origin of the problem.

Notes:

It does not come from the JS "strict mode"
The restart is apparently not generated by the zombie watcher service.
The problem looks to happen without executing calculated attribute related requests
The problem seems to happen either in the WAK3 (main branch) and the WAK4 version (WAK4-dev branch)

A serie of tests is planned on April 2 with the QA Team. I suspect we should look to other recently added features like:

the integration of the remote log service
the connection to aws stats service

AMorgaut commented 11 years ago

We've been able to isolate a bit more the origin of the problem

It doesn't come from the remote log service
neither from the aws stats service

We've been able to reproduce it on a local network (with a single user) The QA team is analysing the report we've been able to get

AMorgaut commented 11 years ago

The WAK-dev branch looks faster and more stable. Still working on issues but migration could already make it better

gery51 commented 11 years ago

Do you use proper pagination on the query ds.Employee.all() ? Its seems that the problem is generated after this query.

Does this query not overload the dom internal memory ? can you place a knob to reset the server after the query has been used ? It's very important that this application should work perfectly in order to create faith in the use of WAKANDA ! Have a nice day Alexandre !

AMorgaut commented 11 years ago

In the context of play, we had a combination of features which made WAK3 unstable. I've been working with the Wakanda QA and we fixed that in WAK4. I took this opportunity to optimize little parts of the Play code and architecture. The new version should be pushed in production today

gery51 commented 11 years ago

Thanks Alexandre, I will test again Tommorow. very goog work Op 11-apr-2013, om 11:25 heeft Alexandre Morgaut het volgende geschreven:

In the context of play, we had a combination of features which made WAK3 unstable. I've been working with the Wakanda QA and we fixed that in WAK4. I took this opportunity to optimize little parts of the Play code and architecture. The new version should be pushed in production today

— Reply to this email directly or view it on GitHub.