desktop version does not start web server in conjunction with configuration program

Comments:

Author Thread:

Jairo.Lopez

desktop version does not start web server in conjunction with configuration program
Posted: Tuesday, May 25, 2004 1:54 PM (EST)

Do you have the log file from the last time this happen?

If you are using Beta 2.1 log files are created every day in the folder where you installed the APL+WebServices.



Owen.Shelksohn

desktop version does not start web server in conjunction with configuration program
Posted: Tuesday, May 25, 2004 2:43 PM (EST)

In my tiredness I forgot one other important thing about this issue.

Once it is running normally, if I close and then restart the configuration program, the server starts in conjunction as I expect and desire.

But, if I use the configuration window to stop and then start webservices, by highlighting the "Web Servers" folder and using stop/start from the Action dropdown menu, then it will no longer recieve requests and the only way I know to get it to start working again is to follow the steps above.

So the problem appears only if I use the configuration window to turn webservices on/off.



Owen.Shelksohn

log output
Posted: Tuesday, May 25, 2004 2:49 PM (EST)

sorry for length, doesn't seem to let me attach a file unless I start a new thread
=====================================
2004-05-25 09:11:42Z
Http server listening on port: 8801 - host: 127.0.0.1 - ipaddress: 127.0.0.1
=====================================
2004-05-25 09:13:13Z
Error executing apl.Detail:
System.InvalidCastException: QueryInterface for interface APLW.IWSEngine failed.
   at APLW.WSEngineClass.Call1(String FunctionName, Object Argument)
   at aplserver.HttpProcessor.AplStartExec()
=====================================
2004-05-25 09:13:27Z
Http server listening on port: 8801 - host: 127.0.0.1 - ipaddress: 127.0.0.1
=====================================
2004-05-25 09:13:46Z
Update action for server: rat. Action: stop
=====================================
2004-05-25 09:13:51Z
Error closing APLCOM: System.InvalidCastException: QueryInterface for interface APLW.IWSEngine failed.
   at APLW.WSEngineClass.set_Visible(Int32 pVal)
   at aplserver.APLCOM.Finalize()
=====================================
2004-05-25 09:13:56Z
Error closing APLCOM: System.InvalidCastException: QueryInterface for interface APLW.IWSEngine failed.
   at APLW.WSEngineClass.set_Visible(Int32 pVal)
   at aplserver.APLCOM.Finalize()
=====================================
2004-05-25 09:14:03Z
Update action for server: rat. Action: start
=====================================
2004-05-25 09:14:03Z
Http server listening on port: 8801 - host: 127.0.0.1 - ipaddress: 127.0.0.1
=====================================
2004-05-25 09:14:19Z
Listener failed accepting socket: System.Net.Sockets.SocketException: A blocking operation was interrupted by a call to WSACancelBlockingCall
   at System.Net.Sockets.Socket.Accept()
   at aplserver.HttpServer.StartListening()
=====================================
2004-05-25 09:14:22Z
Error closing APLCOM: System.InvalidCastException: QueryInterface for interface APLW.IWSEngine failed.
   at APLW.WSEngineClass.set_Visible(Int32 pVal)
   at aplserver.APLCOM.Finalize()
=====================================
2004-05-25 09:14:29Z
Http server listening on port: 8801 - host: 127.0.0.1 - ipaddress: 127.0.0.1
=====================================
2004-05-25 11:13:42Z
Listener failed accepting socket: System.Net.Sockets.SocketException: A blocking operation was interrupted by a call to WSACancelBlockingCall
   at System.Net.Sockets.Socket.Accept()
   at aplserver.HttpServer.StartListening()
=====================================
2004-05-25 11:13:45Z
Error closing APLCOM: System.InvalidCastException: QueryInterface for interface APLW.IWSEngine failed.
   at APLW.WSEngineClass.set_Visible(Int32 pVal)
   at aplserver.APLCOM.Finalize()
=====================================
2004-05-25 11:13:53Z
Http server listening on port: 8801 - host: 127.0.0.1 - ipaddress: 127.0.0.1
=====================================
2004-05-25 11:15:57Z
Listener failed accepting socket: System.Net.Sockets.SocketException: A blocking operation was interrupted by a call to WSACancelBlockingCall
   at System.Net.Sockets.Socket.Accept()
   at aplserver.HttpServer.StartListening()
=====================================
2004-05-25 11:16:01Z
Error closing APLCOM: System.InvalidCastException: QueryInterface for interface APLW.IWSEngine failed.
   at APLW.WSEngineClass.set_Visible(Int32 pVal)
   at aplserver.APLCOM.Finalize()
=====================================
2004-05-25 11:16:16Z
Http server listening on port: 8801 - host: 127.0.0.1 - ipaddress: 127.0.0.1
=====================================
2004-05-25 11:30:54Z
Listener failed accepting socket: System.Net.Sockets.SocketException: A blocking operation was interrupted by a call to WSACancelBlockingCall
   at System.Net.Sockets.Socket.Accept()
   at aplserver.HttpServer.StartListening()
=====================================
2004-05-25 11:31:01Z
Http server listening on port: 8801 - host: 127.0.0.1 - ipaddress: 127.0.0.1
=====================================
2004-05-25 11:31:09Z
Error binding port: 8801 - host: 127.0.0.1 - ipaddress: 198.182.113.81.
Error description: System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port)
is normally permitted
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at aplserver.HttpServer.StartListening()
=====================================
2004-05-25 11:31:20Z
Error closing APLCOM: System.InvalidCastException: QueryInterface for interface APLW.IWSEngine failed.
   at APLW.WSEngineClass.set_Visible(Int32 pVal)
   at aplserver.APLCOM.Finalize()
=====================================
2004-05-25 11:31:25Z
Error closing APLCOM: System.InvalidCastException: QueryInterface for interface APLW.IWSEngine failed.
   at APLW.WSEngineClass.set_Visible(Int32 pVal)
   at aplserver.APLCOM.Finalize()
=====================================
2004-05-25 11:31:32Z
Update action for server: rat. Action: start
=====================================
2004-05-25 11:31:32Z
Http server listening on port: 8801 - host: 127.0.0.1 - ipaddress: 127.0.0.1



Jairo.Lopez

new desktop version 2.3.7
Posted: Friday, May 28, 2004 1:08 PM (EST)

A new version of the desktop has been posted that takes care of this issue


Owen.Shelksohn

new desktop version 2.3.7
Posted: Friday, May 28, 2004 2:28 PM (EST)

Using this new version I am still experiencing the same behavior as before: if I stop it using the Action menu in the config window I can't get it to start accepting requests again normally.

I have checked the log however and I no longer see any errors in it.



Jairo.Lopez

Start/Stop web services
Posted: Tuesday, June 01, 2004 1:47 PM (EST)

Owen,

When a web server is started the following entry is created in the log file:
=====================================
2004-05-26 16:26:47Z
Http server listening on port: 8800 - host: localhost - ipaddress: 127.0.0.1

Do you see it?



Owen.Shelksohn

Start/Stop web services
Posted: Friday, June 04, 2004 6:36 PM (EST)

Jairo,

This is the log generated from beta 2.3.7 when I:

start up webservices and send a request to verify it is working normally

stop and then start it using the action dropdown

try sending a request to verify it won't respond

press the stop button on the specific server

kill webservices and restart it

press the start button on the specific server

send a request to verify it now is responding

kill webservices

The only strange thing I see is that the "Http server closed" line lists the ipddress as the port instead of the address.

=====================================
2004-06-04 15:11:25Z
Http server listening on port: 8801 - host: 127.0.0.1 - ipaddress: 127.0.0.1
=====================================
2004-06-04 15:11:35Z
The listener socket for server: rat has been closed.
=====================================
2004-06-04 15:11:35Z
Closing server: rat
=====================================
2004-06-04 15:11:35Z
Http server closed on port: 8801 - host: 127.0.0.1 - ipaddress: 8801
=====================================
2004-06-04 15:11:38Z
APL+WebServices stopped
=====================================
2004-06-04 15:11:42Z
Http server listening on port: 8801 - host: 127.0.0.1 - ipaddress: 127.0.0.1
=====================================
2004-06-04 15:11:56Z
Update action for server: rat. Action: stop
=====================================
2004-06-04 15:11:56Z
The listener socket for server: rat has been closed.
=====================================
2004-06-04 15:11:56Z
Closing server: rat
=====================================
2004-06-04 15:11:56Z
Http server closed on port: 8801 - host: 127.0.0.1 - ipaddress: 8801
=====================================
2004-06-04 15:11:59Z
Http server closed on port: 8801 - host: 127.0.0.1 - ipaddress: 8801
=====================================
2004-06-04 15:12:03Z
APL+WebServices stopped
=====================================
2004-06-04 15:12:14Z
Update action for server: rat. Action: start
=====================================
2004-06-04 15:12:14Z
Http server listening on port: 8801 - host: 127.0.0.1 - ipaddress: 127.0.0.1
=====================================
2004-06-04 15:12:24Z
The listener socket for server: rat has been closed.
=====================================
2004-06-04 15:12:24Z
Closing server: rat
=====================================
2004-06-04 15:12:24Z
Http server closed on port: 8801 - host: 127.0.0.1 - ipaddress: 8801
=====================================
2004-06-04 15:12:27Z
APL+WebServices stopped



Jairo.Lopez

Start/Stop web services
Posted: Friday, June 04, 2004 6:51 PM (EST)

Owen,

I would like to see the log for the "rat" server. The one you posted is the log for the AplWebServices.

From the log information the AplWebServices has no errors when you start/stop/kill the system. So the error must be happening when the specific web server ("rat" in your case) is processing the request.

You should have at least three entries in the server log:

For the first request between 2004-06-04 15:11:25Z and 2004-06-04 15:11:35Z

For the second request between 2004-06-04 15:11:42Z and 2004-06-04 15:11:56Z

For the third request between 2004-06-04 15:12:14Z and 2004-06-04 15:12:24Z

The server log is located in the path you selected under the "Web Site" page of the server properties window.



Owen.Shelksohn

Start/Stop web services
Posted: Friday, June 11, 2004 2:26 PM (EST)

Jairo,

These are the entries from the rat log. It didn't log anything about the middle requests.

=====================================
2004-06-04 15:11:29Z
GET /ratNavigation HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-powerpoint, application/vnd.ms-excel, application/msword, application/x-shockwave-flash, */*
Referer: http://127.0.0.1:8801/rat
Accept-Language: en-us
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.0.3705; .NET CLR 1.1.4322)
Host: 127.0.0.1:8801
Connection: Keep-Alive
=====================================
2004-06-04 15:11:29Z
GET /ratGrid? HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-powerpoint, application/vnd.ms-excel, application/msword, application/x-shockwave-flash, */*
Referer: http://127.0.0.1:8801/rat
Accept-Language: en-us
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.0.3705; .NET CLR 1.1.4322)
Host: 127.0.0.1:8801
Connection: Keep-Alive
=====================================
2004-06-04 15:12:17Z
GET /rat HTTP/1.1
Accept: */*
Accept-Language: en-us
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.0.3705; .NET CLR 1.1.4322)
Host: 127.0.0.1:8801
Connection: Keep-Alive
=====================================
2004-06-04 15:12:17Z
GET /ratNavigation HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-powerpoint, application/vnd.ms-excel, application/msword, application/x-shockwave-flash, */*
Referer: http://127.0.0.1:8801/rat
Accept-Language: en-us
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.0.3705; .NET CLR 1.1.4322)
Host: 127.0.0.1:8801
Connection: Keep-Alive
=====================================
2004-06-04 15:12:17Z
GET /ratGrid? HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-powerpoint, application/vnd.ms-excel, application/msword, application/x-shockwave-flash, */*
Referer: http://127.0.0.1:8801/rat
Accept-Language: en-us
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.0.3705; .NET CLR 1.1.4322)
Host: 127.0.0.1:8801
Connection: Keep-Alive



Jairo.Lopez

Start/Stop web services
Posted: Friday, June 11, 2004 2:58 PM (EST)

Owen,

Because there are no errors in either log I need to know a little more about your enviroment.

What OS are you using?

What client are you using to access the web server ? (from the log it looks like IE)

We've experienced in the past a latency in windows 2000 from the moment a call to close a socket is made to the time the system actually releases the port and IP address.



Owen.Shelksohn

Start/Stop web services
Posted: Friday, June 11, 2004 5:29 PM (EST)

Jairo,

I'm using Windows2000 Professional (SP4) and IE 6 (SP1).

I don't think it has to do with IE b/c requests to WebServices using the WebTransfer object fail in the same manner.

I don't believe the requests that are failing ever get reported in either log, the ones that we see there I believe are those that were sucessful.

How long of a latency? I've tried for a minute or two once it is in the unresponsive state, but no longer.

  Is it possible that b/c it doesn't immediately stop listening on the port that it gets screwed up when it tries again?