January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6021) Default transaction timeout is not applied for EJB bean when set for second time

by Fedor Gavrilov (JIRA)

[ https://issues.jboss.org/browse/WFLY-6021?page=com.atlassian.jira.plugin.... ] Fedor Gavrilov reassigned WFLY-6021: ------------------------------------ Assignee: Fedor Gavrilov (was: David Lloyd) > Default transaction timeout is not applied for EJB bean when set for second time > -------------------------------------------------------------------------------- > > Key: WFLY-6021 > URL: https://issues.jboss.org/browse/WFLY-6021 > Project: WildFly > Issue Type: Bug > Components: EJB, Transactions > Reporter: Ondřej Chaloupka > Assignee: Fedor Gavrilov > > It seems that transaction subsystem attribute {{default-timeout}} does not have any effect for EJB if it's redefined. It means if I set the default transaction timeout in transaction subystem for second (and next) time it's not applied for EJB beans. It's used the firstly set value. > The transaction timeout is not changed for EJB when server is reloaded. When server is restarted it refreshes all settings and EJB starts using the expected value for timeout settings. > If the value is read from subsystem > {{/subsystem=transactions:read-attribute(name=default-timeout)}} > it shows correct value (that one set for second time). But EJB seems not applying it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1008) KieServer to update container for SNAPSHOT kjar

by Andrew Collins (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1008?page=com.atlassian.jira.plugi... ] Andrew Collins updated DROOLS-1008: ----------------------------------- Description: Description of problem: When a kjar is a snapshot version, kie-server will not react to new snapshot versions deployed to a remote artifact repository. The remote artifact repository is only queried the first time after JVM startup. Retrieving a new snapshot version is only possible through use of KieScanner.scanNow(), which will both fetch the new artifact from the remote repository, and reload the kmodule in the KieServer JVM. was:When a kjar is a snapshot version, kie-server will not react to new snapshot versions deployed to a remote artifact repository. The remote artifact repository is only queried the first time after JVM startup. Updating a KieContainer to a newer snapshot version is only possible through use of the KieScanner, which will both fetch the new artifact from the remote repository, and reload the kmodule in the KieServer JVM. > KieServer to update container for SNAPSHOT kjar > ----------------------------------------------- > > Key: DROOLS-1008 > URL: https://issues.jboss.org/browse/DROOLS-1008 > Project: Drools > Issue Type: Feature Request > Components: kie server > Affects Versions: 6.2.0.Final, 6.3.0.Final > Reporter: Andrew Collins > Assignee: Mario Fusco > Attachments: snapshot_kjar_reproducer.patch > > > Description of problem: > When a kjar is a snapshot version, kie-server will not react to new snapshot versions deployed to a remote artifact repository. The remote artifact repository is only queried the first time after JVM startup. Retrieving a new snapshot version is only possible through use of KieScanner.scanNow(), which will both fetch the new artifact from the remote repository, and reload the kmodule in the KieServer JVM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-13) Interoperability testing with KeyCloak

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-13?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse reassigned ELY-13: ----------------------------------- Assignee: Pedro Igor > Interoperability testing with KeyCloak > -------------------------------------- > > Key: ELY-13 > URL: https://issues.jboss.org/browse/ELY-13 > Project: WildFly Elytron > Issue Type: Sub-task > Reporter: Darran Lofthouse > Assignee: Pedro Igor > Fix For: 1.1.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-19) Add KeyCloak based realm implementation.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-19?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse reassigned ELY-19: ----------------------------------- Assignee: Pedro Igor > Add KeyCloak based realm implementation. > ---------------------------------------- > > Key: ELY-19 > URL: https://issues.jboss.org/browse/ELY-19 > Project: WildFly Elytron > Issue Type: Sub-task > Reporter: Darran Lofthouse > Assignee: Pedro Igor > Fix For: 1.1.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-368) Add optional Supplier<Provider[]> to realm implementations

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-368?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-368: --------------------------------- Fix Version/s: 1.1.0.Beta5 > Add optional Supplier<Provider[]> to realm implementations > ---------------------------------------------------------- > > Key: ELY-368 > URL: https://issues.jboss.org/browse/ELY-368 > Project: WildFly Elytron > Issue Type: Enhancement > Reporter: David Lloyd > Fix For: 1.1.0.Beta5 > > > Realms use key factories, certificate factories, password factories, etc. Most of the time they just use the default installed providers. Enhance the realms to accept an optional {{Supplier<Provider[]>}} which will be used to load these kinds of things. The default supplier should be {{Security::getProviders()}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6076) CLI deployment of WAR exploded JSF2.2 applications fails with exceptions

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-6076?page=com.atlassian.jira.plugin.... ] Farah Juma commented on WFLY-6076: ---------------------------------- Do you have a simple reproducer app you can share? > CLI deployment of WAR exploded JSF2.2 applications fails with exceptions > ------------------------------------------------------------------------ > > Key: WFLY-6076 > URL: https://issues.jboss.org/browse/WFLY-6076 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 10.0.0.CR5 > Reporter: Miroslav Pavleski > Assignee: Farah Juma > Attachments: cli.log, console.log > > > In 9.0.2 FINAL and prior (8.1, 8.2) deploying an exploded WAR using the CLI was working fine. This kind of deployment has benefits during development as the static resources are updated on-save. > The problem occurs probably due JSF initialization, see the attachments. > Deployment using mvn wildfly:deploy works fine. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-107) Add ability for security domains to create SSLContext directly from config

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-107?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-107: -------------------------------------- Probably also worth considering the reference to the security domain could be optional - this way we get the same capability to return the SSLContext instances but where no trust decisions are being made we don't need it backed by a security domain. > Add ability for security domains to create SSLContext directly from config > -------------------------------------------------------------------------- > > Key: ELY-107 > URL: https://issues.jboss.org/browse/ELY-107 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: David Lloyd > Assignee: Darran Lofthouse > Labels: elytron_ssl > Fix For: 1.1.0.Beta4 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-107) Add ability for security domains to create SSLContext directly from config

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-107?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-107: -------------------------------------- I think this is actually likely to sit in a similar position to the HTTP and SASL 'AuthenticationFactory' objects - i.e. some form of policy object that will reference a security domain but will also reference other relevant capabilities to fully assemble the SSLContext. Being a policy object it will also be able to hold things such as protocol and cipher suite rules. > Add ability for security domains to create SSLContext directly from config > -------------------------------------------------------------------------- > > Key: ELY-107 > URL: https://issues.jboss.org/browse/ELY-107 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: David Lloyd > Assignee: Darran Lofthouse > Labels: elytron_ssl > Fix For: 1.1.0.Beta4 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6081) Undertow migration operation doesn't migrate Access log valves

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFLY-6081?page=com.atlassian.jira.plugin.... ] ehsavoie Hugonnet updated WFLY-6081: ------------------------------------ Summary: Undertow migration operation doesn't migrate Access log valves (was: [Migration][WebToUndertow] Access log valves are not automaticaly migrated) > Undertow migration operation doesn't migrate Access log valves > -------------------------------------------------------------- > > Key: WFLY-6081 > URL: https://issues.jboss.org/browse/WFLY-6081 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.CR5 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > Access log valves are not automatically migrated, it should be either printed warning for them to be migrated automatically or migrated automatically. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-107) Add ability for security domains to create SSLContext directly from config

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-107?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-107: --------------------------------- Labels: elytron_ssl (was: ) > Add ability for security domains to create SSLContext directly from config > -------------------------------------------------------------------------- > > Key: ELY-107 > URL: https://issues.jboss.org/browse/ELY-107 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: David Lloyd > Assignee: Darran Lofthouse > Labels: elytron_ssl > Fix For: 1.1.0.Beta4 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 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 January 2016