[JBoss JIRA] (WFLY-6297) Identify problems introduced with new JDK9 versioning scheme
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/WFLY-6297?page=com.atlassian.jira.plugin.... ]
Richard Opalka edited comment on WFLY-6297 at 3/1/16 5:53 AM:
--------------------------------------------------------------
After source code review we identified problems with new JDK9 versioning scheme in these classes:
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/apt/util/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/tool/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/apache/cxf/main/cxf-core-3.1.4.jar', class 'org/apache/cxf/common/util/ClassHelper', contains string [java.version]
modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.1.2.Final.jar', class 'org/apache/log4j/helpers/Loader', contains string [java.version]
was (Author: ropalka):
After source code review we identified problems with new JDK9 versioning scheme in these classes:
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/apt/util/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/tool/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/apache/cxf/main/cxf-core-3.1.4.jar', class 'org/apache/cxf/common/util/ClassHelper', contains string [java.version]
modules/system/layers/base/org/apache/commons/beanutils/main/commons-beanutils-1.9.2.jar', class 'org/apache/commons/beanutils/MethodUtils', contains string [java.specification.version]
modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.1.2.Final.jar', class 'org/apache/log4j/helpers/Loader', contains string [java.version]
> Identify problems introduced with new JDK9 versioning scheme
> ------------------------------------------------------------
>
> Key: WFLY-6297
> URL: https://issues.jboss.org/browse/WFLY-6297
> Project: WildFly
> Issue Type: Sub-task
> Components: Build System
> Affects Versions: 10.0.0.Final
> Reporter: Richard Opalka
> Assignee: Richard Opalka
>
> JDK9 will introduce new versioning scheme described here:
> http://openjdk.java.net/projects/verona/
> We need to identify WildFly components that are realying on
> these properties.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-3272) Running a single test on windows
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3272?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar closed WFLY-3272.
-----------------------------
Resolution: Rejected
you should quote paramters like "-Dtest=clustered" not other way around.
this works also in powershell.
> Running a single test on windows
> --------------------------------
>
> Key: WFLY-3272
> URL: https://issues.jboss.org/browse/WFLY-3272
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 8.1.0.CR1
> Environment: Windows7
> Reporter: Martin Choma
>
> While reading "Running a single test (or specified tests)" on https://docs.jboss.org/author/display/WFLY8/WildFly+Integration+Testsuite...
> Trying
> {noformat}
> integration-tests.bat install -Dtest='*Clustered*' -Dintegration.module -Dts.clust
> integration-tests.bat clean install -Dtest=org/jboss/as/test/integration/ejb/async/*TestCase.java -Dintegration.module -Dts.basic
> {noformat}
> get error
> {noformat}
> c:\Users\mchoma\Documents\GitHub\wildfly>integration-tests.bat install -Dtest="*Clustered*" -Dintegration.module -Dts.clust
> "Calling processTestDirectives install -Dtest "*Clustered*" -Dintegration.module -Dts.clust"
> Calling ..\.\tools\maven\bin\mvn.bat install -Dtest "*Clustered*" -Dintegration.module -Dts.clust -Dintegration.module -Dsmoke.integration.tests
> [INFO] Scanning for projects...
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] WildFly Test Suite: Aggregator
> [INFO] WildFly Test Suite: Integration
> [INFO] WildFly Test Suite: Integration - Smoke
> [INFO] WildFly Test Suite: Integration - Clustering
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building WildFly Test Suite: Aggregator 8.1.0.Final-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WildFly Test Suite: Aggregator .................... FAILURE [0.023s]
> [INFO] WildFly Test Suite: Integration ................... SKIPPED
> [INFO] WildFly Test Suite: Integration - Smoke ........... SKIPPED
> [INFO] WildFly Test Suite: Integration - Clustering ...... SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1.025s
> [INFO] Finished at: Fri Apr 18 09:39:54 CEST 2014
> [INFO] Final Memory: 11M/154M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Unknown lifecycle phase "*Clustered*". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<
> goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-
> sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify,
> install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/LifecyclePhaseNotFoundEx...
> {noformat}
> Isnt docs up to date? Or is there some problem in running tests on windows.
> Thanx,
> Martin
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6297) Identify problems introduced with new JDK9 versioning scheme
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/WFLY-6297?page=com.atlassian.jira.plugin.... ]
Richard Opalka edited comment on WFLY-6297 at 3/1/16 5:47 AM:
--------------------------------------------------------------
After source code review we identified problems with new JDK9 versioning scheme in these classes:
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/apt/util/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/tool/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/apache/cxf/main/cxf-core-3.1.4.jar', class 'org/apache/cxf/common/util/ClassHelper', contains string [java.version]
modules/system/layers/base/org/apache/commons/beanutils/main/commons-beanutils-1.9.2.jar', class 'org/apache/commons/beanutils/MethodUtils', contains string [java.specification.version]
modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.1.2.Final.jar', class 'org/apache/log4j/helpers/Loader', contains string [java.version]
was (Author: ropalka):
After source code review we identified problems with new JDK9 versioning scheme in these classes:
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/apt/util/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/tool/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/apache/cxf/main/cxf-core-3.1.4.jar', class 'org/apache/cxf/common/util/ClassHelper', contains string [java.version]
modules/system/layers/base/org/apache/commons/beanutils/main/commons-beanutils-1.9.2.jar', class 'org/apache/commons/beanutils/MethodUtils', contains string [java.specification.version]
modules/system/layers/base/org/apache/commons/lang/main/commons-lang-2.6.jar', class 'org/apache/commons/lang/SystemUtils', contains strings [java.version]
modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.1.2.Final.jar', class 'org/apache/log4j/helpers/Loader', contains string [java.version]
> Identify problems introduced with new JDK9 versioning scheme
> ------------------------------------------------------------
>
> Key: WFLY-6297
> URL: https://issues.jboss.org/browse/WFLY-6297
> Project: WildFly
> Issue Type: Sub-task
> Components: Build System
> Affects Versions: 10.0.0.Final
> Reporter: Richard Opalka
> Assignee: Richard Opalka
>
> JDK9 will introduce new versioning scheme described here:
> http://openjdk.java.net/projects/verona/
> We need to identify WildFly components that are realying on
> these properties.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-5701) Compile error in clustering/common module with older version of jdk 8
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5701?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar closed WFLY-5701.
-----------------------------
Fix Version/s: 10.0.0.Final
Resolution: Won't Fix
It is bug in javac that was fixed in later versions
> Compile error in clustering/common module with older version of jdk 8
> ---------------------------------------------------------------------
>
> Key: WFLY-5701
> URL: https://issues.jboss.org/browse/WFLY-5701
> Project: WildFly
> Issue Type: Feature Request
> Components: Build System, Clustering
> Reporter: Paul Gier
> Assignee: Paul Gier
> Priority: Minor
> Fix For: 10.0.0.Final
>
>
> When compiling with jdk version "1.8.0_31" I get a compile error in the clustering/common module.
> {noformat}
> [ERROR] /home/pgier/projects/jboss-eap/clustering/common/src/main/java/org/jboss/as/clustering/controller/ExecutionHandler.java:[54,48] no suitable method found for collect(java.util.stream.Collector<E,capture#1 of ?,java.util.Map<java.lang.String,java.lang.Object>>)
> method java.util.stream.Stream.<R>collect(java.util.function.Supplier<R>,java.util.function.BiConsumer<R,? super capture#2 of ? extends E>,java.util.function.BiConsumer<R,R>) is not applicable
> (cannot infer type-variable(s) R
> (actual and formal argument lists differ in length))
> method java.util.stream.Stream.<R,A>collect(java.util.stream.Collector<? super capture#2 of ? extends E,A,R>) is not applicable
> (cannot infer type-variable(s) capture#3 of ?,T,K,U,T
> (argument mismatch; java.util.function.Function<capture#2 of ? extends E,capture#2 of ? extends E> cannot be converted to java.util.function.Function<? super capture#2 of ? extends E,? extends capture#2 of ? extends E>))
> [INFO] 1 error
> {noformat}
> If I use a newer jdk 8 version such as "1.8.0_65", the issue does not occur.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6297) Identify problems introduced with new JDK9 versioning scheme
by Richard Opalka (JIRA)
[ https://issues.jboss.org/browse/WFLY-6297?page=com.atlassian.jira.plugin.... ]
Richard Opalka edited comment on WFLY-6297 at 3/1/16 5:25 AM:
--------------------------------------------------------------
After source code review we identified problems with new JDK9 versioning scheme in these classes:
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/apt/util/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/tool/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/apache/cxf/main/cxf-core-3.1.4.jar', class 'org/apache/cxf/common/util/ClassHelper', contains string [java.version]
modules/system/layers/base/org/apache/commons/beanutils/main/commons-beanutils-1.9.2.jar', class 'org/apache/commons/beanutils/MethodUtils', contains string [java.specification.version]
modules/system/layers/base/org/apache/commons/lang/main/commons-lang-2.6.jar', class 'org/apache/commons/lang/SystemUtils', contains strings [java.version]
modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.1.2.Final.jar', class 'org/apache/log4j/helpers/Loader', contains string [java.version]
was (Author: ropalka):
After source code review we identified problems with new JDK9 versioning scheme in these classes:
jboss-modules.jar', class 'org/jboss/modules/Main', contains string [java.specification.version]
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/apt/util/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/eclipse/jdt/ecj/main/ecj-4.4.2.jar', class 'org/eclipse/jdt/internal/compiler/tool/EclipseFileManager', contains string [java.version]
modules/system/layers/base/org/apache/cxf/main/cxf-core-3.1.4.jar', class 'org/apache/cxf/common/util/ClassHelper', contains string [java.version]
modules/system/layers/base/org/apache/commons/beanutils/main/commons-beanutils-1.9.2.jar', class 'org/apache/commons/beanutils/MethodUtils', contains string [java.specification.version]
modules/system/layers/base/org/apache/commons/lang/main/commons-lang-2.6.jar', class 'org/apache/commons/lang/SystemUtils', contains strings [java.version]
modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.1.2.Final.jar', class 'org/apache/log4j/helpers/Loader', contains string [java.version]
> Identify problems introduced with new JDK9 versioning scheme
> ------------------------------------------------------------
>
> Key: WFLY-6297
> URL: https://issues.jboss.org/browse/WFLY-6297
> Project: WildFly
> Issue Type: Sub-task
> Components: Build System
> Affects Versions: 10.0.0.Final
> Reporter: Richard Opalka
> Assignee: Richard Opalka
>
> JDK9 will introduce new versioning scheme described here:
> http://openjdk.java.net/projects/verona/
> We need to identify WildFly components that are realying on
> these properties.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-5795) HA JMS Topic Subscriber of Colocated life backup symmetrical 2 nodes cluster violates Publish-Subscribe pattern.
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-5795?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil commented on WFLY-5795:
-----------------------------------
I've opened ARTEMIS-425 to report the issue in Artemis codebase.
> HA JMS Topic Subscriber of Colocated life backup symmetrical 2 nodes cluster violates Publish-Subscribe pattern.
> ----------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-5795
> URL: https://issues.jboss.org/browse/WFLY-5795
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.CR4
> Environment: 2 node symmetrical colocated life backup cluster (domain mode). Configuration (domain.xml, host.xml) provided as attachment.
> Reporter: Michal Sudra
> Assignee: Jeff Mesnil
> Priority: Critical
> Fix For: 10.0.0.Final
>
> Attachments: ClusteredTopicTest.java, domain.xml, domain.xml, host-slave.xml, host.xml, host.xml, master.log, slave.log
>
>
> Test Client is producing 10 messages on topic on node 1 and 2 consumers connected to node 1 and the other to node 2 are then consuming the messages.
> Expectation: Every consumer receives 10 Messages.
> Result of test: Consumer connected to node 1 is only getting every second message. Consumer connected to node 2 is receiving all 10 messages:
> Output of test program:
> Sent message: This is text message 0
> Sent message: This is text message 1
> Sent message: This is text message 2
> Sent message: This is text message 3
> Sent message: This is text message 4
> Sent message: This is text message 5
> Sent message: This is text message 6
> Sent message: This is text message 7
> Sent message: This is text message 8
> Sent message: This is text message 9
> 0 Recieved message: This is text message 0 from node 0 from java:/jms/topic/ClusterStateTopic
> 1 Recieved message: This is text message 2 from node 0 from java:/jms/topic/ClusterStateTopic
> 2 Recieved message: This is text message 4 from node 0 from java:/jms/topic/ClusterStateTopic
> 3 Recieved message: This is text message 6 from node 0 from java:/jms/topic/ClusterStateTopic
> 4 Recieved message: This is text message 8 from node 0 from java:/jms/topic/ClusterStateTopic
> 5 error receiving message from node 0
> 6 error receiving message from node 0
> 7 error receiving message from node 0
> 8 error receiving message from node 0
> 9 error receiving message from node 0
> 0 Recieved message: This is text message 0 from node 1 from java:/jms/topic/ClusterStateTopic
> 1 Recieved message: This is text message 1 from node 1 from java:/jms/topic/ClusterStateTopic
> 2 Recieved message: This is text message 2 from node 1 from java:/jms/topic/ClusterStateTopic
> 3 Recieved message: This is text message 3 from node 1 from java:/jms/topic/ClusterStateTopic
> 4 Recieved message: This is text message 4 from node 1 from java:/jms/topic/ClusterStateTopic
> 5 Recieved message: This is text message 5 from node 1 from java:/jms/topic/ClusterStateTopic
> 6 Recieved message: This is text message 6 from node 1 from java:/jms/topic/ClusterStateTopic
> 7 Recieved message: This is text message 7 from node 1 from java:/jms/topic/ClusterStateTopic
> 8 Recieved message: This is text message 8 from node 1 from java:/jms/topic/ClusterStateTopic
> 9 Recieved message: This is text message 9 from node 1 from java:/jms/topic/ClusterStateTopic
> The test program is added and the 2 node names are given as parameters for main.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6269) connector-service resource does not define a module for the classes to load
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-6269?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil commented on WFLY-6269:
-----------------------------------
I've created WFLY-6301 to apply the "global" solution of adding an optional module to WFLY 10.
> connector-service resource does not define a module for the classes to load
> ---------------------------------------------------------------------------
>
> Key: WFLY-6269
> URL: https://issues.jboss.org/browse/WFLY-6269
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
>
> The connector-service resource has only a factory-class attribute and does not specify from which module the class should be loaded.
> {noformat}
> <connector-service name="b"
> factory-class="bar.foo">
> <param name="foo"
> value="${connector.value:bar}"/>
> <param name="bar"
> value="2"/>
> </connector-service>
> {noformat}
> This means that the module defining the class must be a dependency of the org.apache.activemq.artemis module since it's Artemis that currently loads it.
> A module attribute should be added so that the class could be loaded from any module.
> The messaging-activemq subsystem would then be able to load it and pass it to Artemis's ServiceRegistry (similarly to the interceptors).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6301) Add an optional module for classes loaded by ActiveMQ
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-6301?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil updated WFLY-6301:
------------------------------
Summary: Add an optional module for classes loaded by ActiveMQ (was: An an optional module for classes loaded by ActiveMQ)
> Add an optional module for classes loaded by ActiveMQ
> -----------------------------------------------------
>
> Key: WFLY-6301
> URL: https://issues.jboss.org/browse/WFLY-6301
> Project: WildFly
> Issue Type: Enhancement
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Priority: Minor
>
> ActiveMQ Artemis configuration accepts some class definitions for user-specified behaviour (eg connector-services, interceptors, transformers).
> To work in a modular environment, WildFly requires to load the classes from a module and pass it to Artemis (using their ServiceRegistry).
> Not all these resources have been updated to specify such a module (eg transformers and connector-services configuration only specify a class attribute and not a module).
> Currently, the user must modify the org.apache.activemq.artemis module definition to add dependency to the module defining these classes. This breaks patching as the module definition has been manually edited and it is up to the user to undo his changes and reapply them after patching in overlays...
> Adding a module attribute to these resources is a significant management change (adding a new version, new XSD, transformers to previous versions) and should happen on a WFLY minor changes (eg for WFLY 11.x).
> However, we can work around this limitation by adding an _optional_ module (eg named org.apache.activemq.artemis.addons) to the org.apache.activemq.artemis module definition.
> This optional module does not exist by default but it can be created by the user and any classes required by Artemis configuration can be put in it.
> This has the advantage that the org.apache.activemq.artemis module definition is _no longer modified_ if the users needs such classes and patching will work as expected.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (WFLY-6301) An an optional module for classes loaded by ActiveMQ
by Jeff Mesnil (JIRA)
Jeff Mesnil created WFLY-6301:
---------------------------------
Summary: An an optional module for classes loaded by ActiveMQ
Key: WFLY-6301
URL: https://issues.jboss.org/browse/WFLY-6301
Project: WildFly
Issue Type: Enhancement
Components: JMS
Affects Versions: 10.0.0.Final
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Priority: Minor
ActiveMQ Artemis configuration accepts some class definitions for user-specified behaviour (eg connector-services, interceptors, transformers).
To work in a modular environment, WildFly requires to load the classes from a module and pass it to Artemis (using their ServiceRegistry).
Not all these resources have been updated to specify such a module (eg transformers and connector-services configuration only specify a class attribute and not a module).
Currently, the user must modify the org.apache.activemq.artemis module definition to add dependency to the module defining these classes. This breaks patching as the module definition has been manually edited and it is up to the user to undo his changes and reapply them after patching in overlays...
Adding a module attribute to these resources is a significant management change (adding a new version, new XSD, transformers to previous versions) and should happen on a WFLY minor changes (eg for WFLY 11.x).
However, we can work around this limitation by adding an _optional_ module (eg named org.apache.activemq.artemis.addons) to the org.apache.activemq.artemis module definition.
This optional module does not exist by default but it can be created by the user and any classes required by Artemis configuration can be put in it.
This has the advantage that the org.apache.activemq.artemis module definition is _no longer modified_ if the users needs such classes and patching will work as expected.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months