March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3923) Option for suppressing thread interruption during JDBC driver operations

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-3923?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-3923: ----------------------------------- /cc [~lbarreiro] > Option for suppressing thread interruption during JDBC driver operations > ------------------------------------------------------------------------ > > Key: WFLY-3923 > URL: https://issues.jboss.org/browse/WFLY-3923 > Project: WildFly > Issue Type: Enhancement > Components: JCA > Reporter: David Lloyd > Assignee: Jesper Pedersen > > The data source and JCA subsystems should provide a facility to suppress thread interruption during driver operations. The data source attribute should have values "on", "off", and "auto", where "auto" indicates that the subsystem should make a decision based on the driver. > A list of drivers which are known to fail in the presence of interruption is forthcoming. > A facility in JBoss Threads to suppress interruption for the duration of a task is forthcoming. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2423) Elytron resources runtime updates without reload

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2423?page=com.atlassian.jira.plugi... ] Jan Kalina commented on WFCORE-2423: ------------------------------------ [~treblereel] as this start to be related to customer issue WFLY-9917, is this in progress, or should be unassigned? > Elytron resources runtime updates without reload > ------------------------------------------------ > > Key: WFCORE-2423 > URL: https://issues.jboss.org/browse/WFCORE-2423 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta7 > Reporter: Martin Choma > Assignee: Dmitrii Tikhomirov > > When updating elytron resources, server ends up in {{reload-required}} state. For example > {code} > [standalone@localhost:9990 /] /subsystem=elytron/kerberos-security-factory=krbSF:write-attribute(name=debug, value=true) > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {code} > Make it possible for all (most - some may be impossible) resources to support runtime updates. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4522) Add 'com/sun/org/apache/xml/internal/security'++ to 'sun.jdk' module

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-4522?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-4522: ----------------------------------- Is this still needed/desired? It's a bit hacky so I'd rather solve the problem some other way if possible. [~asoldano] is this something that CXF covers now? > Add 'com/sun/org/apache/xml/internal/security'++ to 'sun.jdk' module > -------------------------------------------------------------------- > > Key: WFLY-4522 > URL: https://issues.jboss.org/browse/WFLY-4522 > Project: WildFly > Issue Type: Task > Components: Class Loading, Web Services > Affects Versions: 9.0.0.Beta2 > Reporter: Edvin Syse > Assignee: David Lloyd > > The following paths are needed for xws-security: > com/sun/org/apache/xml/internal/security > com/sun/org/apache/xml/internal/security/exceptions > com/sun/org/apache/xerces/internal/jaxp -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-865) Setting transaction timeout on UserTransaction leaks to the thread and doesn't get cleared

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-865?page=com.atlassian.jira.plugin.s... ] David Lloyd resolved WFLY-865. ------------------------------ Fix Version/s: 11.0.0.Final Resolution: Done > Setting transaction timeout on UserTransaction leaks to the thread and doesn't get cleared > ------------------------------------------------------------------------------------------ > > Key: WFLY-865 > URL: https://issues.jboss.org/browse/WFLY-865 > Project: WildFly > Issue Type: Bug > Components: EE > Reporter: jaikiran pai > Assignee: David Lloyd > Fix For: 11.0.0.Final > > > A user has reported (with an example) that setting a transaction timeout on the UserTransaction will leak the timeout onto the thread and subsequent transaction creation on that thread uses the leaked value instead of new values. > More details in the referenced forum thread. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4257) EJB: Modify service granularity

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-4257?page=com.atlassian.jira.plugin.... ] David Lloyd reassigned WFLY-4257: --------------------------------- Assignee: Flavia Rainone > EJB: Modify service granularity > ------------------------------- > > Key: WFLY-4257 > URL: https://issues.jboss.org/browse/WFLY-4257 > Project: WildFly > Issue Type: Task > Components: EE, EJB > Reporter: David Lloyd > Assignee: Flavia Rainone > > This actually applies to components in general. > The granularity of EJB services is more fine-grained than is necessary. There is essentially a lock-step startup requirement within an application module no matter what, so it doesn't make sense to have services for every EJB; instead there could be one all-EJBs service chain, with aliases to satisfy external dependencies if needed, and that one service chain could internally perform all startup tasks concurrently. This should be much more scalable since the dependency graph of many-EJB deployments currently has a substantial overhead. It may also facilitate simpler embeddability. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-517) Update schema at web url: http://www.jboss.org/schema/jbossas

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-517?page=com.atlassian.jira.plugin... ] David Lloyd reassigned WFCORE-517: ---------------------------------- Assignee: (was: David Lloyd) > Update schema at web url: http://www.jboss.org/schema/jbossas > -------------------------------------------------------------- > > Key: WFCORE-517 > URL: https://issues.jboss.org/browse/WFCORE-517 > Project: WildFly Core > Issue Type: Sub-task > Components: Modules > Reporter: Rob Stryker > > If the primary jira and PR are accepted, the web url must be updated with the more up-to-date schema file. > https://issues.jboss.org/browse/WFCORE-516 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4244) Naming alias to datasource in deployment

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-4244?page=com.atlassian.jira.plugin.... ] David Lloyd reassigned WFLY-4244: --------------------------------- Assignee: (was: David Lloyd) > Naming alias to datasource in deployment > ---------------------------------------- > > Key: WFLY-4244 > URL: https://issues.jboss.org/browse/WFLY-4244 > Project: WildFly > Issue Type: Bug > Components: Naming > Affects Versions: 8.2.0.Final > Reporter: Frank Denninger > Priority: Minor > > Using a name alias to a datasource that is defined in the deployment (with a *-ds.xml in the .war) causes a npe when jpa tries to resolve that datasource with the alias. > <lookup name="java:/de/datasource/sub" lookup="java:/de/datasource/main"/> > When both the datasource and name-alias are defined in the standalone.xml it works as expected. > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-380) Namespace error in jboss-web_8_0.xsd

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/JBMETA-380?page=com.atlassian.jira.plugin... ] David Lloyd reassigned JBMETA-380: ---------------------------------- Assignee: (was: David Lloyd) > Namespace error in jboss-web_8_0.xsd > ------------------------------------ > > Key: JBMETA-380 > URL: https://issues.jboss.org/browse/JBMETA-380 > Project: JBoss Metadata > Issue Type: Bug > Components: web > Affects Versions: 8.0.0.Final > Reporter: Paul Benedict > Priority: Minor > Labels: xsd > > I think there's an error in this XSD which prevents me from using the "javaee" elements you intend to import. > First, the "javaee" namespace is declared as {{http://xmlns.jcp.org/xml/ns/javaee}} in the XML header, but then (surprisingly) the <xsd:import> uses another namepace: > {code} > <xsd:import namespace="http://java.sun.com/xml/ns/javaee" schemaLocation="web-app_3_1.xsd"/> > {code} > I'm fairly confident this is wrong. It's importing under the old Java EE namespace -- not the new one which the header correctly declares. Hence, consumers are unable to get the "javaee" elements. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9917) renewal of server certificate for Undertow without restarting server

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-9917?page=com.atlassian.jira.plugin.... ] Jan Kalina commented on WFLY-9917: ---------------------------------- Nothing like ssl-context reloading is needed - what is actually missing is support of runtime changes of *key-manager/key-store* attributes without AS restart. This should be ensured by using {{allow-resource-service-restart=true}} after the attribute-writing command, but this is not supported by all resources in elytron yet - this is covered by WFCORE-2423/WFCORE-1953. > renewal of server certificate for Undertow without restarting server > -------------------------------------------------------------------- > > Key: WFLY-9917 > URL: https://issues.jboss.org/browse/WFLY-9917 > Project: WildFly > Issue Type: Feature Request > Components: Security > Affects Versions: 11.0.0.Final > Reporter: Hisanobu Okuda > Assignee: Darran Lofthouse > > It is convenient that a server certificate for https interface can be renewed without restarting a server. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-956) deploy hangs if module import doesn't exist

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-956?page=com.atlassian.jira.plugin.s... ] David Lloyd resolved WFLY-956. ------------------------------ Resolution: Done I think this is fixed. > deploy hangs if module import doesn't exist > ------------------------------------------- > > Key: WFLY-956 > URL: https://issues.jboss.org/browse/WFLY-956 > Project: WildFly > Issue Type: Bug > Components: Class Loading > Reporter: Bill Burke > Assignee: David Lloyd > > If you have a module dependency and that module has its own dependency that doesn't exist, deployment will hang. > To reproduce, create a simple WAR that has a jboss-deployment-structure.xml that imports an existing module. Have that existing module import a different module that doesn't exist. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 March 2018