ok i have 2 computers (or two running SGS). if i close one of them everyone gets dissconnected from the game, isnt the other server supposed to take over? i have tryed running the other instance as in Discovery mode not much change here. should my Client try and reconnect when things fallOver (seems to be trying to by itself anyway). A thing i did note when i did change something in the game the other Discovery instances do get updated- so i guess somthing is trying to work here... how do i setup a game grid, so if the one server goes down the others take over without the player seeing any change?

Once you get to the point where what you have is scaling and faultesting, you move to either the Playground or a commericalhost.

This is a purposeful limit to keep the unscrupulous from trying to run servcies of of the free-ware.

Quote

does this development version only work over localhost? i put the game on another computer and pointed the ip to my computer to see if it would connect and i always get an error.

Nope it works just fine networked. Its what we acually used at the show and what we have runnign on our networked alpha-server that we use internally. Did you change your deployment XML files? If so are you using "real" discovery or the FakeDsicovery.xml file? If the latter, did you chnage it, too?

Got a question about Java and game programming? Just new to the Java Game Development Community? Try my FAQ. Its likely you'll learn something!

the ip being the address of the location of the server. on the server i didnt change anything. do i need to change things there also? i do have a discovery.xml, but theres nothing in that file but the root <discovery> tags. i even opened the port 2049 across the whole network here- just to see if it was that ... i must be missing something?

well one slice is cool with me- just wanted to see it working still when one of the servers poped; hay np leaming it with one for now...

discovery: in my document i put:

I assume you mram the client side FakeDiscovery.xml (or whatever you called your own copy if you renamed it.).

You need to reset the server-side deployment XML file. In fact, ina real back end thats all you would change as the disovery manager would create the client-side doc for you from the server side info.

Quote

the ip being the address of the location of the server. on the server i didnt change anything. do i need to change things there also? i do have a discovery.xml, but theres nothing in that file but the root <discovery> tags. i even opened the port 2049 across the whole network here- just to see if it was that ... i must be missing something?

If you waited about 90 seconds and the discovery.xml created byu the DiscoveryManager ahs ntohign but root tags then you dont have anything actually installed into your server.

Loo kat the SGS-apps.conf file. It points to an XML deployment descriptor for each app tht is installed. Those need to be changed to reflect the actual port you want to receieve conenctions on.

If you chnage those, start everything up, and wait about 90 seconds you SHOULD get a discovery.xml generated that shows all your apps. (The same as the FakeDiscovery.xml, ifyou did your FakeDiscovery.xml right).

Got a question about Java and game programming? Just new to the Java Game Development Community? Try my FAQ. Its likely you'll learn something!

for the host- i put my the ip address of the server... im useing the ChatTest as my test code now- just in case theres somthing wrong with my code test, the servers 'sgs-ea1\release\server\discovery.xml' file always looks empty even after waiting 20-30mins. im running on windowsxp (hope its not that). localhost connections work ok

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org