[jira] Commented: (TAPESTRY-1291) Race condition in IoC service creation can create runtime failures

["Howard M. Lewis Ship (JIRA)" <ta...@jakarta.apache.org>]

    [ https://issues.apache.org/jira/browse/TAPESTRY-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478126 ] 

Howard M. Lewis Ship commented on TAPESTRY-1291:
------------------------------------------------

I have a new working theory:  some or all of the errors are derived from a OutOfMemoryError thrown while inside the construction of a service.  This is somewhat consistent with what I've been seeing: an error that prevents a service from being instantiated is the only way I can think of that OneShotServiceCreator could get invoked twice (the first call sets the lock and fails, so on a second call, the OSSC is invoked again ... but fails because the lock is set).

> Race condition in IoC service creation can create runtime 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: Blocker
>             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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org