May 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4392) Make use of TCCL in ARQ ManagedContainer configurable

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4392?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4392: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Make use of TCCL in ARQ ManagedContainer configurable > ----------------------------------------------------- > > Key: WFLY-4392 > URL: https://issues.jboss.org/browse/WFLY-4392 > Project: WildFly > Issue Type: Feature Request > Components: Test Suite > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 9.0.0.CR2 > > > In WildFly it is considerred intended behaviour that test code gets called with the TCCL set to the test deployment. IMHO this shadows potential problems when the functionality under test is not called from an ARQ test case (i.e. from an normal javaee endpoint) > For Camel integration this behaviour is not acceptable. > CrossLink: https://github.com/wildfly-extras/wildfly-camel/issues/340 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4530) Port jboss-as-ejb3_1_5.xsd to WildFly

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4530?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4530: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Port jboss-as-ejb3_1_5.xsd to WildFly > ------------------------------------- > > Key: WFLY-4530 > URL: https://issues.jboss.org/browse/WFLY-4530 > Project: WildFly > Issue Type: Sub-task > Components: EJB > Reporter: Darran Lofthouse > Fix For: 9.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4529) Port jboss-as-ee_1_2.xsd to WildFly

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4529?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4529: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Port jboss-as-ee_1_2.xsd to WildFly > ----------------------------------- > > Key: WFLY-4529 > URL: https://issues.jboss.org/browse/WFLY-4529 > Project: WildFly > Issue Type: Sub-task > Components: EE > Reporter: Darran Lofthouse > Fix For: 9.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4528) Product to Project Schema and Model Sync

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4528?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4528: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Product to Project Schema and Model Sync > ---------------------------------------- > > Key: WFLY-4528 > URL: https://issues.jboss.org/browse/WFLY-4528 > Project: WildFly > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.CR2 > > > Periodic sync of EAP schemas with WildFly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4515) Fix clustering transformers and reenable in mixed-domain tests

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4515?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4515: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Fix clustering transformers and reenable in mixed-domain tests > -------------------------------------------------------------- > > Key: WFLY-4515 > URL: https://issues.jboss.org/browse/WFLY-4515 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 9.0.0.Beta2 > Reporter: Kabir Khan > Assignee: Radoslav Husar > Priority: Critical > Fix For: 9.0.0.CR2 > > > When running the jgroups and infinispan subsystem tests with -Djboss.test.transformers.eap there are some failures in the transformers tests. > Also, in the mixed domain tests it is not possible to enable these subsystems, so I have removed them from DomainAdjuster620 in https://github.com/wildfly/wildfly/pull/7350. They should be reenabled again as part of this Jira. > Some info from private mail: > {quote} > However, when transforming that to 7.2.0 by running: > mvn clean install -DallTests -Djboss.test.mixed.domain.dir=/Users/kabir/old-as7-releases/ -pl testsuite/mixed-domain/ -Dtest=MixedDomain_7_2_0_Final_TestSuite > I get the following error: > 11:59:43,682 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: java.io.IOException: 1-$-WFLYCTL0300: Transforming resource [ > ("profile" => "full-ha"), > ("subsystem" => "infinispan"), > ("cache-container" => "server"), > ("transport" => "TRANSPORT") > ] for host controller 'slave' to subsystem 'infinispan' model version '1.4.0' --there were problems with some of the attributes and this resource will need to be ignored on that host. Details of problems: [WFLYCLINF0027: Could not determine 'stack' attribute from JGroups subsystem] > I am not totally sure if this is the right solution, but I attempted to add a stack attribute to the transport, but it does not seem to get persisted so it goes away after reloading the DC (out of admin-only to normal mode). I also tried in standalone mode, and executing > /subsystem=infinispan/cache-container=server/transport=TRANSPORT:write-attribute(name=stack, value=udp) > and the stack does not get persisted. > It is probably a simple fix, but since I am not sure if it is the right fix or not, especially since adding this to the writer it also seems to be ignored by the parser. Perhaps this is a candidate for something along the lines of https://github.com/wildfly/wildfly/blob/master/clustering/jgroups/extensi... so that we can support old configs, but not actually use it on a server using the current version? > {quote} > Note that the above is when I was working on this, the 7.2.0 test has been removed. We now test EAP 6.2.0 and 6.3.0 compatibility. I believe the problem is similar there although I have not dug in very deeply. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4570) wildfly-init-debian.sh fails on Ubuntu 15.04

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4570?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4570: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > wildfly-init-debian.sh fails on Ubuntu 15.04 > -------------------------------------------- > > Key: WFLY-4570 > URL: https://issues.jboss.org/browse/WFLY-4570 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.0.Beta2, 9.0.0.CR1 > Environment: Ubuntu 15.04, Oracle JDK_1.8.0_45-b14 > Reporter: Dennis Gesker > Assignee: Jason Greene > Priority: Minor > Fix For: 9.0.0.CR2 > > > Init script "wildfly-init-debian.sh" fails on Ubuntu 15.04 but standalone.sh works fine. Env is jdk_1.8.0_45-b14 and wildfly_9.0.0.Beta2. The error returned is: > Failed to start wildfly.service: Unit wildfly.service failed to load: No such file or directory. > Had no issue with the above script on Ubuntu 14.04 so guessing a change in Ubuntu ("Upstart" Maybe?) But, I'm far from an upstart or bash expert. bash -x seems to at least create the pid. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4551) legacy cache containers need org.jboss.as.jpa.hibernate:4 module to have Infinispan access

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4551?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4551: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > legacy cache containers need org.jboss.as.jpa.hibernate:4 module to have Infinispan access > ------------------------------------------------------------------------------------------ > > Key: WFLY-4551 > URL: https://issues.jboss.org/browse/WFLY-4551 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 9.0.0.CR2 > > Attachments: failure.txt > > > Seeing a compliance test failure due to legacy 'cache container' setting: > {quote} > <cache-container name="hibernate" default-cache="local-query" module="org.jboss.as.jpa.hibernate:4"> > {quote} > As a result, the org.jboss.as.jpa.hibernate:4 module also needs access to the hibernate-infinispan module. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4538) Remote tests fail with ClassNotFoundException: org.w3c.dom.ElementTraversal

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4538?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4538: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Remote tests fail with ClassNotFoundException: org.w3c.dom.ElementTraversal > --------------------------------------------------------------------------- > > Key: WFLY-4538 > URL: https://issues.jboss.org/browse/WFLY-4538 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 9.0.0.CR2 > > > {code} > Caused by: java.lang.ClassNotFoundException: org.w3c.dom.ElementTraversal > at java.net.URLClassLoader$1.run(URLClassLoader.java:372) > at java.net.URLClassLoader$1.run(URLClassLoader.java:361) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:360) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:760) > at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:455) > at java.net.URLClassLoader.access$100(URLClassLoader.java:73) > at java.net.URLClassLoader$1.run(URLClassLoader.java:367) > at java.net.URLClassLoader$1.run(URLClassLoader.java:361) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:360) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.apache.xerces.jaxp.DocumentBuilderImpl.newDocument(Unknown Source) > {code} > CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/544 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4537) Servlet protocol leaks into all containers

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4537?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4537: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Servlet protocol leaks into all containers > ------------------------------------------ > > Key: WFLY-4537 > URL: https://issues.jboss.org/browse/WFLY-4537 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 9.0.0.CR2 > > > The arquillian-protocol-servlet leaks into all containers. A test client module should be able to configure its preferred protocol -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4532) Clean up jboss-as-web_2_*.xsd schemas

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4532?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4532: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Clean up jboss-as-web_2_*.xsd schemas > ------------------------------------- > > Key: WFLY-4532 > URL: https://issues.jboss.org/browse/WFLY-4532 > Project: WildFly > Issue Type: Sub-task > Components: Web (JBoss Web) > Reporter: Darran Lofthouse > Assignee: Remy Maucherat > Priority: Blocker > Fix For: 9.0.0.CR2 > > > The last jboss-as-web schema included in a community release is jboss-as-web_2_0.xsd > JBoss EAP contains both jboss-as-web_2_1.xsd and jboss-as-web_2_2.xsd > I believe something was mistakenly added to the 2.1 schema in EAP, this was forward ported to WildFly - then the change to 2.1 was reverted in EAP and a 2.2 schema added. > Version 2.1 and 2.2 of the schemas need porting from EAP to WildFly and the parsers updated to support them accordingly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2015