April 2018 - jboss-jira - Jboss List Archives

[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: -------------------------------------- [~emmartins] Do you know what the status of this in wildfly 12 is? Can I use @Injected JMSContexts in CDI event observers? > 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: JMS, Naming > Affects Versions: 10.1.0.Final, 11.0.0.Final > Environment: Running on Windows 10, Java 64-bit 1.8.0_131 > Reporter: Scott Van Wart > Assignee: Eduardo Martins > 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.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10094) [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFLY-10094?page=com.atlassian.jira.plugin... ] Clebert Suconic commented on WFLY-10094: ---------------------------------------- We need to compile the library with RHEL6 and update it upstream. Do you have an environment where you can compile it.. and send a PR for the RHEL6 compilation upstream? > [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64 > ----------------------------------------------------------------- > > Key: WFLY-10094 > URL: https://issues.jboss.org/browse/WFLY-10094 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Priority: Blocker > Labels: activemq, feature-branch-blocker > > LibAIO does not get loaded on RHEL 6 x86_64: > {code} > [hudson@rhel6-large-2723 bin]$ sh standalone.sh -c standalone-full-ha.xml -Djboss.socket.binding.port-offset=1000 > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /tmp/jboss-eap > JAVA: java > JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > ... > 10:14:31,918 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. > 10:14:32,017 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=true,journalDirectory=/tmp/jboss-eap/standalone/data/activemq/journal,bindingsDirectory=/tmp/jboss-eap/standalone/data/activemq/bindings,largeMessagesDirectory=/tmp/jboss-eap/standalone/data/activemq/largemessages,pagingDirectory=/tmp/jboss-eap/standalone/data/activemq/paging) > 10:14:32,110 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221013: Using NIO Journal > ... > {code} > libAIO in artemis journal module from WF branch. Not from Artemis 2.5.0.Final tag. > Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a) > Artemis: upstreadm master (577b62d5210cdcc0f86ab9bb1b24e944c877dfe7) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3666) Provide Elytron alternative to RoleMappingLoginModule

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3666?page=com.atlassian.jira.plugi... ] Martin Choma commented on WFCORE-3666: -------------------------------------- [~msvehla] Can you create EAP7 issue as we have Dev/QE/GSS agreement? > Provide Elytron alternative to RoleMappingLoginModule > ----------------------------------------------------- > > Key: WFCORE-3666 > URL: https://issues.jboss.org/browse/WFCORE-3666 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Affects Versions: 4.0.0.Final > Reporter: Martin Choma > > In picketbox there is RoleMappingLoginModule [1], which takes role as returned from authorization process and maps to different role. I thought something similar should be configurable with some of Elytron role-mappers. But looking into model/code, it is not obvious to me which of them can be used. I know custom role mapper can be still used, but I wonder if we really do not provide this common funcionality out of the box with Elytron. > Another workaround is to use direct roles from realm (e.g. LDAP ) in target (e.g. web.xml). But seems users tend to map IDM Roles to applicaiton roles. > [1] https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-148) Create Sikuli server environment on selenium server

by Jeeva Kandasamy (JIRA)

[ https://issues.jboss.org/browse/SWSQE-148?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy resolved SWSQE-148. ----------------------------------- Resolution: Done https://github.com/jkandasa/sekuli > Create Sikuli server environment on selenium server > --------------------------------------------------- > > Key: SWSQE-148 > URL: https://issues.jboss.org/browse/SWSQE-148 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > For this task, we have to add Sikuli supported libraries on selenium docker -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-147) Add selenium-sikuli support for Python

by Jeeva Kandasamy (JIRA)

[ https://issues.jboss.org/browse/SWSQE-147?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy resolved SWSQE-147. ----------------------------------- Resolution: Done https://github.com/jkandasa/sekuli > Add selenium-sikuli support for Python > -------------------------------------- > > Key: SWSQE-147 > URL: https://issues.jboss.org/browse/SWSQE-147 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > Currently, we do not have any option(AFAIK) any option to run Sikuli on a remote machine. But we have Java option. We have to implement REST API support on Java side(selenium side) to run Sikuli. When we call via REST we can add any type of client. > Here we have three type of work, > 1. Create Sikuli environment on the remote machine > 2. Add REST API for Sikuli on the server side(Java implementation) > 3. Add REST Client to communicate with Sikuli service on remote machine -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-169) Restructure Python automation framework - it is fetching data very slowly

by Jeeva Kandasamy (JIRA)

[ https://issues.jboss.org/browse/SWSQE-169?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy reassigned SWSQE-169: ------------------------------------- Assignee: Jeeva Kandasamy (was: Michael Foley) > Restructure Python automation framework - it is fetching data very slowly > ------------------------------------------------------------------------- > > Key: SWSQE-169 > URL: https://issues.jboss.org/browse/SWSQE-169 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > https://github.com/Kiali-QE/kiali-qe-python fetching data from slowly and needs some improvements in the overall structure. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-191) Add Sekuli into Zalenium

by Jeeva Kandasamy (JIRA)

Jeeva Kandasamy created SWSQE-191: ------------------------------------- Summary: Add Sekuli into Zalenium Key: SWSQE-191 URL: https://issues.jboss.org/browse/SWSQE-191 Project: Kiali QE Issue Type: QE Task Reporter: Jeeva Kandasamy Assignee: Michael Foley https://github.com/jkandasa/sekuli -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-150) Python remote Sikuli client

by Jeeva Kandasamy (JIRA)

[ https://issues.jboss.org/browse/SWSQE-150?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy resolved SWSQE-150. ----------------------------------- Resolution: Done https://github.com/jkandasa/sekuli/tree/master/sekuli_python > Python remote Sikuli client > --------------------------- > > Key: SWSQE-150 > URL: https://issues.jboss.org/browse/SWSQE-150 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > Create Python client library to run Sikuli actions from remote via Selenium grid/node -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-149) Add Java REST API server code for selenium-Sikuli environment

by Jeeva Kandasamy (JIRA)

[ https://issues.jboss.org/browse/SWSQE-149?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy resolved SWSQE-149. ----------------------------------- Resolution: Done https://github.com/jkandasa/sekuli > Add Java REST API server code for selenium-Sikuli environment > ------------------------------------------------------------- > > Key: SWSQE-149 > URL: https://issues.jboss.org/browse/SWSQE-149 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > In this task, have to add the following code, > * Sikuli node code for selenium node > * Selenium grid code for Sikuli > * REST API to trigger sikuli actions on remote -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-190) Add a filter to remove some jobs - Push Jenkins console log

by Jeeva Kandasamy (JIRA)

[ https://issues.jboss.org/browse/SWSQE-190?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy updated SWSQE-190: ---------------------------------- Summary: Add a filter to remove some jobs - Push Jenkins console log (was: Add a filter to remove some jobs) > Add a filter to remove some jobs - Push Jenkins console log > ----------------------------------------------------------- > > Key: SWSQE-190 > URL: https://issues.jboss.org/browse/SWSQE-190 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > For now, there is no filter to skip posting some of the jobs. We need to add some of type filter to skip posting some jobs status on PR comment. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 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 April 2018