I realized that I am only using intake for the login form, so I may just
remove it for now and see if the "hanging" issue goes away - I can
manage validation on usernames/passwords easily enough in the login
action. I did verify that I have the same Login group defined in my
intake.xml file as the sample app we are generating from the turbine
webapp archetype. I plan to remove it all together from my production
version, let the app run a couple days more to see if this issue is what
is causing the app to hang or not and report back. I will also increase
my logging level for now to debug to see if anything else pops out.
I can't reproduce the bug in my IDE so may be difficult to nail down
unless you have some ideas on how to attack this problem.
--
Jeff
On 07/12/2018 09:24 AM, Jeffery Painter wrote:
Hi guys,
I just finished migrating my users over to my software two days ago
based on Turbine 4.0.1
I need to turn up the logging to debug, but I am starting to see the
"hanging" issue again where you go to the login page and the browser
keeps spinning waiting for a response from Turbine.
Here is what I am seeing in turbine.log
2018-07-11 19:20:01,126 [ajp-nio-8009-exec-22] INFO
org.apache.turbine.Turbine - Turbine: first Request successful
2018-07-11 19:20:01,326 [ajp-nio-8009-exec-22] ERROR
org.apache.turbine.services.intake.IntakeTool - Tried to release
unknown group Login
2018-07-11 21:40:01,903 [ajp-nio-8009-exec-27] ERROR
org.apache.turbine.services.intake.IntakeTool - Tried to release
unknown group Login
2018-07-11 22:00:02,028 [ajp-nio-8009-exec-30] ERROR
org.apache.turbine.services.intake.IntakeTool - Tried to release
unknown group Login
2018-07-11 22:20:01,172 [ajp-nio-8009-exec-24] ERROR
org.apache.turbine.services.intake.IntakeTool - Tried to release
unknown group Login
2018-07-12 05:20:01,140 [ajp-nio-8009-exec-26] ERROR
org.apache.turbine.services.intake.IntakeTool - Tried to release
unknown group Login
No other indication of problems. I will take a look at the IntakeTool
and see what is going on. Anyone else experiencing this issue? And
yes, I did check that caching is enabled in the TR.props for
production mode :-)
Thanks!
Jeff
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
