[
https://issues.apache.org/jira/browse/TAP5-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091514#comment-13091514
]
Howard M. Lewis Ship commented on TAP5-1616:
--------------------------------------------
Hey folks, I'm on vacation!
Anyway, I think I prefer the idea of a tapestry-gae module that
overrides/configures Tapestry to not spawn threads.
Perhaps tapestry-gae could modify PeriodicExecutor to be driven from an
incoming request, rather than thread pool. That is, at the end of a request,
the alternate PE could see what pending jobs are ready to run.
> PeriodicExecutor service prevents running T5.3 on GAE
> -----------------------------------------------------
>
> Key: TAP5-1616
> URL: https://issues.apache.org/jira/browse/TAP5-1616
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Kalle Korhonen
>
> Since GAE doesn't allow user-created threads, constructing PeriodicExecutor
> service fails on GAE, preventing running the whole application on it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
