December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5118) Change WebMigrateOperation to use ModelDescriptionConstants instead of KeyStoreAttributes

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5118?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5118. ---------------------------- > Change WebMigrateOperation to use ModelDescriptionConstants instead of KeyStoreAttributes > ----------------------------------------------------------------------------------------- > > Key: WFLY-5118 > URL: https://issues.jboss.org/browse/WFLY-5118 > Project: WildFly > Issue Type: Task > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 10.0.0.CR1 > > > And remove the domain-management dependency -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5058) Upgrade Narayana to 5.2.1.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5058?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5058. ---------------------------- > Upgrade Narayana to 5.2.1.Final > ------------------------------- > > Key: WFLY-5058 > URL: https://issues.jboss.org/browse/WFLY-5058 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 10.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4898) Change in permissions is not visible until server reload

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4898?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4898. ---------------------------- > Change in permissions is not visible until server reload > -------------------------------------------------------- > > Key: WFLY-4898 > URL: https://issues.jboss.org/browse/WFLY-4898 > Project: WildFly > Issue Type: Bug > Components: Security Manager > Affects Versions: 10.0.0.Alpha4 > Reporter: Josef Cacek > Assignee: Tomas Hofman > Fix For: 10.0.0.Alpha6 > > > When adding permissions in the security-manager subsystem, the changes are not used until server reload. But the CLI operation *doesn't require reload*. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4716) Remove temporary code following core release

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4716?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4716. ---------------------------- > Remove temporary code following core release > -------------------------------------------- > > Key: WFLY-4716 > URL: https://issues.jboss.org/browse/WFLY-4716 > Project: WildFly > Issue Type: Task > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 10.0.0.Alpha3 > > > PR #7555 is the one introducing the temporary code. It prepares for the core release by implementing the new introduced methods, but comments out the @Override annotations so it will compile before the core release is made. > The follow-up work will be to re-add these annotations, which have all been commented out as > {code} > //@Override WFLY-4716 > {code} > and adjustments to AppClientXml > {code} > --- a/appclient/src/main/java/org/jboss/as/appclient/subsystem/parsing/AppClientXml.java > +++ b/appclient/src/main/java/org/jboss/as/appclient/subsystem/parsing/AppClientXml.java > @@ -54,8 +54,9 @@ import org.jboss.as.controller.parsing.ExtensionXml; > import org.jboss.as.controller.parsing.Namespace; > import org.jboss.as.controller.parsing.ParseUtils; > import org.jboss.as.controller.persistence.ModelMarshallingContext; > -import org.jboss.as.controller.resource.SocketBindingGroupResourceDefinition; > import org.jboss.as.server.parsing.CommonXml; > +import org.jboss.as.server.parsing.SocketBindingsXml; > +import org.jboss.as.server.services.net.SocketBindingGroupResourceDefinition; > import org.jboss.dmr.ModelNode; > import org.jboss.dmr.Property; > import org.jboss.modules.ModuleLoader; > @@ -72,7 +73,7 @@ public class AppClientXml extends CommonXml { > private final ExtensionXml extensionXml; > > public AppClientXml(final ModuleLoader loader, final ExtensionRegistry extensionRegistry) { > - super(); > + super(new AppClientSocketBindingsXml()); > extensionXml = new ExtensionXml(loader, null, extensionRegistry); > } > > @@ -410,4 +411,12 @@ public class AppClientXml extends CommonXml { > throws XMLStreamException { > // we don't marshall appclient.xml > } > + > + static class AppClientSocketBindingsXml extends SocketBindingsXml { > + @Override > + protected void writeExtraAttributes(XMLExtendedStreamWriter writer, ModelNode bindingGroup) throws XMLStreamException { > + SocketBindingGroupResourceDefinition.PORT_OFFSET.marshallAsAttribute(bindingGroup, writer); > + } > + } > + > } > {code} > Full diff at https://github.com/wildfly/wildfly/commit/2dd7eb1a3885d6496762ed399745fb1... (if github keeps these when I change my branch) > Another thing is that AutoIgnoredResourcesDomainTestCase should be removed. It now lives in core following the work on WFCORE-401. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

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

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

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

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

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

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

8 years, 1 month

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