October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7418) Batch deployments with a large number of executed jobs can lock up or slow down the web console

by James Perkins (JIRA)

James Perkins created WFLY-7418: ----------------------------------- Summary: Batch deployments with a large number of executed jobs can lock up or slow down the web console Key: WFLY-7418 URL: https://issues.jboss.org/browse/WFLY-7418 Project: WildFly Issue Type: Enhancement Components: Batch, Web Console Reporter: James Perkins Assignee: James Perkins Batch deployments which contain a large number of executed jobs can be extremely slow to process as the {{/deployment=batch.war/subsystem=batch-jberet}} processes each job instance then each job execution of that job instance. One possibly helpful option for the web console would be to add a new description attribute to indicate the resource may be slow to process. The web console might be able to run a background task to populate data rather than locking up the UI. There would still be an issue with a large memory footprint here however. JBeret might want to consider having a way to archive jobs too rather than just purge them. Some users may want to keep all job execution data. Archiving this data could reduce the size of the current data being retrieved. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7416) Minimize usage of deprecated PropertiesAttributeDefintion#setXmlName()

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-7416: --------------------------------- Summary: Minimize usage of deprecated PropertiesAttributeDefintion#setXmlName() Key: WFLY-7416 URL: https://issues.jboss.org/browse/WFLY-7416 Project: WildFly Issue Type: Task Components: Domain Management Reporter: Tomaz Cerar Assignee: Tomaz Cerar There are some leftovers in different subsystems that still use setXmlName() to control the properties single element name instead of name of the attribute itself. For such scenarios custom instance of PropertiesAttributeParser/Marshaller should be created instead -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7417) Minimize usage of deprecated PropertiesAttributeDefintion#setXmlName()

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-7417: --------------------------------- Summary: Minimize usage of deprecated PropertiesAttributeDefintion#setXmlName() Key: WFLY-7417 URL: https://issues.jboss.org/browse/WFLY-7417 Project: WildFly Issue Type: Task Components: Domain Management Reporter: Tomaz Cerar Assignee: Tomaz Cerar There are some leftovers in different subsystems that still use setXmlName() to control the properties single element name instead of name of the attribute itself. For such scenarios custom instance of PropertiesAttributeParser/Marshaller should be created instead -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6882) A client is not able to invoke EJB's deployed as "HASingleton deployment"

by Dennis Reed (JIRA)

[ https://issues.jboss.org/browse/WFLY-6882?page=com.atlassian.jira.plugin.... ] Dennis Reed commented on WFLY-6882: ----------------------------------- In EAP 5 and earlier, this was mostly handled by HA-JNDI. When looking up a singleton in HA-JNDI, you got a non-clustered proxy to whatever node it was deployed on. If it went down, you looked it up again in HA-JNDI and got a proxy to the new singleton. Does this still work (new lookup of the EJB)? > A client is not able to invoke EJB's deployed as "HASingleton deployment" > ------------------------------------------------------------------------- > > Key: WFLY-6882 > URL: https://issues.jboss.org/browse/WFLY-6882 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB > Affects Versions: 10.0.0.Final, 11.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Enrique González Martínez > > Given that an application contains a SLSB and is clustered, any EJB client will be updated to have a view off all cluster members and is able to use and failover to any node in the cluster no matter whether it is in the initial list of servers. > Now if the application is marked as "singleton-deployment" via jboss-all.xml and deployed to all servers only one server in a cluster will pick it and make it active. > Now the expectation is that a client is routed to that server no matter whether this special server is included in the clients initial connection list. > The interesting thing is that the client.log show that both servers are connected it the application is NOT marked as singleton > But only the initial server is connected if the app is marked as singleton! -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7415) Add backup service support for singleton services

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-7415: ---------------------------------- Summary: Add backup service support for singleton services Key: WFLY-7415 URL: https://issues.jboss.org/browse/WFLY-7415 Project: WildFly Issue Type: Feature Request Components: Clustering Affects Versions: 10.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 11.0.0.Alpha1 Currently, singleton services are started on the primary node only - no service is started on the backup nodes. We can generalize this use case by building a singleton service using 2 services: one to be started on the primary node, and the other to be installed on backup nodes. When a node is elected as the primary provider, we stop the backup service, and start the primary service. Conversely, when a primary node loses a re-election, it stops its primary service and starts its backup service. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-700) Fix AuthenticationClient comparison behavior

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-700?page=com.atlassian.jira.plugin.sy... ] David Lloyd commented on ELY-700: --------------------------------- Other helpful things: equal/hashCode-stable suppliers/functions/etc. > Fix AuthenticationClient comparison behavior > -------------------------------------------- > > Key: ELY-700 > URL: https://issues.jboss.org/browse/ELY-700 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: David Lloyd > Assignee: David Lloyd > > The authentication client's comparison behavior is more or less banjaxed. It needs to be fixed, starting probably with killing off multi-valued configuration items. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-700) Fix AuthenticationClient comparison behavior

by David Lloyd (JIRA)

David Lloyd created ELY-700: ------------------------------- Summary: Fix AuthenticationClient comparison behavior Key: ELY-700 URL: https://issues.jboss.org/browse/ELY-700 Project: WildFly Elytron Issue Type: Bug Components: Authentication Client Reporter: David Lloyd Assignee: David Lloyd The authentication client's comparison behavior is more or less banjaxed. It needs to be fixed, starting probably with killing off multi-valued configuration items. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7413) Singleton policy quorum attribute is missing a validator

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-7413: ---------------------------------- Summary: Singleton policy quorum attribute is missing a validator Key: WFLY-7413 URL: https://issues.jboss.org/browse/WFLY-7413 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.1.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 11.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7414) Singleton policy quorum attribute is missing a validator

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-7414: ---------------------------------- Summary: Singleton policy quorum attribute is missing a validator Key: WFLY-7414 URL: https://issues.jboss.org/browse/WFLY-7414 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.1.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 11.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-698) Rework the constructor exclusion logic for authentication rules and configurations

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-698?page=com.atlassian.jira.plugin.sy... ] David Lloyd reassigned ELY-698: ------------------------------- Assignee: David Lloyd > Rework the constructor exclusion logic for authentication rules and configurations > ---------------------------------------------------------------------------------- > > Key: ELY-698 > URL: https://issues.jboss.org/browse/ELY-698 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Minor > > The current authentication rule and configuration classes are designed to ensure that mutually incompatible rules and configurations cannot coexist. However the implementation is applied a bit erratically. There may be problems with commutatively applying checks. Some checks may be missing or extraneous. > We need a new approach where the mutual exclusion set is somehow enforced centrally. One option is to have literal sets, and each class that is a member of one or more sets must remove all other handlers that are also within the set(s). A predicate could be used to make this efficient by only sweeping the list one time, in contrast to the current mechanism which sweeps the list once per exclusive type. > Another option is to have a marker interface for each capability, and to remove all peers with the same capability. A predicate can also be used in this case. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

8 years, 2 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 October 2016