August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (HAWKULARQE-155) New Foreman Hostgroups for Fuse

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-155?page=com.atlassian.jira.pl... ] Hayk Hovsepyan commented on HAWKULARQE-155: ------------------------------------------- "Hawkular/Fuse" hostgroup is created for downstream Fuse installation. > New Foreman Hostgroups for Fuse > ------------------------------- > > Key: HAWKULARQE-155 > URL: https://issues.jboss.org/browse/HAWKULARQE-155 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > > We need several new foreman hostgroups for Fuse MiQ integration testing. > 1. Run JBoss Fuse 6.3 on Karaf container. This is downstream Fuse project running on Karaf container. Install Hawkular Agent on JBoss Fuse. > 2. Run Upstream Apache Karaf (downstream of JBoss Fuse) on Karaf container. Install Hawkular Agent on Upstream Apache Karaf. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-174) Adding link to a VM - MIQ Sprint-67

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-174?page=com.atlassian.jira.pl... ] Hayk Hovsepyan commented on HAWKULARQE-174: ------------------------------------------- Issue was logged here https://github.com/ManageIQ/manageiq-providers-hawkular/issues/35 > Adding link to a VM - MIQ Sprint-67 > ----------------------------------- > > Key: HAWKULARQE-174 > URL: https://issues.jboss.org/browse/HAWKULARQE-174 > Project: Hawkular QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Hayk Hovsepyan > > Enhancement - adding link to a VM also for middleware servers running in domain mode -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1298) GssapiCompatibilitySuiteChild fails on IBM JDK

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/ELY-1298?page=com.atlassian.jira.plugin.s... ] Peter Palaga commented on ELY-1298: ----------------------------------- I have spent a couple of hours looking for a solution, but I have not found any good one. First, it is not possible to apply the strategy used in ELY-1293 - i.e. to add a customizable source of time to the API. It is not possible because GssapiCompatibilitySuiteChild hits several third party layers where there is little to zero hope that their time handling can be changed in any way. This is an incomplete overview of locations from where {{System.currentTimeMillis()}} is called either directly or indirectly (some of them are maybe irrelevant to the test success): * sun.security.util.DerOutputStream.putTime() * java.net.InetAddress$Cache.get() * org.apache.mina.core.session.AbstractIoSession() * org.apache.mina.util.ExpiringMap.put() * org.apache.mina.core.filterchain.DefaultIoFilterChain.fireMessageReceived() * org.apache.directory.shared.kerberos.KerberosTime.convertInternal() * org.apache.mina.core.filterchain.DefaultIoFilterChain$TailFilter.messageReceived() * org.apache.directory.shared.kerberos.KerberosTime() * org.apache.mina.core.polling.AbstractPollingConnectionlessIoAcceptor.write() * org.apache.mina.core.filterchain.DefaultIoFilterChain.fireMessageSent() * sun.security.krb5.internal.KerberosTime.inClockSkew() At some of these locations {{System.currentTimeMillis()}} is wrapped by {{new Date()}} or {{Calendar.getInstance()}} I tried mocking those, but it was not sufficient. Given all the above, I do not think this kind of test can work on IBM JDK. Excluding it on JBM JDK is the only thing we can do. > GssapiCompatibilitySuiteChild fails on IBM JDK > ---------------------------------------------- > > Key: ELY-1298 > URL: https://issues.jboss.org/browse/ELY-1298 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Peter Palaga > Assignee: Peter Palaga > > A followup of ELY-1293 > {{System.currentTimeMillis()}} is native in IBM JDK and at the same time, IBM JDK does not support java.lang.instrument API for native methods. Therefore, {{System.currentTimeMillis()}} cannot be mocked on IBM JDK using jmockit. > {code} > export JAVA_HOME=path/to/ibm/java8 > $JAVA_HOME/bin/java -version > java version "1.8.0" > Java(TM) SE Runtime Environment (build pxa6480sr3fp12-20160919_01(SR3 FP12)) > IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160915_318796 (JIT enabled, AOT enabled) > J9VM - R28_Java8_SR3_20160915_0912_B318796 > JIT - tr.r14.java.green_20160818_122998 > GC - R28_Java8_SR3_20160915_0912_B318796_CMPRSS > J9CL - 20160915_318796) > JCL - 20160914_01 based on Oracle jdk8u101-b13 > mvn clean test > {code} > Expected: the tests mocking {{System.currentTimeMillis()}} should pass > Actual: the tests mocking {{System.currentTimeMillis()}} throw the following exception or similar: > {code} > java.lang.UnsupportedOperationException: class redefinition failed: attempted to change method modifiers > at org.wildfly.security.audit.PeriodicRotatingFileAuditEndpointTest$1.<init>(PeriodicRotatingFileAuditEndpointTest.java:212) > at org.wildfly.security.audit.PeriodicRotatingFileAuditEndpointTest.mockTime(PeriodicRotatingFileAuditEndpointTest.java:212) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.lang.reflect.Method.invoke(Method.java:508) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) > {code} > This is currently the case with > * GssapiCompatibilitySuiteChild -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1715) Running DMN evaluation in parallel causes a ConcurrentModificationException

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1715?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-1715: ----------------------------------- Sprint: 2017 Week 34-35 > Running DMN evaluation in parallel causes a ConcurrentModificationException > --------------------------------------------------------------------------- > > Key: DROOLS-1715 > URL: https://issues.jboss.org/browse/DROOLS-1715 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.2.0.Final > Reporter: David Le Moing > Assignee: Matteo Mortari > > When launching some Parameterized tests in parallel, I noticed that I was not getting any answer (it works with only 1 thread). When I started digging, I found that the cause was a ConcurrentModificationException thrown when iterating over events in the processEvents method of DMNDTExpressionEvaluator. > {code} > at java.util.ConcurrentModificationException.<init>(ConcurrentModificationException.java:78) > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901) > at java.util.ArrayList$Itr.next(ArrayList.java:851) > at org.kie.dmn.core.ast.DMNDTExpressionEvaluator.processEvents(DMNDTExpressionEvaluator.java:101) > at org.kie.dmn.core.ast.DMNDTExpressionEvaluator.evaluate(DMNDTExpressionEvaluator.java:92) > at org.kie.dmn.core.impl.DMNRuntimeImpl.evaluateDecision(DMNRuntimeImpl.java:337) > at org.kie.dmn.core.impl.DMNRuntimeImpl.evaluateAll(DMNRuntimeImpl.java:92) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9264) Remove ClientCompatibilityUnitTestCase as it is already in wildfly-core

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9264?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-9264: --------------------------------- Assignee: Tomaz Cerar > Remove ClientCompatibilityUnitTestCase as it is already in wildfly-core > ----------------------------------------------------------------------- > > Key: WFLY-9264 > URL: https://issues.jboss.org/browse/WFLY-9264 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > also look how much of this is duplicated in core's client-old-server testsuite -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7009) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.security

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7009?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-7009: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly-capabilities/pull/19 (was: https://github.com/wildfly/wildfly-capabilities/pull/13) > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.security > ------------------------------------------------------------------------------------------------- > > Key: WFLY-7009 > URL: https://issues.jboss.org/browse/WFLY-7009 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Stansberry > Assignee: Darran Lofthouse > > This cap was introduced to support an optional requirement for transaction manager integration. Both sides of this contract need examination. > Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7012) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.extension.undertow.handler

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7012?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-7012: ------------------------------ Component/s: Web (Undertow) (was: Security) > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.extension.undertow.handler > ------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7012 > URL: https://issues.jboss.org/browse/WFLY-7012 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Brian Stansberry > Assignee: Stuart Douglas > > The contract for this capability needs examination and recording in the registry. > Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7012) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.extension.undertow.handler

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7012?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-7012: --------------------------------- Assignee: Tomaz Cerar (was: Stuart Douglas) > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.extension.undertow.handler > ------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7012 > URL: https://issues.jboss.org/browse/WFLY-7012 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > > The contract for this capability needs examination and recording in the registry. > Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7011) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.undertow.listener

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7011?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reopened WFLY-7011: ------------------------------- Assignee: Tomaz Cerar (was: Ingo Weiss) > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.undertow.listener > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-7011 > URL: https://issues.jboss.org/browse/WFLY-7011 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > Fix For: 11.0.0.Beta1 > > > The contract for this capability needs examination and recording in the registry. > Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. ListenerService doesn't look like a good API to be exposed to external callers; it exposes details that probably should not be part of a contract. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1033) Enhance XTS AS7 configuration

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-1033?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-1033: -------------------------------- Fix Version/s: (was: 11.0.0.Final) > Enhance XTS AS7 configuration > ----------------------------- > > Key: WFLY-1033 > URL: https://issues.jboss.org/browse/WFLY-1033 > Project: WildFly > Issue Type: Enhancement > Components: XTS > Reporter: Andrew Dinn > Priority: Minor > > The current integration of XTS into AS7 as an AS7 extension allows optional configuration of the coordinator URL from the <xts/> element in the AS7 standalone configuration file. No other configuration options are currently supported. > XTS ought to support more precise configuration. IN particular, it ought to be possible to enable or disable deployment of coordinator, participant or client services independently and also to choose whether to deploy WS-AT or WS-BA services or both. This requires selectively deploying only the required web service endpoints, selectively executing the required initialization routines and selectively loading the required high level service implementations and context factory implementations. > The XTS implementation has already been factored so as to to support such discriminated bootstrapping. So this task only requires modifying the AS7 extension code to manage the relevant configuration information and install the relevant values into the XTS environment configuration beans before starting the XTS service. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2017