[
https://issues.apache.org/jira/browse/TAP5-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091331#comment-13091331
]
Robert Zeigler commented on TAP5-1616:
--------------------------------------
Hm, I think the main issues with soft references are in this paragraph of the
java docs for soft references:
"All soft references to softly-reachable objects are guaranteed to have been
cleared before the virtual machine throws an OutOfMemoryError. Otherwise no
constraints are placed upon the time at which a soft reference will be cleared
or the order in which a set of such references to different objects will be
cleared. Virtual machine implementations are, however, encouraged to bias
against clearing recently-created or recently-used soft references."
(http://download.oracle.com/javase/1.5.0/docs/api/java/lang/ref/SoftReference.html)
1) There is no constraint to remove the references unless memory becomes taxed;
they might be removed, they might not be.
2) Although VM implementations are "encouraged" to bias toward collecting "old"
references first, strictly speaking, there's no guarantee.
> 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
