This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit

EJB Bad Practices: Use of Synchronization Primitives

Revision as of 23:25, 7 April 2009 by KirstenS (talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


#REDIRECT Failure to follow guideline/specification

Last revision (mm/dd/yy): 04/7/2009


The program violates the Enterprise JavaBeans specification by using thread synchronization primitives.

The Enterprise JavaBeans specification requires that every bean provider follow a set of programming guidelines designed to ensure that the bean will be portable and behave consistently in any EJB container [1].

In this case, the program violates the following EJB guideline:

 "An enterprise bean must not use thread synchronization primitives to synchronize execution of multiple instances."

A requirement that the specification justifies in the following way:

 "This rule is required to ensure consistent runtime semantics because while some EJB containers may use a single JVM to 
 execute all enterprise bean's instances, others may distribute the instances across multiple JVMs."

Risk Factors




Related Attacks

Related Vulnerabilities

Related Controls

Related Technical Impacts