Page 1 of 1
SmartFoxServer 2X v2.1.0 patch released!
Posted: 04 May 2012, 09:36
by Bax
We just released the new version (2.1.0) of SmartFoxServer 2X. It is distributed as a patch available on the updates page of the website,
here.
Please visit the page to read the release notes.
Re: SmartFoxServer 2X v2.1.0 patch released!
Posted: 04 May 2012, 15:55
by Bax
If you downloaded the patch before May 4th 2012 at 17.50 GMT+2, you should please get and install it again.
In fact we found an easy solution to an issue causing a malfunctioning in the Dashboard (formerly Runtime Statistics) module of the Admin Tool for those developers using JRE 1.7. Instead of providing a separate patch, we decided to update the just released patch for simplicity.
We are sorry if you already downloaded and installed it.
Re: SmartFoxServer 2X v2.1.0 patch released!
Posted: 04 May 2012, 17:46
by hackshaven
I seem to be encountering an error after applying the patch and entering the admin tool:
Code: Select all
Exception: com.smartfoxserver.v2.exceptions.SFSRuntimeException
Message: Request handler not found: 'runtimeStats.getData'. Make sure the handler is registered in your extension using addRequestHandler()
Description: Error while handling client request in extension: { Ext: Admin, Type: JAVA, Lev: ZONE, { Zone: --=={{{ AdminZone }}}==-- }, {} }
Extension Cmd: runtimeStats.getData
+--- --- ---+
Stack Trace:
+--- --- ---+
com.smartfoxserver.v2.extensions.SFSExtension.handleClientRequest(SFSExtension.java:181)
com.smartfoxserver.v2.controllers.ExtensionController.processRequest(ExtensionController.java:137)
com.smartfoxserver.bitswarm.controllers.AbstractController.run(AbstractController.java:96)
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
java.lang.Thread.run(Unknown Source)
I just download the patch, am I doing something else wrong?
Re: SmartFoxServer 2X v2.1.0 patch released!
Posted: 04 May 2012, 18:01
by rjgtav
Hello. It looks like you're using an older version of the AdminTool. Please clear your browser's cache and try again
Re: SmartFoxServer 2X v2.1.0 patch released!
Posted: 04 May 2012, 18:07
by hackshaven
That seems to have fixed it.
Pure genius.
Re: SmartFoxServer 2X v2.1.0 patch released!
Posted: 14 May 2012, 11:46
by karfau
Is there any update for the AS3-API (the swc is from february)?
After installing the patch to our server no clietn is able to connect to the server.
and when debugging the server, it seems like the custom login is not even reached.
This is what the server tells in his log:
Code: Select all
13:28:35,613 INFO [main] v2.SmartFoxServer - SmartFoxServer 2X (2.1.0) READY!
13:29:26,187 INFO [SocketReader] core.SocketAcceptor - Session created: { Id: 1, Type: DEFAULT, Logged: No, IP: 127.0.0.1:52808 } on Server port: 9933 <---> 52808
13:29:26,191 INFO [SocketReader] text.TextIoHandler - data post-header: 78
13:29:55,625 INFO [SocketReader] sessions.DefaultSessionManager - Session removed: { Id: 1, Type: DEFAULT, Logged: No, IP: 127.0.0.1:52808 }
13:29:55,626 INFO [Scheduler1-thread-1] sessions.DefaultSessionManager - Session removed: { Id: 1, Type: DEFAULT, Logged: No, IP: 127.0.0.1:52808 }
13:29:55,626 INFO [SocketReader] core.SocketReader - Socket closed: java.nio.channels.SocketChannel[closed]
13:31:06,177 INFO [SocketReader] core.SocketAcceptor - Session created: { Id: 2, Type: DEFAULT, Logged: No, IP: 127.0.0.1:52821 } on Server port: 9933 <---> 52821
13:31:06,291 INFO [SocketReader] text.TextIoHandler - data post-header: 56
13:31:24,192 INFO [SocketReader] sessions.DefaultSessionManager - Session removed: { Id: 2, Type: DEFAULT, Logged: No, IP: 127.0.0.1:52821 }
13:31:24,192 INFO [SocketReader] core.SocketReader - Socket closed: java.nio.channels.SocketChannel[closed]
13:38:00,532 INFO [SocketReader] core.SocketAcceptor - Session created: { Id: 3, Type: DEFAULT, Logged: No, IP: 127.0.0.1:52869 } on Server port: 9933 <---> 52869
13:38:00,578 INFO [SocketReader] text.TextIoHandler - data post-header: 56
13:38:09,590 INFO [SocketReader] sessions.DefaultSessionManager - Session removed: { Id: 3, Type: DEFAULT, Logged: No, IP: 127.0.0.1:52869 }
13:38:09,590 INFO [SocketReader] core.SocketReader - Socket closed: java.nio.channels.SocketChannel[closed]
The clients that are trying to connect to it (java and as3) are running locally and don't get a response when calling the connect method.
any idea?
Re: SmartFoxServer 2X v2.1.0 patch released!
Posted: 14 May 2012, 23:27
by rjgtav
Hi.
Well, the latest AS3 API works fine here (the one from february). It seems you're having some problems on the server.
Did the server boot correctly? Are there any errors on the logs, any problems?
Also please don't forget to always close the database connection after using it (use a try/catch/finally statement).
Re: SmartFoxServer 2X v2.1.0 patch released!
Posted: 15 May 2012, 08:37
by karfau
Yes, everything is starting correctly, all event and requesthandlers are attached correctly.
No errors in the log
The database(/-connection) is not the problem, as it doesn't get touched. (If the EventHandler registered for the CustomLogin would get triggered, the connection to the DB would be established, but it doesn't.)
Everything works fine when using the unpatched version.
Re: SmartFoxServer 2X v2.1.0 patch released!
Posted: 15 May 2012, 10:52
by Lapo
Does the AdminTool work for you?
Because if it does it just uses the same AS3 API that you do.
Re: SmartFoxServer 2X v2.1.0 patch released!
Posted: 16 May 2012, 12:20
by karfau
Sorry that I forgot to mention it:
The admintool is not able to connect.
It says
[13:56:05 | WARNING] A disconnection occurred due to unknown reason; please reconnect
[13:55:24 | INFO] Welcome to SmartFoxServer 2X Admin Tool v1.2.0
when pressing connect again it doesn't respond even afrter waiting some minutes.
Any idea how do diagnose this further?
how could the serverlogging get more detailed?
Re: SmartFoxServer 2X v2.1.0 patch released!
Posted: 16 May 2012, 12:44
by Lapo
Yes, please restart the server. Then try to connect with a couple of the examples we provide and the admin tool even if they fail to connect and finally send us the server side logs, or post them here if they are not too long.
Thanks