Is this a Winstone issue then?
I don't really want to have to learn how to switch from Winstone to
Tomcat unless it's the only way...
Are there any docs on this?
Chris
On 29/01/2013 11:57, Pawel Jasinski wrote:
I have to admit the thread is a bit convoluted.
For me the fix was not switching
yeah, I saw that, but:
- I'm on SUSE Linux, not Windows
- it's *only* build result pages (and things below that, such as test
results) for me, the rest of the UI is fine...
cheers,
Chris
On 29/01/2013 08:09, Pawel Jasinski wrote:
just in case you missed this one:
http://jenkins.361315.n4.n
just in case you missed this one:
http://jenkins.361315.n4.nabble.com/Slow-Jenkins-response-to-http-after-upgrade-td4651785.html
On Tue, Jan 29, 2013 at 8:12 AM, Chris Withers wrote:
> Hi All,
>
> Anyone else experience this?
>
> The master is a pretty beefy blade, its filesystem is a nice fast
Hi All,
Anyone else experience this?
The master is a pretty beefy blade, its filesystem is a nice fast san,
and there are now no jobs running on the master...
...and yet it can still take 2+ *minutes* to return the build page.
How can I go about debugging this?
cheers,
Chris
On 25/01/2013
Hi All,
I've noticed this a lot since upgrading to 1.480.2, but it's been an
intermittent problem for a while now..
Going to:
http://:8080/job///
...can take over a minute to render.
How can I figure out why this is taking so long?
cheers,
Chris
--
Simplistix - Content Management, Batch
