Some of the zkau/comet request is taking hours

asked 2017-09-12 19:21:58 +0800

saurabhz gravatar image saurabhz


We are using hybris 6.2 which uses ZK framework for all its cockpit applications. In product cockpit we have observed that the /zkau/comet requests are getting triggered in milliseconds and some of them takes not minutes but hours to finish. As a result Apache web server times out and the user is logged out because the session gets transferred to another server.

Some of the examples of time taken are as follows:

Request Code Time (secs) Time (mins) /rilgroceryproductcockpit/zkau/comet?dtid=gs9v HTTP/1.1 200 5464.293 91.07155 /rilgroceryproductcockpit/zkau/comet?dtid=geb81 HTTP/1.1 200 5337.302 88.95503333 /rilgroceryproductcockpit/zkau/comet?dtid=ggk91 HTTP/1.1 200 5083.214 84.72023333 /rilgroceryproductcockpit/zkau/comet?dtid=gfko1 HTTP/1.1 200 5003.95 83.39916667 /rilgroceryproductcockpit/zkau/comet?dtid=guaa1 HTTP/1.1 200 4953.747 82.56245

If you see above, time takes are like 90 minutes. For sure this is a bug.

We have a clustered environment with 4 nodes , tomcat as application server and apache as a web server to load balance tomcats. We are using modproxyajp to communciate from apache to tomcat.

Please help as this is leading to major issues

delete flag offensive retag edit


did you inspect the comet calls with chrome developer tools? That data is also very intresting to have in the post.

chillworld ( 2017-09-12 19:43:09 +0800 )edit

was not able to post it as my KARMA doesn't allow me to post URL :)

saurabhz ( 2017-09-12 22:26:53 +0800 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2017-09-13 11:15:18 +0800

cor3000 gravatar image cor3000
3907 1 7
ZK Team

Comet uses long polling requests by design. Unless it times out and there's no response from the server this is not an error. Only if the server has a background task trying to notify the client that it's ready the comet request will finish with status 200 - there's no technical reason why this can't take 90 minutes.

Sometimes the request will timeout or disconnect earlier due to network settings (proxy,firewall ...). For those cases it is also possible to configure a shorter client side timeout to avoid long requests from running into disconnections (see Comet Server Push Config).

Those options are available since ZK 8.0.2 (I can't tell which ZK version Hybris ships with - for that you'd have to ask your hybris support).


link publish delete flag offensive edit
Your answer
Please start posting your answer anonymously - your answer will be saved within the current session and published after you log in or create a new account. Please try to give a substantial answer, for discussions, please use comments and please do remember to vote (after you log in)!

[hide preview]

Question tools




Asked: 2017-09-12 19:21:58 +0800

Seen: 11 times

Last updated: Sep 13 '17