Home/ Questions/Q 8164573
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-06T19:20:50+00:00

Couldn’t get FacesContext.getCurrentInstance() in self spawned thread. Required to update the components dynamically based

  • 0

Couldn’t get “FacesContext.getCurrentInstance()” in self spawned thread.

Required to update the components dynamically based on a back-end process. Achieved the same by creating a thread for monitor the process and call back the component updation along with p:poll.

However, seems “FacesContext.getCurrentInstance()” is not available for the new thread. Just getting NPE while calling any utility methods that relies with FacesContext.getCurrentInstance() from the newly spawned thread.

Is there any way to get the “FacesContext.getCurrentInstance()” available in self spawned thread?

Environment JSF2.0, Prettyfaces-jsf2-3.3.2, Primafaces 3.2, Tomcat 6.0.32, JDK 5.0

thank you,

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The FacesContext is as being a ThreadLocal<T> stored in the thread which executes the current HTTP servlet request. You definitely can’t access it in other threads which you spawned yourself, that would break the whole working of JSF/Servlet. You should instead be passing exactly that information which you need from the FacesContext in the runnable object to its constructor, perhaps just the concrete bean instance itself, or some other object which is in turn also referenced as a session attribute.

    By the way, spawning unmanaged threads in a Java EE web application is a smell. Make sure that you really understand what you’re doing. See also Is it safe to start a new thread in a JSF managed bean?

    • 0