[
https://issues.redhat.com/browse/WFLY-13662?page=com.atlassian.jira.plugi...
]
Matěj Novotný commented on WFLY-13662:
--------------------------------------
Hi [~clerum],
it looks like something is using conversation context, could even be some added internal
module perhaps.
Could you provide a bigger segment of the stacktrace?
Or, better still, would you be able to provide a reproducer?
FTR, WFLY 18 is Weld 3.1.2.Final while WFLY 20 is Weld 3.1.4.Final.
Possible problematic issue could be WELD-2612, however it is hard to tell without
reproducer. I am not seeing these failures in any tests weld or wfly have.
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@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)