June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1633) Race condition when forcing immediate jitting

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1633: ----------------------------------- Summary: Race condition when forcing immediate jitting Key: DROOLS-1633 URL: https://issues.jboss.org/browse/DROOLS-1633 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco Setting the jitting threshold to 0 and then forcing immediate constraint jitting can cause a race condition in the jitting process itself that may in turn lead to a wrong constraint evaluation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3009) Incorrect path separator added to the end of the ENC_FILE_DIR property when defining a vault in Windows

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3009?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3009: ------------------------------------- Component/s: CLI I'm adding the CLI component to this as I see nothing in the server side code that would change the value of this vault-option. The vault-option attribute is an opaque key/value map to the server side management code, which just takes the attribute's DMR value, does a simple generic conversion into a Map<String, String> and passes that to the PicketBox code. [~jfdenise] might the CLI be modifying this value client side? > Incorrect path separator added to the end of the ENC_FILE_DIR property when defining a vault in Windows > ------------------------------------------------------------------------------------------------------- > > Key: WFCORE-3009 > URL: https://issues.jboss.org/browse/WFCORE-3009 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Domain Management, Security > Affects Versions: 3.0.0.Beta27 > Reporter: Matthew Casperson > Priority: Minor > > Executing this command: > {code:java} > /host=master/core-service=vault:add(vault-options={"KEYSTORE_URL" => "C:\wildfly_slave\wildfly-11.0.0.Alpha1\domain\configuration\keystore.vault", "KEYSTORE_PASSWORD" => "Password01", "KEYSTORE_ALIAS" => "vault", "SALT" => "12345678", "ITERATION_COUNT" => "50", "ENC_FILE_DIR" => "C:\wildfly_slave\wildfly-11.0.0.Alpha1\domain\configuration\vault"}) > {code} > Will result in this element in the XML: > {code:xml} > </extensions> > <vault> > <vault-option name="KEYSTORE_URL" value="C:\wildfly_slave\wildfly-11.0.0.Alpha1\domain\configuration\keystore.vault"/> > <vault-option name="KEYSTORE_PASSWORD" value="MASK-223/wEo1GLELe8EuQa5u20"/> > <vault-option name="KEYSTORE_ALIAS" value="vault"/> > <vault-option name="SALT" value="12345678"/> > <vault-option name="ITERATION_COUNT" value="50"/> > <vault-option name="ENC_FILE_DIR" value="C:\wildfly_slave\wildfly-11.0.0.Alpha1\domain\configuration\vault/"/> > </vault> > {code} > Note the incorrect slash on the end of the ENC_FILE_DIR option. I assume this value is being normalised to include a trailing slash, but the wrong character is being selected on a Windows system. > WildFly seems quite happy with this incorrect character, but external tools reading this path have to account for the unexpected value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8996) ł

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8996?page=com.atlassian.jira.plugin.... ] Brian Stansberry closed WFLY-8996. ---------------------------------- Resolution: Done > ł > - > > Key: WFLY-8996 > URL: https://issues.jboss.org/browse/WFLY-8996 > Project: WildFly > Issue Type: Bug > Reporter: Jörg Bäsner > Assignee: Jason Greene > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3009) Incorrect path separator added to the end of the ENC_FILE_DIR property when defining a vault in Windows

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3009?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-8993 to WFCORE-3009: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-3009 (was: WFLY-8993) Affects Version/s: 3.0.0.Beta27 (was: 11.0.0.Alpha1) > Incorrect path separator added to the end of the ENC_FILE_DIR property when defining a vault in Windows > ------------------------------------------------------------------------------------------------------- > > Key: WFCORE-3009 > URL: https://issues.jboss.org/browse/WFCORE-3009 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 3.0.0.Beta27 > Reporter: Matthew Casperson > Assignee: Jason Greene > Priority: Minor > > Executing this command: > {code:java} > /host=master/core-service=vault:add(vault-options={"KEYSTORE_URL" => "C:\wildfly_slave\wildfly-11.0.0.Alpha1\domain\configuration\keystore.vault", "KEYSTORE_PASSWORD" => "Password01", "KEYSTORE_ALIAS" => "vault", "SALT" => "12345678", "ITERATION_COUNT" => "50", "ENC_FILE_DIR" => "C:\wildfly_slave\wildfly-11.0.0.Alpha1\domain\configuration\vault"}) > {code} > Will result in this element in the XML: > {code:xml} > </extensions> > <vault> > <vault-option name="KEYSTORE_URL" value="C:\wildfly_slave\wildfly-11.0.0.Alpha1\domain\configuration\keystore.vault"/> > <vault-option name="KEYSTORE_PASSWORD" value="MASK-223/wEo1GLELe8EuQa5u20"/> > <vault-option name="KEYSTORE_ALIAS" value="vault"/> > <vault-option name="SALT" value="12345678"/> > <vault-option name="ITERATION_COUNT" value="50"/> > <vault-option name="ENC_FILE_DIR" value="C:\wildfly_slave\wildfly-11.0.0.Alpha1\domain\configuration\vault/"/> > </vault> > {code} > Note the incorrect slash on the end of the ENC_FILE_DIR option. I assume this value is being normalised to include a trailing slash, but the wrong character is being selected on a Windows system. > WildFly seems quite happy with this incorrect character, but external tools reading this path have to account for the unexpected value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3009) Incorrect path separator added to the end of the ENC_FILE_DIR property when defining a vault in Windows

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3009?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-3009: ---------------------------------------- Component/s: Domain Management Security Assignee: (was: Jason Greene) > Incorrect path separator added to the end of the ENC_FILE_DIR property when defining a vault in Windows > ------------------------------------------------------------------------------------------------------- > > Key: WFCORE-3009 > URL: https://issues.jboss.org/browse/WFCORE-3009 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 3.0.0.Beta27 > Reporter: Matthew Casperson > Priority: Minor > > Executing this command: > {code:java} > /host=master/core-service=vault:add(vault-options={"KEYSTORE_URL" => "C:\wildfly_slave\wildfly-11.0.0.Alpha1\domain\configuration\keystore.vault", "KEYSTORE_PASSWORD" => "Password01", "KEYSTORE_ALIAS" => "vault", "SALT" => "12345678", "ITERATION_COUNT" => "50", "ENC_FILE_DIR" => "C:\wildfly_slave\wildfly-11.0.0.Alpha1\domain\configuration\vault"}) > {code} > Will result in this element in the XML: > {code:xml} > </extensions> > <vault> > <vault-option name="KEYSTORE_URL" value="C:\wildfly_slave\wildfly-11.0.0.Alpha1\domain\configuration\keystore.vault"/> > <vault-option name="KEYSTORE_PASSWORD" value="MASK-223/wEo1GLELe8EuQa5u20"/> > <vault-option name="KEYSTORE_ALIAS" value="vault"/> > <vault-option name="SALT" value="12345678"/> > <vault-option name="ITERATION_COUNT" value="50"/> > <vault-option name="ENC_FILE_DIR" value="C:\wildfly_slave\wildfly-11.0.0.Alpha1\domain\configuration\vault/"/> > </vault> > {code} > Note the incorrect slash on the end of the ENC_FILE_DIR option. I assume this value is being normalised to include a trailing slash, but the wrong character is being selected on a Windows system. > WildFly seems quite happy with this incorrect character, but external tools reading this path have to account for the unexpected value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3008) Server started with blocking=true times out only on a slave host

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3008?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3008: ------------------------------------------ The system property in domain.xml doesn't affect the function of the Host Controllers including the master DC. Did you pass the property to DC as well by including -Djboss.as.management.blocking.timeout=xxx in domain.conf? > Server started with blocking=true times out only on a slave host > ---------------------------------------------------------------- > > Key: WFCORE-3008 > URL: https://issues.jboss.org/browse/WFCORE-3008 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.2.0.Final > Reporter: Osamu Nagano > Assignee: Brian Stansberry > Attachments: repro.zip > > > We use system property {{jboss.as.management.blocking.timeout}} for a slow starting server to avoid a timeout on startup. It works for a server on the master host-controller but doesn't work a server on a slave host. > Suppose a heavy application, for example, sleeping more than 300 seconds in {{ServletContext#contextInitialized()}}, is deployed and system property {{jboss.as.management.blocking.timeout}} is set in domain.xml to avoid timeout. Under the following domain configuration, {{server-one}} fails to start if {{blocking=true}} is specified. > * master > ** server-zero:start(blocking=true) => Success > * slave > ** server-one:start(blocking=true) => Fail > {code} > [domain@localhost:9990 /] /host=slave/server-config=server-one:start(blocking=true) > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "WFLYCTL0409: Execution of operation 'start' on remote process at address '[(\"host\" => \"slave\")]' timed out after 305000 ms while awaiting initial response; remote process has been notified to terminate operation", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3008) Server started with blocking=true times out only on a slave host

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3008?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-8994 to WFCORE-3008: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-3008 (was: WFLY-8994) Component/s: Domain Management (was: Domain Management) Affects Version/s: 2.2.0.Final (was: 10.1.0.Final) > Server started with blocking=true times out only on a slave host > ---------------------------------------------------------------- > > Key: WFCORE-3008 > URL: https://issues.jboss.org/browse/WFCORE-3008 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.2.0.Final > Reporter: Osamu Nagano > Assignee: Brian Stansberry > Attachments: repro.zip > > > We use system property {{jboss.as.management.blocking.timeout}} for a slow starting server to avoid a timeout on startup. It works for a server on the master host-controller but doesn't work a server on a slave host. > Suppose a heavy application, for example, sleeping more than 300 seconds in {{ServletContext#contextInitialized()}}, is deployed and system property {{jboss.as.management.blocking.timeout}} is set in domain.xml to avoid timeout. Under the following domain configuration, {{server-one}} fails to start if {{blocking=true}} is specified. > * master > ** server-zero:start(blocking=true) => Success > * slave > ** server-one:start(blocking=true) => Fail > {code} > [domain@localhost:9990 /] /host=slave/server-config=server-one:start(blocking=true) > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "WFLYCTL0409: Execution of operation 'start' on remote process at address '[(\"host\" => \"slave\")]' timed out after 305000 ms while awaiting initial response; remote process has been notified to terminate operation", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3007) some xxx-realm operations should be marked runtime-only

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3007?page=com.atlassian.jira.plugi... ] Brian Stansberry moved JBEAP-11791 to WFCORE-3007: -------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3007 (was: JBEAP-11791) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Domain Management Security (was: Domain Management) (was: Security) Affects Version/s: (was: 7.1.0.ER1) > some xxx-realm operations should be marked runtime-only > ------------------------------------------------------- > > Key: WFCORE-3007 > URL: https://issues.jboss.org/browse/WFCORE-3007 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Reporter: Martin Simka > Priority: Minor > > some xxx-realm operations should be marked runtime-only. Their handlers extends ElytronRuntimeOnlyHandler and they don't seem to change anything in model. > properties-realm:load > caching-realm:clear-cache > {code} > [domain@localhost:9990 /] /profile=default/subsystem=elytron/properties-realm=ApplicationRealm:read-operation-description(name=load > { > "outcome" => "success", > "result" => { > "operation-name" => "load", > "description" => "Reload the properties files from the file system.", > "request-properties" => {}, > "reply-properties" => {}, > "read-only" => false, > "runtime-only" => false > } > } > [domain@localhost:9990 /] /profile=default/subsystem=elytron/caching-realm=test:read-operation-description(name=clear-cache > { > "outcome" => "success", > "result" => { > "operation-name" => "clear-cache", > "description" => "Removes all entries from the cache.", > "request-properties" => {}, > "reply-properties" => {}, > "read-only" => false, > "runtime-only" => false > } > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1609) Augment FEEL AST node at compilation with return type

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1609?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1609: ----------------------------------- Sprint: 2017 Week 24-25, 2017 Week 26-27 (was: 2017 Week 24-25) > Augment FEEL AST node at compilation with return type > ----------------------------------------------------- > > Key: DROOLS-1609 > URL: https://issues.jboss.org/browse/DROOLS-1609 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Minor > > This is needed so to be able to determine the result of a boxed function at compile time, in turn to be able at compile time to determine a valid compilation without error of a BKM for instance. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1630) DMN support during incremental KieContainer upgrade

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1630?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1630: ----------------------------------- Sprint: 2017 Week 24-25, 2017 Week 26-27 (was: 2017 Week 24-25) > DMN support during incremental KieContainer upgrade > --------------------------------------------------- > > Key: DROOLS-1630 > URL: https://issues.jboss.org/browse/DROOLS-1630 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Critical > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 June 2017