You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@turbine.apache.org by Jeffery Painter <je...@jivecast.com> on 2018/04/01 15:44:47 UTC

Re: Turbine 4.0.1 seems to "stall" after long period

Hi Thomas,

It happened again.  I have 3 Turbine 4.0.1 apps running on the same 
Tomcat 8.5 instance.  I had just uploaded a new version of the software 
yesterday at 2:52pm.  A friend came over, I showed him my software and 
we logged out at 9:20pm.

I checked the logs.  There was no attempted access between 9:20pm and 
this morning (almost 12 hours later) at 9:58am.

I went to the login screen, and it just hangs. The other two 
applications are running fine.  I tried kill -3 <pid> but it didn't 
actually kill the tomcat instance. Instead, I went back to the tomcat 
manager, hit "reload" on the app, and it started responding fine again.

The application.log file shows the following behavior now:


-- last calls to the server last night around 9:20pm...

2018-03-31 21:20:43,037 [http-nio-8080-exec-70] DEBUG 
org.apache.turbine.util.ServerData - setServerScheme(http)
2018-03-31 21:20:43,037 [http-nio-8080-exec-70] DEBUG 
org.apache.turbine.util.ServerData - setScriptName(/app)
2018-03-31 21:20:43,037 [http-nio-8080-exec-70] DEBUG 
org.apache.turbine.util.ServerData - setContextPath(/smarttext)
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
-- end of activity from March-31

-- first call to the server on April-01 at 9:58am

2018-04-01 09:58:35,249 [ajp-nio-8009-exec-59] DEBUG 
org.apache.turbine.Turbine - Changing Input Encoding to UTF-8
2018-04-01 09:58:35,249 [ajp-nio-8009-exec-59] DEBUG 
org.apache.turbine.util.ServerData - setServerName(dev.jivecast.com)
2018-04-01 09:58:35,249 [ajp-nio-8009-exec-59] DEBUG 
org.apache.turbine.util.ServerData - setServerPort(443)
2018-04-01 09:58:35,249 [ajp-nio-8009-exec-59] DEBUG 
org.apache.turbine.util.ServerData - setServerScheme(https)
2018-04-01 09:58:35,249 [ajp-nio-8009-exec-59] DEBUG 
org.apache.turbine.util.ServerData - setScriptName(/app)
2018-04-01 09:58:35,249 [ajp-nio-8009-exec-59] DEBUG 
org.apache.turbine.util.ServerData - setContextPath(/smarttext)
2018-04-01 09:58:35,249 [ajp-nio-8009-exec-59] DEBUG 
org.apache.turbine.pipeline.DetermineActionValve - No action
.
.
.
2018-04-01 09:58:35,278 [ajp-nio-8009-exec-59] DEBUG 
org.apache.turbine.util.ServerData - Copy 
Constructor(https://dev.jivecast.com/smarttext/app)
2018-04-01 09:58:35,278 [ajp-nio-8009-exec-59] DEBUG 
org.apache.turbine.util.ServerData - setServerName(dev.jivecast.com)
2018-04-01 09:58:35,278 [ajp-nio-8009-exec-59] DEBUG 
org.apache.turbine.util.ServerData - setServerPort(443)
2018-04-01 09:58:35,278 [ajp-nio-8009-exec-59] DEBUG 
org.apache.turbine.util.ServerData - setServerScheme(https)
2018-04-01 09:58:35,278 [ajp-nio-8009-exec-59] DEBUG 
org.apache.turbine.util.ServerData - setScriptName(/app)
2018-04-01 09:58:35,278 [ajp-nio-8009-exec-59] DEBUG 
org.apache.turbine.util.ServerData - setContextPath(/smarttext)
2018-04-01 09:58:35,278 [ajp-nio-8009-exec-59] DEBUG 
org.apache.turbine.annotation.AnnotationProcessor - Looking up service 
for injection: org.apache.fulcrum.localization.LocalizationService for 
object org.apache.turbine.services.localization.LocalizationTool@2e2f2614
2018-04-01 09:58:35,278 [ajp-nio-8009-exec-59] DEBUG 
org.apache.turbine.annotation.AnnotationProcessor - Injection of 
org.apache.fulcrum.localization.LocalizationService into object 
org.apache.turbine.services.localization.LocalizationTool@2e2f2614
2018-04-01 09:58:35,278 [ajp-nio-8009-exec-59] DEBUG 
org.apache.turbine.annotation.AnnotationProcessor - Looking up service 
for injection: org.apache.fulcrum.intake.IntakeService for object 
org.apache.turbine.services.intake.IntakeTool@6d9097ee
2018-04-01 09:58:35,278 [ajp-nio-8009-exec-59] DEBUG 
org.apache.turbine.annotation.AnnotationProcessor - Injection of 
org.apache.fulcrum.intake.IntakeService into object 
org.apache.turbine.services.intake.IntakeTool@6d9097ee

--- Application just stops here.... --- Subsequent calls are stopping at 
the same point

2018-04-01 09:59:31,661 [ajp-nio-8009-exec-63] DEBUG 
org.apache.turbine.Turbine - Changing Input Encoding to UTF-8
2018-04-01 09:59:31,661 [ajp-nio-8009-exec-63] DEBUG 
org.apache.turbine.util.ServerData - setServerName(dev.jivecast.com)
2018-04-01 09:59:31,661 [ajp-nio-8009-exec-63] DEBUG 
org.apache.turbine.util.ServerData - setServerPort(443)
2018-04-01 09:59:31,661 [ajp-nio-8009-exec-63] DEBUG 
org.apache.turbine.util.ServerData - setServerScheme(https)
2018-04-01 09:59:31,661 [ajp-nio-8009-exec-63] DEBUG 
org.apache.turbine.util.ServerData - setScriptName(/app)
2018-04-01 09:59:31,661 [ajp-nio-8009-exec-63] DEBUG 
org.apache.turbine.util.ServerData - setContextPath(/smarttext)
2018-04-01 09:59:31,661 [ajp-nio-8009-exec-63] DEBUG 
org.apache.turbine.pipeline.DetermineActionValve - No action
2018-04-01 09:59:31,661 [ajp-nio-8009-exec-63] DEBUG 
org.apache.turbine.pipeline.DetermineActionValve - Action is now:
2018-04-01 09:59:31,661 [ajp-nio-8009-exec-63] DEBUG 
org.apache.turbine.pipeline.DetermineTargetValve - No target screen
2018-04-01 09:59:31,661 [ajp-nio-8009-exec-63] DEBUG 
org.apache.turbine.pipeline.DetermineTargetValve - Screen Target is now:
2018-04-01 09:59:31,661 [ajp-nio-8009-exec-63] DEBUG 
org.apache.turbine.services.assemblerbroker.TurbineAssemblerBrokerService 
- Loading class 
org.apache.turbine.modules.Action:sessionvalidator.TemplateSessionValidator

.
.
.

2018-04-01 09:59:31,676 [ajp-nio-8009-exec-63] DEBUG 
org.apache.turbine.util.ServerData - setContextPath(/smarttext)
2018-04-01 09:59:31,676 [ajp-nio-8009-exec-63] DEBUG 
org.apache.turbine.annotation.AnnotationProcessor - Looking up service 
for injection: org.apache.fulcrum.localization.LocalizationService for 
object org.apache.turbine.services.localization.LocalizationTool@5b07b50e
2018-04-01 09:59:31,676 [ajp-nio-8009-exec-63] DEBUG 
org.apache.turbine.annotation.AnnotationProcessor - Injection of 
org.apache.fulcrum.localization.LocalizationService into object 
org.apache.turbine.services.localization.LocalizationTool@5b07b50e
2018-04-01 09:59:31,677 [ajp-nio-8009-exec-63] DEBUG 
org.apache.turbine.annotation.AnnotationProcessor - Looking up service 
for injection: org.apache.fulcrum.intake.IntakeService for object 
org.apache.turbine.services.intake.IntakeTool@389175eb
2018-04-01 09:59:31,677 [ajp-nio-8009-exec-63] DEBUG 
org.apache.turbine.annotation.AnnotationProcessor - Injection of 
org.apache.fulcrum.intake.IntakeService into object 
org.apache.turbine.services.intake.IntakeTool@389175eb

-- fails to process any further but still listening...


After reload, it will go past this point and the relevant injection 
steps it takes are show below (which do execute properly)

2018-04-01 11:17:11,167 [ajp-nio-8009-exec-64] DEBUG 
org.apache.turbine.util.ServerData - setContextPath(/smarttext)
2018-04-01 11:17:11,168 [ajp-nio-8009-exec-64] DEBUG 
org.apache.turbine.annotation.AnnotationProcessor - Looking up service 
for injection: org.apache.fulcrum.localization.LocalizationService for 
object org.apache.turbine.services.localization.LocalizationTool@7eb80b1d
2018-04-01 11:17:11,168 [ajp-nio-8009-exec-64] DEBUG 
org.apache.turbine.annotation.AnnotationProcessor - Injection of 
org.apache.fulcrum.localization.LocalizationService into object 
org.apache.turbine.services.localization.LocalizationTool@7eb80b1d
2018-04-01 11:17:11,168 [ajp-nio-8009-exec-64] DEBUG 
org.apache.turbine.annotation.AnnotationProcessor - Looking up service 
for injection: org.apache.fulcrum.intake.IntakeService for object 
org.apache.turbine.services.intake.IntakeTool@563e26b0
2018-04-01 11:17:11,168 [ajp-nio-8009-exec-64] DEBUG 
org.apache.turbine.annotation.AnnotationProcessor - Injection of 
org.apache.fulcrum.intake.IntakeService into object 
org.apache.turbine.services.intake.IntakeTool@563e26b0
2018-04-01 11:17:11,170 [ajp-nio-8009-exec-64] DEBUG 
org.apache.turbine.annotation.AnnotationProcessor - Looking up service 
for injection: SecurityService for object 
com.jivecast.smarttext.flux.tools.FluxTool@72834b31
2018-04-01 11:17:11,170 [ajp-nio-8009-exec-64] DEBUG 
org.apache.turbine.annotation.AnnotationProcessor - Injection of 
SecurityService into object 
com.jivecast.smarttext.flux.tools.FluxTool@72834b31
2018-04-01 11:17:11,170 [ajp-nio-8009-exec-64] DEBUG 
org.apache.turbine.annotation.AnnotationProcessor - Injection of 
org.apache.commons.configuration.PropertiesConfiguration@10b3d93b into 
object com.jivecast.smarttext.flux.tools.FluxTool@72834b31
2018-04-01 11:17:11,170 [ajp-nio-8009-exec-64] DEBUG 
org.apache.turbine.services.pull.TurbinePullService - Adding 
org.apache.turbine.services.pull.util.SessionData@708a648a to ctx as 
sessionData
2018-04-01 11:17:11,172 [ajp-nio-8009-exec-64] DEBUG 
org.apache.turbine.services.template.mapper.LayoutTemplateMapper - 
doMapping(Login.vm)
2018-04-01 11:17:11,172 [ajp-nio-8009-exec-64] DEBUG 
org.apache.turbine.services.template.mapper.LayoutTemplateMapper - 
templateName is Login.vm
2018-04-01 11:17:11,172 [ajp-nio-8009-exec-64] DEBUG 
org.apache.turbine.services.template.mapper.LayoutTemplateMapper - 
templatePackage is now:
2018-04-01 11:17:11,172 [ajp-nio-8009-exec-64] DEBUG 
org.apache.turbine.services.template.mapper.LayoutTemplateMapper - 
Looking for layouts/Login.vm
2018-04-01 11:17:11,172 [ajp-nio-8009-exec-64] DEBUG 
org.apache.turbine.services.template.mapper.LayoutTemplateMapper - 
templatePackage is now:
2018-04-01 11:17:11,172 [ajp-nio-8009-exec-64] DEBUG 
org.apache.turbine.services.template.mapper.LayoutTemplateMapper - 
Looking for layouts/Default.vm
2018-04-01 11:17:11,172 [ajp-nio-8009-exec-64] DEBUG 
org.apache.turbine.services.template.mapper.LayoutTemplateMapper - Found 
it, returning Default.vm
2018-04-01 11:17:11,172 [ajp-nio-8009-exec-64] DEBUG 
org.apache.turbine.services.template.mapper.ClassMapper - 
doMapping(Login.vm)
2018-04-01 11:17:11,172 [ajp-nio-8009-exec-64] DEBUG 
org.apache.turbine.services.template.mapper.ClassMapper - className is 
Login.vm
2018-04-01 11:17:11,172 [ajp-nio-8009-exec-64] DEBUG 
org.apache.turbine.services.template.mapper.ClassMapper - classPackage 
is now:
2018-04-01 11:17:11,172 [ajp-nio-8009-exec-64] DEBUG 
org.apache.turbine.services.template.mapper.ClassMapper - Looking for Login

.
.
.
etc...

I am wondering if there is something I may have configured wrong in the 
lifecycle of my FluxTool code.  I am using the same as what I had put on 
github, so Georg, if you have had a chance to look at it, do you see 
anything wrong with how I set it up?

https://github.com/jlpainter/turbine-flux/blob/master/src/main/flux/org/apache/turbine/flux/tools/FluxTool.java

In TR.props, I have it loading as a request tool:

#
# Custom tools
#
tool.request.flux=com.jivecast.smarttext.flux.tools.FluxTool


--
Jeffery







On 03/30/2018 03:41 AM, Thomas Vandahl wrote:
> Hi Jeffery,
>
> On 27.03.18 15:49, Jeffery Painter wrote:
>> After some period (>24 hours), when I go to login to the Turbine app, it
>> just sits there and hangs. I am going to increase the log levels to
>> debug, but I don't see any immediate errors popping up. It just hangs on
>> trying to process the user login action.  If I go into the Tomcat admin
>> manager and stop/start the app, it works again and will process user
>> logins.  I think this is a pretty critical issue.
> If you want to debug this, you may force a thread dump from the command
> line (kill -3 <java-pid>) and see if some locked thread looks familiar.
>
> Bye, Thomas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
> For additional commands, e-mail: dev-help@turbine.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org

Re: [VOTE][GIT] Use (writable) gitbox, start with for Turbine Archetypes

Posted by Thomas Vandahl <tv...@apache.org>.

On 14.05.18 11:47, Georg Kallidis wrote:
> Before more time is wasted, I would like to do this as a vote (procedural 
> type, i.e. majority vote would apply).
> 
> [ ] +1 yes, start using gitbox in general, start the migration to a 
> writeable git repo with one svn repo (turbine archetypes or another one), 
> connect to github and check using more github features, use this feature 
> optionally for more git repos, if needed.
> [X] 0 don't care
> [ ] -1 no, because.

Bye, Thomas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org

Re: [VOTE][GIT] Use (writable) gitbox, start with for Turbine Archetypes

Posted by Georg Kallidis <ge...@cedis.fu-berlin.de>.

[x] +1 yes, start using gitbox in general, start the migration to a 
writeable git repo with one svn repo (turbine archetypes or another one), 
connect to github and check using more github features, use this feature 
optionally for more git repos, if needed.
[ ] 0 don't care
[ ] -1 no, because

-Georg



Von:    "Georg Kallidis" <ge...@cedis.fu-berlin.de>
An:     "Turbine Developers List" <de...@turbine.apache.org>
Kopie:  private@turbine.apache.org
Datum:  14.05.2018 11:47
Betreff:        [VOTE][GIT] Use (writable) gitbox, start with for Turbine 
Archetypes



Hi all, 

As I am in the process to get a GIT clone for Turbine webapp repo, cft. 
INFRA-16437 and reading the last comment 

https://issues.apache.org/jira/browse/INFRA-16437?focusedCommentId=16472623&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16472623


we might consider to migrate Turbine Webapp as a _writeable_ GIT repo to 
apache gitbox! (gitbox.apache.org = "GitHub Dual Master", not Git Wip, 
although only the latter is mentioned in 
https://www.apache.org/dev/writable-git). I think gitbox is just more 
git-centric, the release is done completely with git. Dind one example 
discussion here:
https://mail-archives.apache.org/mod_mbox/infra-issues/201804.mbox/%3CJIRA.13152162.1523589032000.359092.1524717900079@Atlassian.JIRA%3E



This is just implemented as a self service, i.e. we could do this ourself 
(at one point of time), but we are completely free to do it as we like it 
(IMO), even as a SVN backed GIT, cft. 
https://wiki.apache.org/general/GitAtApache, which might not be the 
recommended way IMO.

I would suggest to start with cloning/importing (not the main project) 
just the svn repo

https://svn.apache.org/repos/asf/turbine/maven/archetypes to the gitbox as 

turbine-archetypes-git.

The GitHub - Connection could then be done at any time later as far as I 
can see. 

We may decide to do it before the next release to perform a git release 
(@Jeffery)? 

Before more time is wasted, I would like to do this as a vote (procedural 
type, i.e. majority vote would apply).

[ ] +1 yes, start using gitbox in general, start the migration to a 
writeable git repo with one svn repo (turbine archetypes or another one), 
connect to github and check using more github features, use this feature 
optionally for more git repos, if needed.
[ ] 0 don't care
[ ] -1 no, because.

If there are any further compatible/consistent suggestions and they match 
the general direction, I would just continue the process.

Thanks and...

Best regards, Georg

Re: [VOTE][GIT] Use (writable) gitbox, start with for Turbine Archetypes

Posted by Jeffery Painter <je...@jivecast.com>.

Hi Georg,

Sorry I have been quiet on the list.  I (thankfully) have a new 
contract, so my time has been diverted for the next couple weeks.

> [X] +1 yes, start using gitbox in general, start the migration to a
> writeable git repo with one svn repo (turbine archetypes or another one),
> connect to github and check using more github features, use this feature
> optionally for more git repos, if needed.
> [ ] 0 don't care
> [ ] -1 no, because.
>

Adding to your vote!  I hope to be free again soon to help out.



--
Jeff


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org

[VOTE][GIT] Use (writable) gitbox, start with for Turbine Archetypes

Posted by Georg Kallidis <ge...@cedis.fu-berlin.de>.

Hi all,

As I am in the process to get a GIT clone for Turbine webapp repo, cft.
INFRA-16437 and reading the last comment

https://issues.apache.org/jira/browse/INFRA-16437?focusedCommentId=16472623&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16472623

we might consider to migrate Turbine Webapp as a _writeable_ GIT repo to
apache gitbox! (gitbox.apache.org = "GitHub Dual Master", not Git Wip,
although only the latter is mentioned in
https://www.apache.org/dev/writable-git). I think gitbox is just more
git-centric, the release is done completely with git. Dind one example
discussion here:
https://mail-archives.apache.org/mod_mbox/infra-issues/201804.mbox/%3CJIRA.13152162.1523589032000.359092.1524717900079@Atlassian.JIRA%3E

This is just implemented as a self service, i.e. we could do this ourself
(at one point of time), but we are completely free to do it as we like it
(IMO), even as a SVN backed GIT, cft.
https://wiki.apache.org/general/GitAtApache, which might not be the
recommended way IMO.

I would suggest to start with cloning/importing (not the main project)
just the svn repo

https://svn.apache.org/repos/asf/turbine/maven/archetypes to the gitbox as
turbine-archetypes-git.

The GitHub - Connection could then be done at any time later as far as I
can see.

We may decide to do it before the next release to perform a git release
(@Jeffery)?

Before more time is wasted, I would like to do this as a vote (procedural
type, i.e. majority vote would apply).

[ ] +1 yes, start using gitbox in general, start the migration to a
writeable git repo with one svn repo (turbine archetypes or another one),
connect to github and check using more github features, use this feature
optionally for more git repos, if needed.
[ ] 0 don't care
[ ] -1 no, because.

If there are any further compatible/consistent suggestions and they match
the general direction, I would just continue the process.

Thanks and...

Best regards, Georg