#796 ✓resolved
Lauri Kimmel

Fix F.ArchivedEventStream.notifyNewEvent()

Reported by Lauri Kimmel | May 3rd, 2011 @ 05:44 PM | in 1.2.2

Framework version: 1.2, 1.2.1

Reproduction steps: see attached test case

Details:
F.ArchivedEventStream.notifyNewEvent() is triggering one waiting filter at the time.
In case there are more than one filter waiting for events, notifyNewEvent() is returning right after first one is triggered.

Test case:

package play.libs;

import static org.junit.Assert.*;

import java.util.List;
import java.util.concurrent.ExecutionException;

import org.junit.Before;
import org.junit.Ignore;
import org.junit.Test;

import play.libs.F.ArchivedEventStream;
import play.libs.F.IndexedEvent;
import play.libs.F.Promise;
import play.test.UnitTest;

public class ArchivedEventStreamTest extends UnitTest {

    private static final String VALUE_1 = "ONE";
    private static final String VALUE_2 = "TWO";
    
    private ArchivedEventStream<String> stream;
    
    @Before
    public void setUp() throws Exception {
        stream = new ArchivedEventStream<String>(100);
    }

    @Test
    public void testPublishMultiple() throws InterruptedException, ExecutionException {
        Promise<List<IndexedEvent<String>>> p1 = stream.nextEvents(0);
        Promise<List<IndexedEvent<String>>> p2 = stream.nextEvents(0);
        Promise<List<IndexedEvent<String>>> p3 = stream.nextEvents(0);
        
        stream.publish(VALUE_1);
        assertTrue(p1.isDone());
        assertTrue(p2.isDone()); // <- fails at this line
        assertTrue(p3.isDone());
        
        assertEquals(1, p1.get().size());
        assertEquals(VALUE_1, p1.get().get(0).data);
        assertEquals(1, p2.get().size());
        assertEquals(VALUE_1, p2.get().get(0).data);
        assertEquals(1, p2.get().size());
        assertEquals(VALUE_1, p2.get().get(0).data);
        
        stream.publish(VALUE_2);
        assertTrue(p1.isDone());
        assertTrue(p2.isDone());
        assertTrue(p3.isDone());
        
        assertEquals(1, p1.get().size());
        assertEquals(VALUE_1, p1.get().get(0).data);
        assertEquals(1, p2.get().size());
        assertEquals(VALUE_1, p2.get().get(0).data);
        assertEquals(1, p2.get().size());
        assertEquals(VALUE_1, p2.get().get(0).data);
    }
}

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

Referenced by

Pages