March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8455) Upgrade HAL to 2.9.6.Final

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/WFLY-8455?page=com.atlassian.jira.plugin.... ] Harald Pehl updated WFLY-8455: ------------------------------ Fix Version/s: 11.0.0.CR1 (was: 11.0.0.Beta1) > Upgrade HAL to 2.9.6.Final > -------------------------- > > Key: WFLY-8455 > URL: https://issues.jboss.org/browse/WFLY-8455 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Fix For: 11.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-82) JMAN4 Feature Requests Test Cases Review

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-82?page=com.atlassian.jira.plu... ] Hayk Hovsepyan resolved HAWKULARQE-82. -------------------------------------- Resolution: Done Done review for all in progress JMAN4 tasks. > JMAN4 Feature Requests Test Cases Review > ---------------------------------------- > > Key: HAWKULARQE-82 > URL: https://issues.jboss.org/browse/HAWKULARQE-82 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Critical > > Go through all JMAN4 Features and their QE tasks: > Make sure that all existing Polarion testcases are created and mentioned in QE tasks. > Review polarion testcases, make comments on QE tasks to fix testcases if necessary. > If testcases are missing, request to create them. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-1047) CS tool, meaningless error msg when I create credential store storage file under OracleJDK and access to it under IBMJDK.

by Hynek Švábek (JIRA)

Hynek Švábek created ELY-1047: --------------------------------- Summary: CS tool, meaningless error msg when I create credential store storage file under OracleJDK and access to it under IBMJDK. Key: ELY-1047 URL: https://issues.jboss.org/browse/ELY-1047 Project: WildFly Elytron Issue Type: Bug Reporter: Hynek Švábek Assignee: Darran Lofthouse When I create credential store storage file under OracleJDK or OpenJDK and then I want to access to it under IBMJDK I get meaningless error message about this. I expect some error message about that you must use to access same JDK as was used for creation storage file. *How to reproduce* Create credential store storage file with OracleJDK (or openJDK) {code} java -jar wildfly-elytron-tool.jar credential-store --add moje --secret asdfasdf --location="PATH/TO/store01.jceks" --uri "cr-store://store01.jceks?modifiable=true;create=true;keyStoreType=JCEKS" --password=pass123 --summary {code} Try to list aliases with IBMJDK {code} java -jar wildfly-elytron-tool.jar credential-store --aliases --location="/PATH/TO/store01.jceks" --uri "cr-store://store01.jceks?modifiable=true;create=true;keyStoreType=JCEKS" --password=pass123 --summary ELY09526: Unable to initialize credential store {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-35) Manual Testcases - Create and Run

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-35?page=com.atlassian.jira.plu... ] Hayk Hovsepyan reassigned HAWKULARQE-35: ---------------------------------------- Assignee: Prachi Yadav (was: Vojtech Prusa) > Manual Testcases - Create and Run > --------------------------------- > > Key: HAWKULARQE-35 > URL: https://issues.jboss.org/browse/HAWKULARQE-35 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Prachi Yadav > Priority: Critical > > Add new provider with SSL and check that provider is added successfully and inventory is loaded. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-20) Manual Testcases - Create and Run

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-20?page=com.atlassian.jira.plu... ] Hayk Hovsepyan commented on HAWKULARQE-20: ------------------------------------------ Test case is: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/worki... > Manual Testcases - Create and Run > --------------------------------- > > Key: HAWKULARQE-20 > URL: https://issues.jboss.org/browse/HAWKULARQE-20 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Labels: hawkular-qe-manual > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1504) Resolution of variable with leading or trailing spaces

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-1504: -------------------------------------- Summary: Resolution of variable with leading or trailing spaces Key: DROOLS-1504 URL: https://issues.jboss.org/browse/DROOLS-1504 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-1046) Elytron properties-realm doesn't handle unicode sequences

by Josef Cacek (JIRA)

Josef Cacek created ELY-1046: -------------------------------- Summary: Elytron properties-realm doesn't handle unicode sequences Key: ELY-1046 URL: https://issues.jboss.org/browse/ELY-1046 Project: WildFly Elytron Issue Type: Bug Reporter: Josef Cacek Assignee: Darran Lofthouse Priority: Blocker Users who use property-file based authentication with plain passwords can't authenticate with Elytron if the property file contains Unicode escape sequences (e.g. file generated by using a classical {{java.util.Properties}}). The same authentication works with legacy solution (_/core-service=management/security-realm=ApplicationRealm/authentication=properties(plain-text=true, ...)_). The {{LegacyPropertiesSecurityRealm}} implementation has to be able to support properties files which were supported by legacy security realms. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8481) ClassCastException upon trying to invoke asynchronous method in bean running in EAP7.1 from 7.0 legacy EJB client

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-8481?page=com.atlassian.jira.plugin.... ] Stuart Douglas moved JBEAP-10044 to WFLY-8481: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8481 (was: JBEAP-10044) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: EJB (was: EJB) Affects Version/s: (was: 7.1.0.DR14) > ClassCastException upon trying to invoke asynchronous method in bean running in EAP7.1 from 7.0 legacy EJB client > ----------------------------------------------------------------------------------------------------------------- > > Key: WFLY-8481 > URL: https://issues.jboss.org/browse/WFLY-8481 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Priority: Critical > > Upon asynchronous call from 7.0 client to bean deployed on 7.1 server, the following exception is produced: > {code}Mar 17, 2017 7:25:36 AM org.jboss.as.quickstarts.ejb.asynchronous.client.AsynchronousClient fireAndForget > INFO: The server log should contain a message at (about) Fri Mar 17 07:25:51 UTC 2017, indicating that the call to the asynchronous bean completed. > Exception in thread "main" java.lang.ClassCastException: java.lang.String cannot be cast to java.util.concurrent.Future > at com.sun.proxy.$Proxy0.longerRunning(Unknown Source) > at org.jboss.as.quickstarts.ejb.asynchronous.client.AsynchronousClient.getResultAsync(AsynchronousClient.java:88) > at org.jboss.as.quickstarts.ejb.asynchronous.client.AsynchronousClient.main(AsynchronousClient.java:159){code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2606) Wildfly OpenSSL 1.0.0.CR1

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2606?page=com.atlassian.jira.plugi... ] Stuart Douglas moved JBEAP-10042 to WFCORE-2606: ------------------------------------------------ Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2606 (was: JBEAP-10042) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) > Wildfly OpenSSL 1.0.0.CR1 > ------------------------- > > Key: WFCORE-2606 > URL: https://issues.jboss.org/browse/WFCORE-2606 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3860) Improve dependency handling in clustering/infinispan subsystem tests

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3860?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned WFLY-3860: ------------------------------------ Assignee: Radoslav Husar > Improve dependency handling in clustering/infinispan subsystem tests > -------------------------------------------------------------------- > > Key: WFLY-3860 > URL: https://issues.jboss.org/browse/WFLY-3860 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 9.0.0.Alpha1 > Reporter: Brian Stansberry > Assignee: Radoslav Husar > > The subsystem tests in clustering/infinispan are not configured to use a controller operating in --admin-only mode, but they are also not doing all the needed setup to have needed services and resources (core, jmx, jgroups) available for when the services they add are started. > This is fragile, because all sorts of stuff is failing when things are getting launched, but the tests are not noticing that. That's ok right now, but it could lead to missing regressions. > Also, the changes I'm making for WFCORE-102 mean these problems will no longer go unnoticed and the tests will fail. > I plan to: > 1) Shifts tests to using --admin-only in cases where the tests are clearly not testing anything related to runtime execution; i.e. they are just testing model. > 2) For OperationSequencesTestCase and OperationsTestCase, where there is some validation of runtime behavior going on (explicit in some places; in others perhaps expected, perhaps not) I'm going to switch the tests to a more focused config file that: > a) Only uses local caches, to avoid pulling in requirements for jgroups things that are not present. (I see no indication any of the tests are testing anything not present with local caches.) > b) Uses start="LAZY". This means services will get registered, but not started. Not starting avoids detection of various missing dependencies, including a ModuleLoader dependency that I can't figure out how to satisfy. > The tests can't be trying to validate any behavior when services start, because they've never been able to start. So LAZY is fine. Some tests do seem to be looking for problem related to service conflicts as resources are added/removed. These tests are still valid, because service conflicts happen as soon as services are installed, whether or not the services need to start. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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