payara · kalinchan · Feb 2, 2026
diff --git a/community/docs/modules/ROOT/nav.adoc b/community/docs/modules/ROOT/nav.adoc
@@ -22,7 +22,6 @@
 *** xref:Technical Documentation/Payara Server Documentation/General Administration/Administering the HealthCheck Service.adoc[Administering the HealthCheck Service]
 *** xref:Technical Documentation/Payara Server Documentation/General Administration/Administering the Request Tracing Service.adoc[Administering the Request Tracing Service]
 *** xref:Technical Documentation/Payara Server Documentation/General Administration/Administering the Notification Service.adoc[Administering the Notification Service]
-*** xref:Technical Documentation/Payara Server Documentation/General Administration/Administering Lifecycle Modules.adoc[Administering Lifecycle Modules]
 *** xref:Technical Documentation/Payara Server Documentation/General Administration/Administering Batch Jobs.adoc[Administering Batch Jobs]
 *** xref:Technical Documentation/Payara Server Documentation/General Administration/Administering Database Connectivity.adoc[Administering Database Connectivity]
 *** xref:Technical Documentation/Payara Server Documentation/General Administration/Administering EIS Connectivity.adoc[Administering EIS Connectivity]

diff --git a/...s/ROOT/pages/Technical Documentation/Application Development/Class Loaders.adoc b/...s/ROOT/pages/Technical Documentation/Application Development/Class Loaders.adoc
@@ -58,11 +58,6 @@ Parents the Connector class loader.
 
 Parents both the *Applib* class loader and the *LifeCycleModule* class loader.
 
-|LifeCycleModule
-|The LifeCycleModule class loader is created once per lifecycle module. Each lifecycle module's classpath is used to construct its own class loader.
-
-For more information on lifecycle modules, see xref:Technical Documentation/Application Development/Developing Lifecycle Listeners.adoc#developing-lifecycle-listeners[Developing Lifecycle Listeners].
-
 |Applib
 |The `Applib` class loader loads the library classes (specifically, libraries of the `app` type), specified during deployment, for a specific enabled module or Jakarta EE application;
 

diff --git a/...nical Documentation/Application Development/Developing Lifecycle Listeners.adoc b/...nical Documentation/Application Development/Developing Lifecycle Listeners.adoc
diff --git a/...cumentation/Application Development/Using the JDBC API for Database Access.adoc b/...cumentation/Application Development/Using the JDBC API for Database Access.adoc
@@ -473,7 +473,7 @@ Check your corresponding JDBC driver vendor's documentation for information on t
 [[allowing-non-component-callers]]
 == Allowing Non-Component Callers
 
-You can allow non-Jakarta-EE components, such as lifecycle modules and third party persistence managers, to use a managed JDBC connection pool.
+You can allow non-Jakarta-EE components, such as third party persistence managers, to use a managed JDBC connection pool.
 
 The returned connection is automatically enlisted with the transaction context obtained from the transaction manager. Standard Jakarta EE components can also use such pools.
 

diff --git a/...tion/Application Development/Using the Java Naming and Directory Interface.adoc b/...tion/Application Development/Using the Java Naming and Directory Interface.adoc
@@ -160,19 +160,6 @@ Object o = ic.lookup("corbaname:iiop:host:port#a/b/Foo");
 
 IMPORTANT: Objects stored in the interoperable naming context and component-specific (`java:comp/env`) naming contexts are transient. On each server startup or application reloading, all relevant objects are re-bound to the namespace.
 
-[[naming-environment-for-lifecycle-modules]]
-=== Naming Environment for Lifecycle Modules
-
-Lifecycle listener modules provide a means of running short or long duration tasks based on Java technology within the Payara Server environment, such as instantiation of singletons or RMI servers.
-
-These modules are automatically initiated at server startup and are notified at various phases of the server life cycle.
-
-For details about lifecycle modules, see xref:Technical Documentation/Application Development/Developing Lifecycle Listeners.adoc#developing-lifecycle-listeners[Developing Lifecycle Listeners].
-
-The configured properties for a lifecycle module are passed as properties during server initialization (the `INIT_EVENT`). The initial JNDI naming context is not available until server initialization is complete.
-
-A lifecycle module can get the `InitialContext` for lookups using the method `LifecycleEventContext.getInitialContext()` during, and only during, the `STARTUP_EVENT`, `READY_EVENT`, or `SHUTDOWN_EVENT` server life cycle events.
-
 [[configuring-resources]]
 == Configuring Resources
 

diff --git a/.../Payara Server Documentation/Application Deployment/Deploying Applications.adoc b/.../Payara Server Documentation/Application Deployment/Deploying Applications.adoc
@@ -1123,23 +1123,6 @@ After application clients are downloaded, they remain on the client until they a
 
 If you undeploy an application client, you can no longer download that application client because it might be in an inconsistent state. If you try to launch an application client that was previously downloaded (even though the server side of the application client is no longer present), the results are unpredictable unless the application client has been written to tolerate such situations.
 
-[[lifecycle-module-deployment-guidelines]]
-== Lifecycle Module Deployment Guidelines
-
-A lifecycle module, also called a lifecycle listener module, provides a means of running long or short Java-based tasks within the Payara Server environment, such as instantiation of singletons or RMI servers.
-
-Lifecycle modules are automatically initiated at server startup and are notified at various phases of the server life cycle. All lifecycle module interfaces are in the `as-install/modules/glassfish-api.jar` file.
-
-For general information about lifecycle modules, see "xref:Technical Documentation/Application Development/Developing Lifecycle Listeners.adoc#developing-lifecycle-listeners[Developing Lifecycle Listeners]" in the Application Development section.
-
-You can deploy a lifecycle module using the `create-lifecycle-module` subcommand. Do not use `asadmin deploy` or related commands.
-
-You do not need to specify a classpath for the lifecycle module if you place it in the `domain-dir/lib` or `domain-dir/lib/classes` directory for the Domain Administration Server (DAS). Do not place it in the `lib` directory for a particular server instance, or it will be deleted when that instance synchronizes with Payara Server.
-
-After you deploy a lifecycle module, you must restart the server. During server initialization, the server instantiates the module and registers it as a lifecycle event listener.
-
-NOTE: If the `--failurefatal` option of `create-lifecycle-module` is set to `true` (the default is `false`), lifecycle module failure prevents server initialization or startup, but not shutdown or termination.
-
 [[web-service-deployment-guidelines]]
 == Web Service Deployment Guidelines
 

diff --git a/...er Documentation/Application Deployment/Elements of Deployment Descriptors.adoc b/...er Documentation/Application Deployment/Elements of Deployment Descriptors.adoc
@@ -4017,7 +4017,7 @@ This parameter is mandatory if and only if `is-connection-validation-required` i
 |`non-transactional-connections` |`false` |(optional) If `true`, non-transactional connections can be made to the JDBC connection pool.
 These connections are not automatically enlisted with the transaction manager.
 
-|`allow-non-component-callers` |`false` |(optional) If `true`, non-Java-EE components, such as servlet filters, lifecycle modules, and third party persistence managers, can use this JDBC connection pool.
+|`allow-non-component-callers` |`false` |(optional) If `true`, non-Java-EE components, such as servlet filters, and third party persistence managers, can use this JDBC connection pool.
 The returned connection is automatically enlisted with the transaction context obtained from the transaction manager. Standard Jakarta EE components can also use such pools.
 Connections obtained by non-component callers are not automatically closed at the end of a transaction by the container. They must be explicitly closed by the caller.
 

diff --git a/... Documentation/Payara Server Documentation/Application Deployment/Overview.adoc b/... Documentation/Payara Server Documentation/Application Deployment/Overview.adoc
@@ -116,7 +116,6 @@ Payara Server supports the following types of modules:
 After deploying a Jakarta EE connector module, you must configure it as described in xref:Technical Documentation/Application Development/Developing Connectors.adoc#developing-connectors[Developing Connectors] in the Payara Server Application Development section.
 * *Application Client Module*. An application client module is a deployable software unit that consists of one or more classes, and application client deployment descriptors
 (`application-client.xml` and `glassfish-application-client.xml`). An application client JAR file applies to a Payara Server type of Jakarta EE client. An application client supports the standard Jakarta EE Application Client specifications.
-* *Lifecycle Module*. A lifecycle module provides a means of running short-duration or long-duration Jakarta-based tasks within the Payara Server environment. Lifecycle modules are not Jakarta EE standard modules. See xref:Technical Documentation/Application Development/Developing Lifecycle Listeners.adoc#developing-lifecycle-listeners[Developing Lifecycle Listeners] in thePayara Server Application Development section for more information.
 
 [[module-based-deployment]]
 ==== *Module-Based Deployment*

diff --git a/...ara Server Documentation/Application Deployment/The Deployment Subcommands.adoc b/...ara Server Documentation/Application Deployment/The Deployment Subcommands.adoc
@@ -12,15 +12,9 @@ xref:ROOT:Technical Documentation/Payara Server Documentation/Command Reference/
 xref:ROOT:Technical Documentation/Payara Server Documentation/Command Reference/create-application-ref.adoc[`create-application-ref`]::
   Creates a reference from a cluster or an un-clustered server instance to a previously deployed Jakarta EE application or module. This effectively results in the application element being deployed and made available on the targeted instance or cluster.
 
-xref:ROOT:Technical Documentation/Payara Server Documentation/Command Reference/create-lifecycle-module.adoc[`create-lifecycle-module`]::
-  Creates a lifecycle module. A lifecycle module provides a means of running a short or long duration Jakarta-based task at a specific stage in the server life cycle.
-
 xref:ROOT:Technical Documentation/Payara Server Documentation/Command Reference/delete-application-ref.adoc[`delete-application-ref`]::
   Removes a reference from a cluster or an un-clustered server instance to a previously deployed Jakarta EE application or module. This effectively results in the application element being un-deployed on the targeted instance or cluster.
 
-xref:ROOT:Technical Documentation/Payara Server Documentation/Command Reference/delete-lifecycle-module.adoc[`delete-lifecycle-module`]::
-  Deletes a lifecycle module.
-
 xref:ROOT:Technical Documentation/Payara Server Documentation/Command Reference/deploy.adoc[`deploy`]::
   Deploys an enterprise application, web application, EJB module, connector module, or application client module. If the component is already deployed or already exists, you can forcefully redeploy if you set the `--force` option to `true`.
   A directory can also be deployed. Supported in remote mode only. For usage instructions, see xref:Technical Documentation/Payara Server Documentation/Application Deployment/Deploying Applications.adoc#to-deploy-an-application-or-module[To Deploy an Application or Module].
@@ -55,9 +49,6 @@ xref:ROOT:Technical Documentation/Payara Server Documentation/Command Reference/
   Lists library JAR files that have been added to Payara Server. You can specify whether to list libraries in the Common class loader directory,
   the Jakarta optional package directory, or the application-specific class loader directory.
 
-xref:ROOT:Technical Documentation/Payara Server Documentation/Command Reference/list-lifecycle-modules.adoc[`list-lifecycle-modules`]::
-  Lists lifecycle modules.
-
 xref:ROOT:Technical Documentation/Payara Server Documentation/Command Reference/list-components.adoc[`list-components`]::
   This subcommand is deprecated. Use the `list-applications` subcommand instead.
 

diff --git a/...ation/Payara Server Documentation/Command Reference/create-application-ref.adoc b/...ation/Payara Server Documentation/Command Reference/create-application-ref.adoc
@@ -49,7 +49,7 @@ asadmin-options::
 == Operands
 
 reference_name::
-  The name of the application or module, which can be a Java EE application, Web module, EJB module, connector module, application client module, or lifecycle module. +
+  The name of the application or module, which can be a Java EE application, Web module, EJB module, connector module or application client module. +
   The name can include an optional version identifier, which follows the name and is separated from the name by a colon (`:`). The version identifier must begin with a letter
   or number. It can contain alphanumeric characters plus underscore (`_`), dash (`-`), and period (`.`) characters. If the `--enabled` option is set to false, you can create
   references to multiple disabled versions by using an asterisk (`*`) as a wildcard character. For more information about module and application versions, see