jMonkeyEngine.org

Could you give us listings for those two classes?

You can actually debug SpiderMonkey itself, which I’d recommend. Remember that its SpiderMonkey itself that does the connection brokering – if you set a breakpoint in the right place, you might be able to see why its not calling that method on your class.

Ok, the code is a little complex, contextually, but I zipped up a sparse subset of my com.resounding.apps folder and placed it here.

auth/AuthServer is the server, managing client connections from WorldServers via auth/WorldNetListener

world/WorldServer is the client app to the AuthServer, managing it connection to the AuthServer via world/AuthNetListener

If it helps you see past references to PlayerClients and ShipServers, I’ll explain that the overall network design I am working on is that of a scalable MMP game: AuthServer is the player login-point and lobby system and thus has com.jme3.network.Servers for both PlayerClients and WorldServers, and a WorldServer runs a shard of the game (thus it has a com.jme3.NetworkClient to the AuthServer and com.jme3.network.Servers to PlayerClients and other app instances called ShipServers).

This code fails to cause the clientConnected()/connectionAdded() methods to fire even when I run AuthServer and WorldServer on the same machine and change the AuthServer.DEFAULT_SERVER_ADDRESS to “localhost”. This makes me believe that firewall issues are not at play here.

The machine in use is an iMac running 10.6.8

Thanks in advance for any insights.

tone

pspeed .. I’ll keep cracking. TestChatClient connects easily to TestChatServer on my machine.

When I debug my app and set breakpoints in the server’s KernelAdapter, it blocks forever on kernel.read()

tone

Ok, here is a culled set of code from the serverside (I think perhaps my issue is client side, as I just tried a test wherein my server looked more like TestChatServer

AuthServer (extends SimpleApplication)

    Server mWorldServers;

    @Override
    public void simpleRender(RenderManager rm) {
    }

    @Override
    public void simpleInitApp() {

        // create and start a server to accept and process WorldServer connections
        try {
            mWorldServers = Network.createServer(App.GAME_NAME, WORLD_NETWORK_VERSION, 52500, 52500);
            mWorldServers.start();

            new WorldNetListener(this);
        }  catch (IOException ex) {
            getLogger().log(Level.SEVERE, "Cannot create server for WorldServers: "+ ex);
            return;
        }  catch (KernelException ex) {
            getLogger().log(Level.SEVERE, "Cannot start server for WorldServers: " + ex);
            return;
        }
    }

    public static void main(String[] args) throws Exception  {
        Serializer.registerClass(HandshakeMessage.class);
        Serializer.registerClass(WorldStatusMessage.class);

        AuthServer app = new AuthServer();

        AppSettings settings = new AppSettings(true);
        settings.setFrameRate(25);
        settings.setRenderer(AppSettings.NULL);

        // FIXME: strange way of setting null audio renderer..
        settings.setAudioRenderer(null);

        app.setShowSettings(false);
        app.setPauseOnLostFocus(false);
        app.setSettings(settings);
        app.start();
    }

WorldNetListener implements MessageListener, ConnectionListener

    AuthServer mAuthServer;
    Server mWorldServers;

    public WorldNetListener(AuthServer app) {
        mAuthServer = app;
        mWorldServers = app.mWorldServers;
        mWorldServers.addConnectionListener(this);
        mWorldServers.addMessageListener(this, HandshakeMessage.class, WorldStatusMessage.class);
    }

    // ConnectionListener callback -- never fires
    public void connectionAdded(Server server, HostedConnection client) {
    }

    // ConnectionListener callback -- never fires
    public void connectionRemoved(Server server, HostedConnection client) {
    }

    // MessageListener callback -- never fires
    public void messageReceived(HostedConnection source, Message message) {
    }

re:

If you see logged connections and disconnections and don’t have your connection listener called then either the connection listener isn’t really added right or the connections are never fully setup. You can test that last one on the client if you try sending a message… it will block until the connection is fully setup. So if your app hangs then you know that the connection never really happens. The most likely cause of that is a missed UDP message.

Sometime recently I went round and round about this with another user on the end of some thread and it ultimately turned out to be something in his system configuration that was blocking a port. Pretty sure that was on Linux… on a Mac it seems less likely that you could get into that much trouble.

My connectToServer returns almost instantaneously. There is no sign that it fails to work.

I just now tried changing my port to the same one successfully used in TestChat* — it did not help.

tone

Last little clue…

If I run my client, it appears to run its connectToHost() command in quick order, though there is no indication whatsoever in the Server’s log that anything happened.

However, if I then kill the client app, there are log entries in the server’s log which indicate undeniably that it knew of the client’s connection in some manner:

Nov 19, 2011 1:48:05 PM com.jme3.network.kernel.tcp.SelectorKernel$SelectorThread connect
INFO: Hosting TCP connection:0.0.0.0/0.0.0.0:52500.
Nov 19, 2011 1:48:05 PM com.jme3.network.kernel.tcp.SelectorKernel$SelectorThread run
INFO: Kernel started for connection:0.0.0.0/0.0.0.0:52500.
Nov 19, 2011 1:48:05 PM com.jme3.network.kernel.udp.UdpKernel$HostThread connect
INFO: Hosting UDP connection:0.0.0.0/0.0.0.0:52500.
Nov 19, 2011 1:48:05 PM com.jme3.network.kernel.udp.UdpKernel$HostThread run
INFO: Kernel started for connection:0.0.0.0/0.0.0.0:52500.

THIS IS WHERE THE CONNECTION ATTEMPT OCCURS.
Nothing is output.
When the client process is killed, however, the following additional lines spill out:

Nov 19, 2011 1:49:01 PM com.jme3.network.kernel.tcp.SelectorKernel$SelectorThread cancel
INFO: Closing channel endpoint:NioEndpoint[1, java.nio.channels.SocketChannel[connected local=/192.168.1.101:52500 remote=/192.168.1.101:50502]].
Nov 19, 2011 1:49:01 PM com.jme3.network.base.DefaultServer connectionClosed
INFO: Connection closed:NioEndpoint[1, java.nio.channels.SocketChannel[closed]].

Could this be an issue with GameName/client version number?

I’ll note that NetworkClient provides no means whatsoever to set the version number, as does Client, but neither did I see that the network code actually checks the game name or version number as the comments indicate. The default version number in some places is a playful 42, but may be in my NetworkClient a java-standard 0 which I cannot alter.

tone

Oh, and it definitely checks the version during connection. But the client has to send its connection message with that info and that happens when you _START_ the connection. That gives you time to setup listeners, etc. before actually processing messages.