It's the Jetty web server in SFS that can't start because another web server has already taken its preferred port. There's another thread on the forum with the same problem but I can't find it now. 1. Shut down SFS2X 2. Go to http://localhost:8080 3. Figure out what webserver that is, and shut it do...

No, there's no conflict as the included Jetty runs off port 8080.

You can't AFAIK. You need to install another web server. For most people I think install a WAMP/LAMP stack which bundles MySQL with phpMyAdmin.

We're seeing getConnection hanging in some rare cases. Is it possible that your login thread is also stalled on a getConnection call?

Hang as in getConnection() never returns and the login function never exits. I confirmed it by single stepping through our login function as that's the easiest place to catch it. Prior to this, there were symptoms that other getConnection calls were also hanging (we noticed some data wasn't being sa...

It's not an issue with the login procedure itself; it's only hanging there because we're using a custom login that includes a getConnection() call. It seems that prior to this all our getConnection() calls hang, and it's only most noticeable because when we log back in we can't. I'm guessing the def...

Ever since we upgraded to RC3, we've had hung instances a couple of times. When connecting, the server shows the "Session created: ... <port> <---> <port> " line but no longer proceeds to call our login handler. We managed to debug it once; what happens is that the server hangs on getConne...

Just a note: the version display at the top of the Admin page is sent by the server, and will still show RC3 even though your admin consoles are still cached from RC2a or lower. If the menus on the left are missing the license manager that's an old cached RC2a version even if the version string says...

This is also present in RC2a. The following error is thrown on the server every time we click on a user in the Admin page; I suspect it may be because our users use a JSON string in one of the user variables: Description: Error while handling client request in extension: { Ext: Admin, Type: JAVA, Le...

The error is basically saying the port you specified is in use; perhaps your server is being launched twice somehow. Try this: 1. Select a random port 2. Test if it's in use by "telnet 127.0.0.1 <portnumber>" 3. If it can connect, it's already in use, go back to 1. 4. Change port number to...

You probably have SFS2X running as a service as well as standalone. You should turn it off, or set your current standalone to run off another port.

Ah, I think it's clearer now. I was under the impression that the license server was required for the license to function. After speaking with our IT people, it seems the license server is only required when running under Amazon's EC2+Elastic IP (because of the instance's locally visible IP not matc...

I just rechecked with our IT dept and I think the situation is as follows: - We have our order for an unlimited SFS2X license (processed somewhere in Feb) - There is no license server available yet, and your sales has emailed us that the license will only be sent once the license server comes out - ...

Hi, We've reached the stage where we really need to run a proper load test of our logic running on SFS2X. We have already bought an unlimited license, but with no license server available and our need to have lots of NPCs in our zone, we max out our user allocation really quickly. Right now, NPCs co...

I'm guessing you're not using SFS 2.x?

SFS 1.x trial only allows up to 20 concurrent users IIRC. It's possible your other logins aren't being cleared up and you're hitting this limit. Normally this throws an exception and should be appearing in your logs.