[
https://issues.apache.org/jira/browse/TAPESTRY-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship updated TAPESTRY-1291:
-------------------------------------------
Fix Version/s: 5.0.3
Assignee: Howard M. Lewis Ship
Priority: Critical (was: Major)
Seeing this in the logs:
Construction of service 'tapestry.internal.ActionLinkHandler' has failed due to
recursion: the service depends on itself in some way. Please check
org.apache.tapestry.internal.services.InternalModule.buildActionLinkHandler(ComponentEventResultProcessor)
for references to another service that is itself dependent on service
'tapestry.internal.ActionLinkHandler'.
With a stack trace of:
org.apache.tapestry.ioc.internal.OneShotServiceCreator.createObject(OneShotServiceCreator.java:52)
org.apache.tapestry.internal.services.ComponentActionDispatcher.dispatch(ComponentActionDispatcher.java:115)
org.apache.tapestry.services.TapestryModule$5.service(TapestryModule.java:479)
org.apache.tapestry.integration.app1.services.AppModule$1.service(AppModule.java:50)
org.apache.tapestry.services.TapestryModule$6.service(TapestryModule.java:514)
org.apache.tapestry.internal.services.StaticFilesFilter.service(StaticFilesFilter.java:56)
org.apache.tapestry.internal.services.LocalizationFilter.service(LocalizationFilter.java:43)
org.apache.tapestry.internal.services.CheckForUpdatesFilter$2.invoke(CheckForUpdatesFilter.java:91)
org.apache.tapestry.internal.services.CheckForUpdatesFilter$2.invoke(CheckForUpdatesFilter.java:82)
org.apache.tapestry.ioc.internal.util.ConcurrentBarrier.withRead(ConcurrentBarrier.java:77)
org.apache.tapestry.internal.services.CheckForUpdatesFilter.service(CheckForUpdatesFilter.java:104)
org.apache.tapestry.services.TapestryModule$3.service(TapestryModule.java:402)
org.apache.tapestry.TapestryFilter.doFilter(TapestryFilter.java:114)
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
(the stack traces now edit out the IoC proxy classes)
Something is certainly odd here!
> Flaw in application startup causes continuous integration failures
> ------------------------------------------------------------------
>
> Key: TAPESTRY-1291
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1291
> Project: Tapestry
> Issue Type: Bug
> Components: Core, IoC Container
> Affects Versions: 5.0
> Reporter: Howard M. Lewis Ship
> Assigned To: Howard M. Lewis Ship
> Priority: Critical
> Fix For: 5.0.3
>
>
> Even on my Mac, I occasionally get spurious failures of the integration tests.
> Seems to be some kind of race condition at application startup, where
> construction of some key service fails, claiming (spuriously) to be dependent
> on itself.
> The CI server, tapestry.formos.com, seems very succeptible to this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
