ndt-users list created

[Maurice Volaski <>]

Getting back to you on this... I realized after I switched JDKs that 
I was running the Gentoo kernel and not the vanilla 2.6.15 with the 
web100 patches.

When I did loaded the patched kernel (2.615.6 and web100 2.5.8), I 
immediately began having problems. Processes using the network are 
not behaving properly. We use drbd, which is network RAID, and it 
stalls. When I tried to sync portage tree in Gentoo, which uses 
rsync, it also stalls. Interestingly, ssh is not affected.

This occurs even if I unload the iptable modules, which aren't being 
used, anyway.

So it appears that the web100 selectively chokes network activity and 
is presently unusable!


> Hi Marurice;
>
> At 10:59 AM 3/8/2006, Maurice Volaski wrote:
> > > Hi Maurice;
> > >
> > > OK, I looked at the attached files and I think there is a bug in 
> > > my build system somewhere.  For some reason gnu is creating an 
> > > Admin/Admin directory and putting a copy of the Admin.class file 
> > > there.  It also creates a copy in the parent directory and that is 
> > > installed in the /usr/local/ndt directory during the make install 
> > > process.  This same bug may be causing gnu to complain about the 
> > > ./Tcpbw100 file (or maybe it thinks it's a directory).
> > >
> > > In any case everything seems to be in order and the make install 
> > > process completed despite the errors.  And just to be sure you did 
> > > create the customized tcpbw100.html file by running the 
> > > "conf/create-html.sh" command from the ndt-3.1.4b directory, right?
> > >
> > > Assuming that is done, then I think the question is, why doesn't 
> > > the applet load?  One possible answer is a version difference 
> > > between the SDK (1.5.0_6 in your case) and the plugin JRE version. 
> > > I'm hearing and seeing cases where the 1.4.2 plugin wouldn't run 
> > > the 1.5.0 applet.  There are 2 solutions
> > >         1) recompile the applet with a 1.4.2 SDK
> > >         2) update the browser plugin to a 1.5.0 JRE
> >
> > I can try recompiling it, but shouldn't there actually be a file 
> > called Tcpbw100 somewhere?
>
> No, there is no file called Tcpbw100.  If the fakewww log file shows 
> the .jar file was sent, then I'd really suspect the SDK/JRE version 
> mismatch.  My laptop is running a 1.5.0 JRE so if you send me a URL 
> I can test this out for you.

--

Maurice Volaski, 

Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University