December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5165) Quickstart Arquillian tests log warning deprecated protocol warning

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5165?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5165. ---------------------------- > Quickstart Arquillian tests log warning deprecated protocol warning > ------------------------------------------------------------------- > > Key: WFLY-5165 > URL: https://issues.jboss.org/browse/WFLY-5165 > Project: WildFly > Issue Type: Feature Request > Reporter: Sande Gilda > Assignee: Tomaz Cerar > Fix For: 10.0.0.CR1 > > > A warning is logged during Arquillian tests for the JBoss EAP 7 quickstarts: : > WARN: The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'. > This JIRA was created for the issue: https://issues.jboss.org/browse/JBEAP-579 > [~mjobanek] looked at this and commented in the JIRA: > AFAIK, you are not able to get rid of this warning by any change of the arquillian configuration - this is caused by the wildfly-arquillian-container adapter itself. > During a construction of the ProtocolMetadata [1], the adapter retrieves also JMX context and this retrieval [2] causes the warning. > I've already noticed this behavior, however, I haven't time to investigate it deeper. > Please, feell free to open a jira for this issue. > [1] https://github.com/wildfly/wildfly-arquillian/blob/master/common/src/main... > [2] https://github.com/wildfly/wildfly-arquillian/blob/master/common/src/main... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5116) Removal of the ANTLR version 3.4 module

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5116?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5116. ---------------------------- > Removal of the ANTLR version 3.4 module > --------------------------------------- > > Key: WFLY-5116 > URL: https://issues.jboss.org/browse/WFLY-5116 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 10.0.0.Beta2 > > > The module of version 3.4 of ANTLR is no longer needed, this was being used by the Infinispan Query component which has been removed with WFLY-4695. > Hibernate ORM still uses the goold old ANTLR 2.7.x -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5251) Upgrade JBossWS from 5.1.0.Beta1 to 5.1.0.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5251?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5251. ---------------------------- > Upgrade JBossWS from 5.1.0.Beta1 to 5.1.0.Final > ----------------------------------------------- > > Key: WFLY-5251 > URL: https://issues.jboss.org/browse/WFLY-5251 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Services > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: 10.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4006) Java EE 7 with all BOM lacks JAX-RS 2.0 API dependency

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4006?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4006. ---------------------------- > Java EE 7 with all BOM lacks JAX-RS 2.0 API dependency > ------------------------------------------------------ > > Key: WFLY-4006 > URL: https://issues.jboss.org/browse/WFLY-4006 > Project: WildFly > Issue Type: Enhancement > Affects Versions: 8.1.0.Final > Reporter: Vineet Reynolds > Assignee: Tomaz Cerar > Priority: Optional > Fix For: 9.0.0.CR2, 10.0.0.Alpha1 > > > Adding the {{org.wildfly.bom:jboss-javaee-7.0-with-all}} BOM to a Maven project does not pull in the {{org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_2.0_spec}} dependency. > Hence, users of this BOM are required to add the JAX-RS 2.0 API, specifying the version explicitly, to consume the JAX-RS APIs in their projects. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5145) Jacorb subsystem does not contain operation "describe-migration"

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5145?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5145. ---------------------------- > Jacorb subsystem does not contain operation "describe-migration" > ---------------------------------------------------------------- > > Key: WFLY-5145 > URL: https://issues.jboss.org/browse/WFLY-5145 > Project: WildFly > Issue Type: Bug > Components: IIOP > Affects Versions: 10.0.0.Beta1 > Reporter: Ondra Chaloupka > Assignee: Tomasz Adamski > Priority: Critical > Fix For: 10.0.0.CR1 > > > As part of the migrate functionality for moving from JacORB to IIOP OpenJDK the old subsystem should contain operation {{describe-migration}} > {code} > /subsystem=jacorb:describe-migration() > {code} > for user gets information about following steps. > But JacORB subsystem does not contain any such operation > {code} > /subsystem=jacorb:read-operation-names() > { > "outcome" => "success", > "result" => [ > "add", > "list-add", > "list-clear", > "list-get", > "list-remove", > "map-clear", > "map-get", > "map-put", > "map-remove", > "migrate", > "query", > "read-attribute", > "read-attribute-group", > "read-attribute-group-names", > "read-children-names", > "read-children-resources", > "read-children-types", > "read-operation-description", > "read-operation-names", > "read-resource", > "read-resource-description", > "remove", > "undefine-attribute", > "whoami", > "write-attribute" > ] > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5294) Upgrade HAL to 2.8.8.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5294?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5294. ---------------------------- > Upgrade HAL to 2.8.8.Final > -------------------------- > > Key: WFLY-5294 > URL: https://issues.jboss.org/browse/WFLY-5294 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Tomas Hofman > Assignee: Harald Pehl > Fix For: 10.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5330) Can't start managed domain in --admin-only with EAP 6.4 configuration

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5330?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5330. ---------------------------- > Can't start managed domain in --admin-only with EAP 6.4 configuration > --------------------------------------------------------------------- > > Key: WFLY-5330 > URL: https://issues.jboss.org/browse/WFLY-5330 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 10.0.0.Beta2 > Reporter: Ladislav Thon > Assignee: Stuart Douglas > Priority: Critical > Fix For: 10.0.0.CR1 > > > When starting WildFly 10.0.0.Beta2 managed domain in {{--admin-only}} mode to perform {{:migrate}} operations on old subsystems \[1\], using an unmodified {{domain.xml}} and {{host.xml}} configuration files from EAP 6.4.0, I'm getting errors \[2\]. > Apparently, the domain configuration files in EAP 6.4 still contain the {{configadmin}} extension and subsystems. The standalone configuration files from EAP 6.4 no longer contain that, which is why this problem wasn't found earlier and wasn't described in WFLY-5092. > Based on http://lists.jboss.org/pipermail/wildfly-dev/2015-August/004306.html, I'm expecting that I don't have to perform any changes to the EAP 6.4 configuration files. > \[1\] > {code} > unzip jboss-eap-6.4.0.zip > unzip wildfly-10.0.0.Beta2.zip > rm wildfly-10.0.0.Beta2/domain/configuration/*.xml > cp jboss-eap-6.4/domain/configuration/domain.xml wildfly-10.0.0.Beta2/domain/configuration/ > cp jboss-eap-6.4/domain/configuration/host.xml wildfly-10.0.0.Beta2/domain/configuration/ > ./wildfly-10.0.0.Beta2/bin/domain.sh --admin-only > {code} > \[2\] > {code} > [Host Controller] 09:21:47,835 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0033: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration > [Host Controller] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131) > [Host Controller] at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:673) > [Host Controller] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:272) > [Host Controller] at java.lang.Thread.run(Thread.java:745) > [Host Controller] Caused by: javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to load module org.jboss.as.configadmin > [Host Controller] at org.jboss.as.controller.parsing.ExtensionXml.parseExtensions(ExtensionXml.java:155) > [Host Controller] at org.jboss.as.host.controller.parsing.DomainXml_Legacy.readDomainElement2_0(DomainXml_Legacy.java:377) > [Host Controller] at org.jboss.as.host.controller.parsing.DomainXml_Legacy.readElement(DomainXml_Legacy.java:133) > [Host Controller] ... > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4859) log INFO for messaging-activemq journal-type

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4859?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4859. ---------------------------- > log INFO for messaging-activemq journal-type > -------------------------------------------- > > Key: WFLY-4859 > URL: https://issues.jboss.org/browse/WFLY-4859 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 10.0.0.Alpha5 > > > In the messaging-activemq subsystem, the default journal type is AIO. > This type of journal only works on Linux (with LibAIO installed). On any other platforms, we log a WARN that AIO can not be installed and NIO will be used instead. > We should have no WARN log when starting a pristine EAP servers. > However, having AIO by default ensures that on Linux, we provide the best messaging performance out of the box. > Instead of logging a WARN, we should only log an INFO telling the users that AIO can not be loaded and NIO will be used. > There is no functionality problem using NIO instead of AIO, only best performance will not be achieved. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[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)

8 years, 7 months

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)

8 years, 7 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 December 2017