[JBoss JIRA] (WFLY-13656) Wildfly 18 - Failed to run scheduled task - after redeployment
by ralph Soika (Jira)
ralph Soika created WFLY-13656:
----------------------------------
Summary: Wildfly 18 - Failed to run scheduled task - after redeployment
Key: WFLY-13656
URL: https://issues.redhat.com/browse/WFLY-13656
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 18.0.0.Final
Reporter: ralph Soika
Assignee: Cheng Fang
I have a application deployed on wildfly 18 implementing a @Singleton ejb which starts a ManagedScheduledExecutorService on @PostContstruct init method.
This service runs fine until I do a redeployment without a server restart (auto deploy function).
After a redeployment the following message occurred permanently:
{{imixs-documents_1 | 17:42:23,207 ERROR [org.jboss.as.ee] (EE-ManagedScheduledExecutorService-default-Thread-5) WFLYEE0110: Failed to run scheduled task: org.jboss.as.ee.component.ComponentIsStoppedException: WFLYEE0043: Component is stopped}}
{{imixs-documents_1 | at org.jboss.as.ee@18.0.0.Final//org.jboss.as.ee.component.BasicComponent.waitForComponentStart(BasicComponent.java:110)}}
{{imixs-documents_1 | at org.jboss.as.ee@18.0.0.Final//org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:194)}}
{{imixs-documents_1 | at org.jboss.as.ee@18.0.0.Final//org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185)}}
{{imixs-documents_1 | at org.jboss.as.ee@18.0.0.Final//org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:81)}}
{{imixs-documents_1 | at deployment.imixs-documents.war//org.imixs.workflow.engine.EventLogService$$$view52.releaseDeadLocks(Unknown Source)}}
{{imixs-documents_1 | at jdk.internal.reflect.GeneratedMethodAccessor36.invoke(Unknown Source)}}
{{imixs-documents_1 | at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)}}
{{imixs-documents_1 | at java.base/java.lang.reflect.Method.invoke(Method.java:564)}}
{{imixs-documents_1 | at org.jboss.weld.core@3.1.2.Final//org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:410)}}
{{imixs-documents_1 | at org.jboss.weld.core@3.1.2.Final//org.jboss.weld.module.ejb.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:134)}}
{{imixs-documents_1 | at org.jboss.weld.core@3.1.2.Final//org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56)}}
{{imixs-documents_1 | at org.jboss.weld.core@3.1.2.Final//org.jboss.weld.module.ejb.InjectionPointPropagatingEnterpriseTargetBeanInstance.invoke(InjectionPointPropagatingEnterpriseTargetBeanInstance.java:68)}}
{{imixs-documents_1 | at org.jboss.weld.core@3.1.2.Final//org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:106)}}
{{imixs-documents_1 | at deployment.imixs-documents.war//org.imixs.workflow.engine.EventLogService$Proxy$_$$_Weld$EnterpriseProxy$.releaseDeadLocks(Unknown Source)}}
{{imixs-documents_1 | at deployment.imixs-documents.war//org.imixs.workflow.engine.AsyncEventScheduler.run(AsyncEventScheduler.java:125)}}
{{imixs-documents_1 | at org.jboss.as.ee@18.0.0.Final//org.jboss.as.ee.concurrent.ControlPointUtils$ControlledScheduledRunnable.run(ControlPointUtils.java:158)}}
{{imixs-documents_1 | at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:514)}}
{{imixs-documents_1 | at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)}}
{{imixs-documents_1 | at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:383)}}
{{imixs-documents_1 | at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:534)}}
{{imixs-documents_1 | at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1135)}}
{{imixs-documents_1 | at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)}}
{{imixs-documents_1 | at java.base/java.lang.Thread.run(Thread.java:844)}}
{{imixs-documents_1 | at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250)}}
{{imixs-documents_1 |}}
I can not see how to solve this exception within my application. The message occurs each timeout (in my case every 500ms)
Only a server restart did solve the problem.
But the scheduler runs correctly even with this message.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 2 months
[JBoss JIRA] (WFLY-13648) Make PicketBox PolicyContextHandlers discoverable using ServiceLoader<>
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFLY-13648?page=com.atlassian.jira.plugi... ]
Darran Lofthouse updated WFLY-13648:
------------------------------------
Description:
By making them available using ServlceLoader discovery it will mean the Elytron subsystem will not need mandatory dependencies on PicketBox or the legacy security subsystem to co-exist with the legacy implementations.
This will involve adding a new module security-integration which will contain the service descriptor.
was:
By making them available using ServlceLoader discovery it will mean the Elytron subsystem will not need mandatory dependencies on PicketBox or the legacy security subsystem to co-exist with the legacy implementations.
> Make PicketBox PolicyContextHandlers discoverable using ServiceLoader<>
> -----------------------------------------------------------------------
>
> Key: WFLY-13648
> URL: https://issues.redhat.com/browse/WFLY-13648
> Project: WildFly
> Issue Type: Task
> Components: Build System, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 21.0.0.Beta1
>
>
> By making them available using ServlceLoader discovery it will mean the Elytron subsystem will not need mandatory dependencies on PicketBox or the legacy security subsystem to co-exist with the legacy implementations.
>
> This will involve adding a new module security-integration which will contain the service descriptor.
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 2 months
[JBoss JIRA] (WFCORE-4873) Upgrade JGit to 5.8.0.202006091008-r
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFCORE-4873?page=com.atlassian.jira.plug... ]
Emmanuel Hugonnet updated WFCORE-4873:
--------------------------------------
Description: In order to be able to switch the ssh implementation we need to upgrade JGit to 5.8.0.202006091008-r and update javaewah to 1.1.7 on the way. (was: In order to be able to switch the ssh implementation we need to upgrade JGit to 5.8.0.202006091008-r)
> Upgrade JGit to 5.8.0.202006091008-r
> ------------------------------------
>
> Key: WFCORE-4873
> URL: https://issues.redhat.com/browse/WFCORE-4873
> Project: WildFly Core
> Issue Type: Component Upgrade
> Components: Management
> Affects Versions: 11.0.0.Final
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Major
>
> In order to be able to switch the ssh implementation we need to upgrade JGit to 5.8.0.202006091008-r and update javaewah to 1.1.7 on the way.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 2 months
[JBoss JIRA] (WFLY-13641) WFLYWELD0055: Could not index class [Someclass] from an external bean archive: vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml
by Jens Viebig (Jira)
[ https://issues.redhat.com/browse/WFLY-13641?page=com.atlassian.jira.plugi... ]
Jens Viebig commented on WFLY-13641:
------------------------------------
Here is the sample project.
Source: [https://github.com/JSurf/WFLY-13641]
Binaries: [https://github.com/JSurf/WFLY-13641/releases]
Issue can be reproduced with a fresh download of wildfly by just deploying the ear and war
You can skip step 1 and 2 when using the binaries
# Build ear
{{cd ear}}
{{mvn install}}
{{cd ..}}
# Build war
{{cd war}}
{{mvn install}}
# Download wildfly zip, unpack
# copy ear/ear/target/myear.ear to wildfly standalone/deployments
# copy war/target/mywar.war to wildfly standalone/deployments
# Start wildfly with standalone.bat or standalone.sh
> WFLYWELD0055: Could not index class [Someclass] from an external bean archive: vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-13641
> URL: https://issues.redhat.com/browse/WFLY-13641
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 20.0.0.Final
> Reporter: Jens Viebig
> Assignee: Matěj Novotný
> Priority: Major
>
> When referencing a jar with CDI scan mode "annotaded" inside an ear from an external war via jboss-deployment-structure.xml a warning will be printed for every class:
> WFLYWELD0055: Could not index class [Someclass] from an external bean archive: vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml
> Seems VFS cannot get hold of the classes.
> The warning is logged in ExternalBeanArchiveProcessor which catches an EOFException from the inputstream loading the class. (Line 284). Seems the input stream is not able to load a single byte from the class
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 2 months