July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10746) NullPointerException in ELFlash.get

by Bartosz Spyrko-Śmietanko (JIRA)

[ https://issues.jboss.org/browse/WFLY-10746?page=com.atlassian.jira.plugin... ] Bartosz Spyrko-Śmietanko moved JBEAP-15130 to WFLY-10746: --------------------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-10746 (was: JBEAP-15130) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JSF (was: JSF) Affects Version/s: (was: 7.1.0.GA) Fix Version/s: (was: 7.1.5.GA) > NullPointerException in ELFlash.get > ----------------------------------- > > Key: WFLY-10746 > URL: https://issues.jboss.org/browse/WFLY-10746 > Project: WildFly > Issue Type: Bug > Components: JSF > Environment: Red Hat JBoss Enterprise Application Platform 7.1.0 > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Bartosz Spyrko-Śmietanko > > The following NPE happenes when calling ELFlash.get in EAP 7.1.0. > ~~~ > java.lang.NullPointerException > at com.sun.faces.context.flash.ELFlash.get(ELFlash.java:412) > ~~~ > The same issue was reported in: > Fixes https://java.net/jira/browse/JAVASERVERFACES-3621, All Flash operations cause NPE with distributable webapp and no session > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7419) Include RESTEasy WADL module

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-7419?page=com.atlassian.jira.plugin.... ] Alessio Soldano reassigned WFLY-7419: ------------------------------------- Assignee: Weinan Li (was: Alessio Soldano) > Include RESTEasy WADL module > ---------------------------- > > Key: WFLY-7419 > URL: https://issues.jboss.org/browse/WFLY-7419 > Project: WildFly > Issue Type: Enhancement > Components: REST > Affects Versions: 10.1.0.Final, 11.0.0.Alpha1 > Reporter: Frank Langelage > Assignee: Weinan Li > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2784) CSS for test "expression builder" dock tab design

by Sarah Rambacher (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2784?page=com.atlassian.jira.plugi... ] Sarah Rambacher commented on DROOLS-2784: ----------------------------------------- [~danielezonca] Sorry, that was silly! Here's the first one, filter dock: https://rawgit.com/srambach/BxMS-frontend/master/mgmt-results--save-filte... And here's the process editor detail panel https://rawgit.com/srambach/BxMS-frontend/master/detail-panel-template.html > CSS for test "expression builder" dock tab design > ------------------------------------------------- > > Key: DROOLS-2784 > URL: https://issues.jboss.org/browse/DROOLS-2784 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Sarah Rambacher > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screen Shot 2018-07-24 at 9.19.37 AM.png > > > As a practitioner I want to the option to an expression builder within the UI to: > - search for and select from a set of hierarchical Data Objects > - set conditions > - name variables > so that I can add these selections as Given/Expect input values when creating a scenario test outline. > *Verification conditions:* > - CSS styles that employ relevant PatternFly styles. > - CSS that articulates the design wireframe attached, and: > https://redhat.invisionapp.com/share/BVKORFBUJ24#/screens/302476075, and: > https://docs.google.com/document/d/1I_ghU9An--uQRzuVV9zXB387HLYjZcc01LXFX... > - Reviewed by scrum team prior to PR/dev delivery. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-324) Routing issue with zalenium

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-324?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-324: ------------------------------------- This issue is not related to zalenium. Here is what is happening: OCP nodes use dnsmasq for DN resolution. Dnsmasq is using list of upstream DNS and based on some algorithm it chooses the fastest one for given query. To get debug logging of queries it's necessary to uncomment log-queries in /etc/dnsmasq.conf. For not yet known reason from time to time all queried upstream servers don't provide response for the query which results to DN resolution failure as visible in this ticket. Jul 26 03:50:27 b20 dnsmasq[7295]: query[A] kiali-istio-system.openshift.jonqe.lab.eng.bos.redhat.com from 10.129.1.167 Jul 26 03:50:27 b20 dnsmasq[7295]: forwarded kiali-istio-system.openshift.jonqe.lab.eng.bos.redhat.com to 10.16.23.54 without response so it tries it again after 5s and tries to forward to all upstream DNS: Jul 26 03:50:32 b20 dnsmasq[7295]: query[A] kiali-istio-system.openshift.jonqe.lab.eng.bos.redhat.com from 10.129.1.167 Jul 26 03:50:32 b20 dnsmasq[7295]: forwarded kiali-istio-system.openshift.jonqe.lab.eng.bos.redhat.com to 10.16.23.35 Jul 26 03:50:32 b20 dnsmasq[7295]: forwarded kiali-istio-system.openshift.jonqe.lab.eng.bos.redhat.com to 10.38.5.26 Jul 26 03:50:32 b20 dnsmasq[7295]: forwarded kiali-istio-system.openshift.jonqe.lab.eng.bos.redhat.com to 10.5.30.160 Jul 26 03:50:32 b20 dnsmasq[7295]: forwarded kiali-istio-system.openshift.jonqe.lab.eng.bos.redhat.com to 10.11.5.19 Jul 26 03:50:32 b20 dnsmasq[7295]: forwarded kiali-istio-system.openshift.jonqe.lab.eng.bos.redhat.com to 10.16.23.54 but still no response so again after 5s: Jul 26 03:50:37 b20 dnsmasq[7295]: query[A] kiali-istio-system.openshift.jonqe.lab.eng.bos.redhat.com from 10.129.1.167 Jul 26 03:50:37 b20 dnsmasq[7295]: forwarded kiali-istio-system.openshift.jonqe.lab.eng.bos.redhat.com to 10.16.23.35 Jul 26 03:50:37 b20 dnsmasq[7295]: forwarded kiali-istio-system.openshift.jonqe.lab.eng.bos.redhat.com to 10.38.5.26 Jul 26 03:50:37 b20 dnsmasq[7295]: forwarded kiali-istio-system.openshift.jonqe.lab.eng.bos.redhat.com to 10.5.30.160 Jul 26 03:50:37 b20 dnsmasq[7295]: forwarded kiali-istio-system.openshift.jonqe.lab.eng.bos.redhat.com to 10.11.5.19 Jul 26 03:50:37 b20 dnsmasq[7295]: forwarded kiali-istio-system.openshift.jonqe.lab.eng.bos.redhat.com to 10.16.23.54 still no response so it fails. What is really weird is that other queries during this timeperiod are working fine e.g.: Jul 26 03:50:28 b20 dnsmasq[7295]: query[A] kiali-istio-system.openshift.jonqe.lab.eng.bos.redhat.com from 10.129.1.169 Jul 26 03:50:28 b20 dnsmasq[7295]: forwarded kiali-istio-system.openshift.jonqe.lab.eng.bos.redhat.com to 10.16.23.54 Jul 26 03:50:28 b20 dnsmasq[7295]: reply kiali-istio-system.openshift.jonqe.lab.eng.bos.redhat.com is 10.16.23.38 I have no idea why it fails 3 times for 10.129.1.167 when it's working fine for other clients. > Routing issue with zalenium > --------------------------- > > Key: SWSQE-324 > URL: https://issues.jboss.org/browse/SWSQE-324 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Filip Brychta > > I see the following error(I guess it is routing error) weekly once, > ------ > http_conn_args = {}, host = 'zalenium.prod.os.jonqe.lab.eng.bos.redhat.com' > h = <httplib.HTTPConnection instance at 0x7f45e47c6c68> > err = gaierror(-2, 'Name or service not known') > ------ > Detailed report: http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/run-python-ui-te... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1616) ldap-key-store requires attribute userPKCS12 on ldap entry, even if it should be mandatory

by Jiri Ondrusek (JIRA)

Jiri Ondrusek created ELY-1616: ---------------------------------- Summary: ldap-key-store requires attribute userPKCS12 on ldap entry, even if it should be mandatory Key: ELY-1616 URL: https://issues.jboss.org/browse/ELY-1616 Project: WildFly Elytron Issue Type: Bug Affects Versions: 1.1.11.CR1 Reporter: Jiri Ondrusek Assignee: Jiri Ondrusek The "key-attribute" ("userPKCS12") should not be necessary to use LdapKeyStore as truststore. See Steps to Reproduce for more information. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1616) ldap-key-store requires attribute userPKCS12 on ldap entry, even if it should be mandatory

by Jiri Ondrusek (JIRA)

[ https://issues.jboss.org/browse/ELY-1616?page=com.atlassian.jira.plugin.s... ] Jiri Ondrusek updated ELY-1616: ------------------------------- Steps to Reproduce: * configure twoway ssl (see https://github.com/jboss-developer/jboss-eap-quickstarts/tree/7.1/hellowo...) * move truststore to ldap - http://planet.jboss.org/post/ldap_keystore * if ldap entry contains userCertificate;binary", "userSMIMECertificate", and "userPKCS12" -> it works * remove "userPKCS12", it should work but it doesn't was: * configure tway ssl (see https://github.com/jboss-developer/jboss-eap-quickstarts/tree/7.1/hellowo...) * move truststore to ldap - http://planet.jboss.org/post/ldap_keystore * if ldap entry contains userCertificate;binary", "userSMIMECertificate", and "userPKCS12" -> it works * remove "userPKCS12", it should work but it doesn't > ldap-key-store requires attribute userPKCS12 on ldap entry, even if it should be mandatory > ------------------------------------------------------------------------------------------ > > Key: ELY-1616 > URL: https://issues.jboss.org/browse/ELY-1616 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.11.CR1 > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > > The "key-attribute" ("userPKCS12") should not be necessary to use LdapKeyStore as truststore. > See Steps to Reproduce for more information. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10567) Broken JSF module installer

by Jan Kašík (JIRA)

[ https://issues.jboss.org/browse/WFLY-10567?page=com.atlassian.jira.plugin... ] Jan Kašík closed WFLY-10567. ---------------------------- Resolution: Done Closed in favor of WFLY-10745 > Broken JSF module installer > --------------------------- > > Key: WFLY-10567 > URL: https://issues.jboss.org/browse/WFLY-10567 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 14.0.0.CR1 > Reporter: Jan Kašík > Assignee: Dmitrii Tikhomirov > Fix For: 14.0.0.CR1 > > Attachments: hello-jsf-version-0.0.1-SNAPSHOT.war > > > It is currently not possible to deploy *.cli built by multi-jsf-installer shipped with WildFly. When attempting to deploy, this message will appear: > {code} > org.jboss.as.cli.CommandFormatException: org.jboss.as.cli.CommandLineException: java.util.concurrent.ExecutionException: org.jboss.as.cli.CommandLineException: Failed to locate /tmp/vfs/cli-1528866094723/cli-1528866094723450313ef1dc90cff/install-mojarra-2.2.17.cli-212b6d42ba0c47e1/jsf-api-2.2.17.jar, if you defined a nonexistent resource on purpose you should use the --allow-nonexistent-resources option > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10745) Broken JSF module installer

by Jan Kašík (JIRA)

[ https://issues.jboss.org/browse/WFLY-10745?page=com.atlassian.jira.plugin... ] Jan Kašík reopened WFLY-10745: ------------------------------ > Broken JSF module installer > --------------------------- > > Key: WFLY-10745 > URL: https://issues.jboss.org/browse/WFLY-10745 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 14.0.0.CR1 > Reporter: Jan Kašík > Assignee: Dmitrii Tikhomirov > Fix For: 14.0.0.CR1 > > Attachments: hello-jsf-version-0.0.1-SNAPSHOT.war > > > It is currently not possible to deploy *.cli built by multi-jsf-installer shipped with WildFly. When attempting to deploy, this message will appear: > {code} > org.jboss.as.cli.CommandFormatException: org.jboss.as.cli.CommandLineException: java.util.concurrent.ExecutionException: org.jboss.as.cli.CommandLineException: Failed to locate /tmp/vfs/cli-1528866094723/cli-1528866094723450313ef1dc90cff/install-mojarra-2.2.17.cli-212b6d42ba0c47e1/jsf-api-2.2.17.jar, if you defined a nonexistent resource on purpose you should use the --allow-nonexistent-resources option > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10745) Broken JSF module installer

by Jan Kašík (JIRA)

[ https://issues.jboss.org/browse/WFLY-10745?page=com.atlassian.jira.plugin... ] Jan Kašík updated WFLY-10745: ----------------------------- Comment: was deleted (was: Closed in favor of WFLY-10745) > Broken JSF module installer > --------------------------- > > Key: WFLY-10745 > URL: https://issues.jboss.org/browse/WFLY-10745 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 14.0.0.CR1 > Reporter: Jan Kašík > Assignee: Dmitrii Tikhomirov > Fix For: 14.0.0.CR1 > > Attachments: hello-jsf-version-0.0.1-SNAPSHOT.war > > > It is currently not possible to deploy *.cli built by multi-jsf-installer shipped with WildFly. When attempting to deploy, this message will appear: > {code} > org.jboss.as.cli.CommandFormatException: org.jboss.as.cli.CommandLineException: java.util.concurrent.ExecutionException: org.jboss.as.cli.CommandLineException: Failed to locate /tmp/vfs/cli-1528866094723/cli-1528866094723450313ef1dc90cff/install-mojarra-2.2.17.cli-212b6d42ba0c47e1/jsf-api-2.2.17.jar, if you defined a nonexistent resource on purpose you should use the --allow-nonexistent-resources option > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10745) Broken JSF module installer

by Jan Kašík (JIRA)

[ https://issues.jboss.org/browse/WFLY-10745?page=com.atlassian.jira.plugin... ] Jan Kašík closed WFLY-10745. ---------------------------- Resolution: Done Closed in favor of WFLY-10745 > Broken JSF module installer > --------------------------- > > Key: WFLY-10745 > URL: https://issues.jboss.org/browse/WFLY-10745 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 14.0.0.CR1 > Reporter: Jan Kašík > Assignee: Dmitrii Tikhomirov > Fix For: 14.0.0.CR1 > > Attachments: hello-jsf-version-0.0.1-SNAPSHOT.war > > > It is currently not possible to deploy *.cli built by multi-jsf-installer shipped with WildFly. When attempting to deploy, this message will appear: > {code} > org.jboss.as.cli.CommandFormatException: org.jboss.as.cli.CommandLineException: java.util.concurrent.ExecutionException: org.jboss.as.cli.CommandLineException: Failed to locate /tmp/vfs/cli-1528866094723/cli-1528866094723450313ef1dc90cff/install-mojarra-2.2.17.cli-212b6d42ba0c47e1/jsf-api-2.2.17.jar, if you defined a nonexistent resource on purpose you should use the --allow-nonexistent-resources option > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 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 July 2018