VariantDraft

CWE-383J2EE Bad Practices: Direct Use of Threads

Category: other

Description

Thread management in a Web application is forbidden in some circumstances and is always highly error prone. Thread management in a web application is forbidden by the J2EE standard in some circumstances and is always highly error prone. Managing threads is difficult and is likely to interfere in unpredictable ways with the behavior of the application container. Even without interfering with the container, thread management usually leads to bugs that are hard to detect and diagnose like deadlock, race conditions, and other synchronization errors.

Common consequences· 1

  • Other — Quality Degradation

Potential mitigations· 1

  • [Architecture and Design]For EJB, use framework approaches for parallel execution, instead of using threads.

References

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

Related by meaning· 6

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

CWE
J2EE Bad Practices: Direct Management of Connections
CWE
J2EE Bad Practices: Direct Use of Sockets
CWE
J2EE Bad Practices: Use of System.exit()
CWE
EJB Bad Practices: Use of Synchronization Primitives
CWE
EJB Bad Practices: Use of Sockets
CWE
J2EE Framework: Saving Unserializable Objects to Disk
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.