[JBoss JIRA] (WFCORE-5020) Although elytron has module for JACC factory it is not used for JACC
by Jeff Mesnil (Jira)
[ https://issues.redhat.com/browse/WFCORE-5020?page=com.atlassian.jira.plug... ]
Jeff Mesnil updated WFCORE-5020:
--------------------------------
Fix Version/s: (was: 13.0.0.Beta1)
> Although elytron has module for JACC factory it is not used for JACC
> --------------------------------------------------------------------
>
> Key: WFCORE-5020
> URL: https://issues.redhat.com/browse/WFCORE-5020
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 12.0.1.Final
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
>
> A module can be specified and this is used to load the specified provider class and instantiate it, however this is separate to the one instantiated by PolicyConfigurationFactory.
> Elytron does set a system property to ensure the configured class name is used but does not actually ensure the module is used for class loading.
> At the same time it should be ensuring there is only a single instance of the class.
--
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 edited comment on WFLY-13641 at 7/8/20 5:38 AM:
------------------------------------------------------------
Here is some documentation about cross-module CDI and jboss-deployment-structure
[https://docs.wildfly.org/17/Developer_Guide.html#CDI_Reference]
>From my understanding cross-module CDI should only ever be activated if you specify meta-inf="import" on a dependency. But this is not the case for our deployments
was (Author: jviebig):
Here is some documentation about cross-module CDI and jboss-deploymet-structure
[https://docs.wildfly.org/17/Developer_Guide.html#CDI_Reference]
>From my understanding cross-module CDI should only ever be activated if you specify meta-inf="import" on a dependency. But this is not the case for our deployments
> 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
[JBoss JIRA] (WFLY-13177) ManagedExecutorService: Wrong activeRequestCount at RequestController on RejectedExecutionException
by Ivo Studensky (Jira)
[ https://issues.redhat.com/browse/WFLY-13177?page=com.atlassian.jira.plugi... ]
Ivo Studensky reassigned WFLY-13177:
------------------------------------
Assignee: Ivo Studensky (was: Eduardo Martins)
> ManagedExecutorService: Wrong activeRequestCount at RequestController on RejectedExecutionException
> ---------------------------------------------------------------------------------------------------
>
> Key: WFLY-13177
> URL: https://issues.redhat.com/browse/WFLY-13177
> Project: WildFly
> Issue Type: Bug
> Components: Concurrency Utilities
> Affects Versions: 13.0.0.Final, 16.0.0.Final
> Reporter: Guido Jäkel
> Assignee: Ivo Studensky
> Priority: Critical
> Fix For: 21.0.0.Beta1
>
>
> On WF-13 and WF-16 we observe a serious bug of the RequestCount of the RequestController while using ManagedExecutorService.submit() or ...execute() in the edge case of a full queue. In this case, the caller gets a RejectedExecutionException, but in the RequestController, the number of active requests is erroneously incremented.
> This will lead to a false and monotonously increasing number of active requests. And in case of a limitation configured by the maxRequestCount feature, which is best practice for production environments, over the time this will lead to deadlock of the RequestController and herewith the complete activity of the Wildfly at all.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 2 months