Today, I realized that "type" in cflock is very important and essential for shared data manipulation. In Adobe Coldfusion documentation, which said "type" is optional in cflock but when we need to process shared data, it's not optional. IT'S VERY IMPORTANT. Why I know like that is because of I'm currently preventing about concurrency issues for my project. In these coding, we already used cftransaction as putting the whole queries and processes within cftransaction but cannot prevent at all. After that, I've put cflock again outside of cftransaction like that.

view plain print about
1<cflock name="proc#accountID#">
2    <cftransaction action="BEGIN">
3        <cftry>
4        ....
5        ....
6        ....
7        <cftransaction action="COMMIT" />
8        <cfcatch type="Any">
9            ERROR...!!!
10            <cftransaction action="ROLLBACK" />
11        </cfcatch>
12        </cftry>    
13    </cftransaction>
14</cflock>

Once I've changed my coding and let users know that we've successfully prevent it and told them to test it again. Unfortunately, it cannot prevent concurrency issue again means like we failed again. That's why I've read through documentation and added type = "exclusive" in cflock and told them to test it again.

view plain print about
1<cflock name="proc#accountID#" type="EXCLUSIVE">
2    <cftransaction action="BEGIN">
3        <cftry>
4        ....
5        ....
6        ....
7        <cftransaction action="COMMIT" />
8        <cfcatch type="Any">
9            ERROR...!!!
10            <cftransaction action="ROLLBACK" />
11        </cfcatch>
12        </cftry>    
13    </cftransaction>
14</cflock>

Finally, the outcome is they don't face concurrency issue anymore and seems it's fine. As my experience, I wanna keep in mind that "type" in cflock are not optional.

This entry was posted on July 4, 2011 at 10:42 PM and has received 1091 views. There are currently 6 comments. Print this entry.