ICEfaces-EE
  1. ICEfaces-EE
  2. IPCK-465

Poll: There is no FacesContext on a non-JSF thread

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: EE-3.3.0.GA
    • Component/s: Samples
    • Labels:
      None
    • Environment:
      Poll, WebLogic Server cluster

      Description

      Poll's set-up of the PollMessageService happens on a different non-JSF thread when running in a WebLogic Server cluster environment. It's not possible to get to the FacesContext on this thread unless it's otherwise being cached up front.

        Activity

        Jack Van Ooststroom created issue -
        Jack Van Ooststroom made changes -
        Field Original Value New Value
        Assignee Ken Fyten [ ken.fyten ] Jack Van Ooststroom [ jack.van.ooststroom ]
        Hide
        Jack Van Ooststroom added a comment -

        Sending src/main/java/com/icesoft/faces/demo/poll/PollCollection.java
        Transmitting file data .
        Committed revision 34851.

        Show
        Jack Van Ooststroom added a comment - Sending src/main/java/com/icesoft/faces/demo/poll/PollCollection.java Transmitting file data . Committed revision 34851.
        Hide
        Jack Van Ooststroom added a comment -

        The following check has been moved to an earlier spot where the existence of JMS is checked:

        ApplicationConfiguration.getInstance().isMessagingEnabled()

        The ApplicationConfiguration.getInstance() call underneath is trying to get the FacesContext. This cannot be done on a non-JSF thread. The move actually made more sense in hindsight as well. Marking this one as FIXED.

        Show
        Jack Van Ooststroom added a comment - The following check has been moved to an earlier spot where the existence of JMS is checked: ApplicationConfiguration.getInstance().isMessagingEnabled() The ApplicationConfiguration.getInstance() call underneath is trying to get the FacesContext. This cannot be done on a non-JSF thread. The move actually made more sense in hindsight as well. Marking this one as FIXED.
        Jack Van Ooststroom made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Ken Fyten made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Jack Van Ooststroom
            Reporter:
            Jack Van Ooststroom
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: