You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Ramesh Chatty (Jira)" <ji...@apache.org> on 2022/05/05 07:41:00 UTC

[jira] [Updated] (OWB-1403) Observed frequent logs - Could NOT lazily initialize session context because NO active request context

     [ https://issues.apache.org/jira/browse/OWB-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramesh Chatty updated OWB-1403:
-------------------------------
    Description: 
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?_

  was:
After upgrading TomEE version from  {*}8.0.6 -> 8.0.10{*}, frequently getting warnings logged as below whenever  session timeout occurs:

 
{code:java}

{code}
*org.apache.webbeans.web.context.WebContextsService lazyStartSessionContext
WARNING: Could NOT lazily initialize session context because NO active request context* 

 

 

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?_


> 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)