December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-416) Complete <xs:documentation> for all configuration elements/attributes in Infinispan subsystem's XSD

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-416?page=com.atlassian.jira.plugin.s... ] Kabir Khan closed WFLY-416. --------------------------- > Complete <xs:documentation> for all configuration elements/attributes in Infinispan subsystem's XSD > --------------------------------------------------------------------------------------------------- > > Key: WFLY-416 > URL: https://issues.jboss.org/browse/WFLY-416 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: JBoss AS7 7.2.0.Final, 8.0.0.Final, 8.1.0.Final > Reporter: Martin Gencur > Assignee: Radoslav Husar > Labels: ux > Fix For: 9.0.0.CR2, 10.0.0.Alpha1 > > > Infinispan subsystem's XSD still contains a lot of elements/attributes which do NOT have their description: https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/... > It would be very useful for users to know what each element is supposed to do. > This document can help out: https://docspace.corp.redhat.com/docs/DOC-69249 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4736) UndertowDeploymentService starts web components in MSC thread

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4736?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4736. ---------------------------- > UndertowDeploymentService starts web components in MSC thread > ------------------------------------------------------------- > > Key: WFLY-4736 > URL: https://issues.jboss.org/browse/WFLY-4736 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 9.0.0.CR1 > Reporter: jaikiran pai > Assignee: jaikiran pai > Fix For: 9.0.0.CR2, 10.0.0.Alpha3 > > > The UndertowDeploymentService triggers web components' start and stop lifecycle within the MSC thread which can lead to the server blocking during deployment. This was an issue with the older JBoss Web version of the Service too which was fixed as part of https://issues.jboss.org/browse/AS7-5969 (https://github.com/wildfly/wildfly/pull/3455). The same needs to be ported to this UndertowDeploymentService. > Here's an example where a user deployment ends up being blocked https://developer.jboss.org/message/932681#932681 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5086) [Migration operation] HA configuration is not migrated

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5086?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5086. ---------------------------- > [Migration operation] HA configuration is not migrated > ------------------------------------------------------ > > Key: WFLY-5086 > URL: https://issues.jboss.org/browse/WFLY-5086 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Alpha6 > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Fix For: 10.0.0.CR1 > > > HA configuration is not migrated. > For example: > {code} > <shared-store>true</shared-store> > {code} > does not have equivalent config in in migrated configuration. > Customer with HA configuration for HornetQ will not have this configuration after migration. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4986) LazyValidatorFactoryTestCase fails on IBM jdk

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4986?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4986. ---------------------------- > LazyValidatorFactoryTestCase fails on IBM jdk > --------------------------------------------- > > Key: WFLY-4986 > URL: https://issues.jboss.org/browse/WFLY-4986 > Project: WildFly > Issue Type: Bug > Components: EE, Test Suite > Affects Versions: 10.0.0.Alpha5 > Environment: java version "1.8.0" > Java(TM) SE Runtime Environment (build pxa6480-20150129_02) > IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20150116_231420 (JIT enabled, AOT enabled) > J9VM - R28_Java8_GA_20150116_2030_B231420 > JIT - tr.r14.java_20150109_82886.02 > GC - R28_Java8_GA_20150116_2030_B231420_CMPRSS > J9CL - 20150116_231420) > JCL - 20150123_01 based on Oracle jdk8u31-b12 > Reporter: Petr Kremensky > Assignee: Hardy Ferentschik > Fix For: 10.0.0.Beta1 > > > org.jboss.as.ee.beanvalidation.LazyValidatorFactoryTestCase#testSpecificProviderCanBeConfiguredInValidationXml fails with IBM JDK8 > {noformat} > Running org.jboss.as.ee.beanvalidation.LazyValidatorFactoryTestCase > Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.09 sec <<< FAILURE! - in org.jboss.as.ee.beanvalidation.LazyValidatorFactoryTestCase > testSpecificProviderCanBeConfiguredInValidationXml(org.jboss.as.ee.beanvalidation.LazyValidatorFactoryTestCase) Time elapsed: 0.012 sec <<< ERROR! > javax.validation.ValidationException: HV000123: Unable to parse META-INF/validation.xml. > at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:181) > at java.io.BufferedInputStream.reset(BufferedInputStream.java:457) > at org.hibernate.validator.internal.xml.XmlParserHelper.getSchemaVersion(XmlParserHelper.java:109) > at org.hibernate.validator.internal.xml.ValidationXmlParser.parseValidationXml(ValidationXmlParser.java:79) > at org.hibernate.validator.internal.engine.ConfigurationImpl.getBootstrapConfiguration(ConfigurationImpl.java:287) > at org.hibernate.validator.internal.engine.ConfigurationImpl.parseValidationXml(ConfigurationImpl.java:361) > at org.hibernate.validator.internal.engine.ConfigurationImpl.buildValidatorFactory(ConfigurationImpl.java:214) > at org.jboss.as.ee.beanvalidation.LazyValidatorFactory.initFactory(LazyValidatorFactory.java:81) > at org.jboss.as.ee.beanvalidation.LazyValidatorFactory.getDelegate(LazyValidatorFactory.java:58) > at org.jboss.as.ee.beanvalidation.LazyValidatorFactory.getValidator(LazyValidatorFactory.java:73) > at org.jboss.as.ee.beanvalidation.LazyValidatorFactoryTestCase.testSpecificProviderCanBeConfiguredInValidationXml(LazyValidatorFactoryTestCase.java:70) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4568) Remove support for jboss-as-resource-adapters_1_0.xsd

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4568?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4568. ---------------------------- > Remove support for jboss-as-resource-adapters_1_0.xsd > ----------------------------------------------------- > > Key: WFLY-4568 > URL: https://issues.jboss.org/browse/WFLY-4568 > Project: WildFly > Issue Type: Task > Components: JCA > Reporter: Jesper Pedersen > Assignee: Stefano Maestri > Fix For: 10.0.0.Alpha5 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3095) Weld subsystem exposes way too much dependancies to user deployment

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3095?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-3095. ---------------------------- > Weld subsystem exposes way too much dependancies to user deployment > ------------------------------------------------------------------- > > Key: WFLY-3095 > URL: https://issues.jboss.org/browse/WFLY-3095 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 8.0.0.Final > Reporter: Tomaz Cerar > Assignee: Jozef Hartinger > Priority: Critical > Fix For: 10.0.0.Alpha2 > > > module org.jboss.as.weld should not be added as dependency to user deployment. > It has way too much dependencies and some of them export their dependencies which than end up in user deployment. > We should probably have extra module for stuff that is exposed to deployment. > Also lots of dependencies that weld subsystem has should be optional as we shouldn't be required to have dependency to almost every single subsystem we have as required. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4810) FormAuthenticationWebFailoverTestCase(SYNC-tcp) fails frequently

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4810?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4810. ---------------------------- > FormAuthenticationWebFailoverTestCase(SYNC-tcp) fails frequently > ---------------------------------------------------------------- > > Key: WFLY-4810 > URL: https://issues.jboss.org/browse/WFLY-4810 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Stuart Douglas > Assignee: Paul Ferraro > Fix For: 10.0.0.Alpha4 > > > Seems to have been introduced by https://github.com/wildfly/wildfly/pull/7507 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4792) Undertow deployment-level session statistics not available for distributable webapp

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4792?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4792. ---------------------------- > Undertow deployment-level session statistics not available for distributable webapp > ----------------------------------------------------------------------------------- > > Key: WFLY-4792 > URL: https://issues.jboss.org/browse/WFLY-4792 > Project: WildFly > Issue Type: Bug > Components: Clustering, Web (Undertow) > Affects Versions: 9.0.0.CR2 > Reporter: Martin Kouba > Assignee: Paul Ferraro > Fix For: 10.0.0.Beta1 > > > {{org.wildfly.clustering.web.infinispan.session.InfinispanSessionManager}} which is used by default even for non-HA configurations in WildFly 9.0.0.CR2 (e.g. {{standalone.xml}} in app server distribution) does not implement {{io.undertow.server.session.SessionManagerStatistics}} and so no stats except for {{activeSessions}} are available. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4836) Restore SOAP-over-JMS integration after HornetQ replacement with Apache Active Artemis

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4836?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4836. ---------------------------- > Restore SOAP-over-JMS integration after HornetQ replacement with Apache Active Artemis > -------------------------------------------------------------------------------------- > > Key: WFLY-4836 > URL: https://issues.jboss.org/browse/WFLY-4836 > Project: WildFly > Issue Type: Task > Components: Web Services > Affects Versions: 10.0.0.Alpha3 > Reporter: Jeff Mesnil > Assignee: Alessio Soldano > Fix For: 10.0.0.Alpha5 > > > WildFly 10 replaces HornetQ with Apache Active Artemis. > Most HornetQ runtime will be removed from WildFly dependencies. > This is handled by WFLY-4592 except for the dependencies in org.wildfly:wildfly-webservices-tests-integration that depends on org.hornetq:* artifacts. > These dependencies should be inspected and replaced by their corresponding org.apache.activemq.artemis:* arteficts that provides the messaging runtime for WildFly 10. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4584) Use Apache ActiveMQ Artemis as the messaging broker

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4584?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4584. ---------------------------- > Use Apache ActiveMQ Artemis as the messaging broker > --------------------------------------------------- > > Key: WFLY-4584 > URL: https://issues.jboss.org/browse/WFLY-4584 > Project: WildFly > Issue Type: Task > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 10.0.0.Alpha4 > > > replace the current messaging subsystem (with HornetQ) with a new messaging-activemq subsystem (with ActiveMQ Artemis) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

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 December 2017