[ https://issues.apache.org/jira/browse/OWB-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17538663#comment-17538663 ]
Ramesh Chatty commented on OWB-1403: ------------------------------------ We will be disabling the warnings. > Observed frequent logs - Could NOT lazily initialize session context because > NO active request context > ------------------------------------------------------------------------------------------------------ > > Key: OWB-1403 > URL: https://issues.apache.org/jira/browse/OWB-1403 > Project: OpenWebBeans > Issue Type: Bug > Reporter: Ramesh Chatty > Priority: Major > > After upgrading TomEE version from {*}8.0.6 -> 8.0.10{*}, frequently getting > warnings logged as below whenever session timeout occurs: > > {code:java} > org.apache.webbeans.web.context.WebContextsService lazyStartSessionContext > WARNING: Could NOT lazily initialize session context because NO active > request context > {code} > > I have noticed one change in the *WebContextsService >> > lazyStartSessionContext* method, where the parameter is sending as *false* > for *getRequestContext(false)* method in *openwebbeans-web-2.0.26.jar* with > in *TomEE-8.0.10* , where as this value is sent as *true* in > *openwebbeans-web-2.0.12.jar* with in *TomEE-8.0.6* > > _Can you please suggest how to handle this scenario? Also are there any other > impact scenarios we may be missing due to this change?_ -- This message was sent by Atlassian Jira (v8.20.7#820007)