Re: [VOTE] Release Apache Meecrowave 1.2.14

2022-05-05 Thread Reinhard Sandtner 
+1

lg
reini

> Am 04.05.2022 um 09:14 schrieb Jean-Baptiste Onofré :
> 
> +1 (non binding)
> 
> Regards
> JB
> 
> On Tue, May 3, 2022 at 1:40 PM Mark Struberg  
> wrote:
>> 
>> +1
>> 
>> LieGrue,
>> strub
>> 
>> 
>>> Am 30.04.2022 um 15:21 schrieb Mark Struberg :
>>> 
>>> Hi lords and ladies!
>>> 
>>> 
>>> I'd like to call a VOTE for releasing Apache Meecrowave 1.2.14
>>> 
>>> Please note that this VOTE is depending on Johnzon-1.2.18 which is 
>>> currently under release as well.
>>> Information can be found here:
>>> https://lists.apache.org/thread/6m9zc1p60f8wod5ycj1c290835n363sh 
>>> 
>>> 
>>> 
>>> The following tickets got fixed:
>>> Improvement
>>> 
>>> [MEECROWAVE-307 ] - 
>>> Upgrade to cxf 3.5.0
>>> [MEECROWAVE-308 ] - 
>>> Upgrade to log4j 2.17.0
>>> [MEECROWAVE-309 ] - 
>>> Upgrade to Johnzon 1.2.18
>>> [MEECROWAVE-310 ] - 
>>> Upgrade to Tomcat 9.0.58
>>> [MEECROWAVE-311 ] - 
>>> Upgrade to Log4j 2.17.1
>>> Task
>>> 
>>> [MEECROWAVE-312 ] - 
>>> Upgrade to Tomcat 9.0.59
>>> [MEECROWAVE-313 ] - 
>>> Upgrade to OpenWebBeans 2.0.26
>>> [MEECROWAVE-314 ] - 
>>> Upgrade to CXF 3.5.1
>>> [MEECROWAVE-315 ] - 
>>> Upgrade to Johnzon 1.2.16
>>> [MEECROWAVE-316 ] - 
>>> Upgrade to tomcat 9.0.60
>>> [MEECROWAVE-318 ] - 
>>> CXF 3.5.2
>>> [MEECROWAVE-319 ] - 
>>> Log4j 2.17.2
>>> [MEECROWAVE-320 ] - 
>>> Upgrade to johnzon 1.2.17
>>> 
>>> 
>>> The staging repo is:
>>> https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1080/
>>>  
>>> 
>>> 
>>> The source zip can be found at
>>> https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1080/org/apache/meecrowave/meecrowave/1.2.14/
>>>  
>>> 
>>> sha1 is 5c53e44ba31213a46e6e05083ffb8f90e665be45
>>> 
>>> Please VOTE:
>>> 
>>> [+1] let's ship it!
>>> [+0] meh, don't care
>>> [-1] nope, there is a ${showstopper}
>>> 
>>> The VOTE is open for 72h
>>> 
>>> LieGrue,
>>> strub
>>> 
>>> 
>>

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

2022-05-05 Thread Ramesh Chatty (Jira) 
Ramesh Chatty created OWB-1403:
--

 Summary: 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


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



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

2022-05-05 Thread Ramesh Chatty (Jira) 


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

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

2022-05-05 Thread Romain Manni-Bucau (Jira) 


[ 
https://issues.apache.org/jira/browse/OWB-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17532143#comment-17532143
 ] 

Romain Manni-Bucau commented on OWB-1403:
-

Hi,

It is due to the fact we don't create request context upfront as before 
([https://github.com/apache/openwebbeans/commit/91edc6f3fda6f7b8d65102e9200e331eb1491ceb)]
 so depending your threading model, you can end up not having the request when 
you start using a session scoped bean and therefore the creation does not work 
as expected.

The impact an be that you don't use the session you think and that your bean 
instances are not scoped as expected.

First thing to check is whether you use the servlet container thread or another 
thread pool when it happens.

Romain

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

Re: [VOTE][RESULT] Release Apache Meecrowave 1.2.14

2022-05-05 Thread Mark Struberg 
hi!

The VOTE did pass with the following:

+1: Romain, Jean-Baptiste, Reini, Mark

No -1 nor 0 got casted.

I'll continue with the release steps.

txs and LieGrue,
strub


> Am 30.04.2022 um 15:21 schrieb Mark Struberg :
> 
> Hi lords and ladies!
> 
> 
> I'd like to call a VOTE for releasing Apache Meecrowave 1.2.14
> 
> Please note that this VOTE is depending on Johnzon-1.2.18 which is currently 
> under release as well.
> Information can be found here: 
> https://lists.apache.org/thread/6m9zc1p60f8wod5ycj1c290835n363sh 
> 
> 
> 
> The following tickets got fixed:
> Improvement
> 
> [MEECROWAVE-307 ] - 
> Upgrade to cxf 3.5.0
> [MEECROWAVE-308 ] - 
> Upgrade to log4j 2.17.0
> [MEECROWAVE-309 ] - 
> Upgrade to Johnzon 1.2.18
> [MEECROWAVE-310 ] - 
> Upgrade to Tomcat 9.0.58
> [MEECROWAVE-311 ] - 
> Upgrade to Log4j 2.17.1
> Task
> 
> [MEECROWAVE-312 ] - 
> Upgrade to Tomcat 9.0.59
> [MEECROWAVE-313 ] - 
> Upgrade to OpenWebBeans 2.0.26
> [MEECROWAVE-314 ] - 
> Upgrade to CXF 3.5.1
> [MEECROWAVE-315 ] - 
> Upgrade to Johnzon 1.2.16
> [MEECROWAVE-316 ] - 
> Upgrade to tomcat 9.0.60
> [MEECROWAVE-318 ] - CXF 
> 3.5.2
> [MEECROWAVE-319 ] - 
> Log4j 2.17.2
> [MEECROWAVE-320 ] - 
> Upgrade to johnzon 1.2.17
> 
> 
> The staging repo is:
> https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1080/
>  
> 
> 
> The source zip can be found at
> https://repository.apache.org/content/repositories/orgapacheopenwebbeans-1080/org/apache/meecrowave/meecrowave/1.2.14/
>  
> 
> sha1 is 5c53e44ba31213a46e6e05083ffb8f90e665be45
> 
> Please VOTE:
> 
> [+1] let's ship it!
> [+0] meh, don't care
> [-1] nope, there is a ${showstopper}
> 
> The VOTE is open for 72h
> 
> LieGrue,
> strub
> 
>