1 of 1 people found this helpful
Being stuck for 30-45 seconds in Mojarra sounds unusual, could you post a thread dump showing the thread(s) that were stuck there?
I'm pretty sure you can remove the EJB, JSF and Weld with no effects elsewhere. The management console does not use them. What JSTL/JSP errors were you seeing afterwards?
I will replicate the Mojarra issue and will post the thread dump here in sometime...
When i remove EJB and Weld there is no issue, and glad to hear it won't break other internal's. Regarding JSTL/JSP the moment i remove JFS from the subsystem its showing NoClassDefFoundError for jstl when ever i try to access any jsp, I will post the thread dump and the Exception stacktrace in sometimes.
Then we gets.
Caused by: java.lang.NoClassDefFoundError: javax/servlet/jsp/jstl/core/Config
I have taken the thread dump for JSF Mojarra, Nothing seems to be blocking but the configuration check is taking longer time
2015-08-11 13:01:07,419 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 104) Initializing Mojarra 2.2.11-jbossorg-1 20150505-1501 for context '/portal' at this line it some times spending min 15-20 seconds or more.
We are using Wildfly.9.0.0.Final, we were not facing this delay in CR2.
well no change between CR2 and Final would suggest the behavior change you are seeing.
the CNFE looks like a bug, but looking a the code it would only be problematic if you are using JSLT api inside EAR/ejb-jar directly and not in war modules.
Sorry, its by mistake not CR2 its CR1 (we were not having issues). We don't have EJB's, wildfly started as usual but when we access the login page (its a jsp) we are getting NCDF not CNFE