|
From: Jordan S. <js...@ph...> - 2002-10-11 08:36:30
|
At 11:15 PM 10/10/2002, John Watkinson wrote: >This is the well-known "multiple-listener bug". Matt and I spent hours >scouring the code trying to discover what kind of situation led to this >condition. However, it turned out that it is actually a problem with the >Linux implementation of Java. With hours of use on Windows, Linux and >Solaris, we have only had this problem on Linux, and it also only seems to >happen when bandwidth is tight-- that is, it never happens when I'm >listening to a Linux server locally. It only occurs when I'm accessing it >remotely, and especially when my bandwidth is insufficient to play the >stream. I suspect that we could find a bug report filed with Sun on this >issue. Hopefully a newer version of the J2SE or perhaps even glibc will >solve the problem. > john It's true that this is on Linux, however, I am only listening to the server via the 100mbps switch, and not remotely at all. It might have something to do with swapping, since the server I'm running it on only has 64MB of RAM, which is almost totally consumed by Streamsicle (especially if I reload the 50gigs of songs). Streamsicle is pretty much the sole reason I built this machine, and I should probably just throw another 256MB of RAM in there. The only other thing that I'm running on this machine is Edna (see Sourceforge page). I wouldn't be at all surprised if it only occurs when the machine is paging to disk, since it does do that quite a bit, on occasion. Jordan |