December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4710) Upgrade to Beanutils 1.9.2

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4710?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4710. ---------------------------- > Upgrade to Beanutils 1.9.2 > -------------------------- > > Key: WFLY-4710 > URL: https://issues.jboss.org/browse/WFLY-4710 > Project: WildFly > Issue Type: Component Upgrade > Affects Versions: 10.0.0.Alpha2 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 10.0.0.Alpha4 > > > Apache ActiveMQ Artemis depends on Beanutils 1.9.2 and its BeanIntrospector -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4973) Intermittent failures in client side tests that use remote EJB

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4973?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4973. ---------------------------- > Intermittent failures in client side tests that use remote EJB > -------------------------------------------------------------- > > Key: WFLY-4973 > URL: https://issues.jboss.org/browse/WFLY-4973 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Priority: Critical > Fix For: 10.0.0.Alpha6 > > > There are lots of intermittent failures in tests that use remote EJB, and they all fail with the same failure message (EJBCLIENT000025: No EJB receiver available for handling...). > An example of this is here: http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=61476&buildTyp... > The issue is that there is no guard to make sure that the 'module availability' message for the deployment has been processed before the test starts (there is a guard for this on initial connection, with a hard coded 5 second timeout, however the test suite will re-use connections between tests). > At the moment I don't really have any idea of a good way to fix this. > This failure does not affect end user code because user code does usually perform a deployment then make a call (although it could affect end user Arquillian tests). > This issue can be reproduced 100% of the time by adding a sleep into org.jboss.ejb.client.remoting.ModuleAvailabilityMessageHandler#processMessage, then running the test suite. The first test that uses the remote EJB will pass (because the client waits for the initial module availability message), but all subsequent tests that attempt to use it will fail. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5153) IIOP migrate operation does not translate ior-settings

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5153?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5153. ---------------------------- > IIOP migrate operation does not translate ior-settings > ------------------------------------------------------ > > Key: WFLY-5153 > URL: https://issues.jboss.org/browse/WFLY-5153 > Project: WildFly > Issue Type: Bug > Components: IIOP > Affects Versions: 10.0.0.Beta1 > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 10.0.0.CR1 > > > Ior-settings is not migrated in current time despite the fact that their values seem to be valid for migration. > If I have JacORB configuration like > {code} > <subsystem xmlns="urn:jboss:domain:jacorb:1.4"> > <orb socket-binding="jacorb" ssl-socket-binding="jacorb-ssl"> > <initializers security="identity" transactions="on"/> > </orb> > <security client-requires="ServerAuth" server-supports="ServerAuth" server-requires="ServerAuth"/> > <ior-settings> > <transport-config integrity="required" confidentiality="supported" trust-in-client="required" trust-in-target="supported" " > detect-replay="required" detect-misordering="required"/> > <as-context auth-method="none"/> > <sas-context caller-propagation="supported"/> > </ior-settings> > </subsystem> > {code} > The migration output will be > {code} > <subsystem xmlns="urn:jboss:domain:iiop-openjdk:1.0"> > <orb ssl-socket-binding="jacorb-ssl" socket-binding="jacorb"/> > <initializers transactions="full" security="identity"/> > <security server-requires="ServerAuth" server-supports="ServerAuth" client-requires="ServerAuth"/> > </subsystem> > {code} > but I would rather expect output like > {code} > <subsystem xmlns="urn:jboss:domain:iiop-openjdk:1.0"> > <orb ssl-socket-binding="jacorb-ssl" socket-binding="jacorb"/> > <initializers transactions="full" security="identity"/> > <security server-requires="ServerAuth" server-supports="ServerAuth" client-requires="ServerAuth" client-supports="ServerAuth"/> > <transport-config detect-misordering="required" detect-replay="required" trust-in-client="required" trust-in-target="supported" confidentiality="supported" integrity="required"/> > <as-context auth-method="none"/> > </subsystem> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4688) Update to HAL 2.6.10

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4688?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4688. ---------------------------- > Update to HAL 2.6.10 > -------------------- > > Key: WFLY-4688 > URL: https://issues.jboss.org/browse/WFLY-4688 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 9.0.0.CR2, 10.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5204) Setting mod_cluster advertise frequency to zero does not disable advertise

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5204?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5204. ---------------------------- > Setting mod_cluster advertise frequency to zero does not disable advertise > -------------------------------------------------------------------------- > > Key: WFLY-5204 > URL: https://issues.jboss.org/browse/WFLY-5204 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Beta2 > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 10.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4575) Use Flag.RESTART_RESOURCE_SERVICES for child resources of stack/channel

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4575?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4575. ---------------------------- > Use Flag.RESTART_RESOURCE_SERVICES for child resources of stack/channel > ----------------------------------------------------------------------- > > Key: WFLY-4575 > URL: https://issues.jboss.org/browse/WFLY-4575 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 10.0.0.Beta1 > > > Currently, the attributes for each child resource of a stack or channel use RESTART_ALL_SERVICES, thus any change to one of these attributes requires all services to restart. This is overkill, since only the services of the parent resource (i.e. channel, channel factory) actually require restarting. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5223) Upgrade JSoup version to 1.8.3

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5223?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5223. ---------------------------- > Upgrade JSoup version to 1.8.3 > ------------------------------ > > Key: WFLY-5223 > URL: https://issues.jboss.org/browse/WFLY-5223 > Project: WildFly > Issue Type: Feature Request > Reporter: Hardy Ferentschik > Assignee: Hardy Ferentschik > Fix For: 10.0.0.CR1 > > > Upgrade JSoup version to avoid treating invalid HTML as valid using Hibernate Validator's {{SafeHtml}}, when '>' missing at EOF. See https://hibernate.atlassian.net/browse/HV-1012 and https://github.com/jhy/jsoup/pull/582 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4980) IronJacamar 1.2.5.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4980?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4980. ---------------------------- > IronJacamar 1.2.5.Final > ----------------------- > > Key: WFLY-4980 > URL: https://issues.jboss.org/browse/WFLY-4980 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 10.0.0.Alpha6 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4695) Remove infinispan-query module and its dependencies

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4695?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4695. ---------------------------- > Remove infinispan-query module and its dependencies > --------------------------------------------------- > > Key: WFLY-4695 > URL: https://issues.jboss.org/browse/WFLY-4695 > Project: WildFly > Issue Type: Task > Components: Clustering > Reporter: Sanne Grinovero > Assignee: Paul Ferraro > Fix For: 10.0.0.Beta1 > > > We generally expect people to use the version bundled by the Infinispan project, and there are no strong reasons to include this in WildFly. > Also it makes it much harder to upgrade components such as Hibernate and Infinispan as this components introduces strong coupling on several of these components, essentially mandating that these are all upgraded in lock step. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4839) annotation must be scanned regardless of the version of web.xml unless metadata-complete is explicitly set to true

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4839?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4839. ---------------------------- > annotation must be scanned regardless of the version of web.xml unless metadata-complete is explicitly set to true > ------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-4839 > URL: https://issues.jboss.org/browse/WFLY-4839 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Alpha4 > Reporter: Chao Wang > Assignee: Chao Wang > Fix For: 10.0.0.Beta2 > > > {noformat} > ### Description of problem: > Annotation must be scanned regardless of the version of web.xml unless metadata-complete is explicitly set to true. > Note that Servlet 3.0 specification clearly states the following: > ~~~ > 1.6.2 Processing annotations > In Servlet 2.5, metadata-complete only affected the scanning of annotations at > deployment time. The notion of web-fragments did not exist in servlet 2.5. However > in servlet 3.0 metadata-complete affects scanning of all annotations and web- > fragments at deployment time. The version of the descriptor MUST not affect which > annotations you scan for in a web application. An implementation of a particular > version of the specification MUST scan for all annotations supported in that > configuration, unless metadata-complete is specified. > ~~~ > ### How reproducible: > Anytime > ### Steps to Reproduce: > 1. Create a library jar which contains a servlet filter using @WebFilter > 2. Put the jar under WEB-INF/lib of the web application which web.xml version is 2.3 or 2.4 > 3. Start JBoss EAP 6 > 4. Access the web application and see if the servlet filter works > ### Actual results: > The servlet filter is not invoked > ### Expected results: > The servlet filter is invoked > ### Additional info: > It works when the version of web.xml is 2.5 or 3.0 > [reply] [−] > Private > Comment 1 Masafumi Miura 2015-06-25 07:18:17 EDT > RED HAT CONFIDENTIAL > It looks metadata-complete is always set to true when the version of web.xml is 2.3 or 2.4 at the line 96 of web/src/main/java/org/jboss/as/web/deployment/WarMetaDataProcessor.java. > Though Servlet 2.3/2.3 specification does not have metadata-complete attribute, Servlet 3.0 specification states the following. I think it means that the metadata-complete attribute default to false if it is not specified. > ~~~ > 8.1 Annotations and pluggability > if the metadata-complete attribute is not specified or is set to "false", the > deployment tool must examine the class files of the application for annotations, and > scan for web fragments. > ~~~ > * web/src/main/java/org/jboss/as/web/deployment/WarMetaDataProcessor.java > 76 public class WarMetaDataProcessor implements DeploymentUnitProcessor { > 77 > 78 @Override > 79 public void deploy(DeploymentPhaseContext phaseContext) throws DeploymentUnitProcessingException { > ... > 87 boolean isComplete = false; > 88 WebMetaData specMetaData = warMetaData.getWebMetaData(); > 89 if (specMetaData != null) { > 90 if (specMetaData instanceof Web25MetaData) { > 91 isComplete |= ((Web25MetaData) specMetaData).isMetadataComplete(); > 92 } else if (specMetaData instanceof Web30MetaData) { > 93 isComplete |= ((Web30MetaData) specMetaData).isMetadataComplete(); > 94 } else { > 95 // Any web.xml 2.4 or earlier deployment is metadata complete > 96 isComplete = true; > 97 } > 98 } > 99 > {noformat} -- 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