Hi This is what i did to fix the problem as well even though is not the optimal solution
On Fri, Dec 17, 2021, 15:48 Oliver Kaiser <oliver.kai...@eddyson.de> wrote: > On 12/14/2021 10:40 PM, Dimitris Zenios wrote: > > Hi all it seems there is a raise condition when realizing lazy loaded > > services. > > > I managed to find two issues reported already with the exact same issue > > 1. https://www.mail-archive.com/users@tapestry.apache.org/msg77239.html > > > hi, > > my suggested fix only worked around the problem in one specific > situation; i do believe the root cause is still there. > > at the time my best guess was ConcurrentBarrier; specifically the logic > for upgrading the lock (R->W); which ReentrantReadWriteLock does not > support, so the code tries to work around that. > > this looks non trivial and i couldn't verify my guess, so a workaround > was the easiest choice. > > > if you want to do the same try marking your "service A" as eager load. > > > regards, > Oliver > > -- > > @Thiago: in case you are reading this; w.r.t. Java 17 (ASM update); do > you have a tool / mechanism to do that; or manually copy into "plastic" > + adjust package name? anything else that needs to be done? > > maybe i'll give that a try; no promises :-) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
