VariantDraft

CWE-574EJB Bad Practices: Use of Synchronization Primitives

Category: logic

Description

The product violates the Enterprise JavaBeans (EJB) 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. In this case, the product violates the following EJB guideline: "An enterprise bean must not use thread synchronization primitives to synchronize execution of multiple instances." The specification justifies this requirement 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."

Common consequences· 1

  • Other — Quality Degradation

Potential mitigations· 1

  • [Implementation]Do not use Synchronization Primitives when writing EJBs.

References

  1. https://cwe.mitre.org/data/definitions/574.html

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
EJB Bad Practices: Use of Sockets
CWE
EJB Bad Practices: Use of Class Loader
CWE
EJB Bad Practices: Use of AWT Swing
CWE
EJB Bad Practices: Use of Java I/O
CWE
Use of Singleton Pattern Without Synchronization in a Multithreaded Context
CWE
J2EE Bad Practices: Non-serializable Object Stored in Session
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.