December 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-544) Automate - Service's DR tab 'Status' field

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-544: ------------------------------------ Summary: Automate - Service's DR tab 'Status' field Key: SWSQE-544 URL: https://issues.jboss.org/browse/SWSQE-544 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan Assignee: Michael Foley -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11257) Validate requirement for modules previously exported by javax.ejb.api on org.jboss.as.jsr77

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFLY-11257?page=com.atlassian.jira.plugin... ] Yeray Borges updated WFLY-11257: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/11787 > Validate requirement for modules previously exported by javax.ejb.api on org.jboss.as.jsr77 > ------------------------------------------------------------------------------------------- > > Key: WFLY-11257 > URL: https://issues.jboss.org/browse/WFLY-11257 > Project: WildFly > Issue Type: Sub-task > Components: Server > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Major > Fix For: 15.0.0.Beta1, 15.0.0.Final > > > Validate the need of these module dependencies in org.jboss.as.jsr77 module: > {code:xml} > <module name="javax.transaction.api"/> > <module name="javax.xml.rpc.api"/> > <module name="javax.rmi.api"/> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-543) Optimize test_istio_objects_crud.py

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-543?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-543. ---------------------------------- Resolution: Done PR merged: https://github.com/Kiali-QE/kiali-qe-python/pull/118 ~1 min optimization > Optimize test_istio_objects_crud.py > ----------------------------------- > > Key: SWSQE-543 > URL: https://issues.jboss.org/browse/SWSQE-543 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11143) Message sent to JMSReplyTo from old client does not find correct binding

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-11143?page=com.atlassian.jira.plugin... ] Miroslav Novak commented on WFLY-11143: --------------------------------------- [~ehugonnet] Did all the fixes for JBEAP-15889 get to Wildfly 15 or it will be fixed in Wildfly16? > Message sent to JMSReplyTo from old client does not find correct binding > ------------------------------------------------------------------------ > > Key: WFLY-11143 > URL: https://issues.jboss.org/browse/WFLY-11143 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.0.Final > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > Fix For: 16.0.0.Beta1 > > > There is regression in backward compatibility of messaging client. JMSReplyTo destination set by older client contains incorrect address which causes that reply message does not have correct binding and such message is lost. > Impact: Applications will stop work after upgrade to WF14/EAP 7.2.0.CD14. > Test Scenario: > * Start EAP 7.2.0.CD14/WF14 server (Artemis 2.x) with deployed InQueue and OutQueue > * Send message to InQueue from older EAP 7.2.0.CD13/WF13/Artemis 1.5.5 client to InQueue. Message has JMSReplyTo header set to OutQueue. Client got "OutQueue" queue from JNDI lookup from EAP7.2.0.CD14/WF14 > * Deploy MDB to server > ** MDB consumes message from InQueue and sends new message to destination defined in JMSReplyTo header (so to OutQueue) > * Receive message from OutQueue > Result: > No message is received from OutQueue. There is debug message in server log: > {code} > 11:36:09,565 DEBUG [org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl] (Thread-25 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@22848193)) Message CoreMessage[m > essageID=214,durable=true,userID=c0de8bd0-cba6-11e8-840f-f496342f6705,priority=4, timestamp=Tue Oct 09 11:36:09 CEST 2018,expiration=0, durable=true, address=jms.queue.OutQueue,size=580,properties=TypedPropertie > s[inMessageId=ID:c0383a39-cba6-11e8-95ad-f496342f6705,__AMQ_CID=c0d9349a-cba6-11e8-840f-f496342f6705,_AMQ_DUPL_ID=90d1e80e-116d-4eef-9513-84c6085549db,_AMQ_ROUTING_TYPE=0]]@1680840457 is not going anywhere as it > didn't have a binding on address:jms.queue.OutQueue > {code} > which indicates that jms.queue.OutQueue address does not have a binding. > The same happesn if older EAP/WF server (with Artemis 1.5.5x) is used and new EAP 7.2.0.CD14/WF14(Artemis 2.x) client is used. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3425) Unexpected behavior of docks when multiple editors are opened

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3425?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3425: --------------------------------- Story Points: 5 > Unexpected behavior of docks when multiple editors are opened > ------------------------------------------------------------- > > Key: DROOLS-3425 > URL: https://issues.jboss.org/browse/DROOLS-3425 > Project: Drools > Issue Type: Bug > Components: DMN Editor, Scenario Simulation and Testing, Stunner > Reporter: Klara Kufova > Assignee: Toni Rikkola > Priority: Critical > Labels: ScenarioSimulation, drools-tools > Attachments: screencast-11-12-18.webm, screencast-12-12-18.webm > > > When multiple assets are opened in different editors, their docks incorrectly interfere. After opening two assets in a row, the Business Central freezes with an unexpected error. Closing one asset causes unexpected disappearance of the left panel. > See the attached screencast for detailed information. After the assets are opened for the first time, everything seems correct. Once the {{.dmn}} file is opened for the second time, the issues start to occur. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11475) Counter - registry.counter(metadata)- IllegalArgumentException

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-11475?page=com.atlassian.jira.plugin... ] Bartosz Baranowski updated WFLY-11475: -------------------------------------- Workaround Description: Us Metadata constructor that will set "reusable" flag: https://github.com/eclipse/microprofile-metrics/blob/branch-1.1/api/src/m... (was: Us Metadata constructor that will set "reusable" flag.) > Counter - registry.counter(metadata)- IllegalArgumentException > -------------------------------------------------------------- > > Key: WFLY-11475 > URL: https://issues.jboss.org/browse/WFLY-11475 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Affects Versions: 15.0.0.Final > Reporter: Rostislav Svoboda > Assignee: Bartosz Baranowski > Priority: Critical > > Counter - registry.counter(metadata) returns IllegalArgumentException on second invocation of the endpoint. The same app works fine on Open Liberty. > JavaDoc for counter(Metadata metadata) says @return a new or pre-existing @link Counter. > Second invocation should return the pre-existing counter. > https://github.com/smallrye/smallrye-metrics/issues/43 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3361) Update simulation model to support multiple types (DMO, DMN)

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3361?page=com.atlassian.jira.plugi... ] Gabriele Cardosi closed DROOLS-3361. ------------------------------------ > Update simulation model to support multiple types (DMO, DMN) > ------------------------------------------------------------ > > Key: DROOLS-3361 > URL: https://issues.jboss.org/browse/DROOLS-3361 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > > Update simulation model to support multiple types (DMO, DMN). > Specs: > - DMO: Save name of the session to use > - DMN: Save path to the DMN file -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11475) Counter - registry.counter(metadata)- IllegalArgumentException

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-11475?page=com.atlassian.jira.plugin... ] Bartosz Baranowski updated WFLY-11475: -------------------------------------- Workaround Description: Us Metadata constructor that will set "reusable" flag. > Counter - registry.counter(metadata)- IllegalArgumentException > -------------------------------------------------------------- > > Key: WFLY-11475 > URL: https://issues.jboss.org/browse/WFLY-11475 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Affects Versions: 15.0.0.Final > Reporter: Rostislav Svoboda > Assignee: Bartosz Baranowski > Priority: Critical > > Counter - registry.counter(metadata) returns IllegalArgumentException on second invocation of the endpoint. The same app works fine on Open Liberty. > JavaDoc for counter(Metadata metadata) says @return a new or pre-existing @link Counter. > Second invocation should return the pre-existing counter. > https://github.com/smallrye/smallrye-metrics/issues/43 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11475) Counter - registry.counter(metadata)- IllegalArgumentException

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-11475?page=com.atlassian.jira.plugin... ] Bartosz Baranowski commented on WFLY-11475: ------------------------------------------- https://github.com/smallrye/smallrye-metrics/issues/43#issuecomment-44652... > Counter - registry.counter(metadata)- IllegalArgumentException > -------------------------------------------------------------- > > Key: WFLY-11475 > URL: https://issues.jboss.org/browse/WFLY-11475 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Affects Versions: 15.0.0.Final > Reporter: Rostislav Svoboda > Assignee: Bartosz Baranowski > Priority: Critical > > Counter - registry.counter(metadata) returns IllegalArgumentException on second invocation of the endpoint. The same app works fine on Open Liberty. > JavaDoc for counter(Metadata metadata) says @return a new or pre-existing @link Counter. > Second invocation should return the pre-existing counter. > https://github.com/smallrye/smallrye-metrics/issues/43 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6644) Provide container managed sign on in configuration of pooled-connection-factory

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFLY-6644?page=com.atlassian.jira.plugin.... ] Miroslav Novak updated WFLY-6644: --------------------------------- Affects Version/s: 15.0.0.Final 14.0.0.Final > Provide container managed sign on in configuration of pooled-connection-factory > ------------------------------------------------------------------------------- > > Key: WFLY-6644 > URL: https://issues.jboss.org/browse/WFLY-6644 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Final, 14.0.0.Final, 15.0.0.Final > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Priority: Major > > Currently it's not possible to configure container managed sign-on for Artemis RA in <pooled-connection-factory> in messaging-activemq subsystem. This will allow to provide authentication information when new connection to Artemis broker is created without specifying username and password when calling connectionFactory.createConnection(). > Such security-domain could look like: > {code}<security-domain name="CrashRecoveryDomain0"> > <authentication> > <login-module code="ConfiguredIdentity" flag="required"> > <module-option name="principal" value="crash0"/> > <module-option name="password" value="crash0"/> > <module-option name="password-stacking" value="useFirstPass"/> > <module-option name="userName" value="crash0"/> > </login-module> > </authentication> > </security-domain>{code} > The main benefit is that username and password can be omitted when creating new connection and does not have to be hard cored in EJB/Servlet. This could be used for inbound connections as well. We should allow to specify default-principal-name which would be used for authentication. There is more info about this approach in WebLogic documentatin [1]. > [1] https://docs.oracle.com/cd/E13222_01/wls/docs92/resadapter/security.html -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 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 December 2018