October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-452) New Jenkins Slave For Jaeger Jobs

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-452?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-452: ------------------------------- Sprint: Kiali Sprint #12 (was: Kiali Sprint #12) > New Jenkins Slave For Jaeger Jobs > --------------------------------- > > Key: SWSQE-452 > URL: https://issues.jboss.org/browse/SWSQE-452 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Michael Foley > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-413) Checker Needs To 'Ping' Routes

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-413?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-413: ------------------------------- Sprint: Kiali Sprint #11, Kiali Sprint #12 (was: Kiali Sprint #11) > Checker Needs To 'Ping' Routes > ------------------------------ > > Key: SWSQE-413 > URL: https://issues.jboss.org/browse/SWSQE-413 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Sunil kondkar > Priority: Major > > The 'Checker' script needs to ping routes to ensure applications are not only deployed, but also available to the user. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3090) KieScanner does not work as expected

by Ales Dolecek (Jira)

[ https://issues.jboss.org/browse/DROOLS-3090?page=com.atlassian.jira.plugi... ] Ales Dolecek updated DROOLS-3090: --------------------------------- Attachment: spring.xml kmodule.xml > KieScanner does not work as expected > ------------------------------------ > > Key: DROOLS-3090 > URL: https://issues.jboss.org/browse/DROOLS-3090 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.8.0.Final > Reporter: Ales Dolecek > Assignee: Mario Fusco > Priority: Major > Attachments: kmodule.xml, spring.xml > > > We have published nee version of rules: > {noformat} > 2018-10-09 10:44:58,785 INFO [Timer-2][] ScannerListener Knowledge base scanner SCANNING > 2018-10-09 10:44:59,019 INFO [Timer-2][] ScannerListener Knowledge base scanner UPDATING > 2018-10-09 10:45:00,236 INFO [Timer-2][] KieRepositoryImpl KieModule was added: ZipKieModule[releaseId=cz.dimensiondata.o2:offline-rules:0.0.20,file=F:\GCTI8\assign_manager_2\repository\cz\dimensiondata\o2\offline-rules\0.0.20\offline-rules-0.0.20.jar] > 2018-10-09 10:45:00,345 INFO [Timer-2][] KieScanner The following artifacts have been updated: {cz.dimensiondata.o2:offline-rules:0.0.19=cz.dimensiondata.o2:offline-rules:jar:0.0.20} > 2018-10-09 10:45:00,345 INFO [Timer-2][] ScannerListener Knowledge base scanner RUNNING > 2018-10-09 10:45:00,345 INFO [Timer-2][] ScannerListener Knowledge base scanner RUNNING > {noformat} > As you can see the jar got downloaded to local M2 repository and replace. Yet drools still uses old rules. > We have 3 artefacts: > offline-facts - with classes inserted into operation memory > offline-rules - with rules in 1 DRL file and 2 XLSX file > offline-server - with the application code > offline-server depend on offline-facs (so it can create new insances) > offline-rules depend on offline-facts as well, but with provided scope (so the one on classpath is used) > I have found that Maven has its own caching mechanism so even if new version is published it wont check remote repository more ften than once a day. This can be solved by setting update policy to always. > {code} > <repositories> > <repository> > <id>public</id> > <name>Public Repositories</name> > <url>https://example.org/nexus/content/groups/public/</url> > <releases> > <updatePolicy>always</updatePolicy> > </releases> > <snapshots> > <updatePolicy>always</updatePolicy> > </snapshots> > </repository> > </repositories> > {code} > Everything seems configred correctly. Fragments of spring configuration are added. > I'm bit confused what the message: > {code} > The following artifacts have been updated: {cz.dimensiondata.o2:offline-rules:0.0.19=cz.dimensiondata.o2:offline-rules:jar:0.0.20} > {code} > actually means. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3090) KieScanner does not work as expected

by Ales Dolecek (Jira)

Ales Dolecek created DROOLS-3090: ------------------------------------ Summary: KieScanner does not work as expected Key: DROOLS-3090 URL: https://issues.jboss.org/browse/DROOLS-3090 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.8.0.Final Reporter: Ales Dolecek Assignee: Mario Fusco We have published nee version of rules: {noformat} 2018-10-09 10:44:58,785 INFO [Timer-2][] ScannerListener Knowledge base scanner SCANNING 2018-10-09 10:44:59,019 INFO [Timer-2][] ScannerListener Knowledge base scanner UPDATING 2018-10-09 10:45:00,236 INFO [Timer-2][] KieRepositoryImpl KieModule was added: ZipKieModule[releaseId=cz.dimensiondata.o2:offline-rules:0.0.20,file=F:\GCTI8\assign_manager_2\repository\cz\dimensiondata\o2\offline-rules\0.0.20\offline-rules-0.0.20.jar] 2018-10-09 10:45:00,345 INFO [Timer-2][] KieScanner The following artifacts have been updated: {cz.dimensiondata.o2:offline-rules:0.0.19=cz.dimensiondata.o2:offline-rules:jar:0.0.20} 2018-10-09 10:45:00,345 INFO [Timer-2][] ScannerListener Knowledge base scanner RUNNING 2018-10-09 10:45:00,345 INFO [Timer-2][] ScannerListener Knowledge base scanner RUNNING {noformat} As you can see the jar got downloaded to local M2 repository and replace. Yet drools still uses old rules. We have 3 artefacts: offline-facts - with classes inserted into operation memory offline-rules - with rules in 1 DRL file and 2 XLSX file offline-server - with the application code offline-server depend on offline-facs (so it can create new insances) offline-rules depend on offline-facts as well, but with provided scope (so the one on classpath is used) I have found that Maven has its own caching mechanism so even if new version is published it wont check remote repository more ften than once a day. This can be solved by setting update policy to always. {code} <repositories> <repository> <id>public</id> <name>Public Repositories</name> <url>https://example.org/nexus/content/groups/public/</url> <releases> <updatePolicy>always</updatePolicy> </releases> <snapshots> <updatePolicy>always</updatePolicy> </snapshots> </repository> </repositories> {code} Everything seems configred correctly. Fragments of spring configuration are added. I'm bit confused what the message: {code} The following artifacts have been updated: {cz.dimensiondata.o2:offline-rules:0.0.19=cz.dimensiondata.o2:offline-rules:jar:0.0.20} {code} actually means. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3089) ThreadSafeTrackableTimeJobFactoryManager for default

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3089?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-3089: -------------------------------- Sprint: 2018 Week 39-41 > ThreadSafeTrackableTimeJobFactoryManager for default > ---------------------------------------------------- > > Key: DROOLS-3089 > URL: https://issues.jboss.org/browse/DROOLS-3089 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 7.12.0.Final > Reporter: Toshiya Kobayashi > Assignee: Mario Fusco > Priority: Major > Labels: support > > By default, TrackableTimeJobFactoryManager is set by SessionConfigurationImpl. > https://github.com/kiegroup/drools/blob/7.11.0.Final/drools-core/src/main... > If users access a ksession via multiple threads, it would potentially hit a HashMap concurrency issue (e.g. https://stackoverflow.com/questions/22944918/why-does-the-code-hang-with-...). > ThreadSafeTrackableTimeJobFactoryManager is bundled for multi-thread use. You can use it by > Drools 7: > {noformat} > System.setProperty("drools.timerJobFactory", "thread_safe_trackable"); > {noformat} > Drools 6.3+: > {noformat} > KieSessionConfiguration kconf = KnowledgeBaseFactory.newKnowledgeSessionConfiguration(); > ((org.drools.core.SessionConfiguration)kconf).setTimerJobFactoryType( TimerJobFactoryType.THREAD_SAFE_TRACKABLE ); > KieSession ksession = kContainer.newKieSession("ksession-name", kconf); > {noformat} > However, it's better to make ThreadSafeTrackableTimeJobFactoryManager default because "Suddenly hitting an issue in production" is significant than "small overhead by ConcurrentHashMap". (Generally, users are not very conscious about "it is accessed by multi-threads or not") -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2729) KieScanner tries to read test dependencies

by Ales Dolecek (Jira)

[ https://issues.jboss.org/browse/DROOLS-2729?page=com.atlassian.jira.plugi... ] Ales Dolecek commented on DROOLS-2729: -------------------------------------- Any chance to progres with this? BTW: If you fixed this issue you would not have to hack jdk dependency in DROOLS-2773. In the comments you wrote you do not know how it got in the dependency list in first place. Well - it is because the incorrect way you lookup dependencies as described in this issue. > KieScanner tries to read test dependencies > ------------------------------------------ > > Key: DROOLS-2729 > URL: https://issues.jboss.org/browse/DROOLS-2729 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.8.0.Final > Reporter: Ales Dolecek > Assignee: Mario Fusco > Priority: Major > > Method KieRepositoryScannerImpl#indexArtifacts first reads ALL dependencies and then tries to exclude those with scope test/provided/system. This is wrong since the nested dependencies might have different scope. Conseder this case: > A -> depends on B (with scope test) > B -> depends on C (with scope compile) > Asking for allDependencies will yield following descriptors: > A (compile scope) > B (test scope) > C (compile scope) > B gets discarded, but C remains and scanner will try to resolve it and add to class loader. > Instead of fitering the results of ArtifactResolver#getAllDependencies() (without parameters) you should use overloaded version of this method that accepts dependency filter. > I do not create rules via GUI, but have them in separate Maven project. This projects contains tests cases that check if the rules are OK. The tests create the knowlege base from filesystem and require drools-decisiontables in order to execute. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-444) Add missing Health checks in Istio Config

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-444?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan reassigned SWSQE-444: ------------------------------------ Assignee: Hayk Hovsepyan (was: Michael Foley) > Add missing Health checks in Istio Config > ----------------------------------------- > > Key: SWSQE-444 > URL: https://issues.jboss.org/browse/SWSQE-444 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4160) Unable to install FP when using Java 11

by Rostislav Svoboda (Jira)

Rostislav Svoboda created WFCORE-4160: ----------------------------------------- Summary: Unable to install FP when using Java 11 Key: WFCORE-4160 URL: https://issues.jboss.org/browse/WFCORE-4160 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Rostislav Svoboda Assignee: Jean-Francois Denise Unable to install FP when using Java 11 {code} [galleon]$ install --dir=/Users/rsvoboda/tmp/asd wildfly:current#14.0.1.Final Feature-packs resolved. Packages installed. JBoss modules installed. Generating configuration standalone/standalone.xmlError: Install failed. * Failed to invoke config generator org.wildfly.galleon.plugin.config.generator.WfConfigGenerator * WFLYEMB0014: Cannot load module org.jboss.vfs from: local module loader @9fecd1f (finder: local module finder @69ecf17c (roots: /Users/rsvoboda/.galleon-cli/cache/layout/21f90ea1-a78c-4f4a-a05d-787adf0676d0/staged/modules,/Users/rsvoboda/.galleon-cli/cache/layout/21f90ea1-a78c-4f4a-a05d-787adf0676d0/staged/modules/system/layers/base)) * java.se {code} Works with Java 8. This is another issues with {{--add-modules=java.se}} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11123) Illegal reflective access by org.wildfly.extension.elytron.SSLDefinitions

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-11123?page=com.atlassian.jira.plugin... ] Darran Lofthouse reassigned WFLY-11123: --------------------------------------- Assignee: (was: Darran Lofthouse) > Illegal reflective access by org.wildfly.extension.elytron.SSLDefinitions > ------------------------------------------------------------------------- > > Key: WFLY-11123 > URL: https://issues.jboss.org/browse/WFLY-11123 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 14.0.1.Final > Environment: Windows 7 x64. Java 11: OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11+28-201810022317, mixed mode) > Reporter: Marco Del Percio > Priority: Critical > Labels: Java11, access, elytron, illegal, reflective, wildfly > > After configuring HTTPS using the following guide: [Enable One-way SSL/TLS for Applications|http://docs.wildfly.org/14/WildFly_Elytron_Security.html#con...], configuration seems ok and server boots fine however an illegal reflective access warning comes up from jar within Elytron: > {color:red} > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by org.wildfly.extension.elytron.SSLDefinitions (jar:file:/D:/wildfly-14.0.1.Final_FleetManager/modules/system/layers/base/org/wildfly/extension/elytron/main/wildfly-elytron-integration-6.0.2.Final.jar!/) to method com.sun.net.ssl.internal.ssl.Provider.isFIPS() > WARNING: Please consider reporting this to the maintainers of org.wildfly.extension.elytron.SSLDefinitions > WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations > WARNING: All illegal access operations will be denied in a future release > {color} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11123) Illegal reflective access by org.wildfly.extension.elytron.SSLDefinitions

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-11123?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFLY-11123: ----------------------------------------- The implementation does also 'fail safe' is the method is not accessible to identify if FIPS mode has been enabled it falls back to assuming it has not been enabled. > Illegal reflective access by org.wildfly.extension.elytron.SSLDefinitions > ------------------------------------------------------------------------- > > Key: WFLY-11123 > URL: https://issues.jboss.org/browse/WFLY-11123 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 14.0.1.Final > Environment: Windows 7 x64. Java 11: OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11+28-201810022317, mixed mode) > Reporter: Marco Del Percio > Assignee: Darran Lofthouse > Priority: Critical > Labels: Java11, access, elytron, illegal, reflective, wildfly > > After configuring HTTPS using the following guide: [Enable One-way SSL/TLS for Applications|http://docs.wildfly.org/14/WildFly_Elytron_Security.html#con...], configuration seems ok and server boots fine however an illegal reflective access warning comes up from jar within Elytron: > {color:red} > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by org.wildfly.extension.elytron.SSLDefinitions (jar:file:/D:/wildfly-14.0.1.Final_FleetManager/modules/system/layers/base/org/wildfly/extension/elytron/main/wildfly-elytron-integration-6.0.2.Final.jar!/) to method com.sun.net.ssl.internal.ssl.Provider.isFIPS() > WARNING: Please consider reporting this to the maintainers of org.wildfly.extension.elytron.SSLDefinitions > WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations > WARNING: All illegal access operations will be denied in a future release > {color} -- This message was sent by Atlassian Jira (v7.12.1#712002)

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