On Mon, 2003-11-10 at 09:20, Scott Nichol wrote: > I have not heard of this exact problem. Here are some questions and suggestions. > > 1. Is anything accessed on Tomcat besides the SOAP services (i.e. could the error > come from something completely separate from Apache SOAP within Tomcat)?
To my knowledge, running tomcat by itself without SOAP does not cause any problems. However, I haven't been able to verify that because all of my computers are in constant use and bringing a SOAP server down for a while to test it out is not really an option. I'm working around the crashes right now by running a program on a centralized computer that periodically tests for the freeze, then takes care of it automatically. > 2. Are the servers visible from the Internet (i.e. could someone be attacking > Tomcat)? Again, without saying for sure, I don't think anyone is attacking Tomcat. These servers are on opposite sides of the country and not really interlinked, meaning, someone would have had to launch these strange, random attacks simultaneously on computers in various states for a couple of weeks, which is how long I've had this problem. Not probable. > 3. What JDK/JRE are you using, and have you tried any other version? I'm using j2sdk1.4.1_03. I've heard there were problems between either Tomcat and some recent java versions... is that me? I don't really understand the Apache bug database. > 4. You might want to try the Tomcat list, in case there is a known problem with > versions of Tomcat, Red Hat 9 (you should probably specify the kernel version in > your post), and the JDK/JRE combination. Thanks for your help. Hopefully successive upgrades will solve my problem in the future. Until then, I've got my shoddy system monitor daemon keeping an eye out. > Scott Nichol > > Do not send e-mail directly to this e-mail address, > because it is filtered to accept only mail from > specific mail lists. > ----- Original Message ----- > From: "Cyrus Adkisson" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Saturday, November 08, 2003 12:22 AM > Subject: SOAP servers freeze randomly > > > > I have several severs in various cities running Redhat 9, jakarta-tomcat > > 5.0.12 (I get the same problem with 4.1.27) and Apache SOAP 2.3.1. I've > > got them set up to answer a few requests... simple string passings back > > and forth. One of the services runs a few system processes on the remote > > machine, but nothing out of the ordinary. If I shut all 7 of them down > > and restart them carefully, everything will work fine... then a few > > hours or a day later, I'll find out that one of them has frozen. It > > seems completely arbitrary which server it is or why. > > > > When one freezes, the shutdown.sh script that came with jakarta-tomcat > > doesn't work. A java process remains. During this time, even simple > > calls to whicheverdomain:PORT don't work, which tells me that the whole > > tomcat server has frozen, not just the SOAP layer. As soon as I kill the > > process manually and restart the soap server, everything goes back to > > normal. > > > > I'm really confused as to why this is happening, and have been dealing > > with it for a couple of weeks now. catalina.out nor any of the other log > > files tell me anything. The completely random nature of the freezes has > > me totally baffled. If anyone knows what might be going on or has heard > > of this sort of thing before, please let me know. Or, if you think I > > should be writing to another list, please tell me what it is. > > > > Thanks, > > > > Cyrus > > > > > >
