June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4504) Java Agent using JUL causes JBoss LogManager issues

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4504?page=com.atlassian.jira.plugi... ] James Perkins moved WFLY-10743 to WFCORE-4504: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4504 (was: WFLY-10743) Component/s: Logging Scripts (was: Logging) (was: Scripts) Affects Version/s: (was: 13.0.0.Final) > Java Agent using JUL causes JBoss LogManager issues > --------------------------------------------------- > > Key: WFCORE-4504 > URL: https://issues.jboss.org/browse/WFCORE-4504 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging, Scripts > Reporter: Brad Maxwell > Priority: Major > > To workaround the issue, these steps are required below. It would be better if we could handle this in the scripts or another way such that the user did not have to directly reference the current jboss-logmanager jar. > {code} > JAVA_OPTS="$JAVA_OPTS -Djava.util.logging.manager=org.jboss.logmanager.LogManager" > JAVA_OPTS="$JAVA_OPTS -Xbootclasspath/p:$JBOSS_HOME/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-<version>.jar" > {code} > {code} > if [ "x$JBOSS_MODULES_SYSTEM_PKGS" = "x" ]; then > JBOSS_MODULES_SYSTEM_PKGS="org.jboss.byteman,org.jboss.logmanager" > fi > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4503) A space in $JAVA path causes bad MODULAR_JDK resolution

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4503?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-4503: --------------------------------------- I moved this from https://issues.jboss.org/browse/WFLY-12126 which is what the commit references. I missed the WFLY JIRA referenced in the commit before I merged it. > A space in $JAVA path causes bad MODULAR_JDK resolution > ------------------------------------------------------- > > Key: WFCORE-4503 > URL: https://issues.jboss.org/browse/WFCORE-4503 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Environment: Linux, but it should happen in any environment that uses the bash scripts. > I believe it affects all versions of wildly that started supporting the modular JDK. > Reporter: George Trudeau > Assignee: Jaikiran Pai > Priority: Major > Fix For: 9.0.0.Beta8 > > > When a user setup a JDK in a path containing a space, wildfly yields the following output : > {code} > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /tmp/space test/wildfly-16.0.0.Final > JAVA: /tmp/space test/jdk-11/bin/java > JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > 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.Main.main(Main.java:437) > {code} > The problem lies inside {{bin/common.sh}} : > {code:sh} > setModularJdk() { > $JAVA --add-modules=java.se -version > /dev/null 2>&1 && MODULAR_JDK=true || MODULAR_JDK=false > } > {code} > Since the test fails due to the variable being split, the final $JAVA_OPTS misses options such as {{--add-modules=java.se}}. > The $JAVA variable can be quoted to fix the problem : > {code:sh} > setModularJdk() { > "$JAVA" --add-modules=java.se -version > /dev/null 2>&1 && MODULAR_JDK=true || MODULAR_JDK=false > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4503) A space in $JAVA path causes bad MODULAR_JDK resolution

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4503?page=com.atlassian.jira.plugi... ] James Perkins moved WFLY-12126 to WFCORE-4503: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4503 (was: WFLY-12126) Component/s: Scripts (was: Scripts) Affects Version/s: (was: 16.0.0.Final) (was: 17.0.0.Alpha1) > A space in $JAVA path causes bad MODULAR_JDK resolution > ------------------------------------------------------- > > Key: WFCORE-4503 > URL: https://issues.jboss.org/browse/WFCORE-4503 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Environment: Linux, but it should happen in any environment that uses the bash scripts. > I believe it affects all versions of wildly that started supporting the modular JDK. > Reporter: George Trudeau > Assignee: Jaikiran Pai > Priority: Major > Fix For: 9.0.0.Beta8 > > > When a user setup a JDK in a path containing a space, wildfly yields the following output : > {code} > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /tmp/space test/wildfly-16.0.0.Final > JAVA: /tmp/space test/jdk-11/bin/java > JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > 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.Main.main(Main.java:437) > {code} > The problem lies inside {{bin/common.sh}} : > {code:sh} > setModularJdk() { > $JAVA --add-modules=java.se -version > /dev/null 2>&1 && MODULAR_JDK=true || MODULAR_JDK=false > } > {code} > Since the test fails due to the variable being split, the final $JAVA_OPTS misses options such as {{--add-modules=java.se}}. > The $JAVA variable can be quoted to fix the problem : > {code:sh} > setModularJdk() { > "$JAVA" --add-modules=java.se -version > /dev/null 2>&1 && MODULAR_JDK=true || MODULAR_JDK=false > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12126) A space in $JAVA path causes bad MODULAR_JDK resolution

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-12126?page=com.atlassian.jira.plugin... ] James Perkins reassigned WFLY-12126: ------------------------------------ Assignee: Jaikiran Pai > A space in $JAVA path causes bad MODULAR_JDK resolution > ------------------------------------------------------- > > Key: WFLY-12126 > URL: https://issues.jboss.org/browse/WFLY-12126 > Project: WildFly > Issue Type: Bug > Components: Scripts > Affects Versions: 16.0.0.Final, 17.0.0.Alpha1 > Environment: Linux, but it should happen in any environment that uses the bash scripts. > I believe it affects all versions of wildly that started supporting the modular JDK. > Reporter: George Trudeau > Assignee: Jaikiran Pai > Priority: Major > > When a user setup a JDK in a path containing a space, wildfly yields the following output : > {code} > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /tmp/space test/wildfly-16.0.0.Final > JAVA: /tmp/space test/jdk-11/bin/java > JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > 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.Main.main(Main.java:437) > {code} > The problem lies inside {{bin/common.sh}} : > {code:sh} > setModularJdk() { > $JAVA --add-modules=java.se -version > /dev/null 2>&1 && MODULAR_JDK=true || MODULAR_JDK=false > } > {code} > Since the test fails due to the variable being split, the final $JAVA_OPTS misses options such as {{--add-modules=java.se}}. > The $JAVA variable can be quoted to fix the problem : > {code:sh} > setModularJdk() { > "$JAVA" --add-modules=java.se -version > /dev/null 2>&1 && MODULAR_JDK=true || MODULAR_JDK=false > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4115) [DMN Designer] Included Models - Fix typo in the Included Models tab

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4115?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-4115: ------------------------------------ Description: There's a typo in the Included Models tab: !OR.png|thumbnail! The *of* must be replaced by a *or*. was: There's a typo in the Included Models tab: !OR.png|thumbnail! The *of* must be replaced by a "or". > [DMN Designer] Included Models - Fix typo in the Included Models tab > -------------------------------------------------------------------- > > Key: DROOLS-4115 > URL: https://issues.jboss.org/browse/DROOLS-4115 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: OR.png > > > There's a typo in the Included Models tab: > !OR.png|thumbnail! > The *of* must be replaced by a *or*. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4115) [DMN Designer] Included Models - Fix typo in the Included Models tab

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-4115: --------------------------------------- Summary: [DMN Designer] Included Models - Fix typo in the Included Models tab Key: DROOLS-4115 URL: https://issues.jboss.org/browse/DROOLS-4115 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Guilherme Gomes Assignee: Guilherme Gomes Attachments: OR.png There's a typo in the Included Models tab: !OR.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4115) [DMN Designer] Included Models - Fix typo in the Included Models tab

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4115?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-4115: ------------------------------------ Description: There's a typo in the Included Models tab: !OR.png|thumbnail! The *of* must be replaced by a "or". was: There's a typo in the Included Models tab: !OR.png|thumbnail! > [DMN Designer] Included Models - Fix typo in the Included Models tab > -------------------------------------------------------------------- > > Key: DROOLS-4115 > URL: https://issues.jboss.org/browse/DROOLS-4115 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: OR.png > > > There's a typo in the Included Models tab: > !OR.png|thumbnail! > The *of* must be replaced by a "or". -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12161) The expression for the value of share-prepared-statements does not work in XA datasource .

by Tomas Hofman (Jira)

[ https://issues.jboss.org/browse/WFLY-12161?page=com.atlassian.jira.plugin... ] Tomas Hofman moved JBEAP-17007 to WFLY-12161: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12161 (was: JBEAP-17007) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JCA (was: JCA) Affects Version/s: 17.0.0.Beta1 (was: 7.2.0.GA) > The expression for the value of share-prepared-statements does not work in XA datasource . > ------------------------------------------------------------------------------------------ > > Key: WFLY-12161 > URL: https://issues.jboss.org/browse/WFLY-12161 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 17.0.0.Beta1 > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Priority: Major > > - Although , the "expressions-allowed" is true for "share-prepared-statements" , the expression for it does not work . > -------------------------------------------- > [standalone@localhost:9990 /] /subsystem=datasources/xa-data-source=ExampleXADS:read-resource-description() > "share-prepared-statements" => { > "type" => BOOLEAN, > "description" => "Whether to share prepared statements, i.e. whether asking for same statement twice without closing uses the same underlying prepared statement", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => false, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "all-services" > }, > --------------------------------------------- > - It shows below error if we set expression for share-prepared-statements . > --------------------------------------------- > 18:32:07,698 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 41) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "datasources"), > ("xa-data-source" => "ExampleXADS") > ]): java.lang.IllegalArgumentException > at org.jboss.dmr.ModelValue.asBoolean(ModelValue.java:69) > at org.jboss.dmr.ModelNode.asBoolean(ModelNode.java:324) > at org.jboss.as.connector.subsystems.datasources.DataSourceModelNodeUtil.xaFrom(DataSourceModelNodeUtil.java:292) > at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceAdd.secondRuntimeStep(AbstractDataSourceAdd.java:298) > at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceAdd$1.execute(AbstractDataSourceAdd.java:134) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) > at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > --------------------------------------------- > - However , it works in a non-xa datasource . -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-773) Requirements for Multi-Tenant Pipeline

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-773?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-773: ------------------------------------------ Description: Gathering requirements for the pipeline changes updatream > Requirements for Multi-Tenant Pipeline > --------------------------------------- > > Key: SWSQE-773 > URL: https://issues.jboss.org/browse/SWSQE-773 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Priority: Major > Labels: infrastructure > > Gathering requirements for the pipeline changes updatream -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-773) Requirements for Multi-Tenant Pipeline

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-773?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-773: ------------------------------------------ Description: Gathering requirements for the pipeline to accommodate multi-tenant changes (was: Gathering requirements for the pipeline changes updatream) > Requirements for Multi-Tenant Pipeline > --------------------------------------- > > Key: SWSQE-773 > URL: https://issues.jboss.org/browse/SWSQE-773 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Priority: Major > Labels: infrastructure > > Gathering requirements for the pipeline to accommodate multi-tenant changes -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 June 2019