I bet that is what is happening since the page makes several JDBC
queries. I should be using caching. :)
How do I add more threads to the executor? What is the default?
-James
On 06/14/2012 12:06 PM, Guillaume Bort wrote:
> Or if the action are blocked in IO (and you can't use async feature
> because you are using a blocking API like JDBC), you should add more
> threads to the executor.
>
> On 14 juin 2012, at 19:34, Sebastian <
heinz...@googlemail.com
> <mailto:
heinz...@googlemail.com>> wrote:
>
>> This happens, when play has to wait too long before getting the body
>> parser or the Result (or Promise[Result]) of an action.
>>
>> If an action needs heavy calculations, you should return a
>> asynchronous Promise[Result] instead of calculating everything before
>> returning from the action. Then play will wait for your result as long
>> as you wish.
>>
>> If for any reason you don't want to do this, you can increase the
>> waiting time in application.conf. (at the moment I can't find the
>> correct configuration key for it, but I know there is one).
>>
>> Greetings,
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "play-framework" group.
>> To view this discussion on the web visit
>>
https://groups.google.com/d/msg/play-framework/-/9GlvhlpkmxIJ.
>> To post to this group, send email to
play-fr...@googlegroups.com
>> <mailto:
play-fr...@googlegroups.com>.
>> <mailto:
play-framewor...@googlegroups.com>.
> --
> You received this message because you are subscribed to the Google
> Groups "play-framework" group.