S
Steve
Hi,
I have a product that uses Tomcat to serve web pages. Occasionally
whilst clicking around my pages IE6 freezes & I need to kill it using
the task manager. I have ran repeated stress test on the Tomcat
application using MS web stress tool and I've ran lengthy browser
tests using a mouse macro replay tool on may application pages. The
browser can lock up after 30 minutes or run for several hours before
freezing. I have repeated the browser tests with simple Tomcat
jsp/servlet pages & the test runs for several days without fault
(until I get bored & stop the test). The difference is, my
application pages contain substantial JavaScript and DHTML.
A brief overview:
1. I have 3 frames, each frame has a timer monitoring mouse inactivity
& performing data-refresh duties.
2. I have an applet in one frame gathering data from the server
(Tomcat).
3. The most complex frame has a JavaScript timer that periodically
gets data from the applet (using Liveconnect), formats it & pushes
into the page to provide a nice dynamically updating page content
(tables of numeric data, image swaps etc). I push it into the page by
using document.all[id].innerHTML = "xx", where "xx" is text or it
could be an <img> html tag. Each item on my page has a unique "id".
Some items on the page have JavaScript statement associated with them
that are eval()uated each time the data is to be displayed. A typical
snippet of JavaScript to be evaluated is:
x==6?"images/user6.gif":x==7?"images/user18.gif":"images/user17.gif"
Basically an if-then-elseif which returns a string (in this case an
image) to be formatted & pushed into the innerHTML.
4. Both task manager and my java applet show now signs of memory
leaks.
5. IE CPU usage does increase if one of the dynamic pages are viewed
for several hours & although it is running slow, the application is
still usable (no freeze/lockup). The lockup can occur at anytime.
My browser application is expected to be open 24x7 but the lockup is
stopping this.
My questions:
Q1.Has anybody got experience of using a browser application like this
for lengthy times?
Q2.Is DHTML robust enough for this type of application?
Q3.Any alternative technologies I can use in the browser?
Q4.Any comments on my browser content complexity?
My system:
Win 2K SP4 latest critical patches
IE6 latest critical patches
The problem also exisits on WinXP (latest patches).
All feedback appreciated.
Cheers,
Steve
I have a product that uses Tomcat to serve web pages. Occasionally
whilst clicking around my pages IE6 freezes & I need to kill it using
the task manager. I have ran repeated stress test on the Tomcat
application using MS web stress tool and I've ran lengthy browser
tests using a mouse macro replay tool on may application pages. The
browser can lock up after 30 minutes or run for several hours before
freezing. I have repeated the browser tests with simple Tomcat
jsp/servlet pages & the test runs for several days without fault
(until I get bored & stop the test). The difference is, my
application pages contain substantial JavaScript and DHTML.
A brief overview:
1. I have 3 frames, each frame has a timer monitoring mouse inactivity
& performing data-refresh duties.
2. I have an applet in one frame gathering data from the server
(Tomcat).
3. The most complex frame has a JavaScript timer that periodically
gets data from the applet (using Liveconnect), formats it & pushes
into the page to provide a nice dynamically updating page content
(tables of numeric data, image swaps etc). I push it into the page by
using document.all[id].innerHTML = "xx", where "xx" is text or it
could be an <img> html tag. Each item on my page has a unique "id".
Some items on the page have JavaScript statement associated with them
that are eval()uated each time the data is to be displayed. A typical
snippet of JavaScript to be evaluated is:
x==6?"images/user6.gif":x==7?"images/user18.gif":"images/user17.gif"
Basically an if-then-elseif which returns a string (in this case an
image) to be formatted & pushed into the innerHTML.
4. Both task manager and my java applet show now signs of memory
leaks.
5. IE CPU usage does increase if one of the dynamic pages are viewed
for several hours & although it is running slow, the application is
still usable (no freeze/lockup). The lockup can occur at anytime.
My browser application is expected to be open 24x7 but the lockup is
stopping this.
My questions:
Q1.Has anybody got experience of using a browser application like this
for lengthy times?
Q2.Is DHTML robust enough for this type of application?
Q3.Any alternative technologies I can use in the browser?
Q4.Any comments on my browser content complexity?
My system:
Win 2K SP4 latest critical patches
IE6 latest critical patches
The problem also exisits on WinXP (latest patches).
All feedback appreciated.
Cheers,
Steve