[
https://issues.apache.org/jira/browse/EXTCDI-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg reopened EXTCDI-38:
---------------------------------
The problem here is that my page doesn't have any CODI bean at all.
In this case we will get an 'unused' windowContext at the end of the request.
We should be able to clean this up in DefaultWindowContextManager.
Also I'm not sure if we should really throw an Exception in the case of
exceeding the contexts limit. What about wiping out the context which wasn't
used for the longest time instead (+ logging a warning)?
> @ViewAccessScoped creates new conversation context each time it get's
> involked via GET
> --------------------------------------------------------------------------------------
>
> Key: EXTCDI-38
> URL: https://issues.apache.org/jira/browse/EXTCDI-38
> Project: MyFaces CODI
> Issue Type: Bug
> Components: JEE-JSF12-Module, JEE-JSF20-Module
> Affects Versions: 1.0.0-SNAPSHOT
> Reporter: Mark Struberg
>
> When a page gets invoked via a direct GET, I get the following Exception
> pretty quickly while testing with jmeter:
> java.lang.RuntimeException: Too many active Windows/Tabs have been opened!
> Please continue with one of the existing windows or wait up to 60 minutes.
> at
> org.apache.myfaces.extensions.cdi.javaee.jsf.impl.util.ExceptionUtils.tooManyOpenWindowException(ExceptionUtils.java:28)
> at
> org.apache.myfaces.extensions.cdi.javaee.jsf.impl.scope.conversation.DefaultWindowContextManager.createNewWindowContextId(DefaultWindowContextManager.java:227)
> at
> org.apache.myfaces.extensions.cdi.javaee.jsf.impl.scope.conversation.DefaultWindowContextManager.getCurrentWindowContext(DefaultWindowContextManager.java:207)
> My page is a typical search page which is @ViewScoped, so no context handling
> is needed at all in this case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
