Reality server port numbers... 8080 or 9091?

[jond]

Hello, we've just got our RS up and running but there seems to be a problem with the port numbers. The page is viewable but Flex is not able to connect to the application and the rendered images. I've attached a screen grab of Safari's Activity window to show what I mean. Could you let me knew where our problem might be and how it can be rectified?

Thanks!

[ak]

Hello Jond,

The log output tells you on what port port RealityServer is listening. After having RealityServer started, you may find an information like that in the console:

   ...
  1.0   MAIN main info : RealityServer is ready for processing requests on 0.0.0.0:8080
   ...

Your screen shot shows requests on two different ports. How did you configure these requests? Are they send from a RealityServer application example or did you use your own flex code for that?

[jond]

Thanks for your rely AK.
This swf that I was trying to test was the default WebServicesClientDemo.swf from within the ws_flex_demo application. From what I can tell the getRsDescriptor() method seems to parse the port number from the host that the application resides on so I'm not sure where that 9091 is coming from. I'm not a network tech guy by any means so you'll have to bear with me.

What confuses me is that when I test using the Reality Server Developer Edition I can only get rendered images to happen when I run the "Documentation" CommandLine operation which says that it's looking to process requests on port 9091. Where as the "Reality Server" command line says that it process requests on port 8080. (I'll attach a screen grab of both CommandLine windows). When I don't have the "Documentation" command line running I get similar results as what my last post. With everything but the swf using port 8080 and the swf using 9091.

We have our server guys looking in to changing the server configuration to only use port 9091 so hopefully that will do the trick.

Thanks again.

[ak]

What confuses me is that when I test using the Reality Server Developer Edition I can only get rendered images to happen when I run the "Documentation" CommandLine operation which says that it's looking to process requests on port 9091.

Where as the "Reality Server" command line says that it process requests on port 8080. (I'll attach a screen grab of both CommandLine windows). When I don't have the "Documentation" command line running I get similar results as what my last post. With everything but the swf using port 8080 and the swf using 9091.

The (.bat) scripts you are accessing seems to have different ports set to support bothe scripts running in parallel. If you parse the scripts in <RealityServer tape>/bin/* for the key --http_address you will see how this effects the runtime ports.

It could also help to read the section "Site Configuration" in the documentation.

We have our server guys looking in to changing the server configuration to only use port 9091 so hopefully that will do the trick.

As mentioned above: the RealityServer port configuration can be done easily as a command line key or via site configuration.

Hope that helps.

[jond]

Thanks AK, we have the ports sorted out now.

Now when we load the Flex demo we are getting mixed results.
- Often times it seems to hang and never show a rendered image. As you can see by the Activity Window it seems to be hanging on the /services request.

- Other times it will show an image but it will be black. Then when you try to orbit the camera using your mouse it returns mostly black images with scattered multicoloured pixels. Have you encountered a problem like that before?

Thanks again!

[ak]

Have you encountered a problem like that before?

Not yet.

To help you with this problem, we have to reproduce this on our side.
Could you please tell us some more details about the circumstances:
- What RealityServer version are you using?
- What OS are you using?
- What browser release are you using?
- ...

It would be also good to know how you ran into this situation in a step by step description.

Thanks!

[jond]

Not yet.

To help you with this problem, we have to reproduce this on our side.
Could you please tell us some more details about the circumstances:
- What RealityServer version are you using?
- What OS are you using?
- What browser release are you using?
- ...

It would be also good to know how you ran into this situation in a step by step description.

Thanks!

We're running:
RS 3.0
Windows 7
we've tested on a variety of platforms and browsers all getting the same result.

We're using the unaltered ws_flex_demo example.
If you check the activity window that I attached to my previous post it seems to be havnig problems after making the getCameraForServices() call as its hanging at that point and not getting a response to the server.

Let me know if you require any other info.

Thanks!

[PSMcMichael]

Jon,

While the 8080/9091 port mixup was something that we have seen before, I have not seen RealityServer fail to give images on the ws_flex_demo before. I think we have a few options here:

1. Try a newer version of RS. I recommend that you go to the download site and download the latest -applab version built for your hardware and OS (32 or 64-bit). This release in particular has a number of bug fixes from the one released on December 2nd that you seem to be using (the least of which might be the 8080/9091 confusion -- RealityServer now runs on 9091 all the time)
2. While I appreciate the Activity window screenshot, without knowing what was actually sent as part of those requests, it is difficult to for me to understand what might have gone wrong. If you could provide the full details of those requests (especially the ones that have "services" in the URL) that would be supremely helpful.
3. Try other demos. Is this unique to the ws_flex_demo, or does the ws_sl_demo behave similarly (you will need to have MS silverlight installed to view this one). Do the tutorial demos also behave similarly? Since all these are using the same 3D content, I would expect the rendering errors you are reporting to be the same across all of them. If that's not the case, there is something really wrong with the ws_flex_demo.
4. Try going to the webservices demo live documentation:
   http://localhost:9091/webservices/services (this will redirect you, that's okay)
   Search for and find the "join_world" operation. Execute it using the test-form. Note that the test-form only appears when accessing the server via localhost as above -- if this is an issue, I can help you configure your server to make it always accessible.
   Go back and search for and find the "render" operation. Execute it using the test-form. Do you get an image?

Hopefully this gives you a few things to try. Please let me know if you have any further questions, and/or what you find going forward with some or all of these.

Regards,

Patrick

[jond]

Hi Patrick, thanks for all your suggestions.
The problem seems to have resolved itself with the last server restart. Not sure what it was as I'd attempted restarts before but for now we seem to be up and running.

Thanks again!
Jon