I have:
- IIS 6, Windows 2003 Server on dual PIII with jk 1.2.15 installed and working
- Solaris 10 on Sun E420R with Quad Processors with jBoss / Tomcat version 4.0.3SP1
There is a significant delay in page loading that occurs randomly (every 10-20 clicks) which lasts for 10-18 or so seconds.
I've traced it to the read method in ChannelSocket.java. The delay always occurs while receive() is reading the header portion of the message. The length of the header that the read is trying to read is 4 bytes. The call to BufferedInputStream will block until it gets these 4 bytes of the header (10-18 seconds). I've modified the code and put a call in to available() before and after the read. The before returns 0 and the after returns 1138 or so.
I've tried every imaginable combination of configs on the IIS side to get around the problem ... and then some kernel TCP/IP configs on the Solaris side ... too many to list here.
The problem seems to be isolated to Solaris ... because Linux, XP, Windows 2003 server all work without this problem.
My question is this ... is there any thing that I can configure to have this read return faster? Changes to the Solaris kernel ... some config parameter ... ?? Anyone experience this before?
I'll gladly list the things I've tried to get some idea of how to solve this.
I think ultimately this is my problem:
Thanks in advance!
- IIS 6, Windows 2003 Server on dual PIII with jk 1.2.15 installed and working
- Solaris 10 on Sun E420R with Quad Processors with jBoss / Tomcat version 4.0.3SP1
There is a significant delay in page loading that occurs randomly (every 10-20 clicks) which lasts for 10-18 or so seconds.
I've traced it to the read method in ChannelSocket.java. The delay always occurs while receive() is reading the header portion of the message. The length of the header that the read is trying to read is 4 bytes. The call to BufferedInputStream will block until it gets these 4 bytes of the header (10-18 seconds). I've modified the code and put a call in to available() before and after the read. The before returns 0 and the after returns 1138 or so.
I've tried every imaginable combination of configs on the IIS side to get around the problem ... and then some kernel TCP/IP configs on the Solaris side ... too many to list here.
The problem seems to be isolated to Solaris ... because Linux, XP, Windows 2003 server all work without this problem.
My question is this ... is there any thing that I can configure to have this read return faster? Changes to the Solaris kernel ... some config parameter ... ?? Anyone experience this before?
I'll gladly list the things I've tried to get some idea of how to solve this.
I think ultimately this is my problem:
Thanks in advance!