December 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1212) TestModule does not clean up after itself properly

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1212: ---------------------------------------- Summary: TestModule does not clean up after itself properly Key: WFCORE-1212 URL: https://issues.jboss.org/browse/WFCORE-1212 Project: WildFly Core Issue Type: Bug Components: Test Suite Affects Versions: 2.0.4.Final Reporter: Brian Stansberry TestModule.create() calls mkdirs() to create its filesystem structure, but remove() only removes the from the dir above 'main' and below, leaving behind intermediate dirs. The result of this is if you run the full testsuite with -Dts.basic, the dist/target/wildflyxxx/modules dir ends up with child dir 'test' in addition to the proper 'system'. I'm not sure why this spurious dir doesn't end up in the final dists we publish. Perhaps its just luck due to the release process not running the testsuite when the final build with the 'deploy' target is invoked. I know my process for releasing WildFly Core doesn't re-run tests in that step. Once remove() does its current work it should walk up the filesystem tree until it gets to the file returned by getModulesDir(). For each level in the tree it should check if that file is a dir with no children and if it is it should remove the dir. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-393) Switch to using EvidenceVerifyCallback for certificate verification

by Farah Juma (JIRA)

Farah Juma created ELY-393: ------------------------------ Summary: Switch to using EvidenceVerifyCallback for certificate verification Key: ELY-393 URL: https://issues.jboss.org/browse/ELY-393 Project: WildFly Elytron Issue Type: Task Components: Callbacks Reporter: Farah Juma Assignee: Farah Juma Modify Entity to use {{EvidenceVerifyCallback}} for certificate chain verification instead of {{VerifyPeerTrustedCallback}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5692) Improve Infinispan subsystem rejections test coverage

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5692?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-5692: --------------------------------- Issue Type: Task (was: Feature Request) > Improve Infinispan subsystem rejections test coverage > ----------------------------------------------------- > > Key: WFLY-5692 > URL: https://issues.jboss.org/browse/WFLY-5692 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 10.0.0.CR4 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > Improve rejections test coverage per the following diffs > 6.2.0 - https://gist.github.com/kabir/c08491dd97070c8ee394 > 6.3.0 - https://gist.github.com/kabir/df7b3411e79a596a5d58 > 6.4.0 - https://gist.github.com/kabir/7c757ef03a577db31cb2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5494) Fix Infinispan subsystem cache store properties transformations and improve testing

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5494?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-5494: --------------------------------- Issue Type: Bug (was: Feature Request) > Fix Infinispan subsystem cache store properties transformations and improve testing > ----------------------------------------------------------------------------------- > > Key: WFLY-5494 > URL: https://issues.jboss.org/browse/WFLY-5494 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR2 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Similar to what is done in jgroups, related fixes and move code to common module, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1202) LDAP authentication/authorization fails due to making unneeded role lookup requests

by Derek Horton (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1202?page=com.atlassian.jira.plugi... ] Derek Horton updated WFCORE-1202: --------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1306 > LDAP authentication/authorization fails due to making unneeded role lookup requests > ----------------------------------------------------------------------------------- > > Key: WFCORE-1202 > URL: https://issues.jboss.org/browse/WFCORE-1202 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Brad Maxwell > Assignee: Darran Lofthouse > > LDAP authentication/authorization fails due to making unneeded role lookup requests -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3149) Windows service on 64 bit systems cannot be stopped

by Ty Garside (JIRA)

[ https://issues.jboss.org/browse/WFLY-3149?page=com.atlassian.jira.plugin.... ] Ty Garside commented on WFLY-3149: ---------------------------------- If it helps anyone else, I just encountered this same problem. The issue I had was I do all my development from CMD scripts that set up my JAVA_HOME etc. for various projects I use different version of Java. Anyway, my global JAVA_HOME was set to an invalid uninstalled Java. It seems that its able to run on start using the correct JAVA_HOME, but when stopping from Windows Services panel, for some reason it needs JAVA_HOME global environment variable to be a valid JDK, not using the one in use when I ran the install command. > Windows service on 64 bit systems cannot be stopped > --------------------------------------------------- > > Key: WFLY-3149 > URL: https://issues.jboss.org/browse/WFLY-3149 > Project: WildFly > Issue Type: Bug > Components: Scripts > Affects Versions: 8.0.0.Final > Environment: Windows 2008 Server, Windows 7 professional - both 64 bit systems using JDK 1.7.0_09 > Reporter: Mohan Potturi > Assignee: Mladen Turk > > The Windows service cannot be stopped. It says 'stopping' in the windows service user interface window. The only way to stop it is ti actually kill the java process. It works flawlessly on 32 bit systems though. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1188) Exiting CLI requires stty sane command to be issued on Linux

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1188?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1188: ------------------------------------- Priority: Blocker (was: Major) > Exiting CLI requires stty sane command to be issued on Linux > ------------------------------------------------------------ > > Key: WFCORE-1188 > URL: https://issues.jboss.org/browse/WFCORE-1188 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.4.Final > Environment: Fedora 23 > Linux 4.2.6-301.fc23.x86_64 #1 SMP Fri Nov 20 22:22:41 UTC 2015 GNU/Linux > openjdk version "1.8.0_65" > OpenJDK Runtime Environment (build 1.8.0_65-b17) > OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode) > Reporter: James Perkins > Assignee: Alexey Loubyansky > Priority: Blocker > Fix For: 2.0.5.Final > > > The PR https://github.com/wildfly/wildfly-core/pull/1268/ seemed to have introduced a regression where some times (seems to be most in my case) {{stty sane}} is required to get a shell back to normal. My guess is it's the aesh upgrade, but I'm not certain on that so I'll start the JIRA here and it can be moved to AESH if necessary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1188) Exiting CLI requires stty sane command to be issued on Linux

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1188?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1188: ------------------------------------- Fix Version/s: 2.0.5.Final > Exiting CLI requires stty sane command to be issued on Linux > ------------------------------------------------------------ > > Key: WFCORE-1188 > URL: https://issues.jboss.org/browse/WFCORE-1188 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.4.Final > Environment: Fedora 23 > Linux 4.2.6-301.fc23.x86_64 #1 SMP Fri Nov 20 22:22:41 UTC 2015 GNU/Linux > openjdk version "1.8.0_65" > OpenJDK Runtime Environment (build 1.8.0_65-b17) > OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode) > Reporter: James Perkins > Assignee: Alexey Loubyansky > Priority: Blocker > Fix For: 2.0.5.Final > > > The PR https://github.com/wildfly/wildfly-core/pull/1268/ seemed to have introduced a regression where some times (seems to be most in my case) {{stty sane}} is required to get a shell back to normal. My guess is it's the aesh upgrade, but I'm not certain on that so I'll start the JIRA here and it can be moved to AESH if necessary. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5841) SchemaLocationsRewriteTestCase is checking implementation details

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFLY-5841?page=com.atlassian.jira.plugin.... ] Tomas Hofman moved JBEAP-2365 to WFLY-5841: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-5841 (was: JBEAP-2365) Workflow: GIT Pull Request workflow (was: CDW v1) Component/s: Test Suite Web Services (was: Web Services) (was: Test Suite) Target Release: (was: 7.0.0.GA) Affects Version/s: 10.0.0.CR4 (was: 7.0.0.ER3) > SchemaLocationsRewriteTestCase is checking implementation details > ----------------------------------------------------------------- > > Key: WFLY-5841 > URL: https://issues.jboss.org/browse/WFLY-5841 > Project: WildFly > Issue Type: Bug > Components: Test Suite, Web Services > Affects Versions: 10.0.0.CR4 > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Priority: Minor > > Test case is currently checking implementation details, so it's easy to brake it when implementation changes while still being correct. > Specifically, the test case shouldn't make any assumptions about the format of rewritten schema locations. Instead, it should only check that rewritten location is a retrievable URL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5682) Can't define absolute path for object store location

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5682?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-5682: -------------------------------- Fix Version/s: 10.0.0.CR5 > Can't define absolute path for object store location > ---------------------------------------------------- > > Key: WFLY-5682 > URL: https://issues.jboss.org/browse/WFLY-5682 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 10.0.0.CR4 > Reporter: Ondřej Chaloupka > Assignee: Amos Feng > Fix For: 10.0.0.CR5 > > > As trying to set absolute path for location of transaction log store I've got to suspicion that's not possible. > If I try to set `object-store-relative-to` to some absolute path or set `object-store-relative-to` to empty string and then `object-store-path` to some absolute path the server starts with exceptions [1][2]. > [1] > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.txn.ArjunaObjectStoreEnvironment: org.jboss.msc.service.StartException in service jboss.txn.ArjunaObjectStoreEnvironment: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.IllegalArgumentException: WFLYCTL0256: Could not find a path called '/home/ochaloup/tmp/' > at org.jboss.as.controller.services.path.PathManagerService.resolveRelativePathEntry(PathManagerService.java:87) at org.jboss.as.txn.service.ArjunaObjectStoreEnvironmentService.start(ArjunaObjectStoreEnvironmentService.java:76) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > ... > ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "transactions")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.txn.ArjunaObjectStoreEnvironment" => "org.jboss.msc.service.StartException in service jboss.txn.ArjunaObjectStoreEnvironment: Failed to start service > Caused by: java.lang.IllegalArgumentException: WFLYCTL0256: Could not find a path called '/home/ochaloup/tmp/'"}} > INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status reportWFLYCTL0186: Services which failed to start: service jboss.txn.ArjunaObjectStoreEnvironment: org.jboss.msc.service.StartException in service jboss.txn.ArjunaObjectStoreEnvironment: Failed to start service > {code} > [2] > {code} > ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131) > at org.jboss.as.server.ServerService.boot(ServerService.java:356) at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299) > at java.lang.Thread.run(Thread.java:745) > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[348,13] > Message: "WFLYCTL0113: '' is an invalid value for parameter relative-to. Values must have a minimum length of 1 characters" > at org.jboss.as.controller.SimpleAttributeDefinition.parse(SimpleAttributeDefinition.java:161) at org.jboss.as.controller.SimpleAttributeDefinition.parseAndSetParameter(SimpleAttributeDefinition.java:186) > at org.jboss.as.txn.subsystem.TransactionSubsystem14Parser.parseObjectStoreEnvironmentElementAndEnrichOperation(TransactionSubsystem14Parser.java:205) > at org.jboss.as.txn.subsystem.TransactionSubsystem30Parser.readElement(TransactionSubsystem30Parser.java:67) at org.jboss.as.txn.subsystem.TransactionSubsystem14Parser.readElement(TransactionSubsystem14Parser.java:111) > at org.jboss.as.txn.subsystem.TransactionSubsystem14Parser.readElement(TransactionSubsystem14Parser.java:54) at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) > at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) at org.jboss.as.server.parsing.StandaloneXml_4.parseServerProfile(StandaloneXml_4.java:547) > at org.jboss.as.server.parsing.StandaloneXml_4.readServerElement(StandaloneXml_4.java:244) at org.jboss.as.server.parsing.StandaloneXml_4.readElement(StandaloneXml_4.java:143) > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:69) at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:47) at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123) > ... 3 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 December 2015