[jboss-jira] [JBoss JIRA] (WFLY-13662) Weld Conversation Context Logs when not using Conversation Context

Matěj Novotný (Jira) issues at jboss.org
Mon Jul 13 10:39:01 EDT 2020


    [ https://issues.redhat.com/browse/WFLY-13662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228673#comment-14228673 ] 

Matěj Novotný commented on WFLY-13662:
--------------------------------------

bq. when any page with a view scoped bean is loaded it appears to trigger an @Initialized event for ConversationScoped...

This is strange. {{@ConversationScoped}} and {{@ViewScoped}} are two different things. I don't see how using one triggers another.
Though I don't really know how JSF implements views scoped (that scope is *not* part of built-in CDI scopes, therefore CDI doesn't control it). It could be that they are using conversations to handle view scoped lifecycle, although it sounds a bit crazy.

bq. I'm guessing this is just how the Lazy Initialization works

No, that shouldn't be the case. Lazy init is all about not actually creating or restoring the context until you first attempt to access conversation context bean.

bq. Unfortunately it's just log messages that are printed and not stack traces and it is pretty rare at this point I'm guessing one out of 10000 requests

Ah, ok. So its intermittent. From issue description I originally thought you can reproduce that every time.

> Weld Conversation Context Logs when not using Conversation Context
> ------------------------------------------------------------------
>
>                 Key: WFLY-13662
>                 URL: https://issues.redhat.com/browse/WFLY-13662
>             Project: WildFly
>          Issue Type: Bug
>          Components: CDI / Weld, JSF
>    Affects Versions: 20.0.1.Final
>            Reporter: Cody Lerum
>            Assignee: Matěj Novotný
>            Priority: Major
>
> After upgrading to Widfly 20.0.1 from 18.0.1 I'm starting to receive show log errors regarding the CDI conversation context even though it is not used anywhere in the application.
> These did not present in the same application in 18.0.1.Final
> {code:java}
> 020-07-10 15:42:47,561 ERROR [io.undertow.request] (default task-273) UT005023: Exception handling request to /s/c/voice/fax/view.xhtml: java.lang.NullPointerException2020-07-10 15:42:47,562 WARN  [org.jboss.weld.Servlet] (default task-273) WELD-000717: Unable to deactivate context org.jboss.weld.module.web.context.http.LazyHttpConversationContextImpl at 25333df0 when destroying request HttpServletRequestImpl [ GET /s/c/voice/fax/view.xhtml ]
> 2020-07-10 15:42:48,165 WARN  [org.jboss.weld.Conversation] (default task-273) WELD-000335: Conversation context is already active, most likely it was not cleaned up properly during previous request processing: HttpServletRequestImpl [ GET /i/ticket/46893 ] {code}



--
This message was sent by Atlassian Jira
(v7.13.8#713008)



More information about the jboss-jira mailing list