November 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4065) Warning about private module use issued twice

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4065?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-4065: ----------------------------------- Do you maybe have both jboss-deployment-structure.xml with deps & Dependancies entry in MANIFEST.MF? > Warning about private module use issued twice > --------------------------------------------- > > Key: WFLY-4065 > URL: https://issues.jboss.org/browse/WFLY-4065 > Project: WildFly > Issue Type: Bug > Components: Class Loading > Affects Versions: 10.0.0.CR5 > Reporter: Frank Langelage > Assignee: David Lloyd > Priority: Minor > > My web app is using some modules of WildFly AS which are not public. > The warning about using private modules is issued twice for every module: > 09.11. 22:07:34,088 WARN [org.jboss.as.dependency.private#start] WFLYSRV0018: Deployment "deployment.web-maj2e-langfr-dev.war" is using a private module ("org.jboss.common-core:main") which may be changed or removed in future versions without notice. > 09.11. 22:07:34,090 WARN [org.jboss.as.dependency.private#start] WFLYSRV0018: Deployment "deployment.web-maj2e-langfr-dev.war" is using a private module ("org.jboss.common-core:main") which may be changed or removed in future versions without notice. > 09.11. 22:07:34,091 WARN [org.jboss.as.dependency.private#start] WFLYSRV0018: Deployment "deployment.web-maj2e-langfr-dev.war" is using a private module ("org.apache.commons.collections:main") which may be changed or removed in future versions without notice. > 09.11. 22:07:34,091 WARN [org.jboss.as.dependency.private#start] WFLYSRV0018: Deployment "deployment.web-maj2e-langfr-dev.war" is using a private module ("org.apache.commons.collections:main") which may be changed or removed in future versions without notice. > 09.11. 22:07:34,092 WARN [org.jboss.as.dependency.private#start] WFLYSRV0018: Deployment "deployment.web-maj2e-langfr-dev.war" is using a private module ("org.apache.cxf.impl:main") which may be changed or removed in future versions without notice. > 09.11. 22:07:34,094 WARN [org.jboss.as.dependency.private#start] WFLYSRV0018: Deployment "deployment.web-maj2e-langfr-dev.war" is using a private module ("org.apache.cxf.impl:main") which may be changed or removed in future versions without notice. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3778) Tests in Manualmode test suite fail occasionally

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3778?page=com.atlassian.jira.plugin.... ] Tomaz Cerar resolved WFLY-3778. ------------------------------- Fix Version/s: 10.0.0.CR4 Resolution: Done Resolving based on Frank's comment. For some time now, we have regular CI job that tests on Sparc Solaris 11.1 and it mostly works fine. > Tests in Manualmode test suite fail occasionally > ------------------------------------------------ > > Key: WFLY-3778 > URL: https://issues.jboss.org/browse/WFLY-3778 > Project: WildFly > Issue Type: Bug > Components: Remoting, Test Suite > Affects Versions: 9.0.0.Alpha1 > Environment: Oracle Solaris SPARC 10, Oracle JDK 1.7.0_67. > Reporter: Frank Langelage > Assignee: David Lloyd > Fix For: 10.0.0.CR4 > > Attachments: org.jboss.as.test.manualmode.management.cli.VaultPasswordsInCLITestCase-output.txt, org.jboss.as.test.manualmode.management.cli.VaultPasswordsInCLITestCase.txt, TEST-org.jboss.as.test.manualmode.management.cli.VaultPasswordsInCLITestCase.xml > > > I always see failures in one or few test of manualmode test suite on this platform. I not remember to have seen them on Windows 7. > But I saw a very similar failure today on Linux first time for PR 6638. > See https://github.com/wildfly/wildfly/pull/6638. > Last failure on my machine: > {noformat} > Running org.jboss.as.test.manualmode.management.cli.VaultPasswordsInCLITestCase > Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 72.186 sec <<< FAILURE! - in org.jboss.as.test.manualmode.management.cli.VaultPasswordsInCLITestCase > testRightVaultPassword(org.jboss.as.test.manualmode.management.cli.VaultPasswordsInCLITestCase) Time elapsed: 6.23 sec <<< FAILURE! > java.lang.AssertionError: Password should be right and authentication successful > Expected: a string containing "\"outcome\" => \"success\"" > but: was "0: INFO [org.jboss.modules] JBoss Modules version 1.3.4.Final > INFO [org.jboss.security] PBOX000361: Default Security Vault Implementation Initialized and Ready > INFO [org.xnio] XNIO version 3.3.0.Beta1 > INFO [org.xnio.nio] XNIO NIO Implementation Version 3.3.0.Beta1 > INFO [org.jboss.remoting] JBoss Remoting version 4.0.3.Final > " > at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) > at org.junit.Assert.assertThat(Assert.java:865) > at org.jboss.as.test.manualmode.management.cli.VaultPasswordsInCLITestCase.testRightVaultPassword(VaultPasswordsInCLITestCase.java:158) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1163) Provide an API to access the main XML element parsers

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1163?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFCORE-1163: ------------------------------------------ As discussed in HipChat if you decide you do want to work on this before my PRs are ready to be merged let me know and I can produce a branch with my changes applied to master to work on top of. > Provide an API to access the main XML element parsers > ----------------------------------------------------- > > Key: WFCORE-1163 > URL: https://issues.jboss.org/browse/WFCORE-1163 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Heiko Braun > Labels: affects_elytron > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1163) Provide an API to access the main XML element parsers

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1163?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-1163: ------------------------------------- Labels: affects_elytron (was: ) > Provide an API to access the main XML element parsers > ----------------------------------------------------- > > Key: WFCORE-1163 > URL: https://issues.jboss.org/browse/WFCORE-1163 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Heiko Braun > Labels: affects_elytron > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1163) Provide an API to access the main XML element parsers

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1163?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFCORE-1163: ------------------------------------------ FYI I have already forked most of the management related parsers ready for WildFly 11, also I have various refactoring in place to bring management interface resources closer between standalone and domain mode and also some additional changes to the management interfaces to allow configuration that allows a choice between Elytron and legacy realms. > Provide an API to access the main XML element parsers > ----------------------------------------------------- > > Key: WFCORE-1163 > URL: https://issues.jboss.org/browse/WFCORE-1163 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Heiko Braun > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1163) Provide an API to access the main XML element parsers

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1163?page=com.atlassian.jira.plugi... ] Heiko Braun commented on WFCORE-1163: ------------------------------------- Brian: ... since swarm is assembling together a config from elements fractions plus stuff from standalone.xml and exactly what from standalone.xml should be kept vs ignored is still somewhat in flux letting swarm be in charge of the overall assembly and letting it pull what it needs from kernel-provided parsers seems best at least initially ... the intent would be to allow access to a parser for the main elements i.e. first level children of the <server> element root, excluding 'extension' and 'profile' allowing that seems like a fairly simple refactoring of existing parsing classes ... one aspect to deal with is the parsers for some chunks do validation against data parsed from other chunks e.g. the 'socket-binding-group' parsing validates that 'interface' references point to previously parsed interfaces I think we would need to tweak the internals to disable that kind of validation if things are parsed this way since it's only if the full internal parser is used that we have the necessary state to pass between parser chunks unless we add some complicated API, which I'd prefer not to do ... that's no big loss though that kind of validation will still happen when the List<ModelNode> of operations is executed doing it in the parser is redundant we only do it to provide a better error message if validation fails one that can point to a line/column in the xml > Provide an API to access the main XML element parsers > ----------------------------------------------------- > > Key: WFCORE-1163 > URL: https://issues.jboss.org/browse/WFCORE-1163 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Heiko Braun > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1791) Unable to use Filter Expressions in filter-spec

by Miguel Moquillon (JIRA)

[ https://issues.jboss.org/browse/WFLY-1791?page=com.atlassian.jira.plugin.... ] Miguel Moquillon commented on WFLY-1791: ---------------------------------------- levelRange[DEBUG, ERROR] as a STRING (hence double-quoted in your example) seams to cause an error while being interpreted at Wildfly starting: it fails silently to start. In fact, all filter expressions in filter-spec failed in my case (Wildfly 9.0.2): even with expression from which this bug was filled: substituteAll("JBAS" \, "DUMMY") > Unable to use Filter Expressions in filter-spec > ------------------------------------------------ > > Key: WFLY-1791 > URL: https://issues.jboss.org/browse/WFLY-1791 > Project: WildFly > Issue Type: Bug > Components: CLI > Reporter: ehsavoie Hugonnet > Assignee: Alexey Loubyansky > Priority: Minor > Fix For: 8.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1163) Provide an API to access the main XML element parsers

by Heiko Braun (JIRA)

Heiko Braun created WFCORE-1163: ----------------------------------- Summary: Provide an API to access the main XML element parsers Key: WFCORE-1163 URL: https://issues.jboss.org/browse/WFCORE-1163 Project: WildFly Core Issue Type: Feature Request Components: Domain Management Reporter: Heiko Braun Assignee: Heiko Braun -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1791) Unable to use Filter Expressions in filter-spec

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFLY-1791?page=com.atlassian.jira.plugin.... ] ehsavoie Hugonnet edited comment on WFLY-1791 at 11/26/15 6:35 AM: ------------------------------------------------------------------- /] /subsystem=logging/console-handler=CONSOLE:write-attribute(name=filter-spec, value="levelRange[DEBUG, ERROR]") {"outcome" => "success"} Your value is just incorrect as you are passing a list instead of a String. was (Author: ehugonnet): /] /subsystem=logging/console-handler=CONSOLE:write-attribute(name=filter-spec, value="levelRange[DEBUG, ERROR]") {"outcome" => "success"} Your value is just incorrect as you are passing a list instead of a String. > Unable to use Filter Expressions in filter-spec > ------------------------------------------------ > > Key: WFLY-1791 > URL: https://issues.jboss.org/browse/WFLY-1791 > Project: WildFly > Issue Type: Bug > Components: CLI > Reporter: ehsavoie Hugonnet > Assignee: Alexey Loubyansky > Priority: Minor > Fix For: 8.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1791) Unable to use Filter Expressions in filter-spec

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFLY-1791?page=com.atlassian.jira.plugin.... ] ehsavoie Hugonnet commented on WFLY-1791: ----------------------------------------- /] /subsystem=logging/console-handler=CONSOLE:write-attribute(name=filter-spec, value="levelRange[DEBUG, ERROR]") {"outcome" => "success"} Your value is just incorrect as you are passing a list instead of a String. > Unable to use Filter Expressions in filter-spec > ------------------------------------------------ > > Key: WFLY-1791 > URL: https://issues.jboss.org/browse/WFLY-1791 > Project: WildFly > Issue Type: Bug > Components: CLI > Reporter: ehsavoie Hugonnet > Assignee: Alexey Loubyansky > Priority: Minor > Fix For: 8.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 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