As part of its support for Java EE 7, WebLogic Server 12.2.1 supports the Java EE Concurrency Utilities(JSR236) specification.
specification provides a simple, standardized API(4 types of managed
objects) for using concurrency from Java EE application components(such
as servlets and EJBs). The 4 types of concurrent managed objects
implement these interfaces in javax.enterprise.concurrent package:
If you are still using common Java SE concurrency APIs such as java.lang.Thread or java.util.Timer directly
in your servlets or EJBs, you are strongly recommended to use java EE
Concurrency Utilities instead. Threads created by using Java SE concurrency APIs
are not managed by WebLogic Server, so that services and resources
provided by WebLogic Server are typically unable to be reliably used from these un-managed threads. By using java EE Concurrency Utilities, asynchronous tasks run on WebLogic Server-managed threads. Since WebLogic Server has knowledge of these threads/asynchronous tasks, it can manage them by:
CommonJ API(providing context aware Work Managers and Timers) is WebLogic Server specific, and is the predecessor of Java EE Concurrency Utilities. Comparing to CommonJ API, Java EE Concurrency Utilities is more standardized and easier to use, and provides more functions like custom scheduling, ContextService, ManagedThreadFactory.
Read these articles for details:
See for more details Configuring Concurrent Managed Objects in the product documentation.