voyent
AHS connection  XML
Forum Index -> Async HTTP Server
Author Message
thienp

Joined: 15/Aug/2007 00:00:00
Messages: 17
Offline


Just a general observation about AHS. I don't know if anybody else seeing this same behavior.

If I have a web browser that sends requests to a ICEfaces webapp that utilizes Ajax push in conjunction with AHS, it seems that everytime the webapp is restarted, closing (or refreshing) the client web browser seems to take a long time, giving the "hung" browser impression. Often I find that it is better for me to just bring up a new instance of the web browser while at the same time closing the existing browser down. Is it normal? Is there a way to get around or remove this delay? Thanks.
jack.van.ooststroom


Joined: 26/Oct/2004 00:00:00
Messages: 223
Offline


Hello,

Just to clarify, regarding the "webapp": does this refer to the ICEfaces application or AHS? Which browser(s) are you using? Are you using a web server as a front-end? Are there any proxy servers involved?

Regards,

Jack van Ooststroom
Senior Developer
ICEsoft Technologies, Inc.
[Email]
thienp

Joined: 15/Aug/2007 00:00:00
Messages: 17
Offline


Hi Jack,

The "webapp" in this case is an ICEfaces application that utilizes Ajax push feature. Per recommendations from ICEfaces developer document, I also installed AHS for scalability purpose. When the ICEfaces application (not AHS) is restarted or redeployed, there are times (not necessarily all the time) the web browser (IE in this case) that previously communicated with the ICEfaces app would have a hard time reconnecting (if refresh is done) or closing down (if I try to close the browser). I am not sure if AHS is playing any part in this issue though.
jack.van.ooststroom


Joined: 26/Oct/2004 00:00:00
Messages: 223
Offline


I finally got around to go over a couple of scenarios regarding this. I mainly focused on AuctionMonitor with and without AHS in servlet mode. After accessing the application through a browser and redeploying AuctionMonitor, both reloading and shift-reloading seem to take a couple of seconds. But this is mainly due to reloading the resources and establishing the various connections. Unless the delay you're seeing is quite a bit longer I don't think this is an issue.

I also tested AHS in server mode with a web server as the front-end. I used Apache 2.2.x. Here it might happen that a longer delay is experienced. But this is due to Apache. Once Apache detects a service in the back-end went down, it will not retry within a certain period of time (30 seconds or so).

If you experience a longer delay then mentioned without a web server front-end, please let us know and provide us with some more detailed information of your deployment environment, such as application server brand and version, web server brand and version, which mode AHS is running in and such.

I hope this helps.

Regards,

Jack van Ooststroom
Senior Developer
ICEsoft Technologies, Inc.
[Email]
thienp

Joined: 15/Aug/2007 00:00:00
Messages: 17
Offline


Hi Jack,

I'm using OC4J 10.1.3.3 container from Oracle. The AHS was deployed in servlet mode (i.e. not fronted by a web server). The browser really hangs. Even when I tried to kill it, it took some time (more than a minute) to go down.

If you want, I can try to gather materials needed to reproduce this issue (webapp, AHS, etc.). I have a patched version of icefaces-ahs.jar so that it can work with OC4J's JMS.
 
Forum Index -> Async HTTP Server
Go to:   
Powered by JForum 2.1.7ice © JForum Team