Joined: 07 Feb 2005, 21:30 Location: Cheese factory
I noticed you're currently only leveraging the services layer of OSGi. All modules are in one bundle so runtime updates of modules is not (yet) possible. However if this is not intended as a replacement for ueberserver, but only as a hobby server, then you don't really need support for adding new commands at runtime. Disregarding that, how do you plan to proceed with bundles?
Since it says something about "Unable to start UDP server on port 8201. Ignoring ... java.net.BindException: Address already in use: Cannot bind" I thought maybe it is the windows firewall, so I turned that off but no difference.
i think this error message is pretty trustworthy, as it comes from the java networking core stuff, not SpringLS code in particular. so when it sais address is already in use, the problem is most likely is exactly that, that there is already a service running on that address on that port. the most likely reason for that, is that you alreayd have a lobby server instance running. maybe you double-clicked the jar, and it is running, but only visible in taskmanager or so. .. can't really give more input there, but at worst you might have to reastart the OS, to be sure nothing is running like just described, and then try again to start from a console.
Joined: 22 Feb 2006, 01:02 Location: cheap kitchen
thanks, it works now after restart.
To get back on this:
I remember that windows users had/have a problem with the lobby server, as it has no GUI, and when they double-click it under windows, it starts, but ... actually i don't know what happens. does it open a console to show output?
OS: windows xp Doubleclicking the .jar makes shows a hourglass for a seconde, then nothing more visible happens. (in taskmanager it only shows javaw.exe) Run from console you can see some output. But for players it is hard to know if it is actually working even from that, so maybe add something like "server is running. you can now connect to blabla port:xy" iirc old TAServer also showed connecting players in console, which was helpful to know it was working. --- Does the server no longer send "PING" (and expect "PONG" from client)?
@knorke i read that javaw.exe does not start a console window, while java.exe does, and i guess javaw.exe is used under windows when double-clicking. so please try creating a .bat file with this content:
java -jar springls-0.37-stand-alone.jar
and see if it works with that. There are other ways to do that, but they are much more complicated (using 3rd party tools to create wrapper executables that look for the JVM and ...). if this bat is good enough, i might just create a zip file for windows that contains the jar and the bat in the future.
@Cheesecan yes, OSGi as it is used so far in SpringLS is totally useless. i jsut went down a long boring path (along which i learnt OSGi), to arrive where it is now. where it is now, it is not too much work anymore, to get somewhere where OSGi coolness would actually start to kick in, and get practically usefull for us (online/at-runtime module addition, removal, updating).
TASServer.jar is still ok for now. the LAN only version of SpringLS would be enough, but that one is still ~5.6MB, and i agree it is too much for the installer, considering it will be used by few. i would like most if it was an optional download in hte installer menu, but that is agasint the rules we set ourselfs, so also not an option. is there some other way you can think of, to have it more easily available to those that might need it, except downloading it separately (when it gets removed).
i would say, add it to Download page for sure. if i remember right, TASServer.jar is ~200KB. i would preffer if both new servers were available as optional downloads in installer. but as this is no option (i forgot why exactly but i remember there was a not too bad reason), we should decide hwther to replace TASServer.jar with ueberserver.exe or removing it without replacement. TASServer.jar could still stay as long as it works with commonly used lobby clients. user needs java for that to work, not for ueberserver, but i consider that less important then keeping installer size low. should engine devs vote about that? (anyway only relevant till (mayor) lobby protocol version increase)
Users browsing this forum: No registered users and 0 guests
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum