May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGMGR-246) Wildfly 16 incorrect working log zip rotator

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-246?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-246: --------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/252, https://github.com/jboss-logging/jboss-logmanager/pull/253, https://github.com/jboss-logging/jboss-logmanager/pull/254 > Wildfly 16 incorrect working log zip rotator > -------------------------------------------- > > Key: LOGMGR-246 > URL: https://issues.jboss.org/browse/LOGMGR-246 > Project: JBoss Log Manager > Issue Type: Bug > Components: core > Environment: Windows, > Oracle JDK 8 > Reporter: Igor Dmitriev > Assignee: James Perkins > Priority: Major > > My logging profile configuration is: > 1) > {code:xml} > <periodic-size-rotating-file-handler name="FILE" rotate-on-boot="false" autoflush="true"> > <level name="ALL"/> > <file relative-to="jboss.server.log.dir" path="corp.log"/> > <rotate-size value="300k"/> > <max-backup-index value="10000"/> > <suffix value=".yyyy-MM-dd.zip"/> > <append value="true"/> > </periodic-size-rotating-file-handler> > {code} > File corp.log increase it size permanently, even after new corp.log.yyyy-MM-dd.N.zip file created. Due it, each .zip archive contain same corp.log with maximum current size. > 2) > {code:xml} > <periodic-size-rotating-file-handler name="FILE2" rotate-on-boot="true" autoflush="true"> > <level name="ALL"/> > <file relative-to="jboss.server.log.dir" path="corp.log"/> > <rotate-size value="300k"/> > <max-backup-index value="10000"/> > <suffix value=".yyyy-MM-dd.zip"/> > <append value="false"/> > </periodic-size-rotating-file-handler> > {code} > All work as expected, except each time corp.log reach 300k, appear pair .zip files with same content? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12101) Test for EJBCLIENT-335

by Teresa Miyar Gil (Jira)

Teresa Miyar Gil created WFLY-12101: --------------------------------------- Summary: Test for EJBCLIENT-335 Key: WFLY-12101 URL: https://issues.jboss.org/browse/WFLY-12101 Project: WildFly Issue Type: Task Reporter: Teresa Miyar Gil Assignee: Teresa Miyar Gil -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4479) Upgrade jboss-logmanager from 2.1.10.Final to 2.1.11.Final

by James Perkins (Jira)

James Perkins created WFCORE-4479: ------------------------------------- Summary: Upgrade jboss-logmanager from 2.1.10.Final to 2.1.11.Final Key: WFCORE-4479 URL: https://issues.jboss.org/browse/WFCORE-4479 Project: WildFly Core Issue Type: Component Upgrade Components: Logging Reporter: James Perkins Assignee: James Perkins Upgrade the {{org.jboss.logmanager:jboss-logmanager}} from 2.1.10.Final to 2.1.11.Final. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4043) inappropriate warning appear while building kjar

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4043?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-4043: -------------------------------- Tester: Tibor Zimanyi > inappropriate warning appear while building kjar > ------------------------------------------------ > > Key: DROOLS-4043 > URL: https://issues.jboss.org/browse/DROOLS-4043 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.18.0.Final > Reporter: Hiroko Miura > Assignee: Mario Fusco > Priority: Major > Labels: support > Attachments: buildKjar.zip > > > When bulding kjar, warning something like the following appear. > {noformat} > [WARNING] File 'src/main/resources//work/buildKjar/src/main/resources/com/sample/rules2' is in folder '.work.buildKjar.src.main.resources.com.sample.rules2' but declares package 'com.sample.rules2'. It is advised to have a correspondance between package and folder names. > [WARNING] File 'src/main/resources//work/buildKjar/src/main/resources/com/sample/rules' is in folder '.work.buildKjar.src.main.resources.com.sample.rules' but declares package 'com.sample.rules'. It is advised to have a correspondance between package and folder names. > [WARNING] File 'work/buildKjar/src/main/resources/com/sample/rules2' is in folder 'work.buildKjar.src.main.resources.com.sample.rules2' but declares package 'com.sample.rules2'. It is advised to have a correspondance between package and folder names. > [WARNING] File 'work/buildKjar/src/main/resources/com/sample/rules' is in folder 'work.buildKjar.src.main.resources.com.sample.rules' but declares package 'com.sample.rules'. It is advised to have a correspondance between package and folder names. > {noformat} > But drl are put under appropriate path which matches declared package. > {noformat} > src/main/resources/ > ├── com > │ └── sample > │ ├── rules > │ │ └── Sample.drl > │ └── rules2 > │ └── Sample2.drl > {noformat} > This warning should not appear for this example. > In addition, path of File which is shown in this warning message looks wired. > e.g. > {noformat} > File 'src/main/resources//work/buildKjarTest2/src/main/resources/com/sample/rules2' > {noformat} > i.e. prefix ('src/main/resources/') is added to absolute path. > Therefore, it's hard to understand what is exactly wrong and warned. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4043) inappropriate warning appear while building kjar

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4043?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-4043. --------------------------------- Resolution: Done > inappropriate warning appear while building kjar > ------------------------------------------------ > > Key: DROOLS-4043 > URL: https://issues.jboss.org/browse/DROOLS-4043 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.18.0.Final > Reporter: Hiroko Miura > Assignee: Mario Fusco > Priority: Major > Labels: support > Attachments: buildKjar.zip > > > When bulding kjar, warning something like the following appear. > {noformat} > [WARNING] File 'src/main/resources//work/buildKjar/src/main/resources/com/sample/rules2' is in folder '.work.buildKjar.src.main.resources.com.sample.rules2' but declares package 'com.sample.rules2'. It is advised to have a correspondance between package and folder names. > [WARNING] File 'src/main/resources//work/buildKjar/src/main/resources/com/sample/rules' is in folder '.work.buildKjar.src.main.resources.com.sample.rules' but declares package 'com.sample.rules'. It is advised to have a correspondance between package and folder names. > [WARNING] File 'work/buildKjar/src/main/resources/com/sample/rules2' is in folder 'work.buildKjar.src.main.resources.com.sample.rules2' but declares package 'com.sample.rules2'. It is advised to have a correspondance between package and folder names. > [WARNING] File 'work/buildKjar/src/main/resources/com/sample/rules' is in folder 'work.buildKjar.src.main.resources.com.sample.rules' but declares package 'com.sample.rules'. It is advised to have a correspondance between package and folder names. > {noformat} > But drl are put under appropriate path which matches declared package. > {noformat} > src/main/resources/ > ├── com > │ └── sample > │ ├── rules > │ │ └── Sample.drl > │ └── rules2 > │ └── Sample2.drl > {noformat} > This warning should not appear for this example. > In addition, path of File which is shown in this warning message looks wired. > e.g. > {noformat} > File 'src/main/resources//work/buildKjarTest2/src/main/resources/com/sample/rules2' > {noformat} > i.e. prefix ('src/main/resources/') is added to absolute path. > Therefore, it's hard to understand what is exactly wrong and warned. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4051) Wrong compiled type definition

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4051?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-4051. --------------------------------- Resolution: Won't Fix We use the keyword 'declare' both to define a brand new type and to add new declaration on an existing type. Normally there is no ambiguity because in case you want to perform a redeclaration you have to import the existing type. Unfortunately this doesn't work for classes in java.lang package that is imported automatically, so in that specific case there's no way to disambiguate (do you want to define a new Process type or for instance flag java.lang.Process as an event?) and then the only way to resolve the ambiguity is using the fully qualified name as you alredy discovered. > Wrong compiled type definition > ------------------------------ > > Key: DROOLS-4051 > URL: https://issues.jboss.org/browse/DROOLS-4051 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.21.0.Final > Reporter: Stéphane Tondini > Assignee: Mario Fusco > Priority: Major > > I defined a drl file that declare a type like : > {code} > package com.test.rules.model.process; > // Process related objects > declare Process > caseRef : String @key > owner : String @key > end > {code} > At rules compile time, Drools throws the following exception : > {code} > Caused by: java.lang.IllegalArgumentException: Error parsing bootstrap resources : New declaration of java.lang.Process can't declare a different set of fields > existing : [] > declared : [caseRef] > diff : [++caseRef] > Unable to process type Process > {code} > Drools compiles *java.lang.Process* instead of my customized type. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12098) Thread context class loader is wrong for ScheduledExecutorService threads

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12098?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-12098: --------------------------------------- Component/s: Concurrency Utilities (was: Class Loading) Assignee: Eduardo Martins (was: Richard Opalka) > Thread context class loader is wrong for ScheduledExecutorService threads > ------------------------------------------------------------------------- > > Key: WFLY-12098 > URL: https://issues.jboss.org/browse/WFLY-12098 > Project: WildFly > Issue Type: Bug > Components: Concurrency Utilities > Affects Versions: 16.0.0.Final > Reporter: Paul Pogonyshev > Assignee: Eduardo Martins > Priority: Major > > Tasks submitted to the standard ScheduledExecutorService (JNDI: java:comp/DefaultManagedScheduledExecutorService) are executed in threads with class loader that cannot find application classes. This is a regression in 16.0 compared to 14.0 (haven't tested 15). Tasks submitted to the simple ExecutorService (JNDI: java:comp/DefaultManagedExecutorService) see the correct class loader. > I.e. if I submit something like > () -> { System.out.println (Thread.currentThread ().getContextClassLoader (); } > to both services (i.e. exactly the same task), I get the following output. For ScheduledExecutorService (wrong): > ModuleClassLoader for Module "org.jboss.as.ee" version 16.0.0.Final from local module loader @275710fc (finder: local module finder @525f1e4e (roots: [...]/wildfly/modules,[...]/wildfly/modules/system/layers/base)) > For ExecutorService (as expected): > ModuleClassLoader for Module "deployment.[...].war" from Service Module Loader > Plain ExecutorService sees exactly the same class loader as normal threads in which HTTP request are processed. In version 14.0 this was also true for ScheduledExecutorService. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12100) Upgrade Infinispan to 9.4.14.Final

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12100: ----------------------------------- Summary: Upgrade Infinispan to 9.4.14.Final Key: WFLY-12100 URL: https://issues.jboss.org/browse/WFLY-12100 Project: WildFly Issue Type: Component Upgrade Components: Clustering Affects Versions: 17.0.0.Alpha1 Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4043) inappropriate warning appear while building kjar

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4043?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-4043: -------------------------------- Fixed by https://github.com/kiegroup/drools/commit/dd5043d9d582633b465b77f8977ed03... > inappropriate warning appear while building kjar > ------------------------------------------------ > > Key: DROOLS-4043 > URL: https://issues.jboss.org/browse/DROOLS-4043 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.18.0.Final > Reporter: Hiroko Miura > Assignee: Mario Fusco > Priority: Major > Labels: support > Attachments: buildKjar.zip > > > When bulding kjar, warning something like the following appear. > {noformat} > [WARNING] File 'src/main/resources//work/buildKjar/src/main/resources/com/sample/rules2' is in folder '.work.buildKjar.src.main.resources.com.sample.rules2' but declares package 'com.sample.rules2'. It is advised to have a correspondance between package and folder names. > [WARNING] File 'src/main/resources//work/buildKjar/src/main/resources/com/sample/rules' is in folder '.work.buildKjar.src.main.resources.com.sample.rules' but declares package 'com.sample.rules'. It is advised to have a correspondance between package and folder names. > [WARNING] File 'work/buildKjar/src/main/resources/com/sample/rules2' is in folder 'work.buildKjar.src.main.resources.com.sample.rules2' but declares package 'com.sample.rules2'. It is advised to have a correspondance between package and folder names. > [WARNING] File 'work/buildKjar/src/main/resources/com/sample/rules' is in folder 'work.buildKjar.src.main.resources.com.sample.rules' but declares package 'com.sample.rules'. It is advised to have a correspondance between package and folder names. > {noformat} > But drl are put under appropriate path which matches declared package. > {noformat} > src/main/resources/ > ├── com > │ └── sample > │ ├── rules > │ │ └── Sample.drl > │ └── rules2 > │ └── Sample2.drl > {noformat} > This warning should not appear for this example. > In addition, path of File which is shown in this warning message looks wired. > e.g. > {noformat} > File 'src/main/resources//work/buildKjarTest2/src/main/resources/com/sample/rules2' > {noformat} > i.e. prefix ('src/main/resources/') is added to absolute path. > Therefore, it's hard to understand what is exactly wrong and warned. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4047) Unable to use CSV in a ruleTemplate

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4047?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-4047: -------------------------------- Sprint: 2019 Week 20-22 > Unable to use CSV in a ruleTemplate > ----------------------------------- > > Key: DROOLS-4047 > URL: https://issues.jboss.org/browse/DROOLS-4047 > Project: Drools > Issue Type: Bug > Components: decision tables > Affects Versions: 6.5.0.Final, 7.21.0.Final > Environment: Any Java env > Reporter: Adam Baxter > Assignee: Mario Fusco > Priority: Major > Attachments: csv_import_test.tar.gz > > > I believe there is a bug where you cannot use a CSV file to use as a decision table to drive a ruleTemplate. Our issue appears to be a duplicate of the one mentioned in this pull request -https://github.com/kiegroup/drools/pull/1920 > The drools version we're using is 6.50.FINAL, but the reproducer I've attached is for the latest released version. > We'd like to move away from binary files as they're opaque to most version control and it makes branching difficult. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 May 2019