Set webserver port during runtime

[ckis]

Hello everybody,

I'm want to start the webserver during runtime on another port than the default port. Therefore I use a single property node where I first set "WebSrvr.Port" then "WebSrvr.TCPAccess" and finally start the server with "WebSrvr.Active". This method worked really nice in LV 8.0 but now that I'm migrating to LV 2009 the webserver will always start on the default port 8080 though the webserver is completely disabled in the Tools/Options/Web Server menu.

Does anybody know how to get back to the behavior in LV 8.0?

Thanks in advance!

[keptat]

Hello, ckis.

It seems like the Web Server must be running to change the port number, so, start it first, change port, and activate it again.

I've attached an example.

Addendum: Sorry, ignore the frame and the delay, they're not necessary.

[ckis]

Hi keptat,

thanks for the reply, I think you are right, the webserver must be running to change the port. But the behavior looks strange to me and has the smell of a bug. I made the following experience:

A) local port 8080 is not used (checked with netstat -a | grep tcp)

1) run the attached vi with start=true: this will start a listener on port 8080, no error, WebSrvR.Active == false, checked with netstat -a | grep tcp

2) run the attached vi with start=true: this will start a listener on port 8004, no error, WebSrvR.Active == true, checked with netstat -a | grep tcp

B) local port 8080 is used by another application (checked with netstat -a | grep tcp)

1) run the attached vi with start=true: this will do nothing, no error, WebSrvR.Active == false, HTTP Port == 8080, checked with netstat -a | grep tcp

2) run the attached vi with start=true: this will start a listener on port 8004, no error, WebSrvR.Active == false, HTTP Port == 8080, checked with netstat -a | grep tcp

    Is the server now running or not?

3) stop the other application to free port 8080, run the attached vi with start=false an go back to A) will apparently start the web server on port 8004

So my questions are:

- why do I not see any error messages even if the web server doesn't start as specified?

- in state B)2): is the server running or not?

- Does this mean I cannot start the web server if port 8080 is occupied?

- could I solve this by editing the default configuration file for the application? This would be a bad solution but if there is no other way...

- which would be the default configuration file? Is it right that .labviewrc isn't used anymore?

I forgot to mention in my first post that I'm working on Suse Linux 11.0.