November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4211) Embedded container does not work without the JVM being launched with java.se module on Java 11

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4211?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4211: ---------------------------------- Issue Type: Task (was: Bug) > Embedded container does not work without the JVM being launched with java.se module on Java 11 > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-4211 > URL: https://issues.jboss.org/browse/WFCORE-4211 > Project: WildFly Core > Issue Type: Task > Components: Embedded > Reporter: James Perkins > Priority: Major > Labels: Documentation, Java11 > > With the embedded API the container can't be started on Java 11 without the {{--add-module=java.se}} argument being added to the JVM. There may not be a way to solve this, but it should likely at lest be documented. If this becomes just a documentation issue then the type should likely be changed to "Task". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4211) Embedded container does not work without the JVM being launched with java.se module on Java 11

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4211?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4211: ---------------------------------- Labels: Documentation Java11 (was: Java11) > Embedded container does not work without the JVM being launched with java.se module on Java 11 > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-4211 > URL: https://issues.jboss.org/browse/WFCORE-4211 > Project: WildFly Core > Issue Type: Task > Components: Embedded > Reporter: James Perkins > Priority: Major > Labels: Documentation, Java11 > > With the embedded API the container can't be started on Java 11 without the {{--add-module=java.se}} argument being added to the JVM. There may not be a way to solve this, but it should likely at lest be documented. If this becomes just a documentation issue then the type should likely be changed to "Task". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11322) RemoteStatefulEJBConcurrentFailoverTestCase is unreliable

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-11322: --------------------------------------- Summary: RemoteStatefulEJBConcurrentFailoverTestCase is unreliable Key: WFLY-11322 URL: https://issues.jboss.org/browse/WFLY-11322 Project: WildFly Issue Type: Bug Components: Clustering Reporter: Brian Stansberry Assignee: Paul Ferraro Test is failing regularly. https://ci.wildfly.org/project.html?projectId=WF&buildTypeId=&tab=testDet... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4211) Embedded container does not work without the JVM being launched with java.se module on Java 11

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4211?page=com.atlassian.jira.plugi... ] James Perkins reassigned WFCORE-4211: ------------------------------------- Assignee: James Perkins > Embedded container does not work without the JVM being launched with java.se module on Java 11 > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-4211 > URL: https://issues.jboss.org/browse/WFCORE-4211 > Project: WildFly Core > Issue Type: Task > Components: Embedded > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Labels: Documentation, Java11 > > With the embedded API the container can't be started on Java 11 without the {{--add-module=java.se}} argument being added to the JVM. There may not be a way to solve this, but it should likely at lest be documented. If this becomes just a documentation issue then the type should likely be changed to "Task". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4211) Embedded container does not work without the JVM being launched with java.se module on Java 11

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4211?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-4211: --------------------------------------- After I thought about this for a bit I agree it's not a bug and just something we need to document. There's not we can do in WildFly itself. > Embedded container does not work without the JVM being launched with java.se module on Java 11 > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-4211 > URL: https://issues.jboss.org/browse/WFCORE-4211 > Project: WildFly Core > Issue Type: Task > Components: Embedded > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Labels: Documentation, Java11 > > With the embedded API the container can't be started on Java 11 without the {{--add-module=java.se}} argument being added to the JVM. There may not be a way to solve this, but it should likely at lest be documented. If this becomes just a documentation issue then the type should likely be changed to "Task". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4211) Embedded container does not work without the JVM being launched with java.se module on Java 11

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4211?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-4211: --------------------------------------- The issue is really MODULES-372. I guess this could just be a documentation task. However you can boot a JVM on Java 11 without the {{--add-module=java.se}} argument and it will work until it reaches the {{EmbeddedProcessFactory.setupVfsModule()}}. That's the only argument I have for it being a bug. That's admittedly a bit of a soft argument :) {code} Exception in thread "main" java.lang.RuntimeException: WFLYEMB0014: Cannot load module org.jboss.vfs from: local module loader @75329a49 (finder: local module finder @161479c6 (roots: /home/jperkins/servers/wildfly-14.0.1.Final/modules,/home/jperkins/servers/wildfly-14.0.1.Final/modules/system/layers/base)) at org.wildfly.core.embedded.EmbeddedProcessFactory.setupVfsModule(EmbeddedProcessFactory.java:299) at org.wildfly.core.embedded.EmbeddedProcessFactory.createStandaloneServer(EmbeddedProcessFactory.java:154) at com.jamezp.test.Main.main(Main.java:161) Caused by: org.jboss.modules.ModuleNotFoundException: java.se at org.jboss.modules.Module.addPaths(Module.java:1266) at org.jboss.modules.Module.link(Module.java:1622) at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:280) at org.wildfly.core.embedded.EmbeddedProcessFactory.setupVfsModule(EmbeddedProcessFactory.java:297) ... 2 more {code} > Embedded container does not work without the JVM being launched with java.se module on Java 11 > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-4211 > URL: https://issues.jboss.org/browse/WFCORE-4211 > Project: WildFly Core > Issue Type: Bug > Components: Embedded > Reporter: James Perkins > Priority: Major > Labels: Java11 > > With the embedded API the container can't be started on Java 11 without the {{--add-module=java.se}} argument being added to the JVM. There may not be a way to solve this, but it should likely at lest be documented. If this becomes just a documentation issue then the type should likely be changed to "Task". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4211) Embedded container does not work without the JVM being launched with java.se module on Java 11

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4211?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-4211: ------------------------------------------ I don't see how this can be regarded as a bug, except if you want to treat lack of doc coverage as a bug. Running WildFly with JDK 11 requires passing --add-module=java.se to the JVM and that's not something we control. > Embedded container does not work without the JVM being launched with java.se module on Java 11 > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-4211 > URL: https://issues.jboss.org/browse/WFCORE-4211 > Project: WildFly Core > Issue Type: Bug > Components: Embedded > Reporter: James Perkins > Priority: Major > Labels: Java11 > > With the embedded API the container can't be started on Java 11 without the {{--add-module=java.se}} argument being added to the JVM. There may not be a way to solve this, but it should likely at lest be documented. If this becomes just a documentation issue then the type should likely be changed to "Task". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11321) Document the "Arbitrary Descriptors" we use in our attribute definitions

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11321?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-11321: ----------------------------------------- [~ehugonnet] I assigned this to you because IIRC you were involved with the key ones we use a lot, like "attached-streams" and "filesystem-path". > Document the "Arbitrary Descriptors" we use in our attribute definitions > ------------------------------------------------------------------------ > > Key: WFLY-11321 > URL: https://issues.jboss.org/browse/WFLY-11321 > Project: WildFly > Issue Type: Enhancement > Components: Documentation, Management > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Priority: Minor > > Over the years we've added some commonly used "arbitrary descriptors" for management attributes and params. Cover these in the docs at [1]. Finding uses of SimpleAttributeDefinitionBuilder.addArbitraryDescriptor is a good way to identify these. Perhaps not all uses of that should be documented, but the ones that represent a standard way we want to handle certain things should be. > [1] https://github.com/wildfly/wildfly/blame/master/docs/src/main/asciidoc/_a... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11321) Document the "Arbitrary Descriptors" we use in our attribute definitions

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-11321: --------------------------------------- Summary: Document the "Arbitrary Descriptors" we use in our attribute definitions Key: WFLY-11321 URL: https://issues.jboss.org/browse/WFLY-11321 Project: WildFly Issue Type: Enhancement Components: Documentation, Management Reporter: Brian Stansberry Assignee: ehsavoie Hugonnet Over the years we've added some commonly used "arbitrary descriptors" for management attributes and params. Cover these in the docs at [1]. Finding uses of SimpleAttributeDefinitionBuilder.addArbitraryDescriptor is a good way to identify these. Perhaps not all uses of that should be documented, but the ones that represent a standard way we want to handle certain things should be. [1] https://github.com/wildfly/wildfly/blame/master/docs/src/main/asciidoc/_a... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-404) Consumer Job For Istio Trigger

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-404?page=com.atlassian.jira.plugin.... ] Matt Mahoney commented on SWSQE-404: ------------------------------------ Completed Jenkins job: http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/mb-consumer-mais... Note, to fully enable, remote Topic Name "DELETEME", so that the job triggers. > Consumer Job For Istio Trigger > ------------------------------ > > Key: SWSQE-404 > URL: https://issues.jboss.org/browse/SWSQE-404 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Major > > Once Istio QE creates the Msg Bus Trigger, create a consumer job that will in turn run the needed Kiali jobs/tests. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 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 2018