[
https://issues.redhat.com/browse/WFLY-13662?page=com.atlassian.jira.plugi...
]
Cody Lerum commented on WFLY-13662:
-----------------------------------
[~manovotn] 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 but it
might even be more rare than that so I haven't been able hone in on anything to
reproduce or debug as of yet.
I'll continue to monitor and some debugging to see what if anything is creating the
conversation context.
I'm thinking something like
{code:java}
public class ScopeObservers {
static final Logger log = Logger.getLogger(ScopeObservers.class);
public void init(@Observes @Initialized(ConversationScoped.class) Object o) {
log.infof("Conversation Context Initialized for %s",
Objects.toString(o));
Thread.dumpStack();
}
} {code}
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)