April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2336) Probe: add support for running on TCP

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2336?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2336. ---------------------------- Resolution: Done > Probe: add support for running on TCP > ------------------------------------- > > Key: JGRP-2336 > URL: https://issues.jboss.org/browse/JGRP-2336 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.0 > > > Probe / DiagnosticsHandler currently only supports UDP / IP multicasting. > Add support for listening on TCP sockets. In this case, probe.sh needs to be invoked with the address of _one_ member, e.g. {{probe.sh -aadr 192.168.1.5}}. > This will help to run JGroups on GraalVM (JGRP-2332) as MulticastSocket is currently not supported (see {{./doc/design/PortingToGraalVM.txt}} for details). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11963) ejb3 thread-pool thread-factory should be shown deprecated in management api

by Chao Wang (Jira)

[ https://issues.jboss.org/browse/WFLY-11963?page=com.atlassian.jira.plugin... ] Chao Wang reassigned WFLY-11963: -------------------------------- Assignee: (was: Chao Wang) > ejb3 thread-pool thread-factory should be shown deprecated in management api > ---------------------------------------------------------------------------- > > Key: WFLY-11963 > URL: https://issues.jboss.org/browse/WFLY-11963 > Project: WildFly > Issue Type: Enhancement > Components: EJB > Affects Versions: 16.0.0.Final > Reporter: Chao Wang > Priority: Major > > ejb3 thread-pool thread-factory should be shown deprecated in management api > The threads subsystem was deprecated and is not in the EAP 7.x configurations, so the thread-factory attribute on the ejb3 thread-pool configuration should indicate it is deprecated and should not be used. > {code} > /subsystem=ejb3/thread-pool=default:read-resource-description( > "thread-factory" => { > "type" => STRING, > "description" => "Specifies the name of a specific thread factory to use to create worker threads. If not defined an appropriate default thread factory will be used.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "all-services" > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11963) ejb3 thread-pool thread-factory should be shown deprecated in management api

by Chao Wang (Jira)

[ https://issues.jboss.org/browse/WFLY-11963?page=com.atlassian.jira.plugin... ] Chao Wang moved JBEAP-16694 to WFLY-11963: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11963 (was: JBEAP-16694) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: EJB (was: EJB) Affects Version/s: 16.0.0.Final (was: 7.2.0.GA) > ejb3 thread-pool thread-factory should be shown deprecated in management api > ---------------------------------------------------------------------------- > > Key: WFLY-11963 > URL: https://issues.jboss.org/browse/WFLY-11963 > Project: WildFly > Issue Type: Enhancement > Components: EJB > Affects Versions: 16.0.0.Final > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Major > > ejb3 thread-pool thread-factory should be shown deprecated in management api > The threads subsystem was deprecated and is not in the EAP 7.x configurations, so the thread-factory attribute on the ejb3 thread-pool configuration should indicate it is deprecated and should not be used. > {code} > /subsystem=ejb3/thread-pool=default:read-resource-description( > "thread-factory" => { > "type" => STRING, > "description" => "Specifies the name of a specific thread factory to use to create worker threads. If not defined an appropriate default thread factory will be used.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "all-services" > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-706) Update jenkins docker slave image

by Filip Brychta (Jira)

Filip Brychta created SWSQE-706: ----------------------------------- Summary: Update jenkins docker slave image Key: SWSQE-706 URL: https://issues.jboss.org/browse/SWSQE-706 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Assignee: Filip Brychta We will need new requirements so it's necessary to update jenkins slave image -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3298) EnumValidator should avoid trying to modify protected nodes

by Michal Petrov (Jira)

[ https://issues.jboss.org/browse/WFCORE-3298?page=com.atlassian.jira.plugi... ] Michal Petrov reassigned WFCORE-3298: ------------------------------------- Assignee: Michal Petrov > EnumValidator should avoid trying to modify protected nodes > ----------------------------------------------------------- > > Key: WFCORE-3298 > URL: https://issues.jboss.org/browse/WFCORE-3298 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Brian Stansberry > Assignee: Michal Petrov > Priority: Major > > EnumValidator is trying to "correct" inputs by converting the input node to the official name of the enum. This results a caught and discarded UnsupportedOperationException if the node is protected. Catching an exception is a poor way to do this. > Simply not doing the write if the input is the same as the official value is one way to mitigate this, but better is to wait for DMR-37 and just check if the node is protected. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11116) Wildfly 12.0.0 Final Delay in Getting the Value Attributes of the Session Variables (Result in Null Pointer Exception)

by ziad saade (Jira)

[ https://issues.jboss.org/browse/WFLY-11116?page=com.atlassian.jira.plugin... ] ziad saade commented on WFLY-11116: ----------------------------------- Issue still reproduced under WildFly 16.0.0.Final Is there any settings to configure sessions variables in JBoss? Best regards= > Wildfly 12.0.0 Final Delay in Getting the Value Attributes of the Session Variables (Result in Null Pointer Exception) > ---------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11116 > URL: https://issues.jboss.org/browse/WFLY-11116 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 14.0.1.Final, 12.0.0.Final, 13.0.0.Final, 15.0.0.Final > Reporter: ziad saade > Assignee: Paul Ferraro > Priority: Critical > > I have two Servlets Book and BookPreview the attribute is set in Book Servlet as follow: > > Book.java > TestBean testBean=null; > if(session.getAttribute("testBean")!=null) > testBean = (TestBean)session.getAttribute("testBean"); > else{ > testBean=new TestBean(); > session.setAttribute("testBean",testBean); > } > testBean.setAmount("10"); > > response.sendRedirect("BookPreview"); > > > The session attribute can be retrieved and the page is loaded normally and the Amount value is displayed however when submitting the form (Post Action in BookPreview.java) Null Pointer exception is generated. > > BookPreview.java > > TestBean testBean = (TestBean)session.getAttribute("testBean"); > String amount = testBean.getAmount; //Null pointer exception when submitting the form > > <form method="Post" action="BookPreview"> > > </form> > > TestBean.java > > public class TestBean implements java.io.Serializable { > > private static final long serialVersionUID = 1L; > private String amount; > > public String getAmount() { > return amount; > } > > public void setAmount(String amount) { > this.amount = amount; > } > } > > Kindly advice how to fix the problem at the level of the server configuration. > PS: I am not getting the exception when deploying the same application under other J EE application servers (Tomcat....) > > Thanks and Best Regards -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3864) Kubernetes configuration for remote debug

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3864?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-3864: --------------------------------------- Issue Type: Task (was: Feature Request) > Kubernetes configuration for remote debug > ----------------------------------------- > > Key: DROOLS-3864 > URL: https://issues.jboss.org/browse/DROOLS-3864 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3865) Document internal flow

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3865?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-3865: --------------------------------------- Issue Type: Task (was: Feature Request) > Document internal flow > ---------------------- > > Key: DROOLS-3865 > URL: https://issues.jboss.org/browse/DROOLS-3865 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3865) Document internal flow

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-3865: ------------------------------------------ Summary: Document internal flow Key: DROOLS-3865 URL: https://issues.jboss.org/browse/DROOLS-3865 Project: Drools Issue Type: Feature Request Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-705) Update kiali build job to work with new kiali operator

by Filip Brychta (Jira)

Filip Brychta created SWSQE-705: ----------------------------------- Summary: Update kiali build job to work with new kiali operator Key: SWSQE-705 URL: https://issues.jboss.org/browse/SWSQE-705 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta There is new PR which is enabling kiali operator and removing old bash script which was used for building and deploying kiali. We need to update our jobs to work with this new operator. https://github.com/kiali/kiali/pull/974 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 April 2019