June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5420) Change log level in KieRepositoryImpl.addKieModule to DEBUG

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5420?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5420: --------------------------------- Story Points: 1 > Change log level in KieRepositoryImpl.addKieModule to DEBUG > ----------------------------------------------------------- > > Key: DROOLS-5420 > URL: https://issues.redhat.com/browse/DROOLS-5420 > Project: Drools > Issue Type: Task > Components: core engine > Affects Versions: 7.38.0.Final > Reporter: Martin Weiler > Assignee: Luca Molteni > Priority: Minor > > The following message should be logged at DEBUG level instead of INFO: > {noformat} > o.d.c.k.builder.impl.KieRepositoryImpl : Adding KieModule dependency from resource: ByteArrayResource[bytes=[80, 75, 3, 4, 20, 0, 8, 8, 8, 0, ...], encoding=null] > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5288) Execution default-generateModel ... failed: Scope expression for ... is not present!

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5288?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5288: --------------------------------- Sprint: 2020 Week 25-27 (from Jun 15) > Execution default-generateModel ... failed: Scope expression for ... is not present! > ------------------------------------------------------------------------------------ > > Key: DROOLS-5288 > URL: https://issues.redhat.com/browse/DROOLS-5288 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Matteo Mortari > Assignee: Luca Molteni > Priority: Major > Attachments: image-2020-04-30-16-32-07-591.png > > > Reproducer: https://github.com/tarilabs/reproducer20200430 > To reproduce: > {code} > mvn clean compile -X > {code} > Example: > !image-2020-04-30-16-32-07-591.png! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4841) Externalise Rule Unit's Lambdas

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-4841?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-4841: --------------------------------- [~tkobayashi] as you're taking a look at Kogito programmatic API, can I assign you this? Thanks > Externalise Rule Unit's Lambdas > ------------------------------- > > Key: DROOLS-4841 > URL: https://issues.redhat.com/browse/DROOLS-4841 > Project: Drools > Issue Type: Feature Request > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > Labels: good-first-issue > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5420) Change log level in KieRepositoryImpl.addKieModule to DEBUG

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5420?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5420: --------------------------------- Sprint: 2020 Week 25-27 (from Jun 15) (was: 2020 Week 22-24 (from May 25)) > Change log level in KieRepositoryImpl.addKieModule to DEBUG > ----------------------------------------------------------- > > Key: DROOLS-5420 > URL: https://issues.redhat.com/browse/DROOLS-5420 > Project: Drools > Issue Type: Task > Components: core engine > Affects Versions: 7.38.0.Final > Reporter: Martin Weiler > Assignee: Luca Molteni > Priority: Minor > > The following message should be logged at DEBUG level instead of INFO: > {noformat} > o.d.c.k.builder.impl.KieRepositoryImpl : Adding KieModule dependency from resource: ByteArrayResource[bytes=[80, 75, 3, 4, 20, 0, 8, 8, 8, 0, ...], encoding=null] > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5275) Descope Traits

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5275?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5275: --------------------------------- Sprint: 2020 Week 25-27 (from Jun 15) (was: 2020 Week 22-24 (from May 25)) > Descope Traits > -------------- > > Key: DROOLS-5275 > URL: https://issues.redhat.com/browse/DROOLS-5275 > Project: Drools > Issue Type: Enhancement > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4367) Tests in drools coverage are not really using the executable model

by Daniel Rosa (Jira)

[ https://issues.redhat.com/browse/DROOLS-4367?page=com.atlassian.jira.plug... ] Daniel Rosa updated DROOLS-4367: -------------------------------- Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 13-15 (from Mar 23), 2020 Week 25-27 (from Jun 15) (was: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 13-15 (from Mar 23)) > Tests in drools coverage are not really using the executable model > ------------------------------------------------------------------ > > Key: DROOLS-4367 > URL: https://issues.redhat.com/browse/DROOLS-4367 > Project: Drools > Issue Type: Bug > Reporter: Luca Molteni > Assignee: Daniel Rosa > Priority: Minor > > Such as > https://github.com/kiegroup/drools/blob/ba9c79c4bfaf9cfc1ec2363bee3865c3d... > Even if the test itself is parametrized, in the body it calls directly buildAll therefore discarding the executable model -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2086) Intermittent failure in OperationCancellationTestCase

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFCORE-2086?page=com.atlassian.jira.plug... ] Yeray Borges Santana reassigned WFCORE-2086: -------------------------------------------- Assignee: Yeray Borges Santana > Intermittent failure in OperationCancellationTestCase > ----------------------------------------------------- > > Key: WFCORE-2086 > URL: https://issues.redhat.com/browse/WFCORE-2086 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 5.0.0.Beta5 > Reporter: Brian Stansberry > Assignee: Yeray Borges Santana > Priority: Major > > Investigate this: > https://ci.wildfly.org/viewLog.html?buildId=36108&buildTypeId=WildFlyCore... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13559) Header response has changed and missing fields

by Luis Cabral (Jira)

[ https://issues.redhat.com/browse/WFLY-13559?page=com.atlassian.jira.plugi... ] Luis Cabral edited comment on WFLY-13559 at 6/15/20 4:17 AM: ------------------------------------------------------------- Can confirm that this issue happens when using a {{@RequestContext}} bean and {{JAX-RS}} filters, causing the filters to be ignored entirely. Not having a {{@RequestContext}} bean, the filters are picked up correctly. This is happening both on WildFly 19 and 20, but works correctly on 18. So, [~brian.stansberry], imho, not a question, but a valid bug... was (Author: blaghed): Can confirm that this issue happens when using a {{@RequestContext}} bean and {{JAX-RS}} filters, causing the filters to be ignored entirely. Not having a {{@RequestContext}} bean, the filters are picked up correctly. This is happening both on WildFly 19 and 20, but works correctly on 18. So, imho, not a question, but a valid bug... > Header response has changed and missing fields > ---------------------------------------------- > > Key: WFLY-13559 > URL: https://issues.redhat.com/browse/WFLY-13559 > Project: WildFly > Issue Type: Bug > Affects Versions: 19.1.0.Final > Reporter: Alexandru Ciouca > Priority: Major > Attachments: standalone_18.0.0.final.xml, standalone_19.1.0.final.xml > > > I have an application running in WildFly with some open endpoints to call and I tried an upgrade to WildFly 19.1.0.final from 18.0.0.final, but I noticed that something changed when calling the endpoints. In the Response Header I see that some of the fields are changed or are missing. Is this supposed to happen or do I need to add some extra configuration with WildFly 19? > Response WildFly 18.0.0.final: > {code} > HTTP/2 500 > cache-control: no-store, no-cache, must-revalidate > set-cookie: JSESSIONID=pLpPEvZZVekh0Bkqq06muz_cJ4_fmwxsqrt0HUdP.myservices-container-6f5b87f79d-ngzhf; path=/myservices > access-control-allow-headers: origin, content-type, accept, X-XSRF-TOKEN > content-type: application/json > content-length: 182 > link: <http://test.com/afs/rest>; rel="profile" > date: Thu, 04 Jun 2020 07:34:10 GMT > set-cookie: 7951a12696148c7a83e36db56eeb5f91=5ede0885e2c831c4946125e91d3facba; path=/; HttpOnly; Secure > strict-transport-security: max-age=31536000; includeSubdomains > x-xss-protection: 1; mode=block > x-content-type-options: nosniff > x-frame-options: SAMEORIGIN > {code} > Response WildFly 19.1.0.final: > {code} > HTTP/2 200 > set-cookie: JSESSIONID=9siDVU14OoFXojIIVxlMWbxNg1gcuSmLokwamY29.myservices-container-7c8dbf55f5-ctcks; path=/myservices > content-type: application/json > content-length: 182 > date: Thu, 04 Jun 2020 07:27:57 GMT > set-cookie: 7951a12696148c7a83e36db56eeb5f91=3edfc7a7549d107b41669532f6cb594a; path=/; HttpOnly; Secure > cache-control: private > strict-transport-security: max-age=31536000; includeSubdomains > x-xss-protection: 1; mode=block > x-content-type-options: nosniff > x-frame-options: SAMEORIGIN > {code} > As you can see the first thing that changed is the response code, even though the code is the same for both versions. The cache-control is also different and access-control-allow-headers and link fields are missing. > I am attaching also the standalone.xml for both versions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13559) Header response has changed and missing fields

by Luis Cabral (Jira)

[ https://issues.redhat.com/browse/WFLY-13559?page=com.atlassian.jira.plugi... ] Luis Cabral commented on WFLY-13559: ------------------------------------ Can confirm that this issue happens when using a {{@RequestContext}} bean and {{JAX-RS}} filters, causing the filters to be ignored entirely. Not having a {{@RequestContext}} bean, the filters are picked up correctly. This is happening both on WildFly 19 and 20, but works correctly on 18. So, imho, not a question, but a valid bug... > Header response has changed and missing fields > ---------------------------------------------- > > Key: WFLY-13559 > URL: https://issues.redhat.com/browse/WFLY-13559 > Project: WildFly > Issue Type: Bug > Affects Versions: 19.1.0.Final > Reporter: Alexandru Ciouca > Priority: Major > Attachments: standalone_18.0.0.final.xml, standalone_19.1.0.final.xml > > > I have an application running in WildFly with some open endpoints to call and I tried an upgrade to WildFly 19.1.0.final from 18.0.0.final, but I noticed that something changed when calling the endpoints. In the Response Header I see that some of the fields are changed or are missing. Is this supposed to happen or do I need to add some extra configuration with WildFly 19? > Response WildFly 18.0.0.final: > {code} > HTTP/2 500 > cache-control: no-store, no-cache, must-revalidate > set-cookie: JSESSIONID=pLpPEvZZVekh0Bkqq06muz_cJ4_fmwxsqrt0HUdP.myservices-container-6f5b87f79d-ngzhf; path=/myservices > access-control-allow-headers: origin, content-type, accept, X-XSRF-TOKEN > content-type: application/json > content-length: 182 > link: <http://test.com/afs/rest>; rel="profile" > date: Thu, 04 Jun 2020 07:34:10 GMT > set-cookie: 7951a12696148c7a83e36db56eeb5f91=5ede0885e2c831c4946125e91d3facba; path=/; HttpOnly; Secure > strict-transport-security: max-age=31536000; includeSubdomains > x-xss-protection: 1; mode=block > x-content-type-options: nosniff > x-frame-options: SAMEORIGIN > {code} > Response WildFly 19.1.0.final: > {code} > HTTP/2 200 > set-cookie: JSESSIONID=9siDVU14OoFXojIIVxlMWbxNg1gcuSmLokwamY29.myservices-container-7c8dbf55f5-ctcks; path=/myservices > content-type: application/json > content-length: 182 > date: Thu, 04 Jun 2020 07:27:57 GMT > set-cookie: 7951a12696148c7a83e36db56eeb5f91=3edfc7a7549d107b41669532f6cb594a; path=/; HttpOnly; Secure > cache-control: private > strict-transport-security: max-age=31536000; includeSubdomains > x-xss-protection: 1; mode=block > x-content-type-options: nosniff > x-frame-options: SAMEORIGIN > {code} > As you can see the first thing that changed is the response code, even though the code is the same for both versions. The cache-control is also different and access-control-allow-headers and link fields are missing. > I am attaching also the standalone.xml for both versions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3766) Improve error message if a parent profile references a child profile's value

by Moulali Shikalwadi (Jira)

[ https://issues.redhat.com/browse/WFCORE-3766?page=com.atlassian.jira.plug... ] Moulali Shikalwadi reassigned WFCORE-3766: ------------------------------------------ Assignee: Moulali Shikalwadi > Improve error message if a parent profile references a child profile's value > ---------------------------------------------------------------------------- > > Key: WFCORE-3766 > URL: https://issues.redhat.com/browse/WFCORE-3766 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Affects Versions: 3.1.0.Final, 4.0.0.Final, 5.0.0.Alpha3 > Reporter: Brad Maxwell > Assignee: Moulali Shikalwadi > Priority: Major > Labels: domain-mode > Attachments: WFCORE-3766-config.zip > > > EAP 7.1 CP1 boot up fails with the following error message when a profile extension is used > {code:java} > 14:13:39,201 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=temp-full-ha/subsystem=infinispan/cache-container=hibernate/transport=jgroups' are not available: [Host Controller] org.wildfly.clustering.jgroups.default-channel-factory in context 'profile=temp-full-ha'; Possible registration points for this capability: [Host Controller] /profile=*/subsystem=jgroups [Host Controller] > 14:13:39,202 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=temp-full-ha/subsystem=messaging-activemq/server=default/broadcast-group=bg-group1' are not available: [Host Controller] org.wildfly.clustering.jgroups.default-channel-factory in context 'profile=temp-full-ha'; Possible registration points for this capability: [Host Controller] /profile=*/subsystem=jgroups [Host Controller] > 14:13:39,202 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=temp-full-ha/subsystem=infinispan/cache-container=web/transport=jgroups' are not available: [Host Controller] org.wildfly.clustering.jgroups.default-channel-factory in context 'profile=temp-full-ha'; Possible registration points for this capability: [Host Controller] /profile=*/subsystem=jgroups [Host Controller] > 14:13:39,202 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=temp-full-ha/subsystem=messaging-activemq/server=default/discovery-group=dg-group1' are not available: [Host Controller] org.wildfly.clustering.jgroups.default-channel-factory in context 'profile=temp-full-ha'; Possible registration points for this capability: [Host Controller] /profile=*/subsystem=jgroups [Host Controller] > 14:13:39,203 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=temp-full-ha/subsystem=infinispan/cache-container=server/transport=jgroups' are not available: [Host Controller] org.wildfly.clustering.jgroups.default-channel-factory in context 'profile=temp-full-ha'; Possible registration points for this capability: [Host Controller] /profile=*/subsystem=jgroups [Host Controller] > 14:13:39,203 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/profile=temp-full-ha/subsystem=infinispan/cache-container=ejb/transport=jgroups' are not available: [Host Controller] org.wildfly.clustering.jgroups.default-channel-factory in context 'profile=temp-full-ha'; Possible registration points for this capability: [Host Controller] /profile=*/subsystem=jgroups [Host Controller] > 14:13:39,215 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. [Host Controller] > 14:13:39,217 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0178: Aborting with exit code 99 [Host Controller] > 14:13:39,265 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0050: JBoss EAP 7.1.1.GA (WildFly Core 3.0.12.Final-redhat-1) stopped in 26ms [Host Controller] > 14:13:39,611 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) WFLYPC0011: Process 'Host Controller' finished with an exit status of 99 > 14:13:39,613 INFO [org.jboss.as.process] (Thread-8) WFLYPC0017: Shutting down process controller 14:13:39,613 INFO [org.jboss.as.process] (Thread-8) WFLYPC0016: All processes finished; exiting > {code} > Can this error be improved to better direct the user to the issue? -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2020