@On close triggering multiple times

[Ben Kuhl]

I'm unsure as to the exact cause here.  If I open my browser, it triggers open() correctly.

If I refresh the page, I would expect the events:

1. Close
2. Open

But instead, it triggers close twice...

1. Close
2. Open
3. Close

My socket handler:

abstract public class SocketHandler {

    @Wire

    Room socket;

    @On

    public void open(Socket socket) {

        getSocket().add(socket);

    }

    @On

    public void close(Socket socket) {

        getSocket().remove(socket);

    }

    public Room getSocket() {

        return socket;

    }

I'm integrating with AngularJS...:

                $rootScope.socket = portal.open(socketUrl+slug, {

                    transports: ['ws', 'sse'],

                    notifyAbort: true

                });

[Ben Kuhl]

What ends up happening here is that there isn't an open socket.  So my Java app can't send data to the browser.  The browser is able to make requests via the socket to the java side and get a reply - I guess because it opens a new connection.

Any thoughts on what might be the cause?

[Ben Kuhl]

Here's my POM.xml:

        <dependency>

            <groupId>com.github.flowersinthesand</groupId>

            <artifactId>portal-core</artifactId>

            <version>0.6</version>

        </dependency>

        <dependency>

            <groupId>com.github.flowersinthesand</groupId>

            <artifactId>portal-spring</artifactId>

            <version>0.6</version>

        </dependency>

        <dependency>

            <groupId>com.github.flowersinthesand</groupId>

            <artifactId>portal-atmosphere</artifactId>

            <version>0.6</version>

        </dependency>

        <dependency>

            <groupId>org.atmosphere</groupId>

            <artifactId>atmosphere-runtime</artifactId>

            <version>1.0.12</version>

            <exclusions>

                <exclusion>

                    <groupId>org.slf4j</groupId>

                    <artifactId>slf4j-api</artifactId>

                </exclusion>

            </exclusions>

        </dependency>

[Donghwan Kim]

Hello,

Before considering the server side, the browser's unload event might be a cause. See https://github.com/flowersinthesand/portal/wiki/Browser-Quirks#the-unload-event-causes-the-browser-to-open-a-second-connection-when-refreshing-page

Let me know how it goes.

-- Donghwan

--
You received this message because you are subscribed to the Google Groups "Portal" group.
To unsubscribe from this group and stop receiving emails from it, send an email to portal_projec...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Ben Kuhl]

The issue I'm experiencing isn't a second connection being opened, it's that once the page is refreshed it closes the connection that was just opened.  So it's firing close() when it shouldn't be.

[Ben Kuhl]

To be more clear... when I visit my URL, it opens a connection.  When I close that tab it closes the connection - which is correct.  If I open a new tab and navigate to the page again, it'll Open/Close the connection when it should just be opening the connection.

[Ben Kuhl]

This seems it may have been my fault as I made a change and the error went away.  I had a section where I was manually closing the Room to ensure everything was disconnected.