Hi Jeffery,

On 02.04.18 19:41, Jeffery Painter wrote:
> I suspect the problem was with the lifecycle of the FluxTool I had built
> for the turbine-webapp - I just pushed a change to the SVN repo (modeled
> it more closely after the Intake tool's dispose lifecycle).  I will test
> a couple more days and see if this fixes the stalling bug I have been
> seeing.

Especially when service injection is used extensively, it is important
to set module.cache=true in TR.props. It looks like the following
sequence repeats a lot:

>> 2018-03-31 21:20:43,037 [http-nio-8080-exec-70] DEBUG
>> org.apache.turbine.annotation.AnnotationProcessor - Looking up service
>> for injection: org.apache.fulcrum.localization.LocalizationService for
>> object org.apache.turbine.services.localization.LocalizationTool@bc7a8a9
>> 2018-03-31 21:20:43,037 [http-nio-8080-exec-70] DEBUG
>> org.apache.turbine.annotation.AnnotationProcessor - Injection of
>> org.apache.fulcrum.localization.LocalizationService into object
>> org.apache.turbine.services.localization.LocalizationTool@bc7a8a9
>> 2018-03-31 21:20:43,037 [http-nio-8080-exec-70] DEBUG
>> org.apache.turbine.annotation.AnnotationProcessor - Looking up service
>> for injection: org.apache.fulcrum.intake.IntakeService for object
>> org.apache.turbine.services.intake.IntakeTool@4489ce5c
>> 2018-03-31 21:20:43,037 [http-nio-8080-exec-70] DEBUG
>> org.apache.turbine.annotation.AnnotationProcessor - Injection of
>> org.apache.fulcrum.intake.IntakeService into object
>> org.apache.turbine.services.intake.IntakeTool@4489ce5c

This may help with lifecycle issues, too.

Bye, Thomas.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to