« The University of... | Main | Snow in Denver »
20030423 Wednesday April 23, 2003

This site's performance This site crashes more than a 16-year old trying to pick up the ladies. You can check out all the errors in my catalina.out (3+ MB) file (snapshot from last night). Mostly OutOfMemory errors causing the issues. I'm going to try and configure jikes to run as my JSP compiler, we'll see if that helps. I'd like to try it locally first (on my Win2K machine), but it looks like I have to compile it with the -encoding option to make it work. Ughhh. Why don't they have an encoding-enabled download!? Posted in Java at Apr 23 2003, 04:36:28 PM MDT 6 Comments

Comments:

Could this Tomcat bug be contributing to your out of memory errors? http://insultconsult.com/archives/000026.html

Posted by Kurt Wiersma on April 23, 2003 at 07:28 PM MDT #

Besides using Jikes, try and configure the JVM mem sizes with -Xms and -Xmx params. I tried using them and they do not work on Win32 boxes, not sure if it will work for you.

Posted by dsuspense on April 23, 2003 at 08:24 PM MDT #

I'm not sure why dsuspense says the -Xms/-Xmx params don't work on Windows - as my experience says they do (we used them heavily in our apps). But I'm really writing to say be careful with Jikes. I used to be a huge fan of Jikes, but am no longer. I was mainly a fan because it compiled so much faster than javac. On my last project though, javac (from 1.4.1) compiled our 1300+ source files about 25% faster. I think Jikes may still be faster when compiling a single file, but in that case it's so fast that you can barely compare. But, what actually led to me switching was that Jikes had some bad bugs that simply prevented our code from even running. The problem was that stuff compiled, but then it had these weird bugs. I wound up debugging down into JVM source before I found a bug on the Jikes bug db that was pertinant to our situation (basically compiling lots of files). We've since run into other problems as well (on later versions), so now I simply just always use javac. You may also want to play with -Xincgc, and -server (can't use that with the JRE on Windows though, must use the JDK VM).

Posted by Chris Bailey on April 23, 2003 at 10:07 PM MDT #

I have my memory set to 256, so that shouldn't be the issue. Like you, Chris, I've experienced problems with Jikes. I think the last version I used was 1.14 or something like that. I found an issue where compiling my Struts classes with it causes my app to fail. Of course, it took me a whole fricken day to figure it out. My catalina.out file has all kinds of errors in it, so it's probably a bad velocity macro, or something else in the latest Roller release. I might try JRockit too - we'll see.

Posted by Matt Raible on April 23, 2003 at 10:32 PM MDT #

I've one word for you: "Blojsom"

Posted by Andy on April 24, 2003 at 12:53 PM MDT #

That is some ancient Jikes version you are using! Get the latest and enjoy it. If you think Jikes is slower than javac, you must be using old Jikes and new javac. Get Jikes 1.18.

Posted by Anonymous on April 25, 2003 at 10:53 AM MDT #

Post a Comment:
  • HTML Syntax: Allowed
Click me to subscribe
Matt Raible is the Lead UI Architect at LinkedIn. The opinions on this site are mine, not my employers.
« November 2008
SunMonTueWedThuFriSat
      
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
      
Today

Recent Entries

Tag Cloud

abbie acegi appfuse denver flex grails gwt hibernate jack java jsf linkedin maven myfaces oscon rails skiing spring springmvc struts struts2 tapestry travel webframeworks wicket