GitHub user bzz opened a pull request:

    https://github.com/apache/incubator-zeppelin/pull/558

    ZEPPELIN-312: fix a bug with blocking websocket broadcast

    ### What is this PR for?
    Fix the bug of Z, blocking broadcast to websocket connections. 
    
    ### What type of PR is it?
    Bug Fix
    
    ### Is there a relevant Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-312
    
    ### How should this be tested?
    See JIRA
    
    ### Questions:
    * Does the licenses files need update? No
    * Is there breaking changes for older versions? No
    * Does this needs documentation? No

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bzz/incubator-zeppelin 
fix/zeppelin-312-blocking-broadcast

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-zeppelin/pull/558.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #558
    
----
commit 524c4017bab20a79859d6b36ace5a7debb253537
Author: Alexander Bezzubov <b...@apache.org>
Date:   2015-12-19T04:13:44Z

    ZEPPELIN-312: refactoring ZeppelinServer to adhere Java naming conventions

commit 497a6cad361b78f659e026a9ebb18af267ecd843
Author: Alexander Bezzubov <b...@apache.org>
Date:   2015-12-21T06:34:01Z

    ZEPPELIN-312: replace sync \w lock-free collection
    
    Replacing synchronization though critical section over the collection of
    sockets with the lock-free datastructure impl of
    java.util.concurrent.ConcurrentLinkedQueue
    
    Synchronization was used to avoid parallel collection modifications, as
    the calls `.sendMessage()` in Jetty implementation of Websockets are
    thread-safe and can proceed concurrently.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to