February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (HAWKULARQE-43) Hawkular Agent for EAP 6.4

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-43?page=com.atlassian.jira.plu... ] Hayk Hovsepyan commented on HAWKULARQE-43: ------------------------------------------ Depends on BZ https://bugzilla.redhat.com/show_bug.cgi?id=1384949 > Hawkular Agent for EAP 6.4 > -------------------------- > > Key: HAWKULARQE-43 > URL: https://issues.jboss.org/browse/HAWKULARQE-43 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > > Smoke test based on template https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/testr... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-971) LdapRealm - referral mode: direct verification + FOLLOW mode

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-971?page=com.atlassian.jira.plugin.sy... ] Jan Kalina updated ELY-971: --------------------------- Description: The same problem as ELY-804 but in FOLLOW mode of DirContext. > LdapRealm - referral mode: direct verification + FOLLOW mode > ------------------------------------------------------------- > > Key: ELY-971 > URL: https://issues.jboss.org/browse/ELY-971 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Critical > > The same problem as ELY-804 but in FOLLOW mode of DirContext. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-971) LdapRealm - referral mode: direct verification + FOLLOW mode

by Jan Kalina (JIRA)

Jan Kalina created ELY-971: ------------------------------ Summary: LdapRealm - referral mode: direct verification + FOLLOW mode Key: ELY-971 URL: https://issues.jboss.org/browse/ELY-971 Project: WildFly Elytron Issue Type: Bug Components: Realms Reporter: Jan Kalina Assignee: Jan Kalina Priority: Critical -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-45) Setup Jenkins Slave server on openstack to run cf-ui smoke test suite

by Sunil kondkar (JIRA)

Sunil kondkar created HAWKULARQE-45: --------------------------------------- Summary: Setup Jenkins Slave server on openstack to run cf-ui smoke test suite Key: HAWKULARQE-45 URL: https://issues.jboss.org/browse/HAWKULARQE-45 Project: Hawkular QE Issue Type: Task Reporter: Sunil kondkar Assignee: mfoley user At present Jenkins slave is on BC and sometimes smoke test suites fai due to timeout issue. This task is to setup Jenkins slave on openstack instance. Install: Python Chrome/FF Headless Selenium xvfb connect via vnc -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2158) NPE from org.apache.log4j.CategoryKey.

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2158?page=com.atlassian.jira.plugin.... ] Bela Ban closed JGRP-2158. -------------------------- Resolution: Rejected Not a JGroups problem > NPE from org.apache.log4j.CategoryKey. > -------------------------------------- > > Key: JGRP-2158 > URL: https://issues.jboss.org/browse/JGRP-2158 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.11 > Reporter: Biswajit Bhuyan > Assignee: Bela Ban > > Getting NPE from jGroup. Please find the stacktrace below: > java.lang.NullPointerException > at org.apache.log4j.CategoryKey.<init>(CategoryKey.java:32) > at org.apache.log4j.Hierarchy.getLogger(Hierarchy.java:266) > at org.apache.log4j.Hierarchy.getLogger(Hierarchy.java:247) > at org.apache.log4j.LogManager.getLogger(LogManager.java:228) > at org.apache.log4j.Logger.getLogger(Logger.java:104) > at com.webmethods.rtl.util.Debug$JuliToLog4jHandler.getTargetLogger(Debug.java:1798) > at com.webmethods.rtl.util.Debug$JuliToLog4jHandler.publish(Debug.java:1790) > at java.util.logging.Logger.log(Logger.java:738) > at org.jgroups.logging.JDKLogImpl.log(JDKLogImpl.java:49) > at org.jgroups.logging.JDKLogImpl.log(JDKLogImpl.java:28) > at org.jgroups.logging.JDKLogImpl.warn(JDKLogImpl.java:122) > at org.jgroups.stack.Configurator.setDefaultValues(Configurator.java:754) > at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:117) > at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:57) > at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:476) > at org.jgroups.JChannel.init(JChannel.java:852) > at org.jgroups.JChannel.<init>(JChannel.java:159) > at org.jgroups.JChannel.<init>(JChannel.java:148) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2158) NPE from org.apache.log4j.CategoryKey.

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2158?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2158: -------------------------------- The NPE is not from JGroups but from log4j; please investigate there. > NPE from org.apache.log4j.CategoryKey. > -------------------------------------- > > Key: JGRP-2158 > URL: https://issues.jboss.org/browse/JGRP-2158 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.11 > Reporter: Biswajit Bhuyan > Assignee: Bela Ban > > Getting NPE from jGroup. Please find the stacktrace below: > java.lang.NullPointerException > at org.apache.log4j.CategoryKey.<init>(CategoryKey.java:32) > at org.apache.log4j.Hierarchy.getLogger(Hierarchy.java:266) > at org.apache.log4j.Hierarchy.getLogger(Hierarchy.java:247) > at org.apache.log4j.LogManager.getLogger(LogManager.java:228) > at org.apache.log4j.Logger.getLogger(Logger.java:104) > at com.webmethods.rtl.util.Debug$JuliToLog4jHandler.getTargetLogger(Debug.java:1798) > at com.webmethods.rtl.util.Debug$JuliToLog4jHandler.publish(Debug.java:1790) > at java.util.logging.Logger.log(Logger.java:738) > at org.jgroups.logging.JDKLogImpl.log(JDKLogImpl.java:49) > at org.jgroups.logging.JDKLogImpl.log(JDKLogImpl.java:28) > at org.jgroups.logging.JDKLogImpl.warn(JDKLogImpl.java:122) > at org.jgroups.stack.Configurator.setDefaultValues(Configurator.java:754) > at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:117) > at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:57) > at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:476) > at org.jgroups.JChannel.init(JChannel.java:852) > at org.jgroups.JChannel.<init>(JChannel.java:159) > at org.jgroups.JChannel.<init>(JChannel.java:148) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8167) Properties of Elytron dir-context are parsed incorrectly

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFLY-8167: ---------------------------------- Summary: Properties of Elytron dir-context are parsed incorrectly Key: WFLY-8167 URL: https://issues.jboss.org/browse/WFLY-8167 Project: WildFly Issue Type: Bug Components: Security Reporter: Ondrej Lukas Assignee: Darran Lofthouse Priority: Critical Properties added for Elytron {{dir-context}} through server configuration are parsed incorrectly. In case when some value is used in server configuration then its representation in server obtains also quotation marks, i.e. {{something}} is parsed as string {{"something"}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8158) JSP source code leak when space and periods added at the end of the URL

by Markus Wahl (JIRA)

[ https://issues.jboss.org/browse/WFLY-8158?page=com.atlassian.jira.plugin.... ] Markus Wahl commented on WFLY-8158: ----------------------------------- Great. I will look into that commit. Thanks [~swd847] BTW why can't we study the JIRA UNDERTOW-576 (or UNDERTOW-432 for that matter)? I received a response from a Vlastimil Elias (software engineer, jboss.org Development Team) who said it was because of a security issue. But since everything is readily accessibly via the public git-hib-repository I believe that response to not have much merit. Please, what is your opinion? Is it possible to change that policy so that we can inspect all JIRA-issues for undertow? > JSP source code leak when space and periods added at the end of the URL > ----------------------------------------------------------------------- > > Key: WFLY-8158 > URL: https://issues.jboss.org/browse/WFLY-8158 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.2.0.Final > Environment: WildFly executing on Windows > Reporter: Markus Wahl > Assignee: Stuart Douglas > Priority: Blocker > > All of the following requests will return the jsp file content untransformed, meaning that the actual content of the jsp-file is returned to the browser. > {code} > http://localhost:8080/application/HostPage.jsp%2E > http://localhost:8080/application/HostPage.jsp%2E%2E > http://localhost:8080/application/HostPage.jsp%20%2E > http://localhost:8080/application/HostPage.jsp%20%2E%2E > {code} > The problem with periods has perhaps to do with windows removing/accepting trailing periods in file names: [here|http://stackoverflow.com/questions/17746494/why-is-directory-name-wh...], [and here|http://stackoverflow.com/questions/11681207/how-to-create-a-filename...] because {{io.undertow.server.handlers.resource.FileResourceManager.getResource()}} delegates to {{java.io.File}} to test whether a file path is valid or not, and {{java.io.File}} does presumably delegate to Windows. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-44) Verify events generated on failed operations

by Sunil kondkar (JIRA)

Sunil kondkar created HAWKULARQE-44: --------------------------------------- Summary: Verify events generated on failed operations Key: HAWKULARQE-44 URL: https://issues.jboss.org/browse/HAWKULARQE-44 Project: Hawkular QE Issue Type: Task Reporter: Sunil kondkar Assignee: mfoley user Few test cases(Related to events genration due to failed operation) were blocked due to below bug: https://bugzilla.redhat.com/show_bug.cgi?id=1396238 Tasks: Re-verify blocked test cases and mark the status in polarion -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-41) Hawkular Agent for EAP7.1

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-41?page=com.atlassian.jira.plu... ] Hayk Hovsepyan updated HAWKULARQE-41: ------------------------------------- Description: Smoke test is required based on template https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/testr... Bug should be fixed https://bugzilla.redhat.com/show_bug.cgi?id=1370499 was:Smoke test is required based on template https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/testr... > Hawkular Agent for EAP7.1 > ------------------------- > > Key: HAWKULARQE-41 > URL: https://issues.jboss.org/browse/HAWKULARQE-41 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: mfoley user > > Smoke test is required based on template https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/testr... > Bug should be fixed https://bugzilla.redhat.com/show_bug.cgi?id=1370499 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 February 2017