February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4345) Upgrade WildFly Elytron Tool to 1.6.0.Final

by Farah Juma (Jira)

Farah Juma created WFCORE-4345: ---------------------------------- Summary: Upgrade WildFly Elytron Tool to 1.6.0.Final Key: WFCORE-4345 URL: https://issues.jboss.org/browse/WFCORE-4345 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4344) Upgrade Elytron Web to 1.4.0.Final

by Farah Juma (Jira)

Farah Juma created WFCORE-4344: ---------------------------------- Summary: Upgrade Elytron Web to 1.4.0.Final Key: WFCORE-4344 URL: https://issues.jboss.org/browse/WFCORE-4344 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4343) Upgrade WildFly Elytron to 1.8.0.Final

by Farah Juma (Jira)

Farah Juma created WFCORE-4343: ---------------------------------- Summary: Upgrade WildFly Elytron to 1.8.0.Final Key: WFCORE-4343 URL: https://issues.jboss.org/browse/WFCORE-4343 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3567) Import tab, with cards.

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3567?page=com.atlassian.jira.plugi... ] Guilherme Carreiro commented on DROOLS-3567: -------------------------------------------- [~uxdlc] [~stetson.robinson], I would use something similar to what we have on Data Types: Current Data Types empty state: {quote}*No custom data types have been defined*. There are currently no custom data types available for you to view or edit. To get started, add a custom data type.{quote} Here's my proposal for the Included models tab: {quote}*No DMN models have been inclued*. There are currently no DMN models included. To get started, click on "Include model".{quote} > Import tab, with cards. > ----------------------- > > Key: DROOLS-3567 > URL: https://issues.jboss.org/browse/DROOLS-3567 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UXTeam, drools-tools > Attachments: 3.png, Import-tab.pdf > > > Detail Import design as presented in: https://issues.jboss.org/browse/DROOLS-2999 > Specify any details not already covered by the patternfly card pattern: https://www.patternfly.org/pattern-library/content-views/card-view/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3567) Import tab, with cards.

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3567?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3567: ------------------------------------- [~stetson.robinson] We're planning to use the PF "empty state" pattern when are no imported items/cards to show. https://www.patternfly.org/pattern-library/communication/empty-state/ Would you be able to provide a text intro for [~karreiro] to add? > Import tab, with cards. > ----------------------- > > Key: DROOLS-3567 > URL: https://issues.jboss.org/browse/DROOLS-3567 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UXTeam, drools-tools > Attachments: 3.png, Import-tab.pdf > > > Detail Import design as presented in: https://issues.jboss.org/browse/DROOLS-2999 > Specify any details not already covered by the patternfly card pattern: https://www.patternfly.org/pattern-library/content-views/card-view/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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: -------------------------------------- I've definitely seen issues (especially at deployment time) with injecting TransactionSynchronizationRegistry as [~clerum] describes. The injected JMSContext was simply the easiest to reproduce. I've also had issues with submitting tasks to ManagedExecutorService within @Observes @Initialized or @PostConstruct-annotated bean methods. Sometimes the bean initializers are called before the executor service is ready. The workaround there was to use ManagedScheduledExecutorService and submit a recurring task that cancels itself when it first (successfully) runs. I'm just wondering if that's related, especially since [~clerum] mentioned the ManagedExecutorService. Alas I haven't been able to reproduce that issue reliably enough to submit a report about it. > 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)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4342) Bump the Elytron subsystem version.

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4342?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-4342: ------------------------------------- Fix Version/s: 9.0.0.Beta1 (was: 8.0.0.Beta6) > Bump the Elytron subsystem version. > ----------------------------------- > > Key: WFCORE-4342 > URL: https://issues.jboss.org/browse/WFCORE-4342 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 9.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

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

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-9529?page=com.atlassian.jira.plugin.... ] Eduardo Martins commented on WFLY-9529: --------------------------------------- Hi everyone, just to let you guys know that we have discussed this issue and decided to (finally) go for a fix, stay tuned. > 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)

7 years, 2 months

1
0
0 / 0

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

by Cody Lerum (Jira)

[ https://issues.jboss.org/browse/WFLY-9529?page=com.atlassian.jira.plugin.... ] Cody Lerum edited comment on WFLY-9529 at 2/20/19 12:49 PM: ------------------------------------------------------------ Just hit this again trying to use {code} @Resource private TransactionSynchronizationRegistry transactionSynchronizationRegistry; {code} >From within a CDI bean that is in a ManagedExectuorTask The MES starts creates and tears down a Request context like {code} try { context = CDI.current().select(BoundRequestContext.class).get(); context.associate(storage); context.activate(); //Do some work } finally { if (context != null) { context.invalidate(); context.deactivate(); context.dissociate(storage); } {code} Is there something special I need to do to hook the MES into the the Transaction Registry? All works fine if it isn't called from within a MES was (Author: clerum): Just hit this again trying to use {code} @Resource private TransactionSynchronizationRegistry transactionSynchronizationRegistry; {code} >From within a CDI bean that is in a ManagedExectuorTask The MES starts creates and tears down a Request context like {code} try { context = CDI.current().select(BoundRequestContext.class).get(); context.associate(storage); context.activate(); //Do some work } finally { if (context != null) { context.invalidate(); context.deactivate(); context.dissociate(storage); } {code} Is there something special I need to do to hook the MES into the the Transaction Registry? > 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)

7 years, 2 months

1
0
0 / 0

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

by Cody Lerum (Jira)

[ https://issues.jboss.org/browse/WFLY-9529?page=com.atlassian.jira.plugin.... ] Cody Lerum edited comment on WFLY-9529 at 2/20/19 12:48 PM: ------------------------------------------------------------ Just hit this again trying to use {code} @Resource private TransactionSynchronizationRegistry transactionSynchronizationRegistry; {code} >From within a CDI bean that is in a ManagedExectuorTask The MES starts creates and tears down a Request context like {code} try { context = CDI.current().select(BoundRequestContext.class).get(); context.associate(storage); context.activate(); //Do some work } finally { if (context != null) { context.invalidate(); context.deactivate(); context.dissociate(storage); } {code} Is there something special I need to do to hook the MES into the the Transaction Registry? was (Author: clerum): Just hit this again trying to use {code} @Resource private TransactionSynchronizationRegistry transactionSynchronizationRegistry; {code} >From within a CDI bean that is in a ManagedExectuorTask The MES starts creates and tears down a Request context like {code} try { context = CDI.current().select(BoundRequestContext.class).get(); context.associate(storage); context.activate(); //Do some work } finally { if (context != null) { context.invalidate(); context.deactivate(); context.dissociate(storage); } {code} Is there something special I need to do to hook the MES into the the Transaction Registry? > 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)

7 years, 2 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 February 2019