September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-5126) WARN if user tries to set unrealistic io subsystem stack-size

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFCORE-5126?page=com.atlassian.jira.plug... ] Ranabir Chakraborty updated WFCORE-5126: ---------------------------------------- Summary: WARN if user tries to set unrealistic io subsystem stack-size (was: [GSS](7.3.z) WARN if user tries to set unrealistic io subsystem stack-size) > WARN if user tries to set unrealistic io subsystem stack-size > ------------------------------------------------------------- > > Key: WFCORE-5126 > URL: https://issues.redhat.com/browse/WFCORE-5126 > Project: WildFly Core > Issue Type: Enhancement > Components: IO > Reporter: Ranabir Chakraborty > Assignee: Ranabir Chakraborty > Priority: Minor > > The default stack-size for java is 512k , 1M on 64bit. With a simple jsp test, it looks like 150000-200000 bytes of stack would be required at least. > It appears some Java 8 ignores a request to set stack-size=32 bytes but some Java 11 honor the request resulting in java.lang.StackOverflowError. The actual call could potentially be different that ends with java.lang.StackOverflowError. > > {code:java} > [standalone@embedded /] /subsystem=io/worker=default:write-attribute(name=stack-size,value=32) > {"outcome" => "success"} {code} > > {code:java} > <xs:attribute name="stack-size" type="xs:long" default="0"> > <xs:annotation> > <xs:documentation> > <![CDATA[ > The stack size (in bytes) to attempt to use for worker threads. > ]]> > </xs:documentation> > </xs:annotation> > </xs:attribute> {code} > > Possible overflow: > {code:java} > Caused by: java.lang.StackOverflowError > at java.base/java.io.UnixFileSystem.getBooleanAttributes0(Native Method) > at java.base/java.io.UnixFileSystem.getBooleanAttributes(Unknown Source) > at java.base/java.io.File.exists(Unknown Source) > at org.jboss.modules.LocalModuleFinder.parseModuleXmlFile(LocalModuleFinder.java:249) > ... > at java.base/java.lang.Class.forName(Unknown Source) > at io.undertow.jsp@2.0.8.Final-redhat-00001//org.apache.jasper.JspCompilationContext.createCompiler(JspCompilationContext.java:265) > at io.undertow.jsp@2.0.8.Final-redhat-00001//org.apache.jasper.JspCompilationContext.createCompiler(JspCompilationContext.java:244) > {code} > Overflow when using byteman to try to debug: > {code:java} > Caused by: java.lang.StackOverflowError > at java.base/java.lang.StackStreamFactory$AbstractStackWalker.callStackWalk(Native Method) > at java.base/java.lang.StackStreamFactory$AbstractStackWalker.beginStackWalk(Unknown Source) > at java.base/java.lang.StackStreamFactory$AbstractStackWalker.walk(Unknown Source) > at java.base/java.lang.StackWalker.walk(Unknown Source) > at org.jboss.logmanager@2.1.14.Final-redhat-00001//org.jboss.logmanager.JDKSpecific.findCallingClasses(JDKSpecific.java:72) > at org.jboss.logmanager@2.1.14.Final-redhat-00001//org.jboss.logmanager.ClassLoaderLogContextSelector$1.run(ClassLoaderLogContextSelector.java:93) > ... > at org.jboss.as.logging@10.1.7.Final-redhat-00001//org.jboss.as.logging.stdio.LogContextStdioContextSelector.getStdioContext(LogContextStdioContextSelector.java:49) > at org.jboss.stdio@1.1.0.Final-redhat-00001//org.jboss.stdio.StdioContext$2.getDelegate(StdioContext.java:153) > at org.jboss.stdio@1.1.0.Final-redhat-00001//org.jboss.stdio.StdioContext$DelegatingPrintStream.println(StdioContext.java:474) > at org.jboss.byteman.rule.helper.Helper.dotraceln(Helper.java:461) > ... > at java.base/java.lang.Class.forName(Unknown Source) > at io.undertow.jsp@2.0.8.Final-redhat-00001//org.apache.jasper.JspCompilationContext.createCompiler(JspCompilationContext.java:265) > {code} > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5126) [GSS](7.3.z) WARN if user tries to set unrealistic io subsystem stack-size

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFCORE-5126?page=com.atlassian.jira.plug... ] Ranabir Chakraborty moved JBEAP-20170 to WFCORE-5126: ----------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-5126 (was: JBEAP-20170) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: IO (was: IO) Affects Version/s: (was: 7.3.2.GA) Fix Version/s: (was: 7.3.4.GA) > [GSS](7.3.z) WARN if user tries to set unrealistic io subsystem stack-size > -------------------------------------------------------------------------- > > Key: WFCORE-5126 > URL: https://issues.redhat.com/browse/WFCORE-5126 > Project: WildFly Core > Issue Type: Enhancement > Components: IO > Reporter: Ranabir Chakraborty > Assignee: Ranabir Chakraborty > Priority: Minor > > The default stack-size for java is 512k , 1M on 64bit. With a simple jsp test, it looks like 150000-200000 bytes of stack would be required at least. > It appears some Java 8 ignores a request to set stack-size=32 bytes but some Java 11 honor the request resulting in java.lang.StackOverflowError. The actual call could potentially be different that ends with java.lang.StackOverflowError. > > {code:java} > [standalone@embedded /] /subsystem=io/worker=default:write-attribute(name=stack-size,value=32) > {"outcome" => "success"} {code} > > {code:java} > <xs:attribute name="stack-size" type="xs:long" default="0"> > <xs:annotation> > <xs:documentation> > <![CDATA[ > The stack size (in bytes) to attempt to use for worker threads. > ]]> > </xs:documentation> > </xs:annotation> > </xs:attribute> {code} > > Possible overflow: > {code:java} > Caused by: java.lang.StackOverflowError > at java.base/java.io.UnixFileSystem.getBooleanAttributes0(Native Method) > at java.base/java.io.UnixFileSystem.getBooleanAttributes(Unknown Source) > at java.base/java.io.File.exists(Unknown Source) > at org.jboss.modules.LocalModuleFinder.parseModuleXmlFile(LocalModuleFinder.java:249) > ... > at java.base/java.lang.Class.forName(Unknown Source) > at io.undertow.jsp@2.0.8.Final-redhat-00001//org.apache.jasper.JspCompilationContext.createCompiler(JspCompilationContext.java:265) > at io.undertow.jsp@2.0.8.Final-redhat-00001//org.apache.jasper.JspCompilationContext.createCompiler(JspCompilationContext.java:244) > {code} > Overflow when using byteman to try to debug: > {code:java} > Caused by: java.lang.StackOverflowError > at java.base/java.lang.StackStreamFactory$AbstractStackWalker.callStackWalk(Native Method) > at java.base/java.lang.StackStreamFactory$AbstractStackWalker.beginStackWalk(Unknown Source) > at java.base/java.lang.StackStreamFactory$AbstractStackWalker.walk(Unknown Source) > at java.base/java.lang.StackWalker.walk(Unknown Source) > at org.jboss.logmanager@2.1.14.Final-redhat-00001//org.jboss.logmanager.JDKSpecific.findCallingClasses(JDKSpecific.java:72) > at org.jboss.logmanager@2.1.14.Final-redhat-00001//org.jboss.logmanager.ClassLoaderLogContextSelector$1.run(ClassLoaderLogContextSelector.java:93) > ... > at org.jboss.as.logging@10.1.7.Final-redhat-00001//org.jboss.as.logging.stdio.LogContextStdioContextSelector.getStdioContext(LogContextStdioContextSelector.java:49) > at org.jboss.stdio@1.1.0.Final-redhat-00001//org.jboss.stdio.StdioContext$2.getDelegate(StdioContext.java:153) > at org.jboss.stdio@1.1.0.Final-redhat-00001//org.jboss.stdio.StdioContext$DelegatingPrintStream.println(StdioContext.java:474) > at org.jboss.byteman.rule.helper.Helper.dotraceln(Helper.java:461) > ... > at java.base/java.lang.Class.forName(Unknown Source) > at io.undertow.jsp@2.0.8.Final-redhat-00001//org.apache.jasper.JspCompilationContext.createCompiler(JspCompilationContext.java:265) > {code} > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-352) All checks are returned if mp.health.disable-default-procedures=true in META-INF

by Martin Choma (Jira)

[ https://issues.redhat.com/browse/WFWIP-352?page=com.atlassian.jira.plugin... ] Martin Choma commented on WFWIP-352: ------------------------------------ In our testsuite we have 3 examples of using `mp.health.disable-default-procedures` [2] which were introduced by [1]. Are you saying these occurences are ignored? Is it behaviour change with this RFE, or it was there already before? [1] https://github.com/jboss-eap-qe/eap-microprofile-test-suite/pull/206 [2] https://github.com/jboss-eap-qe/eap-microprofile-test-suite/search?q=mp.h... > All checks are returned if mp.health.disable-default-procedures=true in META-INF > -------------------------------------------------------------------------------- > > Key: WFWIP-352 > URL: https://issues.redhat.com/browse/WFWIP-352 > Project: WildFly WIP > Issue Type: Bug > Components: MP Health > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > Attachments: HealthDeprecatedTest.war > > > According to [0] I understand mp.health.disable-default-procedures=true should disable default checks added by RFE https://issues.redhat.com/browse/EAP7-1322. > But we have tests where we configure this property and `boot-errors`, `server-state`, `deployments-status` are returned. > When I set mp.health.disable-default-procedures=true globally by ./standalone.sh -Dmp.health.disable-default-procedures=true it works corectly. Problems seems mp.health.disable-default-procedures is configured through META-INF file in war file. Is this behaviour expected? > [0] https://github.com/wildfly/wildfly/commit/f5bd3daebce865c3215a65454cc2f6d... > [1] https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-microp... > [2] https://github.com/jboss-eap-qe/eap-microprofile-test-suite/blob/058910f9... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-352) All checks are returned if mp.health.disable-default-procedures=true in META-INF

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFWIP-352?page=com.atlassian.jira.plugin... ] Jeff Mesnil commented on WFWIP-352: ----------------------------------- Explained by a note in the community docs: https://github.com/wildfly/wildfly/pull/13397/files#diff-e9dc6f6a10d4a146... > All checks are returned if mp.health.disable-default-procedures=true in META-INF > -------------------------------------------------------------------------------- > > Key: WFWIP-352 > URL: https://issues.redhat.com/browse/WFWIP-352 > Project: WildFly WIP > Issue Type: Bug > Components: MP Health > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > Attachments: HealthDeprecatedTest.war > > > According to [0] I understand mp.health.disable-default-procedures=true should disable default checks added by RFE https://issues.redhat.com/browse/EAP7-1322. > But we have tests where we configure this property and `boot-errors`, `server-state`, `deployments-status` are returned. > When I set mp.health.disable-default-procedures=true globally by ./standalone.sh -Dmp.health.disable-default-procedures=true it works corectly. Problems seems mp.health.disable-default-procedures is configured through META-INF file in war file. Is this behaviour expected? > [0] https://github.com/wildfly/wildfly/commit/f5bd3daebce865c3215a65454cc2f6d... > [1] https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-microp... > [2] https://github.com/jboss-eap-qe/eap-microprofile-test-suite/blob/058910f9... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5183) DMN DT Analysis Validation for output values constraint

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5183?page=com.atlassian.jira.plug... ] Matteo Mortari edited comment on DROOLS-5183 at 9/10/20 3:28 AM: ----------------------------------------------------------------- this is related to [DROOLS-5054]: DMN models made with the DMN editor might contain decision tables where the allowed values are not "cascaded" from the itemDefinition to the allowedValues decision table output. This JIRA solves for the DMN Engine and Validation for semantically valid DMN XML only was (Author: tari_manga): this is related to [DROOLS-5054]: DMN models made with the DMN editor might contain decision tables where the allowed values are not "cascaded" from the itemDefinition to the allowedValues decision table output > DMN DT Analysis Validation for output values constraint > ------------------------------------------------------- > > Key: DROOLS-5183 > URL: https://issues.redhat.com/browse/DROOLS-5183 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.34.0.Final > Reporter: Donato Marrazzo > Assignee: Matteo Mortari > Priority: Minor > Attachments: completeness.dmn > > > from the spec: > {quote}The list of output values is optional. If provided, it is a list restricting output entries to the given list of values.{quote} > the validation does not highlight when if the user enters a wrong value. > Example: > [^completeness.dmn] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5183) DMN DT Analysis Validation for output values constraint

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5183?page=com.atlassian.jira.plug... ] Matteo Mortari commented on DROOLS-5183: ---------------------------------------- this is related to [DROOLS-5054]: DMN models made with the DMN editor might contain decision tables where the allowed values are not "cascaded" from the itemDefinition to the allowedValues decision table output > DMN DT Analysis Validation for output values constraint > ------------------------------------------------------- > > Key: DROOLS-5183 > URL: https://issues.redhat.com/browse/DROOLS-5183 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.34.0.Final > Reporter: Donato Marrazzo > Assignee: Matteo Mortari > Priority: Minor > Attachments: completeness.dmn > > > from the spec: > {quote}The list of output values is optional. If provided, it is a list restricting output entries to the given list of values.{quote} > the validation does not highlight when if the user enters a wrong value. > Example: > [^completeness.dmn] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-352) All checks are returned if mp.health.disable-default-procedures=true in META-INF

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFWIP-352?page=com.atlassian.jira.plugin... ] Jeff Mesnil commented on WFWIP-352: ----------------------------------- The server runtime checks the mp.health.disable-default-procedures when the server is started to determine which server check procedures are installed. This means that the only way to configure this property is using a system property or an environment variable. If a deployment is provided a microprofile-config.properties with that property, it will not be taken into account. This also prevents to have conflicting values in 2 deployments... I'll update the doc to clarify that this property is read at boot time and can only be set using a system property or an environment variable. > All checks are returned if mp.health.disable-default-procedures=true in META-INF > -------------------------------------------------------------------------------- > > Key: WFWIP-352 > URL: https://issues.redhat.com/browse/WFWIP-352 > Project: WildFly WIP > Issue Type: Bug > Components: MP Health > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > Attachments: HealthDeprecatedTest.war > > > According to [0] I understand mp.health.disable-default-procedures=true should disable default checks added by RFE https://issues.redhat.com/browse/EAP7-1322. > But we have tests where we configure this property and `boot-errors`, `server-state`, `deployments-status` are returned. > When I set mp.health.disable-default-procedures=true globally by ./standalone.sh -Dmp.health.disable-default-procedures=true it works corectly. Problems seems mp.health.disable-default-procedures is configured through META-INF file in war file. Is this behaviour expected? > [0] https://github.com/wildfly/wildfly/commit/f5bd3daebce865c3215a65454cc2f6d... > [1] https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-microp... > [2] https://github.com/jboss-eap-qe/eap-microprofile-test-suite/blob/058910f9... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-352) All checks are returned if mp.health.disable-default-procedures=true in META-INF

by Martin Choma (Jira)

[ https://issues.redhat.com/browse/WFWIP-352?page=com.atlassian.jira.plugin... ] Martin Choma updated WFWIP-352: ------------------------------- Steps to Reproduce: * Deploy applicaiton from attachment HealthDeprecatedTest.war, which has mp.health.disable-default-procedures=true configured in META-INF * check operation returns full list of checks {code} [standalone@localhost:9990 /] /subsystem=microprofile-health-smallrye:check { "outcome" => "success", "result" => { "status" => "UP", "checks" => [ { "name" => "deployments-status", "status" => "UP", "data" => {"_DEFAULT___DEFAULT__HealthDeprecatedTest.war" => "OK"} }, { "name" => "boot-errors", "status" => "UP" }, { "name" => "server-state", "status" => "UP", "data" => {"value" => "running"} }, { "name" => "deprecated-health", "status" => "UP", "data" => {"key" => "value"} } ] } } {code} was: * Deploy applicaiton from attachment HealthDeprecatedTest.war, which has mp.health.disable-default-procedures=configured in META-INF * check operation returns full list of checks {code} [standalone@localhost:9990 /] /subsystem=microprofile-health-smallrye:check { "outcome" => "success", "result" => { "status" => "UP", "checks" => [ { "name" => "deployments-status", "status" => "UP", "data" => {"_DEFAULT___DEFAULT__HealthDeprecatedTest.war" => "OK"} }, { "name" => "boot-errors", "status" => "UP" }, { "name" => "server-state", "status" => "UP", "data" => {"value" => "running"} }, { "name" => "deprecated-health", "status" => "UP", "data" => {"key" => "value"} } ] } } {code} > All checks are returned if mp.health.disable-default-procedures=true in META-INF > -------------------------------------------------------------------------------- > > Key: WFWIP-352 > URL: https://issues.redhat.com/browse/WFWIP-352 > Project: WildFly WIP > Issue Type: Bug > Components: MP Health > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > Attachments: HealthDeprecatedTest.war > > > According to [0] I understand mp.health.disable-default-procedures=true should disable default checks added by RFE https://issues.redhat.com/browse/EAP7-1322. > But we have tests where we configure this property and `boot-errors`, `server-state`, `deployments-status` are returned. > When I set mp.health.disable-default-procedures=true globally by ./standalone.sh -Dmp.health.disable-default-procedures=true it works corectly. Problems seems mp.health.disable-default-procedures is configured through META-INF file in war file. Is this behaviour expected? > [0] https://github.com/wildfly/wildfly/commit/f5bd3daebce865c3215a65454cc2f6d... > [1] https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-microp... > [2] https://github.com/jboss-eap-qe/eap-microprofile-test-suite/blob/058910f9... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13822) I am configuring the infinispan cache in my security domain and configure the cache in infinispan subsystem. But when i login the CustomLoginModule stores the password in cache and never expires. This is using jboss 7.1.1Final default cache.

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFLY-13822?page=com.atlassian.jira.plugi... ] Bartosz Baranowski closed WFLY-13822. ------------------------------------- Resolution: Out of Date > I am configuring the infinispan cache in my security domain and configure the cache in infinispan subsystem. But when i login the CustomLoginModule stores the password in cache and never expires. This is using jboss 7.1.1Final default cache. > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-13822 > URL: https://issues.redhat.com/browse/WFLY-13822 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: JBoss AS7 7.1.1.Final > Reporter: ak maurya > Assignee: Bartosz Baranowski > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13822) I am configuring the infinispan cache in my security domain and configure the cache in infinispan subsystem. But when i login the CustomLoginModule stores the password in cache and never expires. This is using jboss 7.1.1Final default cache.

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFLY-13822?page=com.atlassian.jira.plugi... ] Bartosz Baranowski commented on WFLY-13822: ------------------------------------------- As is AS7 7.1.1.Final is archive release and there is no support available. Please update to newer version. > I am configuring the infinispan cache in my security domain and configure the cache in infinispan subsystem. But when i login the CustomLoginModule stores the password in cache and never expires. This is using jboss 7.1.1Final default cache. > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-13822 > URL: https://issues.redhat.com/browse/WFLY-13822 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: JBoss AS7 7.1.1.Final > Reporter: ak maurya > Assignee: Bartosz Baranowski > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 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 September 2020