December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4758) Upgrade to WF core 2.0.0.Alpha4

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4758?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4758. ---------------------------- > Upgrade to WF core 2.0.0.Alpha4 > ------------------------------- > > Key: WFLY-4758 > URL: https://issues.jboss.org/browse/WFLY-4758 > Project: WildFly > Issue Type: Feature Request > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 10.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4583) Do not log messages about XAResources which implement XAResourceWrapper SPI and that are known to have completed safely

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4583?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4583. ---------------------------- > Do not log messages about XAResources which implement XAResourceWrapper SPI and that are known to have completed safely > ----------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-4583 > URL: https://issues.jboss.org/browse/WFLY-4583 > Project: WildFly > Issue Type: Enhancement > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 10.0.0.Alpha1 > > > n the XA protocol a time window exists wherein the RM has committed and thus forgotten a tx branch but the TM has not yet deleted its log. A crash during this window currently results in an unrecoverable situation, as the TM assumes the branch belongs to an RM that is uncontactable and will retry recovery indefinitely. This stems from an inability to relate the Xid to a specific RM. It can be overridden globally with JTAEnvironmentBean.xaAssumeRecoveryComplete, but we would prefer more fine-grained control. With the availability of RM id information from XAResourceWrapper this becomes feasible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4612) EjbJndiBindingsDeploymentUnitProcessor logs non-i18n message at INFO

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4612?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4612. ---------------------------- > EjbJndiBindingsDeploymentUnitProcessor logs non-i18n message at INFO > -------------------------------------------------------------------- > > Key: WFLY-4612 > URL: https://issues.jboss.org/browse/WFLY-4612 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.CR1 > Reporter: Brian Stansberry > Assignee: Bartosz Baranowski > Fix For: 10.0.0.Alpha4 > > > ejb3/src/main/java/org/jboss/as/ejb3/deployment/processors/EjbJndiBindingsDeploymentUnitProcessor.java > {code} > jndiBindingsLogMessage.append("JNDI bindings for session bean named " + sessionBean.getEJBName() + " in deployment unit " + deploymentUnit + " are as follows:\n\n"); > {code} > That eventually gets logged at INFO. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4848) Ignore failing legacy messaging transformer tests

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4848?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4848. ---------------------------- > Ignore failing legacy messaging transformer tests > ------------------------------------------------- > > Key: WFLY-4848 > URL: https://issues.jboss.org/browse/WFLY-4848 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: James Perkins > Assignee: James Perkins > Fix For: 10.0.0.Alpha5 > > > When running {{legacy/messages}} subsystem tests with {{-Djboss.test.transformers.eap}} fail. Two fail with a {{ClassNotFoundException}} and two fail assertions. See http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=58617&buildTyp... for details. > For now I'll {{@Ignore}} the tests. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[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, 5 months

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, 5 months

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, 5 months

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, 5 months

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, 5 months

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, 5 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