December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4264) Update ejb-client version to 2.1.1.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4264?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4264. ---------------------------- > Update ejb-client version to 2.1.1.Final > ---------------------------------------- > > Key: WFLY-4264 > URL: https://issues.jboss.org/browse/WFLY-4264 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Panagiotis Sotiropoulos > Assignee: David Lloyd > Fix For: 9.0.0.CR2, 10.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4833) Upgrade wildfly-arquillian from 1.0.0.CR1 to 1.0.0.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4833?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4833. ---------------------------- > Upgrade wildfly-arquillian from 1.0.0.CR1 to 1.0.0.Final > -------------------------------------------------------- > > Key: WFLY-4833 > URL: https://issues.jboss.org/browse/WFLY-4833 > Project: WildFly > Issue Type: Component Upgrade > Components: Test Suite > Reporter: James Perkins > Assignee: James Perkins > Fix For: 9.0.0.Final, 10.0.0.Alpha4 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5255) EJB3 needs transformers for EAP 6.4.0

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5255?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5255. ---------------------------- > EJB3 needs transformers for EAP 6.4.0 > ------------------------------------- > > Key: WFLY-5255 > URL: https://issues.jboss.org/browse/WFLY-5255 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Affects Versions: 10.0.0.Beta2 > Reporter: Kabir Khan > Assignee: Kabir Khan > 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-5076) Enhance testsuite with WS-Trust/STS tests

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5076?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5076. ---------------------------- > Enhance testsuite with WS-Trust/STS tests > ----------------------------------------- > > Key: WFLY-5076 > URL: https://issues.jboss.org/browse/WFLY-5076 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Fix For: 10.0.0.CR1 > > > Port WS-Trust tests from JBossWS testsuite, try to reuse as much as possible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5275) Connection Factory parameter disappears after code deployment

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5275?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5275. ---------------------------- > Connection Factory parameter disappears after code deployment > ------------------------------------------------------------- > > Key: WFLY-5275 > URL: https://issues.jboss.org/browse/WFLY-5275 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Mike Millson > Assignee: Chao Wang > Fix For: 10.0.0.CR1 > > > The min-pool-size setting in the following connection Factory disappears from domain.xml after any code deployments or change made in the console to the queues for the connection factory: > {code} > <connection-definition class-name="org.apache.activemq.ra.ActiveMQManagedConnectionFactory" jndi-name="java:jboss/activemq/XAConnectionFactory" enabled="true" use-java-context="true" pool-name="ConnectionFactory" min-pool-size="0"></connection> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5002) Undertow mod_cluster CLI: Display node's Flushpackets, Flushwait, Ping, Smax and Ttl properties

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5002?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5002. ---------------------------- > Undertow mod_cluster CLI: Display node's Flushpackets, Flushwait, Ping, Smax and Ttl properties > ----------------------------------------------------------------------------------------------- > > Key: WFLY-5002 > URL: https://issues.jboss.org/browse/WFLY-5002 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Reporter: Michal Karm Babacek > Assignee: Stuart Douglas > Labels: mod_cluster > Fix For: 10.0.0.Alpha6 > > > As a follow up to JBEAP-215, this bug report is a member of a series addressing crucial CLI management capabilities. > h3. Display node's Flushpackets, Flushwait, Ping, Smax and Ttl properties > At the moment, this is all there is to see: > {noformat} > "balancer" => { > "qa_balancer" => {"node" => {"worker-2" => { > "load" => 89, > "status" => "NODE_UP", > "context" => {"/clusterbench" => { > "requests" => 0, > "status" => "enabled" > }} > }}}, > ... > {noformat} > h3. Call to action > For any serious enterprise deployment, users need to tweak at least ping and ttl attributes and they will need to be able to see their values on Undertow mod_cluster proxy balancer CLI console per each worker. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

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

by Kabir Khan (JIRA)

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

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4624) JGroups protocol properties are not applied

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4624?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4624. ---------------------------- > JGroups protocol properties are not applied > ------------------------------------------- > > Key: WFLY-4624 > URL: https://issues.jboss.org/browse/WFLY-4624 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 9.0.0.CR1 > Reporter: Farah Juma > Assignee: Radoslav Husar > Priority: Blocker > Fix For: 9.0.0.CR2, 10.0.0.Alpha1 > > > Protocol properties are never applied, the check for applying properties is done on the legacy resource that only registers operation tranformation on old the old property address. > Original report: > ---- > When the JGroups subsystem is configured to use TCPPING, the following error occurs when deploying a distributable app: > {code} > 14:50:11,930 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.jgroups.channel.ee: org.jboss.msc.service.StartException in service jboss.jgroups.channel.ee: java.security.PrivilegedActionException: java.lang.Exception: Property assignment of initial_hosts in TCPPING with original property value null and converted to null could not be assigned > at org.wildfly.clustering.jgroups.spi.service.ChannelBuilder.start(ChannelBuilder.java:79) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.security.PrivilegedActionException: java.lang.Exception: Property assignment of initial_hosts in TCPPING with original property value null and converted to null could not be assigned > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:638) > at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:99) > at org.wildfly.clustering.jgroups.spi.service.ChannelBuilder.start(ChannelBuilder.java:77) > ... 5 more > Caused by: java.lang.Exception: Property assignment of initial_hosts in TCPPING with original property value null and converted to null could not be assigned > at org.jgroups.stack.Configurator.resolveAndAssignField(Configurator.java:1153) > at org.jgroups.stack.Configurator.createLayer(Configurator.java:444) > at org.jgroups.stack.Configurator.createProtocols(Configurator.java:398) > at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:90) > at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:57) > at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:477) > at org.jgroups.JChannel.init(JChannel.java:854) > at org.jgroups.JChannel.<init>(JChannel.java:159) > at org.jboss.as.clustering.jgroups.JChannelFactory$1.run(JChannelFactory.java:96) > at org.jboss.as.clustering.jgroups.JChannelFactory$1.run(JChannelFactory.java:93) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:634) > ... 7 more > Caused by: java.lang.Exception: Conversion of initial_hosts in TCPPING with original property value null failed > at org.jgroups.conf.PropertyHelper.getConvertedValue(PropertyHelper.java:84) > at org.jgroups.stack.Configurator.resolveAndAssignField(Configurator.java:1147) > ... 17 more > Caused by: java.lang.NullPointerException > at java.util.StringTokenizer.<init>(StringTokenizer.java:199) > at java.util.StringTokenizer.<init>(StringTokenizer.java:221) > at org.jgroups.util.Util.parseCommaDelimitedHosts(Util.java:2650) > at org.jgroups.conf.PropertyConverters$InitialHosts.convert(PropertyConverters.java:67) > at org.jgroups.conf.PropertyHelper.getConvertedValue(PropertyHelper.java:81) > ... 18 more > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3771) Implement graceful shutdown for clustering

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3771?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-3771. ---------------------------- > Implement graceful shutdown for clustering > ------------------------------------------ > > Key: WFLY-3771 > URL: https://issues.jboss.org/browse/WFLY-3771 > Project: WildFly > Issue Type: Sub-task > Components: Clustering > Reporter: Stuart Douglas > Assignee: Paul Ferraro > Fix For: 10.0.0.Beta1 > > > I am not sure exactly what needs to happen here, I think all that is required is for the node to leave the cluster before suspend starts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5174) Upgrade jberet-core to 1.2.0.Beta1

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5174?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5174. ---------------------------- > Upgrade jberet-core to 1.2.0.Beta1 > ---------------------------------- > > Key: WFLY-5174 > URL: https://issues.jboss.org/browse/WFLY-5174 > Project: WildFly > Issue Type: Component Upgrade > Components: Batch > Reporter: Cheng Fang > Assignee: James Perkins > Fix For: 10.0.0.CR1 > > > JBeret 1.2.0.Beta1: > https://issues.jboss.org/browse/JBERET/fixforversion/12327647/?selectedTa... -- 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