hi there, had this problem: tomcat didn't start reporting a "socket closed"-error (see stack trace of other posted questions). the problem occurred when i tried to port a webapp from my home system (where it was working just fine on linux) to an environment i knew nothing about (apart from the fact that linux was running the server and people i had instructed to make sure that there was a postgres installation with jdbc-driver plus jakarta tomcat had signalled thumbs up). after a hilariously great amount of stress i found out that the jdk was wrong. suse-linux (via ftp) had installed jdk1.1.8, i believe, which is too old. maybe i was just too stupid to consider this earlier, but shouldn't a linux distribution know? anyway, check your jdk version if you get the 'socket error'! and avoid stress ... :-) heiko
