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.
Deleting core/src/main/java/org/icepush/ConfigurationServer.java
Sending core/src/main/java/org/icepush/servlet/AsyncAdaptingServlet.java
Sending core/src/main/java/org/icepush/servlet/BrowserBoundServlet.java
Adding core/src/main/java/org/icepush/servlet/ConfigurationServlet.java
Sending core/src/main/java/org/icepush/servlet/MainServlet.java
Transmitting file data ....
Committed revision 37782.
Sending core-ee/src/main/java/com/icesoft/icepush/BrowserBoundServlet.java
Sending eps/src/main/java/com/icesoft/push/BlockingConnectionServer.java
Transmitting file data ..
Committed revision 35344.