May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-709) Push Kiali-QE Builds To Quay.io

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-709?page=com.atlassian.jira.plugin.... ] Matthew Mahoney edited comment on SWSQE-709 at 5/1/19 2:11 PM: --------------------------------------------------------------- Branch with install_kiali.sh enhancments: https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-utils/tree/SWSQE-709 Kiali builds pushed to quay.io: https://quay.io/repository/kiali-qe/kiali?tab=tags Jenkins job (added param CONTAINER_STORAGE): - Looks like tag is incorrect (thus added CONTAINER_STORAGE): quay.io/docker.io/kialiqe/kiali:latestcore1040 - http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-on-Openshi... - http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Istio-and-Kiali-... was (Author: mmahoney): Branch with install_kiali.sh enhancments: https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-utils/tree/SWSQE-709 Kiali builds pushed to quay.io: https://quay.io/repository/kiali-qe/kiali?tab=tags Jenkins job (added param CONTAINER_STORAGE): - Looks like tag is incorrect (thus added CONTAINER_STORAG): quay.io/docker.io/kialiqe/kiali:latestcore1040 - http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-on-Openshi... - http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Istio-and-Kiali-... > Push Kiali-QE Builds To Quay.io > ------------------------------- > > Key: SWSQE-709 > URL: https://issues.jboss.org/browse/SWSQE-709 > Project: Kiali QE > Issue Type: Task > Reporter: Matthew Mahoney > Assignee: Matthew Mahoney > Priority: Major > Labels: infrastructure > > Push kialiqe builds to Quay.io, and not Dockerhub. > Perhaps there is an alternative internal Repo. If not Quay.io seems to be the direction the team is headed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-709) Push Kiali-QE Builds To Quay.io

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-709?page=com.atlassian.jira.plugin.... ] Matthew Mahoney edited comment on SWSQE-709 at 5/1/19 11:35 AM: ---------------------------------------------------------------- Branch with install_kiali.sh enhancments: https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-utils/tree/SWSQE-709 Kiali builds pushed to quay.io: https://quay.io/repository/kiali-qe/kiali?tab=tags Jenkins job (added param CONTAINER_STORAGE): - Looks like tag is incorrect (thus added CONTAINER_STORAG): quay.io/docker.io/kialiqe/kiali:latestcore1040 - http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-on-Openshi... - http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Istio-and-Kiali-... was (Author: mmahoney): Branch with install_kiali.sh enhancments: https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-utils/tree/SWSQE-709 Kiali builds pushed to quay.io: https://quay.io/repository/kiali-qe/kiali?tab=tags Jenkins job (added param CONTAINER_STORAGE): - Looks like tag is incorrect: quay.io/docker.io/kialiqe/kiali:latestcore1040 - http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-on-Openshi... - http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Istio-and-Kiali-... > Push Kiali-QE Builds To Quay.io > ------------------------------- > > Key: SWSQE-709 > URL: https://issues.jboss.org/browse/SWSQE-709 > Project: Kiali QE > Issue Type: Task > Reporter: Matthew Mahoney > Assignee: Matthew Mahoney > Priority: Major > Labels: infrastructure > > Push kialiqe builds to Quay.io, and not Dockerhub. > Perhaps there is an alternative internal Repo. If not Quay.io seems to be the direction the team is headed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1800) Enhanced mapping of X509Certificate to the underlying identity

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1800?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1800: ---------------------------------- Fix Version/s: 1.9.0.CR5 > Enhanced mapping of X509Certificate to the underlying identity > -------------------------------------------------------------- > > Key: ELY-1800 > URL: https://issues.jboss.org/browse/ELY-1800 > Project: WildFly Elytron > Issue Type: Feature Request > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.9.0.CR5 > > > Presently we support decoding the distinguished name however there are requests to use alternative such as the subject alternative name. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3953) DMN UX - error highlight in boxed expression.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3953?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3953: -------------------------------------- Sprint: 2019 Week 17-19 > DMN UX - error highlight in boxed expression. > --------------------------------------------- > > Key: DROOLS-3953 > URL: https://issues.jboss.org/browse/DROOLS-3953 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png > > > As user after a test run, I want see not only the cell that are not correct (red background) but also the reason. > For instance have the possibility to see the actual value that is different from the expected or the error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8217) ActiveMQ leaks connections if a JMS message is sent from an MDB

by Scott Van Wart (Jira)

[ https://issues.jboss.org/browse/WFLY-8217?page=com.atlassian.jira.plugin.... ] Scott Van Wart commented on WFLY-8217: -------------------------------------- For anyone continuing to have issues with this, it appears to be corrected in 15.x but not 14.x or 13.x. I experienced it again with the following scenario: - Thread spawned by 3rd party library calls a method on an @ApplicationScoped CDI bean. - This in turn calls a @Transactional method on another @ApplicationScoped CDI bean. - ... calls a @Transactional method on a @Dependent CDI bean. - ... calls a method on an @ApplicationScoped bean. - ... calls a method on an @Inject'ed @Stateless EJB. - The EJB uses its @Inject'ed JMSContext and calls createBytesMessage(): {noformat} 2019-05-01 14:12:06,906 INFO [org.jboss.jca.core.api.connectionmanager.ccm.CachedConnectionManager] (hz._hzInstance_1_dev.cached.thread-5) IJ000100: Closing a connection for you. Please close them yourself: org.apache.activemq.artemis.ra.ActiveMQRASession@4dc6784e: java.lang.Throwable: STACKTRACE at org.jboss.ironjacamar.impl@1.4.11.Final//org.jboss.jca.core.connectionmanager.ccm.CachedConnectionManagerImpl.registerConnection(CachedConnectionManagerImpl.java:308) at org.jboss.ironjacamar.impl@1.4.11.Final//org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:819) at org.apache.activemq.artemis.ra@2.6.3.jbossorg-001//org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.allocateConnection(ActiveMQRASessionFactoryImpl.java:872) at org.apache.activemq.artemis.ra@2.6.3.jbossorg-001//org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.createSession(ActiveMQRASessionFactoryImpl.java:531) at org.apache.activemq.artemis.ra@2.6.3.jbossorg-001//org.apache.activemq.artemis.ra.ActiveMQRASessionFactoryImpl.createSession(ActiveMQRASessionFactoryImpl.java:746) at org.apache.activemq.artemis@2.6.3.jbossorg-001//org.apache.activemq.artemis.jms.client.ActiveMQJMSContext.checkSession(ActiveMQJMSContext.java:140) at org.apache.activemq.artemis@2.6.3.jbossorg-001//org.apache.activemq.artemis.jms.client.ActiveMQJMSContext.createBytesMessage(ActiveMQJMSContext.java:242) at org.wildfly.extension.messaging-activemq//org.wildfly.extension.messaging.activemq.deployment.injection.JMSContextWrapper.createBytesMessage(JMSContextWrapper.java:122) {noformat} This was reported 3 times in a single transaction so it looks like the original problem might be related to improperly or neglecting to attach the JMS session to the current transaction. I don't see this behaviour in 15.x but I'm including all this for anyone searching for solutions to a similar problem; the marked Fixed Version says 13.x but this doesn't seem to be the case. > ActiveMQ leaks connections if a JMS message is sent from an MDB > --------------------------------------------------------------- > > Key: WFLY-8217 > URL: https://issues.jboss.org/browse/WFLY-8217 > Project: WildFly > Issue Type: Bug > Components: JMS, Transactions > Affects Versions: 10.1.0.Final > Environment: Running on Windows 10. Java(TM) SE Runtime Environment (build 1.8.0_92-b14) > Reporter: Scott Van Wart > Assignee: Emmanuel Hugonnet > Priority: Minor > Fix For: 13.0.0.Final > > Attachments: leak.zip, leak.zip, log.txt, log.txt, server.log > > > If an MDB causes a JMS message to be sent during the call to onMessage(), ActiveMQ won't close its connection. I'm using JMS2 through an @Inject'ed JMSContext. My sample project is an EAR with an EJB JAR (containing a service and an MDB) and a JAX-RS endpoint (entry point for the test). > 1) Build the EAR > 2) Run wildfly with the standalone-full.xml configuration: > {{standalone.bat --server-config=standalone-full.xml}} > 3) Enable debug and error reporting for leaked connections with ActiveMQ/CCM: > {{jboss-cli.bat -c}} > {{/subsystem=jca/cached-connection-manager=cached-connection-manager:write-attribute(name=debug,value=true)}} > {{/subsystem=jca/cached-connection-manager=cached-connection-manager:write-attribute(name=error,value=true)}} > 4) Deploy the EAR. > 5) Access http://localhost:8080/leak-web/rest/test?message=Hi > The REST endpoint will send a message to the test topic (Defined in leak-ejb/src/main/java/test/mdb/TestTopic.java). TestTopicListener (in the same package as TestTopic) will receive the message and send a second message to the topic. Upon returning from TestTopicListener.onMessage(), the message is sent, but this shows up in the logs > (see attached log.txt) > I have no idea why JIRA attached each file twice. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9529) Using injected JMS in a background task/thread leads to NameNotFoundException: java:comp/TransactionSynchronizationRegistry

by Scott Van Wart (Jira)

[ https://issues.jboss.org/browse/WFLY-9529?page=com.atlassian.jira.plugin.... ] Scott Van Wart commented on WFLY-9529: -------------------------------------- That's good to hear; thanks for the update. My connection leak issue I mentioned off-hand is much more likely to be [WFLY-8217] which seems to still be present in 13.x and 14.x but fixed in 15.x so it's not an issue. We're continuing to use an EJB wrapper for our other JMS scenarios. I do wish there could be a grand unification of of EJB/CDI/JSF in the EE spec complete with mass deprecation that would eliminate a good deal of confusion. Our explicit use of EJB is very limited though required implicitly once MDBs and executor threads are involved, even though most of our dependencies are strictly CDI. It just looks like it creates unnecessary complexity. Thanks again. > Using injected JMS in a background task/thread leads to NameNotFoundException: java:comp/TransactionSynchronizationRegistry > --------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9529 > URL: https://issues.jboss.org/browse/WFLY-9529 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, JMS, Naming > Affects Versions: 14.0.1.Final, 10.1.0.Final, 11.0.0.Final, 12.0.0.Final, 13.0.0.Final > Environment: Running on Windows 10, Java 64-bit 1.8.0_131 > Reporter: Scott Van Wart > Assignee: Eduardo Martins > Priority: Major > Labels: ActiveMQ, jms, transaction > Attachments: injected-jms.zip, injected-jms2.zip, wildfly-11-injected-jms.txt > > > If I try to use an @Injected JMSContext while executing within a background task (ManagedExecutorService) or thread (ManagedThreadFactory), I get the attached stacktrace. I've experienced this a number of times with Wildfly 10.1.0, including messages sent in Infinispan's expiry task thread. > My original workaround was to submit an additional task on a separate thread to send the message, then wait for it to complete. That seemed unreliable (sometimes it would still produce NameNotFoundException). I've resorted to creating my own JMSContext by using @Resource( lookup="java:/ConnectionFactory" ) and sending messages that way. Both workarounds prevent the message sending logic from participating in any ongoing transactions. > I'm also attaching a sample EAR project. It can be built with Maven. It creates a background task that waits 3 seconds and then tries to send a JMS message in a new transaction using an injected JMS context. I use the standalone-full.xml profile to run it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3956) Designer - Improve DMN rule task properties UX

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3956?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-3956: ------------------------------------------- [~roger.martinez] [~manstis] [~ibek] Posting a design, that seems suitable for short term needs: https://docs.google.com/document/d/15DEFyNDeSVULjlhO4RFmyjgsIDe6QH2nT11FS... Please let me know if you need me to mockup different states, or create a clic-thru version. > Designer - Improve DMN rule task properties UX > ---------------------------------------------- > > Key: DROOLS-3956 > URL: https://issues.jboss.org/browse/DROOLS-3956 > Project: Drools > Issue Type: Story > Components: Stunner > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: Stunner, UX, UXTeam, drools-tools > > Currently, the user has to know all properties from the head or find them in DMN Modeler which is too long and error-prone task. Define input fields that allow fields/properties to be pre-populated to streamline experience for the user. > Properties that need be set: > * DMN file selector: The Namespace is provided in the background. > * Decision name (optional field): Decision service, Decision, or _blank_. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-727) E2E Test Coverage

by Matthew Mahoney (Jira)

Matthew Mahoney created SWSQE-727: ------------------------------------- Summary: E2E Test Coverage Key: SWSQE-727 URL: https://issues.jboss.org/browse/SWSQE-727 Project: Kiali QE Issue Type: QE Task Reporter: Matthew Mahoney Assignee: Matthew Mahoney Generate E2E code coverage metrics. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1801) Add travis configuration to use the jboss developer repo.

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1801: ------------------------------------- Summary: Add travis configuration to use the jboss developer repo. Key: ELY-1801 URL: https://issues.jboss.org/browse/ELY-1801 Project: WildFly Elytron Issue Type: Task Components: Build Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.9.0.CR5 This is needed to ensure downloads are over https without triggering an enforcer error. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11751) Error in JBoss Management Console when clicking on the deployed subsystem jaxrs/rest-resource

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11751?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-11751: ------------------------------------ Security: (was: Red Hat Internal) > Error in JBoss Management Console when clicking on the deployed subsystem jaxrs/rest-resource > --------------------------------------------------------------------------------------------- > > Key: WFLY-11751 > URL: https://issues.jboss.org/browse/WFLY-11751 > Project: WildFly > Issue Type: Bug > Components: EJB, REST > Affects Versions: 16.0.0.Beta1 > Reporter: Pravin Barate > Assignee: Lin Gao > Priority: Major > Labels: downstream_dependency > Fix For: 17.0.0.Final > > Attachments: Screenshot from 2019-02-20 15-03-27.png, laborEAR.ear > > > Error in JBoss Management Console when clicking on the deployed subsystem jaxrs/rest-resource. > Getting below error > {noformat} > 15:02:52,134 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 8) WFLYCTL0013: Operation ("read-resource") failed - address: ([ > ("deployment" => "laborEAR.ear"), > ("subdeployment" => "labor3.jar"), > ("subsystem" => "jaxrs"), > ("rest-resource" => "com.epicdata.lmac.transactions.labor.common.ejbs.BadgeActivation") > ]) - failure description: "WFLYCTL0216: Management resource '[ > (\"deployment\" => \"laborEAR.ear\"), > (\"subdeployment\" => \"labor3.jar\"), > (\"subsystem\" => \"jaxrs\"), > (\"rest-resource\" => \"com.epicdata.lmac.transactions.labor.common.ejbs.BadgeActivation\") > ]' not found" > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2019