Pages not fully rendered

[patricka]

Config:

Server1
JBoss 3.2.1
Linux Debian 2.4.16-686

Server2
Windows Server 2000
SQL Server 2000

The following are intermittent faults.

Users are complaining about receiving web pages that are not fully rendered. The web browser (IE) is displaying 'done', but page is either not displayed (i.e. blank) or partial information is displayed.

In addition to this users are (via web interface) sending database requests that are not being performed but web page is returning indicating it has been.

Checking through JBoss logs (request and server) no information is being displayed to indicate any errors.

Any more info required?

Help.

1. Is there a way in order for JBoss to produce a more accurate log of what is happening i.e. various switches for error reporting?

2. Anybody have any idea of what this might be?

Thanks for any help in advance
ADAM

[french_c]

Although your question is pretty low on detail I would check whether you loose sessions at some point. I have seen the "blank" page issue popping up whenever cookies were involved and somehow got lost. I have never seen partial content though.

If you can reproduce the problem easily use VM remote debugging instead of logging/tracing.

[dankim1978]

I've seen the situation where a page half renders gets flushed and then an exception is thrown. Try figuring out where the code stops and put in some exception checking.

Can you post code?

[french_c]

I forgot:

Also check whether you encounter an HTTP Connection timeout.

[verilet]

Insufficient buffer size perhaps? I have seen blank pages rendered when pages are too large. Also, if the compiled method exceeds 64K (plenty of print statements) the JVM chokes.

<%@page buffer="32kb" ...

[patricka]

thanx for all the replies, this is what is currently being thought to be the cause of the problem...

There is no escape!!! :0)

[treespace]

I would have bet money on the default 8k page buffer being the problem: seen that one myself.

Also, if you have written your own tags make sure you reset the tag's state. New web containers are aggressive about reusing tag objects whereas you could get away with improper tag implementations in the past because it created new objects for each instance.