Hm, I just decided to test the "stream terminated unexpectedly" upload bug with JK2/IIS/TC5 and your statement that adding DEBUG to JK2 removes the problem.
Firstly, I uploaded a series of files of increasing size from 50K through to 60K at 1K intervals. The bug appears at files of 54K+ (tested up to 60K and tried one at 250K) workers2.properties file for failure of upload at 54K+. ====================================================== file=D:\Tomcat 5.0.18\work\jk2.shm size=1048576 [channel.socket:127.0.0.1:8009] info=Ajp13 worker, connects to tomcat instance using AJP 1.3 protocol tomcatId=127.0.0.1:8009 [uri:/*.do] info=iQ2 context=/ [uri:/*.jsp] info=iQ2 context=/ I now add the debug configuration to the workers file as follows: workers2.properties file for success of upload at 54K+. ====================================================== file=D:\Tomcat 5.0.18\work\jk2.shm size=1048576 # add this section to test the proposition that it resolved the upload bug [logger] level=DEBUG [channel.socket:127.0.0.1:8009] info=Ajp13 worker, connects to tomcat instance using AJP 1.3 protocol tomcatId=127.0.0.1:8009 [uri:/*.do] info=iQ2 context=/ [uri:/*.jsp] info=iQ2 context=/ And repeat the same tests to find that I cannot replicate the bug anymore and it does indeed work for upload up to and over 54K. In order to double prove this, I again removed the logger configuration from the workers file and repeated the test and the upload bug reappeared again at 54K+ uploads. I have no idea why adding this statement solves the problem but someone out there may do. Hope this goes towards a solution. We had an awful hack to get around this - wish I had known about the logger hack! By the way where do I find the JK2 log file? ADC -----Original Message----- From: JoAnn Lemm [mailto:[EMAIL PROTECTED] Sent: 16 April 2004 18:17 To: 'Tomcat Users List' Subject: RE: JK connector -- isapi2 -- file upload Importance: High While we're discussing this ... has anyone developed a work-around for this problem? I have beta product clients calling me, so this is extremely critical. Leaving debug running seems to only fix the problem intermittently. Is there another ISAPI that will work? --JoAnn -----Original Message----- From: E Cunningham [mailto:[EMAIL PROTECTED] Sent: Friday, April 16, 2004 9:59 AM To: Tomcat Users List Subject: Re: JK connector -- isapi2 -- file upload We verified this using Tomcat 4.1.30 not 5.x. Therein may be the problem. The connector code in Tomcat. Let's ask this then. Is there a dependency between JK2 and Tomcat? When they started to release separately one would think that any JK2 would work with any Tomcat? Does JK2 need to include a jk2.jar? JoAnn, thanks for provoking more thought on this. e --- JoAnn Lemm <[EMAIL PROTECTED]> wrote: > Hi All, > > I've search the archives and I've seen several posts > indicating that there > is a bug in the isapi connector in regards to large > file uploads (or not > that large, since the error seems to occur at or > around 50Kb.) The problem > being that "the stream ended unexpectedly. > > The strange thing is, I don't see this problem when > I upload a large file > (3M) within our intranet (I'm using IIS6, Tomcat 5 & > jk2.0.4), only when I > try to access from the internet. > > This leads me to believe there is some sort of > timing problem (the connector > trying to grab data that hasn't yet arrived?) > Interestingly, I solved the > problem by turning debug on - forcing the isapi > connector to log debug > messages and making is slow down a bit. That 3M file > uploaded with no > problem. > > So, here's the question ... is there a properties > file, ini file ... > anything ... where I can set the size of the buffer > in the connector? It > looks like it's grabbing about 8Kb each time. > > --JoAnn > > <FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE> ------------------------------------------------------- QAS Ltd. Developers of QuickAddress Software <a href="http://www.qas.com";>www.qas.com</a> Registered in England: No 2582055 Registered in Australia: No 082 851 474 ------------------------------------------------------- </FONT> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
