July 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1665) Uncomment gc logging function in startup scripts; require env var to enable it

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1665: ---------------------------------------- Summary: Uncomment gc logging function in startup scripts; require env var to enable it Key: WFCORE-1665 URL: https://issues.jboss.org/browse/WFCORE-1665 Project: WildFly Core Issue Type: Task Components: Scripts Reporter: Brian Stansberry Assignee: Tomaz Cerar Fix For: 3.0.0.Alpha4 Our startup scripts have gc logging functionality specified by EAP6-121 that is commented out by default. This approach to disabling this function makes it difficult to use these scripts in EAP; see JBEAP-5374. We should uncomment function this but only enable it if an env var is set. The .conf files core ships will not set this env var. The ones EAP ships can. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1640) Intermittent failure in DeploymentScannerUnitTestCase

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1640?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet edited comment on WFCORE-1640 at 7/22/16 11:28 AM: --------------------------------------------------------------------- It seems to fail only on IPv6 Windows was (Author: ehugonnet): It seems to fail only on Windows > Intermittent failure in DeploymentScannerUnitTestCase > ----------------------------------------------------- > > Key: WFCORE-1640 > URL: https://issues.jboss.org/browse/WFCORE-1640 > Project: WildFly Core > Issue Type: Bug > Components: Deployment Scanner, Test Suite > Affects Versions: 2.2.0.CR5 > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > > DeploymentScannerUnitTestCase.testStartup() has been failing intermittently since May: > https://ci.wildfly.org/project.html?projectId=WildFlyCore&buildTypeId=&ta... > The May 4 failure is the first that was not associated with some large scale failure; i.e. is more likely to be relevant to the test itself. > I'll send up a PR to @Ignore this test. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-595) Ability to provide CallbackHandler and SSLContext when AuthenticationConfiguration dynamically loaded.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-595: ------------------------------------ Summary: Ability to provide CallbackHandler and SSLContext when AuthenticationConfiguration dynamically loaded. Key: ELY-595 URL: https://issues.jboss.org/browse/ELY-595 Project: WildFly Elytron Issue Type: Feature Request Components: Authentication Client Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta7 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4316) InvalidBytecodeException when an EJB local interface declares static method

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4316?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4316: ----------------------------------------------- Fedor Gavrilov <fgavrilo(a)redhat.com> changed the Status of [bug 1346242|https://bugzilla.redhat.com/show_bug.cgi?id=1346242] from POST to MODIFIED > InvalidBytecodeException when an EJB local interface declares static method > --------------------------------------------------------------------------- > > Key: WFLY-4316 > URL: https://issues.jboss.org/browse/WFLY-4316 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Jozef Hartinger > Assignee: Jozef Hartinger > Fix For: 9.0.0.Beta1 > > > {noformat} > Caused by: org.jboss.classfilewriter.InvalidBytecodeException: Cannot load variable at 1. Local Variables: Local Variables: [StackEntry [descriptor=Ljava/lang/String;, type=OBJECT]] > at org.jboss.classfilewriter.code.CodeAttribute.aload(CodeAttribute.java:185) > at org.jboss.invocation.proxy.ProxyFactory$ProxyMethodBodyCreator.overrideMethod(ProxyFactory.java:150) > at org.jboss.invocation.proxy.AbstractSubclassFactory.overrideMethod(AbstractSubclassFactory.java:106) > at org.jboss.invocation.proxy.AbstractSubclassFactory.addInterface(AbstractSubclassFactory.java:363) > at org.jboss.invocation.proxy.ProxyFactory.generateClass(ProxyFactory.java:286) > at org.jboss.invocation.proxy.AbstractClassFactory.buildClassDefinition(AbstractClassFactory.java:207) > at org.jboss.invocation.proxy.AbstractClassFactory.defineClass(AbstractClassFactory.java:160) > at org.jboss.invocation.proxy.AbstractProxyFactory.getCachedMethods(AbstractProxyFactory.java:150) > at org.jboss.as.ejb3.component.stateless.StatelessComponentDescription$3.configure(StatelessComponentDescription.java:150) > at org.jboss.as.ee.component.DefaultComponentViewConfigurator.configure(DefaultComponentViewConfigurator.java:68) > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:81) > ... 6 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-593) Optimisation of Gs2SaslClientFactory.createSaslClient

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-593?page=com.atlassian.jira.plugin.sy... ] Farah Juma commented on ELY-593: -------------------------------- Correct, that's addressed in [PR #472|https://github.com/wildfly-security/wildfly-elytron/pull/472]. > Optimisation of Gs2SaslClientFactory.createSaslClient > ----------------------------------------------------- > > Key: ELY-593 > URL: https://issues.jboss.org/browse/ELY-593 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Affects Versions: 1.1.0.Beta6 > Reporter: Darran Lofthouse > Assignee: Farah Juma > Fix For: 1.1.0.Beta7 > > > There are a couple of opportunities to optimise the createSaslClient method. > # Check that one of the mechanisms in the list is supported in principal. > # The ChannelBindingCallback can possibly also be delayed until the selection reaches a mechanism that requires it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6873) WebCERTTestsSecurityDomainSetup prevents other TestCases to deploy arquillian service

by Petr Kremensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-6873?page=com.atlassian.jira.plugin.... ] Petr Kremensky moved JBEAP-5377 to WFLY-6873: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-6873 (was: JBEAP-5377) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Test Suite) Affects Version/s: (was: 7.1.0.DR1) > WebCERTTestsSecurityDomainSetup prevents other TestCases to deploy arquillian service > ------------------------------------------------------------------------------------- > > Key: WFLY-6873 > URL: https://issues.jboss.org/browse/WFLY-6873 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Petr Kremensky > Assignee: Petr Kremensky > > WebCERTTestsSecurityDomainSetup doesn't reload a server after security related configuration tearDown making EAP instance unavailable to subsequent tests in test.integration.web module. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6851) Add test for MODULES-218

by Martin Simka (JIRA)

[ https://issues.jboss.org/browse/WFLY-6851?page=com.atlassian.jira.plugin.... ] Martin Simka closed WFLY-6851. ------------------------------ Resolution: Rejected this test should go to WildFly Core, it will be part of https://github.com/wildfly/wildfly-core/pull/1677 > Add test for MODULES-218 > ------------------------ > > Key: WFLY-6851 > URL: https://issues.jboss.org/browse/WFLY-6851 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Martin Simka > Assignee: Martin Simka > > Add test for MODULES-218 - Support absolute paths for module.xml resource-root elements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1103) FireAllRules can trigger java.util.concurrent.RejectedExecutionException from the JDKTimerService

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1103?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-1103: ------------------------------------- It is not necessary to open a different jira for now. Give me a bit of time to run your reproducer first. > FireAllRules can trigger java.util.concurrent.RejectedExecutionException from the JDKTimerService > ------------------------------------------------------------------------------------------------- > > Key: DROOLS-1103 > URL: https://issues.jboss.org/browse/DROOLS-1103 > Project: Drools > Issue Type: Bug > Affects Versions: 6.3.0.Final, 6.4.0.Final > Reporter: Juan Carlos Garcia > Assignee: Mario Fusco > Attachments: RejectedExecutionExceptionBugReport.zip > > > Under very rare circumstance we have found the following exception *java.util.concurrent.RejectedExecutionException* in our production log. > Our guess is that the Drools Session is on its way to be dispose, while a new incoming request is in the middle of a fireAllRules operation (race condition). > I will try to provide a reproducible testcase for this. > {code} > Caused by: java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@3e896443 rejected from java.util.concurrent.ScheduledThreadPoolExecutor@71cc2f4c[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0] > at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047) > at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823) > at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:326) > at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:549) > at org.drools.core.time.impl.JDKTimerService.internalSchedule(JDKTimerService.java:118) > at org.drools.core.time.impl.JDKTimerService.scheduleJob(JDKTimerService.java:101) > at org.drools.core.phreak.PhreakTimerNode.scheduleTimer(PhreakTimerNode.java:304) > at org.drools.core.phreak.PhreakTimerNode.scheduleLeftTuple(PhreakTimerNode.java:233) > at org.drools.core.phreak.PhreakTimerNode.doLeftUpdates(PhreakTimerNode.java:131) > at org.drools.core.phreak.PhreakTimerNode.doNode(PhreakTimerNode.java:65) > at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:357) > at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:161) > at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:116) > at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:194) > at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:67) > at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:935) > at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1200) > at org.drools.core.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:957) > at org.drools.core.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:936) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:260) > at XXXXXX.XXXXX.XXXXX.processEventDrools(EventProcessorImpl.java:128) > at XXXXXX.XXXXX.XXXXX.processEvent(EventProcessorImpl.java:101) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5916) jackson-datatype-jsr310 and jackson-datatype-jdk8 are missing

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFLY-5916?page=com.atlassian.jira.plugin.... ] Marek Kopecký reopened WFLY-5916: --------------------------------- Reopen, because * This dependency is missing in ./modules/system/layers/base/com/fasterxml/jackson/datatype/jackson-datatype-jdk8/main/module.xml : {code:xml} <module name="com.fasterxml.jackson.core.jackson-annotations"/> {code} * This feature works correctly only if "jboss-deployment-structure.xml" is in deployment. "jboss-deployment-structure.xml" needs to contain dependency to "com.fasterxml.jackson.datatype.jackson-datatype-jsr310" and "com.fasterxml.jackson.datatype.jackson-datatype-jdk8". I created test application, see [^test-application.zip] > jackson-datatype-jsr310 and jackson-datatype-jdk8 are missing > ------------------------------------------------------------- > > Key: WFLY-5916 > URL: https://issues.jboss.org/browse/WFLY-5916 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 10.0.0.CR5 > Reporter: Juergen Zimmermann > Assignee: Stuart Douglas > Fix For: 10.1.0.CR1 > > Attachments: test-application.zip > > > WildFly doesn't provide jackson-datatype-jsr310 and jackson-datatype-jdk8 for RESTEasy. jackson-datatype-jsr310 supports the new JDK 8 time API, and jackson-datatype-jdk8 supports the new JDK 8 Optional type. > The GAVs are: > com.fasterxml.jackson.datatype:jackson-datatype-jsr310:2.6.3 > com.fasterxml.jackson.datatype:jackson-datatype-jdk8:2.6.3 > The latest Jackson GA version is 2.6.4. Please see also https://issues.jboss.org/browse/WFLY-5915. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5916) jackson-datatype-jsr310 and jackson-datatype-jdk8 are missing

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFLY-5916?page=com.atlassian.jira.plugin.... ] Marek Kopecký updated WFLY-5916: -------------------------------- Attachment: test-application.zip > jackson-datatype-jsr310 and jackson-datatype-jdk8 are missing > ------------------------------------------------------------- > > Key: WFLY-5916 > URL: https://issues.jboss.org/browse/WFLY-5916 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 10.0.0.CR5 > Reporter: Juergen Zimmermann > Assignee: Stuart Douglas > Fix For: 10.1.0.CR1 > > Attachments: test-application.zip > > > WildFly doesn't provide jackson-datatype-jsr310 and jackson-datatype-jdk8 for RESTEasy. jackson-datatype-jsr310 supports the new JDK 8 time API, and jackson-datatype-jdk8 supports the new JDK 8 Optional type. > The GAVs are: > com.fasterxml.jackson.datatype:jackson-datatype-jsr310:2.6.3 > com.fasterxml.jackson.datatype:jackson-datatype-jdk8:2.6.3 > The latest Jackson GA version is 2.6.4. Please see also https://issues.jboss.org/browse/WFLY-5915. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2016