Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 3.3, EE-3.3.0.GA_P01
-
Fix Version/s: 4.0.BETA, EE-3.3.0.GA_P02
-
Component/s: Push Library
-
Labels:None
-
Environment:ICEpush
Description
It is possible for creating a BlockingConnectionServer that maps to a BrowserID set to null. This is incorrect and due to the ConfigurationServer being down the chain too far. It should be moved up to before a BlockingConnectionServer is created to ensure the incoming Request contains the ice.push.browser.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #37782 | Thu Sep 05 08:27:04 MDT 2013 | jack.van.ooststroom | Fixed JIRA |
| Files Changed | ||||
MODIFY
/icepush/trunk/icepush/core/src/main/java/org/icepush/servlet/MainServlet.java
MODIFY
/icepush/trunk/icepush/core/src/main/java/org/icepush/servlet/AsyncAdaptingServlet.java
MODIFY
/icepush/trunk/icepush/core/src/main/java/org/icepush/servlet/BrowserBoundServlet.java
ADD
/icepush/trunk/icepush/core/src/main/java/org/icepush/servlet/ConfigurationServlet.java
DEL
/icepush/trunk/icepush/core/src/main/java/org/icepush/ConfigurationServer.java
|