November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBMETA-390) Improve and enhance ValidationHelper and associated tools for XML/XSD use

by Weston Price (JIRA)

[ https://issues.jboss.org/browse/JBMETA-390?page=com.atlassian.jira.plugin... ] Weston Price updated JBMETA-390: -------------------------------- Component/s: common > Improve and enhance ValidationHelper and associated tools for XML/XSD use > ------------------------------------------------------------------------- > > Key: JBMETA-390 > URL: https://issues.jboss.org/browse/JBMETA-390 > Project: JBoss Metadata > Issue Type: Feature Request > Components: common, ejb > Affects Versions: 10.0.0.Beta1 > Reporter: Weston Price > Assignee: Weston Price > Priority: Optional > Fix For: 10.0.0.Beta2 > > > Currently support for XML validation, XSD maintenance and general XML/XSD handling is quite weak. While a ValidationHelper class exists, it needs to be enhance to remove hard coded references and allow for updating the underling XSD catalogs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1825) ReadWriteLock

by Manuel Dominguez Sarmiento (JIRA)

[ https://issues.jboss.org/browse/JGRP-1825?page=com.atlassian.jira.plugin.... ] Manuel Dominguez Sarmiento commented on JGRP-1825: -------------------------------------------------- Hi Bela, we would appreciate a native ReadWriteLock implementation in JGroups. We are working on improving the EhCache-JGroups replication integration so that cluster consistency can be achieved with replicated read-write caches. ReadWriteLocks are a necessity for many scenarios and corner cases. The alternative seems to be using the current exclusive lock construct, with two different locks (one for reads, another for writes) together with a distributed COUNTER, but this is far from being efficient (too chatty). Perhaps something along the lines of the algorithms described in https://en.wikipedia.org/wiki/Readers–writers_problem > ReadWriteLock > ------------- > > Key: JGRP-1825 > URL: https://issues.jboss.org/browse/JGRP-1825 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.6 > > Attachments: JgroupTest.zip > > > Adds a read/write lock to LockService. The impl is attached -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-390) Improve and enhance ValidationHelper and associated tools for XML/XSD use

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/JBMETA-390?page=com.atlassian.jira.plugin... ] Carlo de Wolf updated JBMETA-390: --------------------------------- Fix Version/s: 10.0.0.Beta2 (was: 8.1.2.Final) > Improve and enhance ValidationHelper and associated tools for XML/XSD use > ------------------------------------------------------------------------- > > Key: JBMETA-390 > URL: https://issues.jboss.org/browse/JBMETA-390 > Project: JBoss Metadata > Issue Type: Feature Request > Components: ejb > Affects Versions: 10.0.0.Beta1 > Reporter: Weston Price > Assignee: Weston Price > Priority: Optional > Fix For: 10.0.0.Beta2 > > > Currently support for XML validation, XSD maintenance and general XML/XSD handling is quite weak. While a ValidationHelper class exists, it needs to be enhance to remove hard coded references and allow for updating the underling XSD catalogs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-358) Wrap all LDAP testing in a single suite

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-358: ------------------------------------ Summary: Wrap all LDAP testing in a single suite Key: ELY-358 URL: https://issues.jboss.org/browse/ELY-358 Project: WildFly Elytron Issue Type: Enhancement Components: Testsuite Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta2 If we wrap all these tests in a single suite we can start up the LDAP server one, run all the tests and then stop the server - this will stop us incurring the set-up / tear-down cost for each test case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-357) LegacyPropertiesRealm requires group loading completing

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-357: ------------------------------------ Summary: LegacyPropertiesRealm requires group loading completing Key: ELY-357 URL: https://issues.jboss.org/browse/ELY-357 Project: WildFly Elytron Issue Type: Enhancement Components: Realms Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta2 This part of the implementation was never completed as the API was still being designed, we now need this especially as we are using this realm to begin with by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5615) Security module options not parsed

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5615?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-5615: ---------------------------------------- [~heiko.braun] In the description your CLI read-resource is against "myauth" not "myauth2". Is this a problem if the correct address is used? > Security module options not parsed > ---------------------------------- > > Key: WFLY-5615 > URL: https://issues.jboss.org/browse/WFLY-5615 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 10.0.0.CR4 > Reporter: Heiko Braun > Assignee: Brian Stansberry > Priority: Critical > > I've created a login module with several options and the result appears in standalone.xml. However when I read the resource using the CLI, these options are not shown. > {noformat} > <security-domain name="myDomain" cache-type="default"> > <authentication> > <login-module name="myauth" code="Simple" flag="optional"/> > <login-module name="myauth2" code="SimpleUsers" flag="sufficient"> > <module-option name="foo" value="bar"/> > <module-option name="one" value="two"/> > </login-module> > </authentication> > </security-domain> > {noformat} > {noformat} > [standalone@localhost:9990 /] /subsystem=security/security-domain=myDomain/authentication=classic/login-module=myauth:read-resource(recursive=true) > { > "outcome" => "success", > "result" => { > "code" => "Simple", > "flag" => "optional", > "module" => undefined, > "module-options" => undefined > } > } > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-390) Improve and enhance ValidationHelper and associated tools for XML/XSD use

by Weston Price (JIRA)

Weston Price created JBMETA-390: ----------------------------------- Summary: Improve and enhance ValidationHelper and associated tools for XML/XSD use Key: JBMETA-390 URL: https://issues.jboss.org/browse/JBMETA-390 Project: JBoss Metadata Issue Type: Feature Request Components: ejb Affects Versions: 10.0.0.Beta1 Reporter: Weston Price Assignee: Weston Price Priority: Optional Fix For: 8.1.2.Final Currently support for XML validation, XSD maintenance and general XML/XSD handling is quite weak. While a ValidationHelper class exists, it needs to be enhance to remove hard coded references and allow for updating the underling XSD catalogs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5556) Configure remote tx timeout via system property

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5556?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-5556: ----------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1265300|https://bugzilla.redhat.com/show_bug.cgi?id=1265300] from ON_QA to VERIFIED > Configure remote tx timeout via system property > ----------------------------------------------- > > Key: WFLY-5556 > URL: https://issues.jboss.org/browse/WFLY-5556 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > Fix For: 10.0.0.CR4 > > > Description of problem: > The hardcoded 5 minute timeout period was replace with Integer.MAX_VALUE for the timeout period of "remote" distributed transaction branches. > - https://issues.jboss.org/browse/WFLY-2789 > - https://bugzilla.redhat.com/show_bug.cgi?id=1056585#c1 > An "infinite" timeout is a problem as this value is also passed to the database to control statement execution. This means that database statements may run uncontrolled in most cases. Too, in one case we have seen that the database driver or the database is mishandling the value and aborting almost immediately (e.g. after only 2 or 3 seconds). > Version-Release number of selected component (if applicable): > How reproducible: > Consistently > Steps to Reproduce: > 1. Start a transaction in server "one" > 2. Using JTA/EJB remoting, propagate that transaction to a remote server > 3. The timeout for the transaction on the remote can be seen to be Integer.MAX_VALUE > Actual results: > Either an "infinite" timeout period for database statement execution or else an immediate abort > Expected results: > A "reasonable" smaller value must be used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5348) Propagate transaction timeout value for distributed transaction when using JTA and EJB remoting

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5348?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-5348: ----------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1265300|https://bugzilla.redhat.com/show_bug.cgi?id=1265300] from ON_QA to VERIFIED > Propagate transaction timeout value for distributed transaction when using JTA and EJB remoting > ----------------------------------------------------------------------------------------------- > > Key: WFLY-5348 > URL: https://issues.jboss.org/browse/WFLY-5348 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Beta2 > Reporter: Stephen Fikes > Assignee: Panagiotis Sotiropoulos > Labels: ejb3, jta, transactions > Fix For: 10.0.0.CR4 > > > When a transaction begins in "server 1" and an EJB remoting request is made to "server 2" the timeout value for the transaction branch in "server 2" is initially set to {{Integer.MAX_VALUE}} which means {{set-tx-query-timeout}} does not work properly on datasources enlisted in the distributed branch of the transaction in server 2. This essentially requests that statement execution not be timed out at all (though in some cases the large value seems to result in abnormally fast timeout after a couple of seconds). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-126) Log rotation fails on Windows if target already exists

by Panagiotis Sotiropoulos (JIRA)

Panagiotis Sotiropoulos created LOGMGR-126: ---------------------------------------------- Summary: Log rotation fails on Windows if target already exists Key: LOGMGR-126 URL: https://issues.jboss.org/browse/LOGMGR-126 Project: JBoss Log Manager Issue Type: Bug Reporter: Panagiotis Sotiropoulos Assignee: James Perkins Fix For: 2.0.4.Final, 2.1.0.Beta1 PeriodicRotatingFileHandler (and others) use File.renameTo() to rename the file. That method is documented as having many implementation-defined aspects, see http://docs.oracle.com/javase/7/docs/api/java/io/File.html#renameTo%28jav... One that can be a problem is that on Windows, it will fail if the target file already exists. If you use a ".dd" suffix, this will occur when it rolls over to a new month. It has rarely been a problem, since most people use the year month and day so they are unique. Files.move() can replace existing files, so may be better, and some of the costs of that are likely not to be a problem with how it is using here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 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 November 2015