DB2 deadlock issue

I have been experiencing this issue: SQL0911N The current transaction has been rolled back because of a deadlock or timeout. Reason code "2". This is on a newly developed j2ee based SOA app that uses db2 jdbc driver to access the db. Quick search on google groups and google regular revealed as usual a plethora of settings that needs to be done on the db2 sie of the house. Reminded me of the plethora of settings that we had to work with websphere and WSAD. This makes me wonder, Is this one of the value points or corporate manthra of IBM's products to just make even the simplest features appear complicated and thus earn revenues thru service and support?