Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: EE-3.3.0.GA_P01
-
Fix Version/s: EE-3.3.0.GA_P02, EE-4.0.0.GA
-
Component/s: Enterprise Push Server
-
Labels:None
-
Environment:JBoss AS 6.x, EPS
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
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
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.
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.