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

Manuel K commented on MYFACES-4587:
-----------------------------------

So I've redeployed 10 times now using the 4.0.1-SNAPSHOT and the problem has 
not reappeared so far. Either I'm incredibly lucky or you managed to find the 
solution! I'll keep an eye on it.

Thank you very much, you guys are awesome!

> Intermittent deployment error on WildFly 27
> -------------------------------------------
>
>                 Key: MYFACES-4587
>                 URL: https://issues.apache.org/jira/browse/MYFACES-4587
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 4.0.0
>         Environment: Windows 10, WildFly 27.0.1
>            Reporter: Manuel K
>            Priority: Major
>         Attachments: stacktrace.txt
>
>
> When deploying our JSF application using MyFaces on WildFly 27.0.1, we 
> intermittently get the following exception:
> {code:java}
> org.jboss.weld.exceptions.IllegalArgumentException: WELD-001456: Argument 
> bean must not be null{code}
> I have attached the full stack trace.
> Debugging leads me to CDIUtils#get, where the following statement returns an 
> empty set:
> {code:java}
> bm.getBeans(clazz); // clazz is ClientWindowScopeContextualStorageHolder{code}
> It doesn't happen on every deployment but too often to ignore. Do you have 
> any insight on this?
> It happens whether 
> _org.apache.myfaces.annotation.USE_CDI_FOR_ANNOTATION_SCANNING_ is _true_ or 
> _false_ (just a wild experiment) and the following in the web.xml (another 
> wild experiment):
> {code:java}
>     <servlet>
>         <servlet-name>Faces Servlet</servlet-name>
>         <servlet-class>jakarta.faces.webapp.FacesServlet</servlet-class>
>         <load-on-startup>1</load-on-startup>
>     </servlet>{code}
> Thank you very much in advance!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to