[JBoss JIRA] (WFLY-11134) SecurityAuditingTestCase fails intermittently
by Vilém Obrátil (Jira)
[ https://issues.jboss.org/browse/WFLY-11134?page=com.atlassian.jira.plugin... ]
Vilém Obrátil commented on WFLY-11134:
--------------------------------------
I have been able to reproduce it once out of three tries and even in the testing pipeline this error appeared intermittently. So if you don't manage to reproduce it on RHEL x64 either, I suppose we've done all we could and there is no point wasting any more time on this one.
> SecurityAuditingTestCase fails intermittently
> ---------------------------------------------
>
> Key: WFLY-11134
> URL: https://issues.jboss.org/browse/WFLY-11134
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Environment: RHEL6 (x86_64), dynamic, large
> OpenJDK 1.8 and OpenJDK 1.11
> Apache Maven 3.5.0
> and
> Apache Maven 3.5.0 (Red Hat 3.5.0-6)
> Maven home: /usr/share/maven
> Java version: 1.8.0_181, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.181.b15-0.fc27.x86_64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.18.10-100.fc27.x86_64", arch: "amd64", family: "unix"
> ---
> openjdk version "1.8.0_181"
> OpenJDK Runtime Environment (build 1.8.0_181-b15)
> OpenJDK 64-Bit Server VM (build 25.181-b15, mixed mode)
> Reporter: Vilém Obrátil
> Priority: Major
>
> org.jboss.as.test.integration.security.auditing.SecurityAuditingTestCase.testSingleMethodAnnotationsUser1Template seems to occasionally fail with the following message:
> Login record has not been written into audit log! (time expired). Checked regex=(TRACE.+org.jboss.security.audit.+Success.+user1|SecurityAuthenticationSuccessfulEvent.*"name":"user1")
> This seems to be happening most often on RHEL 6 x64 machines.
> *Stack Trace:*
> java.lang.AssertionError: Login record has not been written into audit log! (time expired). Checked regex=(TRACE.+org.jboss.security.audit.+Success.+user1|SecurityAuthenticationSuccessfulEvent.*"name":"user1")
> at org.jboss.as.test.integration.security.auditing.SecurityAuditingTestCase.checkAuditLog(SecurityAuditingTestCase.java:234)
> at org.jboss.as.test.integration.security.auditing.SecurityAuditingTestCase.testSingleMethodAnnotationsUser1Template(SecurityAuditingTestCase.java:188)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.jboss.arquillian.junit.Arquillian$8$1.invoke(Arquillian.java:379)
> at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60)
> at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:85)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:143)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53)
> at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:85)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129)
> at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92)
> at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130)
> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92)
> at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73)
> at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:143)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136)
> at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:372)
> at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:246)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:431)
> at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:55)
> at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:260)
> at org.jboss.arquillian.junit.Arquillian$7$1.invoke(Arquillian.java:324)
> at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99)
> at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:72)
> at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:85)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124)
> at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92)
> at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130)
> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92)
> at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73)
> at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:92)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:143)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.fireCustomLifecycle(EventTestRunnerAdaptor.java:159)
> at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:317)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:205)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:431)
> at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:55)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:219)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:167)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFWIP-133) wildfly-microprofile-metrics-smallrye_1_0.xsd should provide some documentation for allowed attributes
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFWIP-133?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil commented on WFWIP-133:
-----------------------------------
I'm rather -1 on this one.
WildFly management model is thoroughly described both in the CLI and on http://wildscribe.github.io (including metadata).
As long as the XSD maps quite simply to the management model, I prefer to avoid documentation duplication (and the maintenance cost associated to it).
> wildfly-microprofile-metrics-smallrye_1_0.xsd should provide some documentation for allowed attributes
> ------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-133
> URL: https://issues.jboss.org/browse/WFWIP-133
> Project: WildFly WIP
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Rostislav Svoboda
> Assignee: Jeff Mesnil
> Priority: Major
>
> wildfly-microprofile-metrics-smallrye_1_0.xsd should provide some documentation for allowed attributes
> CLI provides description for attributes via {{/subsystem=microprofile-metrics-smallrye:read-resource-description}}.
> Same information should be present in wildfly-microprofile-metrics-smallrye_1_0.xsd via {{<xs:annotation>}} and {{<xs:documentation>}}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (JGRP-2312) LazyThreadFactory can keep threads instances alive for a long period
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2312?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2312:
---------------------------
Fix Version/s: 3.6.17
> LazyThreadFactory can keep threads instances alive for a long period
> --------------------------------------------------------------------
>
> Key: JGRP-2312
> URL: https://issues.jboss.org/browse/JGRP-2312
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.15
> Reporter: William Burns
> Assignee: Bela Ban
> Priority: Major
> Fix For: 4.0.16, 3.6.17
>
>
> The LazyThreadFactory keeps all Thread objects in a ConcurrentLinkedQueue wrapped by a WeakReference. This means that once a thread terminates, its instance along with all native memory required for it can linger until the GC eventually reclaims it. Normally this is not an issue when the JVM heap is being recycled often, but in cases where you have low heap requirement operations (ie. off heap data container) this can cause these objects to pile up and eventually exhaust native memory.
> This queue is also a very slow JVM heap leak as threads are tossed out, since the WeakReference and Queue Node objects are never reclaimed unless the transport is stopped.
> The best way to fix this would be to plug into when the thread is set to TERMINATED state and to remove these nodes.
> Also a workaround is to increase the core thread count and increase the keepalive timeout so that threads are not destroyed and created nearly as often.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-2727) [DMN Designer] Demo the Custom Data Type definition
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2727?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-2727:
-------------------------------------
[~karreiro] Please provide the link for your blog.
> [DMN Designer] Demo the Custom Data Type definition
> ---------------------------------------------------
>
> Key: DROOLS-2727
> URL: https://issues.jboss.org/browse/DROOLS-2727
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.9.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> We should demo the definition of custom data type using our DMN authoring tool. I think we have multiple options:
> - Youtube video
> - Github wiki page
> - drools website
> - drools docs
> For last two options I think we can work on some custom branch and publish when more content about DMN authoring will be prepared.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-2727) [DMN Designer] Demo the Custom Data Type definition
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2727?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2727:
--------------------------------
Fix Version/s: 7.14.0.Final
> [DMN Designer] Demo the Custom Data Type definition
> ---------------------------------------------------
>
> Key: DROOLS-2727
> URL: https://issues.jboss.org/browse/DROOLS-2727
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.9.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Fix For: 7.14.0.Final
>
>
> We should demo the definition of custom data type using our DMN authoring tool. I think we have multiple options:
> - Youtube video
> - Github wiki page
> - drools website
> - drools docs
> For last two options I think we can work on some custom branch and publish when more content about DMN authoring will be prepared.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-2727) [DMN Designer] Demo the Custom Data Type definition
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-2727?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro resolved DROOLS-2727.
----------------------------------------
Resolution: Done
> [DMN Designer] Demo the Custom Data Type definition
> ---------------------------------------------------
>
> Key: DROOLS-2727
> URL: https://issues.jboss.org/browse/DROOLS-2727
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.9.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> We should demo the definition of custom data type using our DMN authoring tool. I think we have multiple options:
> - Youtube video
> - Github wiki page
> - drools website
> - drools docs
> For last two options I think we can work on some custom branch and publish when more content about DMN authoring will be prepared.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-2727) [DMN Designer] Demo the Custom Data Type definition
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-2727?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-2727:
---------------------------------------
Summary: [DMN Designer] Demo the Custom Data Type definition (was: [DMN Editor] Demo the Custom Data Type definition)
> [DMN Designer] Demo the Custom Data Type definition
> ---------------------------------------------------
>
> Key: DROOLS-2727
> URL: https://issues.jboss.org/browse/DROOLS-2727
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.9.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> We should demo the definition of custom data type using our DMN authoring tool. I think we have multiple options:
> - Youtube video
> - Github wiki page
> - drools website
> - drools docs
> For last two options I think we can work on some custom branch and publish when more content about DMN authoring will be prepared.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months