WarStorm Posted June 2, 2008 Share Posted June 2, 2008 Ok guys. I am currently developing a few web applications. Currently only using JSPs. With JDBC and postgres. I am quite new linux, still learning. Here the problem: I can access the web server from my external computer for a certain amount of time before for some reason tomcat freezes and no pages will load. I originally thought that It was to do with me not closing database connections (grinding the server to a halt) but closing these connections makes no difference I read there are error log files in the tomcat directory on linux (attached screenshot). I ve opened up one of the files for today and found this error: Basically I need help debugging why this happens - I don't think it is the code I've written - i believe its to do with my tomcat setup. Again remember I am new so the error might be obvious to you but not to me ;) Cheers, greg Link to comment Share on other sites More sharing options...
markwolfe Veteran Posted June 2, 2008 Veteran Share Posted June 2, 2008 Well, I know nothing of Java, and precious little about webservers (other than just playing in my local home PC with Apache - not exposed to the outside). However, one item in the second screenshot sticks out to me. There is an "argument exception" posted there with a URI of "file:./", and that doesn't seem right. Should not the format of a 'file' address be identified as "file://" then followed by the path? Link to comment Share on other sites More sharing options...
Commodore Max Posted June 3, 2008 Share Posted June 3, 2008 I'm currently working with Tomcat at my work. I'm not on Ubuntu though ... I recommend you tail the log file in one shell and do your work in the other, kinda helps to see errors. Now about the error you're having, it seems to have to do with a file:// style path somewhere, which is kinda weird IMO ... Hope that helps. Link to comment Share on other sites More sharing options...
kjordan2001 Posted June 4, 2008 Share Posted June 4, 2008 Also, you seem to be using the GCJ (part of the GCC toolkit) environment instead of the Sun JRE. And since the problem seems to originate from GCJ, you might try switching to the Sun JRE since it might have something to do with the way GCJ does jar paths. Link to comment Share on other sites More sharing options...
Recommended Posts