June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1628) Cannot invoke Java function from DMN on IBM JDK

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1628?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-1628: ------------------------------------- Assignee: Tihomir Surdilovic (was: Edson Tirelli) > Cannot invoke Java function from DMN on IBM JDK > ----------------------------------------------- > > Key: DROOLS-1628 > URL: https://issues.jboss.org/browse/DROOLS-1628 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.0.0.Final > Reporter: Tibor Zimányi > Assignee: Tihomir Surdilovic > Labels: reported-by-qe > Fix For: 7.1.0.Final > > > When running our DMNRuntimeTest.testJavaFunctionContext() and DMNRuntimeTest.testJavaFunctionContext_withErrors() tests on IBM JDK, the tests fail with following outputs [1][2]. > [1] https://gist.github.com/baldimir/66c30176716cb260e49e8b99a281759c > [2] https://gist.github.com/baldimir/03104bef2bd608a32afe85d82c436a08 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1628) Cannot invoke Java function from DMN on IBM JDK

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1628?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-1628: ------------------------------------- Assignee: Edson Tirelli (was: Tihomir Surdilovic) > Cannot invoke Java function from DMN on IBM JDK > ----------------------------------------------- > > Key: DROOLS-1628 > URL: https://issues.jboss.org/browse/DROOLS-1628 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.0.0.Final > Reporter: Tibor Zimányi > Assignee: Edson Tirelli > Labels: reported-by-qe > Fix For: 7.1.0.Final > > > When running our DMNRuntimeTest.testJavaFunctionContext() and DMNRuntimeTest.testJavaFunctionContext_withErrors() tests on IBM JDK, the tests fail with following outputs [1][2]. > [1] https://gist.github.com/baldimir/66c30176716cb260e49e8b99a281759c > [2] https://gist.github.com/baldimir/03104bef2bd608a32afe85d82c436a08 -- 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 resolved WFCORE-3009. -------------------------------------- Resolution: Rejected Thanks for the quick heads up! > 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] (WFCORE-3009) Incorrect path separator added to the end of the ENC_FILE_DIR property when defining a vault in Windows

by Matthew Casperson (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3009?page=com.atlassian.jira.plugi... ] Matthew Casperson commented on WFCORE-3009: ------------------------------------------- Sorry, this was actually because of an unrelated problem. The slash was inserted because of a bad script, and wildfly was just happy to work around it. This can be closed. > 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] (DROOLS-1626) Kie-server management: Pressing upgrade throws an error

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1626?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-1626: ------------------------------------- Assignee: Guilherme Carreiro (was: Edson Tirelli) > Kie-server management: Pressing upgrade throws an error > ------------------------------------------------------- > > Key: DROOLS-1626 > URL: https://issues.jboss.org/browse/DROOLS-1626 > Project: Drools > Issue Type: Bug > Affects Versions: 7.0.0.Final > Reporter: Toni Rikkola > Assignee: Guilherme Carreiro > > I have kie-server and workbench running on the same Wildfly. > The project deploys to kie-server correctly and runs ok. > Using the KIE workbench kie-server management. > When I upgrade I get an error "a.c is undefined". Most likely there is an NPE in the client code. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2199) JDBC_PING cluster doesn't handle shutdown members

by Douglas Adams (JIRA)

Douglas Adams created JGRP-2199: ----------------------------------- Summary: JDBC_PING cluster doesn't handle shutdown members Key: JGRP-2199 URL: https://issues.jboss.org/browse/JGRP-2199 Project: JGroups Issue Type: Bug Affects Versions: 4.0 Reporter: Douglas Adams Assignee: Bela Ban Attachments: file-ping.xml, jdbc-ping.xml, stuck_starting_up.log FILE_PING and JDBC_PING have different behavior when a cluster's coordinator stops. With FILE_PING the coordinator will delete the whole cluster's file on shutdown of the coordinator. JDBC_PING does not do this and reveals a problematic flaw in how node's are handled on shutdown. When I added my own logging to the source of these files I observed that they're both continuously writing to the database/file all of the members because {{write()}} is called very frequently. --- Current behavior: GIVEN a cluster of JDBC_PING registered nodes WHEN a node shuts down THEN it removes itself from the database table AND the coordinator almost immediately re-adds the shut down member to the table because of the {{List<PingData>}} sent to write() GIVEN a cluster of JDBC_PING registered nodes has only the coordinator left WHEN the coordinator shuts down THEN the coordinator removes itself from the database and because there's no coordinator left the database shows a list of only the 'members' with no coordinator GIVEN a cluster of JDBC_PING registered nodes WHEN the coordinator shuts down or crashes and does not have time to remove itself from the database THEN the next node to start will never finish negotiating membership with the cluster because a phantom coordinator still exists (see attachement: stuck_starting_up.log) --- I expected the behavior between JDBC_PING and FILE_PING to remain consistent -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8996) ł

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-8996?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-8996: ----------------------------------- Keep up the good work everyone! > ł > - > > 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] (WFLY-8984) Fix tests which currently fail with -Dwildfly.tmp.enable.elytron.profile.tests

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-8984?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-8984: ----------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/10245 > Fix tests which currently fail with -Dwildfly.tmp.enable.elytron.profile.tests > ------------------------------------------------------------------------------- > > Key: WFLY-8984 > URL: https://issues.jboss.org/browse/WFLY-8984 > Project: WildFly > Issue Type: Task > Components: Security > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Blocker > > Several tests fail with -Dwildfly.tmp.enable.elytron.profile.tests=true and -Delytron as seen in > https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterElytron > Having a cursory glance at the build log there also appears to be some tests taking about 10 minutes before failing -- 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 commented on WFCORE-3007: ------------------------------------------ Following is the complete set of ops whose metadata I am correcting as part of this fix: cache-manager:clear-cache key-store:load key-store:store key-store:read-aliases key-store:read-alias key-store:remove-alias ldap-key-store:read-aliases ldap-key-store:read-alias ldap-key-store:remove-alias filtering-key-store:read-aliases filtering-key-store:read-alias filtering-key-store:remove-alias properties-realm:load key-manager:init trust-manager:reload-certificate-revocation-list > 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 > Assignee: Brian Stansberry > 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] (WFCORE-3009) Incorrect path separator added to the end of the ENC_FILE_DIR property when defining a vault in Windows

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3009?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-3009: ---------------------------------------------- I am surprised that "\" characters are properly handled in the file path. They should be escaped: e.g.: c:\\x\\y\\...). You can look at JBEAP-4412 What does echo-dmr prints for: echo-dmr <the operation> ? Thanks. > 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

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