You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a Jakarta Data application is started, the EMs are built asynchronously, which may result in errors if the application is stopped before the asynchronous threads complete. The errors appear as below.
Note that FFDC is no longer logged, as it is suppressed in FutureEMBuilder in favor of logging CWWKD1080E.
The most common scenario for the error is:
Thread 1 : createEMBuilder creates the DatabaseStore
Thread 2 : application stop - destroys the DatabaseStore (DataProvider.applicationStopped)
Thread 1 : attempts to go on and use the DatabaseStore it just created, only to find it destroyed.
Some thoughts on resolving:
Application stopping could:
attempt to cancel all of the async threads; but currently the futures for them are not saved anywhere
attempt to wait for any futures that could not be cancelled
createEMBuild could
check periodically to see if the app was uninstalled and stop processing
[10/28/24, 21:31:11:268 PDT] 0000009c com.ibm.wsspi.persistence.internal.DatabaseStoreImpl E CWWKD0202E: This DatabaseStore has been deactivated.
[10/28/24, 21:31:11:284 PDT] 0000009c io.openliberty.data.internal.persistence.cdi.DataExtension E CWWKD1080E: One or more repository interfaces (ee.jakarta.tck.data.framework.read.only.AsciiCharacters, ee.jakarta.tck.data.framework.read.only.CustomRepository, ee.jakarta.tck.data.framework.read.only.NaturalNumbers, ee.jakarta.tck.data.framework.read.only.PositiveIntegers, ee.jakarta.tck.data.standalone.entity.Boxes) from the null application artifact are not available because of an error. The error might be due to a configuration problem, or the java:comp/DefaultDataSource data store for the repository might not be available. The error is: java.lang.IllegalStateException: CWWKD0202E: This DatabaseStore has been deactivated.
at com.ibm.wsspi.persistence.internal.DatabaseStoreImpl.createPersistenceServiceUnit(DatabaseStoreImpl.java:304)
at io.openliberty.data.internal.persistence.service.DBStoreEMBuilder.<init>(DBStoreEMBuilder.java:452)
at io.openliberty.data.internal.persistence.cdi.FutureEMBuilder.createEMBuilder(FutureEMBuilder.java:367)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1768)
at com.ibm.ws.threading.internal.ExecutorServiceImpl$RunnableWrapper.run(ExecutorServiceImpl.java:298)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:857)
.```
The text was updated successfully, but these errors were encountered:
When a Jakarta Data application is started, the EMs are built asynchronously, which may result in errors if the application is stopped before the asynchronous threads complete. The errors appear as below.
Note that FFDC is no longer logged, as it is suppressed in FutureEMBuilder in favor of logging CWWKD1080E.
The most common scenario for the error is:
Thread 1 : createEMBuilder creates the DatabaseStore
Thread 2 : application stop - destroys the DatabaseStore (DataProvider.applicationStopped)
Thread 1 : attempts to go on and use the DatabaseStore it just created, only to find it destroyed.
Some thoughts on resolving:
Application stopping could:
createEMBuild could
The text was updated successfully, but these errors were encountered: