March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8388) Remove version.org.wildfly.security.elytron-subsystem

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-8388?page=com.atlassian.jira.plugin.... ] Kabir Khan deleted WFLY-8388: ----------------------------- > Remove version.org.wildfly.security.elytron-subsystem > ----------------------------------------------------- > > Key: WFLY-8388 > URL: https://issues.jboss.org/browse/WFLY-8388 > Project: WildFly > Issue Type: Bug > Reporter: Kabir Khan > Assignee: Kabir Khan > > The pom still contains an unused version.org.wildfly.security.elytron-subsystem. The elytron subsystem now comes in via core -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8388) Remove version.org.wildfly.security.elytron-subsystem

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-8388?page=com.atlassian.jira.plugin.... ] Kabir Khan moved JBEAP-9618 to WFLY-8388: ----------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8388 (was: JBEAP-9618) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) > Remove version.org.wildfly.security.elytron-subsystem > ----------------------------------------------------- > > Key: WFLY-8388 > URL: https://issues.jboss.org/browse/WFLY-8388 > Project: WildFly > Issue Type: Bug > Reporter: Kabir Khan > Assignee: Kabir Khan > > The pom still contains an unused version.org.wildfly.security.elytron-subsystem. The elytron subsystem now comes in via core -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2164) Probe: option -addr doesn't work

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2164?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2164. ---------------------------- Resolution: Done > Probe: option -addr doesn't work > -------------------------------- > > Key: JGRP-2164 > URL: https://issues.jboss.org/browse/JGRP-2164 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0.2 > > > First off, IPv6 addresses are not parsed correctly. Second, "addrs" as keyword is too generic, change this to "member-addrs". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2164) Probe: option {{-addr}} doesn't work

by Bela Ban (JIRA)

Bela Ban created JGRP-2164: ------------------------------ Summary: Probe: option {{-addr}} doesn't work Key: JGRP-2164 URL: https://issues.jboss.org/browse/JGRP-2164 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 4.0.2 First off, IPv6 addresses are not parsed correctly. Second, "addrs" as keyword is too generic, change this to "member-addrs". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2164) Probe: option -addr doesn't work

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2164?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2164: --------------------------- Summary: Probe: option -addr doesn't work (was: Probe: option {{-addr}} doesn't work) > Probe: option -addr doesn't work > -------------------------------- > > Key: JGRP-2164 > URL: https://issues.jboss.org/browse/JGRP-2164 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0.2 > > > First off, IPv6 addresses are not parsed correctly. Second, "addrs" as keyword is too generic, change this to "member-addrs". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-928) CLI is not terminated correctly with invalid address on HPUX

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-928?page=com.atlassian.jira.plugin... ] Jean-Francois Denise closed WFCORE-928. --------------------------------------- Resolution: Cannot Reproduce Bug > CLI is not terminated correctly with invalid address on HPUX > ------------------------------------------------------------ > > Key: WFCORE-928 > URL: https://issues.jboss.org/browse/WFCORE-928 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.0.Beta4 > Reporter: Marek Kopecký > Assignee: Jean-Francois Denise > Priority: Minor > > *Description of problem:* > CLI is not terminated correctly with invalid address on HPUX. > *How reproducible:* > Always on HPUX > *Steps to Reproduce:* > # ./jboss-cli.sh -c --controller=nonsence > *Actual results:* > CLI is terminated after input on stdin. > *Expected results:* > CLI is terminated correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-70) Refactor existing CF-UI shell scripts for starting/stopping CFME on docker server

by Sunil kondkar (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-70?page=com.atlassian.jira.plu... ] Sunil kondkar reassigned HAWKULARQE-70: --------------------------------------- Assignee: Sunil kondkar (was: mfoley user) > Refactor existing CF-UI shell scripts for starting/stopping CFME on docker server > --------------------------------------------------------------------------------- > > Key: HAWKULARQE-70 > URL: https://issues.jboss.org/browse/HAWKULARQE-70 > Project: Hawkular QE > Issue Type: Task > Reporter: Sunil kondkar > Assignee: Sunil kondkar > > Need of the task: > To make sure the CFME docker instance that we use on Jenkins nightly run has CFME containers always running, we use docker scripts. > These are existing shell scripts which are using old methods to create cfme docker container and then start the cfme instance which are irrelevant now: > These are located at: > https://github.com/Hawkular-QE/cf-ui/tree/master/scripts/automation/docker > This task is to: > 1) Modify the scripts (common.sh, start.sh) to: > -Stop the CFME instance > -Start the CFME instance > -Check if the URL is ready using curl > -Check the logs if CFME is started > 2) Git clone the modified scripts to CFME server > 3) Execute the scripts on CFME server > ( Use 'execute shell script' on Jenkins nightly job to ssh/git clone and execute script on CFME server) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-70) Refactor existing CF-UI shell scripts for starting/stopping CFME on docker server

by Sunil kondkar (JIRA)

Sunil kondkar created HAWKULARQE-70: --------------------------------------- Summary: Refactor existing CF-UI shell scripts for starting/stopping CFME on docker server Key: HAWKULARQE-70 URL: https://issues.jboss.org/browse/HAWKULARQE-70 Project: Hawkular QE Issue Type: Task Reporter: Sunil kondkar Assignee: mfoley user Need of the task: To make sure the CFME docker instance that we use on Jenkins nightly run has CFME containers always running, we use docker scripts. These are existing shell scripts which are using old methods to create cfme docker container and then start the cfme instance which are irrelevant now: These are located at: https://github.com/Hawkular-QE/cf-ui/tree/master/scripts/automation/docker This task is to: 1) Modify the scripts (common.sh, start.sh) to: -Stop the CFME instance -Start the CFME instance -Check if the URL is ready using curl -Check the logs if CFME is started 2) Git clone the modified scripts to CFME server 3) Execute the scripts on CFME server ( Use 'execute shell script' on Jenkins nightly job to ssh/git clone and execute script on CFME server) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8383) The current JBoss EAP version is not load balancing websocket requests when using Undertow as a load balancer when mod_cluster is used. This causes all websocket sessions to be created at a single backend server.

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-8383?page=com.atlassian.jira.plugin.... ] Stuart Douglas closed WFLY-8383. -------------------------------- Resolution: Rejected > The current JBoss EAP version is not load balancing websocket requests when using Undertow as a load balancer when mod_cluster is used. This causes all websocket sessions to be created at a single backend server. > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-8383 > URL: https://issues.jboss.org/browse/WFLY-8383 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Reporter: David Mulford > Assignee: Stuart Douglas > > User is looking for functionality similar to that of mod_proxy_wstunnel for Apache httpd, and wants this in Undertow's mod_cluster implementation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1005) Incompatible handling of digest-uri from legacy clients.

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/ELY-1005?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved ELY-1005. --------------------------------- Resolution: Done > Incompatible handling of digest-uri from legacy clients. > -------------------------------------------------------- > > Key: ELY-1005 > URL: https://issues.jboss.org/browse/ELY-1005 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Affects Versions: 1.1.0.Beta29 > Reporter: Darran Lofthouse > Assignee: Stuart Douglas > Priority: Blocker > Fix For: 1.1.0.Beta32 > > > When using the jboss-remote-naming library from EAP 7.0 against EAP 7.1.0.DR13 the client is unable to authenticate and all lookups time out ( {{java.net.ConnectException: Operation failed with status WAITING after 5000 MILLISECONDS}} ) > The exact same client code with the same dependencies works when running against EAP 7.1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 March 2017