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

Difference between revisions of "EJB Bad Practices: Use of Synchronization Primitives"

From OWASP
Jump to: navigation, search
Line 24: Line 24:
  
 
==Related Attacks==
 
==Related Attacks==
 
[[:Category:API Abuse Attack]]
 
  
 
==Related Vulnerabilities==
 
==Related Vulnerabilities==
Line 42: Line 40:
  
 
[[Category:Use of Dangerous API]]
 
[[Category:Use of Dangerous API]]
 +
 +
[[Category:API Abuse]]

Revision as of 18:36, 18 July 2006

This article includes content generously donated to OWASP by MicroFocus Logo.png

This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.


Abstract

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

Description

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."

Examples

Related Threats

Related Attacks

Related Vulnerabilities

Related Countermeasures

References

[1] Enterprise JavaBeans 2.1 Specification. Sun Microsystems. http://java.sun.com/products/ejb/docs.html.

Categories