[JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem
by Richard Achmatowicz (Jira)
[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ]
Richard Achmatowicz commented on WFLY-13433:
--------------------------------------------
The only differences I can see between running -DallTests locally and what the CI runs is:
* -Djboss.test.mixed.domain.dir to run the mixed domain tests, as described above
* -Dipv6 to enforce IPv6
* -Djboss.test.transformers.eap to run the EAP transformer tests
* -DlegacyBuild to require a legacy build (using Wildfly Build Tools) for Galleon feature pack purposes
* -DlegacyRelease to require a legacy release (using Wildfly Build Tools) for Galleon feature pack purposes
* -Dmaven.test.failure.ignore=true to prevent maven from stopping testsuite execution on a failure
* -DfailIfNoTests=false to prevent surefire stopping when no tests available to run
It would be nice to have a special target to represent these which would be used locally; or to make -DallTests match what the CI does.
This may also require some local configuration for running the clustering tests using IPv6, as mentioned in testsuite/pom.xml :
{noformat}
<!-- Allow loopback to multicast -->
<!-- ip -6 route add table local local ff13::/16 dev lo metric 5 -->
{noformat}
> Improve capability support in EJB3 subsystem
> --------------------------------------------
>
> Key: WFLY-13433
> URL: https://issues.redhat.com/browse/WFLY-13433
> Project: WildFly
> Issue Type: Enhancement
> Components: EJB
> Affects Versions: 20.0.0.Beta1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Priority: Major
>
> Survey all external subsystem dependencies and introduce capability based dependencies where required.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (WFCORE-5053) Prometheus JMX exporter jar, stops starting the wildfly server.
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-5053?page=com.atlassian.jira.plug... ]
James Perkins commented on WFCORE-5053:
---------------------------------------
[~rakesh.shah1977] It's already been released. You can just download JBoss Modules 1.10.1 (https://search.maven.org/artifact/org.jboss.modules/jboss-modules/1.10.1....). You'll also need to modify your {{standalone.bat}} script too. You'll need to remove the reset the the {{MODULE_OPTS}} environment variable. See https://github.com/wildfly/wildfly-core/pull/4131/files#diff-ce685ca37a3d... and https://github.com/wildfly/wildfly-core/pull/4131/files#diff-0859a1503bc9....
> Prometheus JMX exporter jar, stops starting the wildfly server.
> ----------------------------------------------------------------
>
> Key: WFCORE-5053
> URL: https://issues.redhat.com/browse/WFCORE-5053
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: Rakesh Kumar Shah
> Assignee: James Perkins
> Priority: Major
> Fix For: 13.0.0.Beta1
>
>
> Trying to integrate the Prometheus JMX exporter with wildfly. After spending lot of time and work around it, wildfly is not starting. It throws following exception.
> {code}
> java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager
> at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
> at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at java.logging/java.util.logging.LogManager$1.run(LogManager.java:239)
> at java.logging/java.util.logging.LogManager$1.run(LogManager.java:223)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at java.logging/java.util.logging.LogManager.<clinit>(LogManager.java:223)
> at java.logging/java.util.logging.Logger.demandLogger(Logger.java:648)
> at java.logging/java.util.logging.Logger.getLogger(Logger.java:717)
> at java.logging/java.util.logging.Logger.getLogger(Logger.java:701)
> at io.prometheus.jmx.shaded.io.prometheus.jmx.JmxCollector.<clinit>(JmxCollector.java:39)
> at io.prometheus.jmx.shaded.io.prometheus.jmx.JavaAgent.premain(JavaAgent.java:29)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:513)
> at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:525)
> WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logmanager/Level
> at java.base/java.lang.Class.forName0(Native Method)
> at java.base/java.lang.Class.forName(Class.java:398)
> at org.jboss.modules.Module.run(Module.java:340)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:617)
> Caused by: java.lang.ClassNotFoundException: org.jboss.logmanager.Level
> at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
> at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at org.jboss.modules.JDKSpecific.getSystemClass(JDKSpecific.java:183)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:395)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (DROOLS-5522) Fix InternalKieModule.createKieModule
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-5522?page=com.atlassian.jira.plug... ]
Mario Fusco updated DROOLS-5522:
--------------------------------
Sprint: 2020 Week 28-30 (from Jul 6)
> Fix InternalKieModule.createKieModule
> -------------------------------------
>
> Key: DROOLS-5522
> URL: https://issues.redhat.com/browse/DROOLS-5522
> Project: Drools
> Issue Type: Task
> Reporter: Gabriele Cardosi
> Assignee: Mario Fusco
> Priority: Major
>
> {code:java}
> org.drools.compiler.kie.builder.impl.InternalKieModule.createKieModule(ReleaseId releaseId, File jar)
> {code}
> has a couple of issues
> 1) there is not a check on the actual type of File received as parameter: it expects it to be a "jar" - but this is not checked anywhere - so
> {code:java}
> ZipFile zipFile = new ZipFile(jar)
> {code}
> throws an exception whenever the given file is not a "jar"
> 2) every exceptions are catch and simply logged; but it seems that whatever exception may happen inside this if
> {code:java}
> if (zipEntry != null) {
> KieModuleModel kieModuleModel = KieModuleModelImpl.fromXML( zipFile.getInputStream( zipEntry ) );
> setDefaultsforEmptyKieModule( kieModuleModel );
> return kieModuleModel != null ? InternalKieModuleProvider.get( adapt( releaseId ), kieModuleModel, jar ) : null;
> }
> {code}
> it is actually a grave exception, since it means that it was impossible to retrieve an expected KieModule out of a given "kjar" (we know it is a kjar because zipEntry != null)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem
by Richard Achmatowicz (Jira)
[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ]
Richard Achmatowicz commented on WFLY-13433:
--------------------------------------------
The mixed domain tests basically run various types of tests (deployment, operation invocation, etc) in a domain with mixed versions of EAP, if I understand correctly. They also "adjust" domain.xml profiles in a version specific way: default profiles have certain resources removed before running the test for compatibility reasons.
The mixed domain tests are enabled as follows:
{noformat}
-Djboss.test.mixed.domain.dir=/some/dir/
{noformat}
where /some/dir/ is a directory holding jboss-eap-6.4.0.zip, jboss-eap-7.0.0.zip, jboss-eap-7.1.0.zip, jboss-eap-7.2.0.zip and jboss-eap-7.3.0.zip (these are the current legacy versions used in the mixed domain tests). No other command line flags are necessary.
The resulting test output looks like:
{noformat}
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainOverlay700TestSuite
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 22.678 s - in org.jboss.as.test.integration.domain.mixed.eap700.MixedDomainOverlay700TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap700.ElytronOnlyMaster700TestSuite
[INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 22.692 s - in org.jboss.as.test.integration.domain.mixed.eap700.ElytronOnlyMaster700TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap700.MixedDomain700TestSuite
[INFO] Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 42.546 s - in org.jboss.as.test.integration.domain.mixed.eap700.MixedDomain700TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap700.KernelBehavior700TestSuite
[INFO] Tests run: 30, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 18.075 s - in org.jboss.as.test.integration.domain.mixed.eap700.KernelBehavior700TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap700.LegacyConfig700TestSuite
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 34.868 s - in org.jboss.as.test.integration.domain.mixed.eap700.LegacyConfig700TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap710.LegacyConfig710TestSuite
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 38.46 s - in org.jboss.as.test.integration.domain.mixed.eap710.LegacyConfig710TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap710.KernelBehavior710TestSuite
[INFO] Tests run: 30, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 18.465 s - in org.jboss.as.test.integration.domain.mixed.eap710.KernelBehavior710TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap710.MixedDomain710TestSuite
[WARNING] Tests run: 20, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 45.875 s - in org.jboss.as.test.integration.domain.mixed.eap710.MixedDomain710TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap710.MixedDomainOverlay710TestSuite
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 23.353 s - in org.jboss.as.test.integration.domain.mixed.eap710.MixedDomainOverlay710TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap710.ElytronOnlyMaster710TestSuite
[INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 23.671 s - in org.jboss.as.test.integration.domain.mixed.eap710.ElytronOnlyMaster710TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap720.LegacyConfig720TestSuite
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 41.066 s - in org.jboss.as.test.integration.domain.mixed.eap720.LegacyConfig720TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap720.ElytronOnlyMaster720TestSuite
[INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 25.567 s - in org.jboss.as.test.integration.domain.mixed.eap720.ElytronOnlyMaster720TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap720.MixedDomainOverlay720TestSuite
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 24.598 s - in org.jboss.as.test.integration.domain.mixed.eap720.MixedDomainOverlay720TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap720.MixedDomain720TestSuite
[INFO] Tests run: 20, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 48.496 s - in org.jboss.as.test.integration.domain.mixed.eap720.MixedDomain720TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap720.KernelBehavior720TestSuite
[INFO] Tests run: 30, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 18.575 s - in org.jboss.as.test.integration.domain.mixed.eap720.KernelBehavior720TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap640.ElytronOnlyMaster640TestSuite
[INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 22.498 s - in org.jboss.as.test.integration.domain.mixed.eap640.ElytronOnlyMaster640TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap640.MixedDomain640TestSuite
[INFO] Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 54.406 s - in org.jboss.as.test.integration.domain.mixed.eap640.MixedDomain640TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap640.LegacyConfig640TestSuite
// my failure now identified locally
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.58 s - in org.jboss.as.test.integration.domain.mixed.eap640.KernelBehavior640TestSuite
[INFO] Tests run: 30, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 18.14 s - in org.jboss.as.test.integration.domain.mixed.eap640.KernelBehavior640TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap640.MixedDomainOverlay640TestSuite
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 29.139 s - in org.jboss.as.test.integration.domain.mixed.eap640.MixedDomainOverlay640TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap730.KernelBehavior730TestSuite
[INFO] Tests run: 30, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 23.435 s - in org.jboss.as.test.integration.domain.mixed.eap730.KernelBehavior730TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap730.ElytronOnlyMaster730TestSuite
[INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 27.105 s - in org.jboss.as.test.integration.domain.mixed.eap730.ElytronOnlyMaster730TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap730.MixedDomain730TestSuite
[WARNING] Tests run: 20, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 48.693 s - in org.jboss.as.test.integration.domain.mixed.eap730.MixedDomain730TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap730.MixedDomainOverlay730TestSuite
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 26.293 s - in org.jboss.as.test.integration.domain.mixed.eap730.MixedDomainOverlay730TestSuite
[INFO] Running org.jboss.as.test.integration.domain.mixed.eap730.LegacyConfig730TestSuite
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 52.543 s - in org.jboss.as.test.integration.domain.mixed.eap730.LegacyConfig730TestSuite
{noformat}
In an ideal world, there would be a shorthand in integration-tests.sh, something like -Dmixed-domain, which would create and populate the required legacy versions directory and run the tests. This would improve the visibility of the tests and make running them locally a little easier, without having any custom knowledge. The documentation would be updated as well.
> Improve capability support in EJB3 subsystem
> --------------------------------------------
>
> Key: WFLY-13433
> URL: https://issues.redhat.com/browse/WFLY-13433
> Project: WildFly
> Issue Type: Enhancement
> Components: EJB
> Affects Versions: 20.0.0.Beta1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Priority: Major
>
> Survey all external subsystem dependencies and introduce capability based dependencies where required.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (WFLY-13686) Deadlock on Wildfly startup
by Cheng Fang (Jira)
[ https://issues.redhat.com/browse/WFLY-13686?page=com.atlassian.jira.plugi... ]
Cheng Fang commented on WFLY-13686:
-----------------------------------
may be somewhat related to WFLY-10879
> Deadlock on Wildfly startup
> ---------------------------
>
> Key: WFLY-13686
> URL: https://issues.redhat.com/browse/WFLY-13686
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 20.0.1.Final
> Reporter: K G
> Assignee: Cheng Fang
> Priority: Major
>
> On Wildfly startup there can be a deadlock related to ejb/singleton access and more specifically: StartupAwaitInterceptor and ContainerManagedConcurrencyInterceptor. This can happen when there is a too early client request (occurring during app startup) or a request caused by thread running in managed executor (that's what happened to me). A thread that is blocked by StartupAwaitInterceptor also holds a lock from ContainerManagedConcurrencyInterceptor and blocks other threads. This is related to the following pull request, link to the comment: [https://github.com/wildfly/wildfly/pull/9009#issuecomment-656147415] .
> I guess possible solution is to change interceptors ordering. Other possibility is to add "privileged" flag (see pull request for explanation) to threads from managed thread factory but in this case a too early client request could also cause a dealock.
>
> Scenario of deadlock (description copied from pull request's comment):
> * startup singleton A's initialization starts and completes successfully
> * startup singleton B is initializing and during that it starts a task X via managedThreadExecutor
> * X wants to access A and is blocked by StartupCountdown.await
> * meanwhile B continues initializing and wants to access A but X already holds a lock on A (I can see ContainerManagedConcurrencyInterceptor.processInvocation in the tread dump) hence after 5000ms B's initialization fails as well as whole deployment
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months