nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Visualisation of assets

Hazzie

Hi,

We have just started to have problems reported to us with users not being able to see files when they click on them within TS.

TS holds xml files for us. When a user clicks on an XML file in a workarea it gets previewed by being sent to an IIS server and the user sees an asp representation of the xml after the correct xsl has been applied.

Just reccently these previews have been stalling and just a white screen appears - viewing the source reveals nothing. After looking at the IIS servers web logs it seems to have built and served the page so i am wondering if TS's proxy server that forwards the request to display the page to the IIS server and then delivers the IIS's results back to the user has a timeout. If it does can some one point me in the right direction as to where this figure is.

This problem does not happen all the time.
It does not happen on all pages.
The Teamsite server & IIS servers are not stressed.
Using 5.5.2 on NT4 (yeah i know we are updating).

Find more posts tagged with

Comments

Migrateduser

You might start out by running iwproxy in debug mode. To do this, stop the iwproxy service (net stop iwproxy) and start it again with the -d flag... such as "iwproxy.exe -d".

Adam Stoller

After looking at the IIS servers web logs it seems to have built and served the page so i am wondering if TS's proxy server that forwards the request to display the page to the IIS server and then delivers the IIS's results back to the user has a timeout. If it does can some one point me in the right direction as to where this figure is.

I'm not sure - but I believe there's a default timeout for http traffic (60 seconds?) On Unix this is controlled at the OS level I believe. Not sure where it's controlled on Windows - but probably either at OS or IIS level.

Migrateduser

I'm not sure - but I believe there's a default timeout for http traffic (60 seconds?) On Unix this is controlled at the OS level I believe. Not sure where it's controlled on Windows - but probably either at OS or IIS level.

I was under the impression that "keepAlive" in apache configuration defines the timeout setting for http requests.

Do you know with unix OS configuration determines this timeout value?

Adam Stoller

I was under the impression that "keepAlive" in apache configuration defines the timeout setting for http requests.

Do you know with unix OS configuration determines this timeout value?

You may be right - I think I was thinking about a different timeout - one that affected deployments not http requests. Sorry about that.

Migrateduser

On Windows, it is controlled at the IIS level but your code or network would need to be pretty screwed up for it to timeout. The default is either 60 or 90 seconds for IIS.