Spring with ACEGI

There are a number of posts out there that do Spring with ACEGI.
I found this an interesting and useful tutorial when trying to hookup the Password encoder with acegi

http://www.i-proving.ca/space/Technologies/Acegi+Security+System+for+Spring

Firefox Addons for a Performance Engineer

In my life as a performance engineer, I used a few Firefox addons. They're useful in "thin slicing" as my old boss would call it.

1. Firebug
2. Web Developer
3. Live HTTP Headers (I've not used this, but am told is good)
4. Load Time Analyzer.

Spring java.lang.ClassCastException: java.lang.Long

In the error Log, you'll notice it occurs in toLoggableString within the Hibernate code


When you notice that, change your logger settings to INFO from DEBUG. It seems to go away.

This seems to be a bug with Spring / Hibernate.

Originally Where I got this answer from

Spring Hibernate tips

I've started coding in Spring - Hibernate now. I've come across many hurdles, interesting nonetheless.

Here's what I learnt today.

To get hibernate to "actually" perform the update / create on the database
use:

hibernate.hbm2ddl.auto">create
The hibernate suffix is essential.

If that doesn't work this may
http://forum.springframework.org/showthread.php?t=15009



classpath:hibernate.cfg.xml
true

As I grow to become a Performance Engineer ....Essential points to remember

1. Always instrument whats happening.
2. Make a baseline. For eg: if a process is failing at 100 users, start from 10, and create a baseline. See where the user load and memory load change dramatically. That will give you an idea of where to start looking.
3. Know the code. The code is your friend. Logging helps.
4. Don't assume that what the developers think is the probelm is the real cause of the problem. Make your own tests and verifications. More often that not, big words like "Memory Leak" etc may be used, but that may not be the real cause of the problem.

Here are some useful steps
1. Recreate the problem.
2. Create your baseline.
3. Create logging information.
4. Try to find the "breaking point" for the code.
5. Make sure you're looking at the real problem and not a referred problem. Drill down the code. Understand it well. It will help!
6. Memory problems can well be traced using Jprobe or Xloggc in java.

Connection Pooling with Java....

Remember to close the Statement, PrepareStatement & ResultSet before returning the connection back to the connection pool.

Otherwise, you'll more than likely get "Open cursors exceeded" and that connection will be useless. Even if you return it to the pool, more than likely those will not be closed.