ICEfaces-EE
  1. ICEfaces-EE
  2. IPCK-501

Timing of JBoss AS 6 JMS Provider start-up can cause JMS Topic to get not detected by EPS

    Details

      Description

      During JBoss AS 6.x start-up it seems possible that EPS is unable to detect the icepush JMS Topic. This causes ICEfaces applications not being able to detect and communicate with EPS and will revert to not using EPS.

        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 ]
        Jack Van Ooststroom made changes -
        Fix Version/s EE-3.3.0.GA_P02 [ 11372 ]
        Jack Van Ooststroom made changes -
        Priority Major [ 3 ] Critical [ 2 ]
        Jack Van Ooststroom made changes -
        Fix Version/s EE-4.0.0.GA [ 11071 ]
        Hide
        Jack Van Ooststroom added a comment -

        Sending icepush-ee/eps/src/main/java/com/icesoft/push/servlet/ICEpushServlet.java
        Transmitting file data .
        Committed revision 38479.

        Sending icefaces/core/src/main/java/org/icefaces/impl/push/servlet/ICEpushResourceHandler.java
        Transmitting file data .
        Committed revision 41240.

        Show
        Jack Van Ooststroom added a comment - Sending icepush-ee/eps/src/main/java/com/icesoft/push/servlet/ICEpushServlet.java Transmitting file data . Committed revision 38479. Sending icefaces/core/src/main/java/org/icefaces/impl/push/servlet/ICEpushResourceHandler.java Transmitting file data . Committed revision 41240.
        Repository Revision Date User Message
        ICEsoft Public SVN Repository #41241 Thu May 29 05:21:36 MDT 2014 jack.van.ooststroom Fixed JIRA IPCK-501 : Timing of JBoss AS 6 JMS Provider start-up can cause JMS Topic to get not detected by EPS
        Files Changed
        Commit graph MODIFY /icefaces4/trunk/icefaces/core/src/main/java/org/icefaces/impl/push/servlet/ICEpushResourceHandler.java
        Hide
        Jack Van Ooststroom added a comment -

        JMS detection by EPS on JBoss AS 6.x is now done on a separate thread, causing the caller thread to be freed for JBoss to continue its JMS provider set-up. Due to the EPS retry-mechanism the JMS provider gets detected as expected. This logic only applies to JBoss AS 6.x. Marking this one as FIXED.

        Show
        Jack Van Ooststroom added a comment - JMS detection by EPS on JBoss AS 6.x is now done on a separate thread, causing the caller thread to be freed for JBoss to continue its JMS provider set-up. Due to the EPS retry-mechanism the JMS provider gets detected as expected. This logic only applies to JBoss AS 6.x. 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: