Slowness in website, CLOSE_WAIT connection

miuprint

Hi all,

Just wondering if any developer encountering this issue where we have encounter several hundreds of close_wait connection after publishing, which result in slowness of the website.

1. I publish the files in the folder of "sites/facebook/",(inside the facebook folder,
there is no default.site and there are only some jsp files)
2. FTP some .class files to livesite "web-inf/classes"

when user access livesite page(.jsp), we know livesite render manager will treat the
"facebook" as a site and try to check the default.site/default.sitemap, thus throw the
error as below:
"ERROR
[com.interwoven.livesite.runtime.impl.BaseLiveSiteDal] Missing a sitemap for
site... " show in the case note, it look like a sitemap "Facebook" is missing."

but the .jsp still accessible and the functionality of this page also works fine, our concern is, does it affect the slowness of the website?

thanks in advance

Rick Poulin

*giggles* at the thought of Facebook running on LiveSite.

Anyway, the sitepub dev guide specifically says not to do this (under the best practices section). Yes, your JSPs (and other assets) will work but at a minimum, you're incurring extra overhead that you don't need, and at worst, you're maybe triggering some kind of memory leak in LiveSite's code. AFAIK, this is the first time in the platform's history that they've actually bothered to document best practices for everyone, so it's probably a good idea to follow them.

I wonder, is there a particular requirement as to why you were storing non-LiveSite artifacts in that folder structure? Also, I almost don't want to suggest this, but perhaps try creating a "facebook" SitePub site properly and drop your JSPs back in that folder and see if performance improves?

BTW, I must question the sanity of this, but that's another convo:

2. FTP some .class files to livesite "web-inf/classes"