I am using Wildfly 17 and I have recieved the folowing Exception two times in the last month:
(PriorityExampleScheduler_Worker-1) WFLYEE0043: Component is stopped: org.jboss.as.ee.component.ComponentIsStoppedException: WFLYEE0043: Component is stopped
at [email protected]//org.jboss.as.ee.component.BasicComponent.waitForComponentStart(BasicComponent.java:110)
at [email protected]//org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:194)
at [email protected]//org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185)
at [email protected]//org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:81)
at deployment.heimdi.war//at.home.digest.services.AVeDBService$$$view41.clearWinner(Unknown Source)
at deployment.heimdi.war//at.home.digest.model.dave.OnAveCompletionJob.execute(OnAveCompletionJob.java:36)
at deployment.heimdi.war//org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at deployment.heimdi.war//org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)
AVeDBService is marked as a @Stateless and represents a class accessing the database using JPA.
Wildfly makes and invokes a proxy of this class with the name
at.home.digest.services.AVeDBService$$$view41
Now: when and why could this compoment be stopped? Why I recieved this exception only two times in the last month, although the code has been invoked many times?
After I restarted the application, the exception was not thrown anymore, But this does not solve my problem.
This error isn't usually the cause but the result of something else (like app server crash). Monitor app server with tool like VisualVM + create heap dump automatically when app server crash in case of out of memory: -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=
It seems to me that your app server (or your deployed component) was already down when you call this method.
Long time monitor with tool like VisualVM may help you trace the cause of this problem.