December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4933) Upgrade jberet-core to 1.2.0.Alpha2

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4933?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4933. ---------------------------- > Upgrade jberet-core to 1.2.0.Alpha2 > ----------------------------------- > > Key: WFLY-4933 > URL: https://issues.jboss.org/browse/WFLY-4933 > Project: WildFly > Issue Type: Component Upgrade > Components: Batch > Reporter: Cheng Fang > Assignee: James Perkins > Fix For: 10.0.0.Beta1 > > > 1.2.0.Alpha2: > https://issues.jboss.org/browse/JBERET/fixforversion/12327492/?selectedTa... > 1.2.0.Alpha1: > https://issues.jboss.org/browse/JBERET/fixforversion/12326900/?selectedTa... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3290) Cannot use a cluster name other than "ejb"

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3290?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-3290. ---------------------------- > Cannot use a cluster name other than "ejb" > ------------------------------------------ > > Key: WFLY-3290 > URL: https://issues.jboss.org/browse/WFLY-3290 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.0.0.Final > Reporter: Chris Stillwell > Assignee: Richard Achmatowicz > Priority: Critical > Fix For: 10.0.0.CR1 > > Attachments: helloworld-test.zip > > > When deploying a clustered session bean the cluster will form only if the cluster name is "ejb". If the standalone-ha.xml is modified to use a different cluster name then the cluster will not form. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4995) Upgrade HAL to 2.8.3

by Kabir Khan (JIRA)

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

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5292) Missleading link to console from Wildfly10 homepage in domain mode

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5292?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5292. ---------------------------- > Missleading link to console from Wildfly10 homepage in domain mode > ------------------------------------------------------------------ > > Key: WFLY-5292 > URL: https://issues.jboss.org/browse/WFLY-5292 > Project: WildFly > Issue Type: Bug > Components: Server, Web Console > Affects Versions: 10.0.0.Beta2 > Reporter: Pavel Jelinek > Assignee: Darran Lofthouse > Priority: Minor > Fix For: 10.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4917) Invalid context set up for batch threads

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4917?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4917. ---------------------------- > Invalid context set up for batch threads > ---------------------------------------- > > Key: WFLY-4917 > URL: https://issues.jboss.org/browse/WFLY-4917 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 10.0.0.Alpha5 > Reporter: James Perkins > Assignee: James Perkins > Fix For: 10.0.0.Alpha6 > > > Batch tasks incorrectly set-up the contexts needed for the executed tasks. The task needs to be set-up outside the new thread. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4997) Upgrade jboss-transaction-spi

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4997?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4997. ---------------------------- > Upgrade jboss-transaction-spi > ----------------------------- > > Key: WFLY-4997 > URL: https://issues.jboss.org/browse/WFLY-4997 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Affects Versions: 10.0.0.Alpha5 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 10.0.0.Beta1 > > > We have just released 7.3.0.Final which introduced a locator method for obtaining an implementation of the TransactionListenerRegistry interface that JPA uses to monitor thread to transaction association changes. > The upgrade also pulls in 7.2.0.Final which introduced a change to make ServerVMClientUserTransaction implement javax.naming.Referenceable (so that it can be looked up via JNDI). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4715) Webservices subsystem requires reload when it does not actually need to

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4715?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4715. ---------------------------- > Webservices subsystem requires reload when it does not actually need to > ----------------------------------------------------------------------- > > Key: WFLY-4715 > URL: https://issues.jboss.org/browse/WFLY-4715 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Web Services > Affects Versions: 9.0.0.CR1 > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: 10.0.0.Alpha3 > > > When trying undefining and already undefined attribute of the webservices subsystem of a WildFly container on which at least a WS deployment is active, the operation requires reload if the attribute has a default value. > See http://lists.jboss.org/pipermail/wildfly-dev/2015-June/004013.html for further details. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5281) [Migration operation] [Web to Undertow] When migrating SSO configuration path should be defined as "/"

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5281?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5281. ---------------------------- > [Migration operation] [Web to Undertow] When migrating SSO configuration path should be defined as "/" > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-5281 > URL: https://issues.jboss.org/browse/WFLY-5281 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Beta2 > Reporter: Radim Hatlapatka > Assignee: Tomaz Cerar > Fix For: 10.0.0.CR1 > > > When using SSO with JBoss Web all contexts are authenticated via SSO. In case of Undertow by default are only those with the same context name. > As such {{:migrate}} operation should define {{path=/}} when migrating SSO configuration as that makes the behaviour the same as it was in JBoss Web and thus having the server configured equivalently. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5192) XTSSubsystemDefinition says HOST attribute doesn't allow null, but it should

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5192?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5192. ---------------------------- > XTSSubsystemDefinition says HOST attribute doesn't allow null, but it should > ---------------------------------------------------------------------------- > > Key: WFLY-5192 > URL: https://issues.jboss.org/browse/WFLY-5192 > Project: WildFly > Issue Type: Bug > Components: XTS > Affects Versions: 10.0.0.Beta2 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 10.0.0.CR1 > > > The xsd for the xts subsystem says the "host" element is not required, and the parser behaves accordingly, but the HOST attribute in XTSSubsystemDefinition says the attribute doesn't allow null, while simultaneously configuring a default value for it. > Setting a default value for an attribute is pointless if it doesn't allow null; the default value is what the runtime services will use if the persistent config value is null. > This situation prevents booting of legacy xml configs using schema versions that predate the "host element. (Specifically, EAP 6 configs.) The boot validates the entire config to ensure that required attributes are configured, and that validation fails. Booting configs that conform to the current schema would fail too if "host" was not present. > This should be a simple one line change. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5088) [Migration operation] If acceptor has set factory-class org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory then migration operation does not translate it to Artemis equivalent

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5088?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5088. ---------------------------- > [Migration operation] If acceptor has set factory-class org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory then migration operation does not translate it to Artemis equivalent > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-5088 > URL: https://issues.jboss.org/browse/WFLY-5088 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Alpha6 > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Fix For: 10.0.0.Beta2 > > > This is the same problem as reported with connectors in JBEAP-638. > org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory should be migrated to equivalent org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptorFactory. -- 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