December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2166) NPE in KieModuleMetaDataImpl in projects with invalid pom.xml

by Jan Hrcek (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2166?page=com.atlassian.jira.plugi... ] Jan Hrcek moved AF-924 to DROOLS-2166: -------------------------------------- Project: Drools (was: AppFormer) Key: DROOLS-2166 (was: AF-924) Workflow: GIT Pull Request workflow (was: classic default workflow) > NPE in KieModuleMetaDataImpl in projects with invalid pom.xml > ------------------------------------------------------------- > > Key: DROOLS-2166 > URL: https://issues.jboss.org/browse/DROOLS-2166 > Project: Drools > Issue Type: Bug > Reporter: Jan Hrcek > Assignee: Eder Ignatowicz > > When indexing assets in projects which have some problems with pom.xml (e.g. the parent of that pom can't be resolved), there's the following exception in server.log > {code:java} > 14:34:46,627 ERROR [stderr] (Thread-144) java.lang.NullPointerException > 14:34:46,627 ERROR [stderr] (Thread-144) at org.kie.scanner.KieModuleMetaDataImpl.init(KieModuleMetaDataImpl.java:167) > 14:34:46,627 ERROR [stderr] (Thread-144) at org.kie.scanner.KieModuleMetaDataImpl.<init>(KieModuleMetaDataImpl.java:86) > 14:34:46,627 ERROR [stderr] (Thread-144) at org.kie.scanner.KieModuleMetaData$Factory.newKieModuleMetaData(KieModuleMetaData.java:60) > 14:34:46,627 ERROR [stderr] (Thread-144) at org.kie.workbench.common.services.backend.builder.core.Builder.getKieModuleMetaDataIgnoringErrors(Builder.java:593) > 14:34:46,627 ERROR [stderr] (Thread-144) at org.kie.workbench.common.services.backend.builder.service.BuildInfoImpl.getKieModuleMetaDataIgnoringErrors(BuildInfoImpl.java:46) > 14:34:46,627 ERROR [stderr] (Thread-144) at org.kie.workbench.common.services.datamodel.backend.server.cache.ProjectDataModelOracleBuilderProvider.newBuilder(ProjectDataModelOracleBuilderProvider.java:62) > 14:34:46,627 ERROR [stderr] (Thread-144) at org.kie.workbench.common.services.datamodel.backend.server.cache.LRUProjectDataModelOracleCache.makeProjectOracle(LRUProjectDataModelOracleCache.java:80) > 14:34:46,627 ERROR [stderr] (Thread-144) at org.kie.workbench.common.services.datamodel.backend.server.cache.LRUProjectDataModelOracleCache.assertProjectDataModelOracle(LRUProjectDataModelOracleCache.java:72) > 14:34:46,627 ERROR [stderr] (Thread-144) at org.kie.workbench.common.services.datamodel.backend.server.cache.LRUProjectDataModelOracleCache$Proxy$_$$_WeldClientProxy.assertProjectDataModelOracle(Unknown Source) > 14:34:46,627 ERROR [stderr] (Thread-144) at org.kie.workbench.common.services.datamodel.backend.server.DataModelServiceImpl.getProjectDataModel(DataModelServiceImpl.java:91) > {code} > The root cause is that kieModule.getPomModel() [here|https://github.com/kiegroup/drools/blob/master/kie-ci/src/main/java/...] returns null, because pom model is [not created in this case|https://github.com/kiegroup/drools/blob/master/drools-compiler/src/m...] because it can't be parsed or can't be validated. > In this case we should at least avoid many NPEs being shown in server.log by doing null check and doing nothing if getPomModel() returns null -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2166) NPE in KieModuleMetaDataImpl in projects with invalid pom.xml

by Jan Hrcek (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2166?page=com.atlassian.jira.plugi... ] Jan Hrcek reassigned DROOLS-2166: --------------------------------- Assignee: Mario Fusco (was: Eder Ignatowicz) > NPE in KieModuleMetaDataImpl in projects with invalid pom.xml > ------------------------------------------------------------- > > Key: DROOLS-2166 > URL: https://issues.jboss.org/browse/DROOLS-2166 > Project: Drools > Issue Type: Bug > Reporter: Jan Hrcek > Assignee: Mario Fusco > > When indexing assets in projects which have some problems with pom.xml (e.g. the parent of that pom can't be resolved), there's the following exception in server.log > {code:java} > 14:34:46,627 ERROR [stderr] (Thread-144) java.lang.NullPointerException > 14:34:46,627 ERROR [stderr] (Thread-144) at org.kie.scanner.KieModuleMetaDataImpl.init(KieModuleMetaDataImpl.java:167) > 14:34:46,627 ERROR [stderr] (Thread-144) at org.kie.scanner.KieModuleMetaDataImpl.<init>(KieModuleMetaDataImpl.java:86) > 14:34:46,627 ERROR [stderr] (Thread-144) at org.kie.scanner.KieModuleMetaData$Factory.newKieModuleMetaData(KieModuleMetaData.java:60) > 14:34:46,627 ERROR [stderr] (Thread-144) at org.kie.workbench.common.services.backend.builder.core.Builder.getKieModuleMetaDataIgnoringErrors(Builder.java:593) > 14:34:46,627 ERROR [stderr] (Thread-144) at org.kie.workbench.common.services.backend.builder.service.BuildInfoImpl.getKieModuleMetaDataIgnoringErrors(BuildInfoImpl.java:46) > 14:34:46,627 ERROR [stderr] (Thread-144) at org.kie.workbench.common.services.datamodel.backend.server.cache.ProjectDataModelOracleBuilderProvider.newBuilder(ProjectDataModelOracleBuilderProvider.java:62) > 14:34:46,627 ERROR [stderr] (Thread-144) at org.kie.workbench.common.services.datamodel.backend.server.cache.LRUProjectDataModelOracleCache.makeProjectOracle(LRUProjectDataModelOracleCache.java:80) > 14:34:46,627 ERROR [stderr] (Thread-144) at org.kie.workbench.common.services.datamodel.backend.server.cache.LRUProjectDataModelOracleCache.assertProjectDataModelOracle(LRUProjectDataModelOracleCache.java:72) > 14:34:46,627 ERROR [stderr] (Thread-144) at org.kie.workbench.common.services.datamodel.backend.server.cache.LRUProjectDataModelOracleCache$Proxy$_$$_WeldClientProxy.assertProjectDataModelOracle(Unknown Source) > 14:34:46,627 ERROR [stderr] (Thread-144) at org.kie.workbench.common.services.datamodel.backend.server.DataModelServiceImpl.getProjectDataModel(DataModelServiceImpl.java:91) > {code} > The root cause is that kieModule.getPomModel() [here|https://github.com/kiegroup/drools/blob/master/kie-ci/src/main/java/...] returns null, because pom model is [not created in this case|https://github.com/kiegroup/drools/blob/master/drools-compiler/src/m...] because it can't be parsed or can't be validated. > In this case we should at least avoid many NPEs being shown in server.log by doing null check and doing nothing if getPomModel() returns null -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2160) Enhance UI in Test Scenarios Editor

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2160?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2160: ------------------------------------- Button size increased in PR https://github.com/kiegroup/drools-wb/pull/723 > Enhance UI in Test Scenarios Editor > ----------------------------------- > > Key: DROOLS-2160 > URL: https://issues.jboss.org/browse/DROOLS-2160 > Project: Drools > Issue Type: Enhancement > Components: Test Scenarios Editor > Reporter: Ivo Bek > Assignee: Toni Rikkola > Attachments: Screenshot from 2017-12-01 16-38-52.png > > > Test Scenarios editor needs to be polished: > * Delete Buttons are too small - it would be good to enlarge them. > * Some other elements doesn't have enough space around them. > * Please do any other small visual changes which makes sense. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7234) Ability to identify primary singleton provider node

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-7234?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-7234: ------------------------------- Issue Type: Enhancement (was: Feature Request) > Ability to identify primary singleton provider node > --------------------------------------------------- > > Key: WFLY-7234 > URL: https://issues.jboss.org/browse/WFLY-7234 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > The current Singleton interface only allow a user to tell whether or not the current node is the singleton provider. Most backup services will proxy the service of the primary node, and thus will need to be able to identify which node is the current primary provider. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-283) Investigate Elytron and gssproxy interoperability

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-283?page=com.atlassian.jira.plugin.sy... ] Jan Kalina edited comment on ELY-283 at 12/6/17 8:41 AM: --------------------------------------------------------- Few notes: * property *sun.security.jgss.native* needs to be set using JAVA_OPTS="-D ..." before standalone.sh (setting in standalone.xml is applied to late and is ignored by JVM) * to debug SunNativeProvider add property: *sun.security.nativegss.debug=true* * currently Elytron initialize LoginContext/Krb5LoginModule even if native provider should be used - should be made optional for future, but for now there is need to provide keystore with given credential to continue (obtained credential should be ignored by GSSManager if correctly set) * Currently gssproxy supports krb5 only to have filled in mechs in gssproxy.conf - we are unable to put SPNEGO here - cannot be used for SPNEGO HTTP auth * To start: {code}GSSPROXY_BEHAVIOR=REMOTE_FIRST GSS_USE_PROXY=1 JAVA_OPTS="-Djavax.security.auth.useSubjectCredsOnly=false -Dsun.security.jgss.lib=/usr/lib64/libgssapi_krb5.so.2.2 -Dsun.security.jgss.native=true -Dsun.security.nativegss.debug=true -Dsun.security.krb5.debug=true -Dsun.security.jgss.debug=true" bin/standalone.sh{code} was (Author: honza889): Few notes: * property *sun.security.jgss.native* needs to be set using JAVA_OPTS="-D ..." before standalone.sh (setting in standalone.xml is applied to late and is ignored by JVM) * to debug SunNativeProvider add property: *sun.security.nativegss.debug=true* * currently Elytron initialize LoginContext/Krb5LoginModule even if native provider should be used - should be made optional for future, but for now there is need to provide keystore with given credential to continue (obtained credential should be ignored by GSSManager if correctly set) * To start: {code}GSSPROXY_BEHAVIOR=REMOTE_FIRST GSS_USE_PROXY=1 JAVA_OPTS="-Djavax.security.auth.useSubjectCredsOnly=false -Dsun.security.jgss.lib=/usr/lib64/libgssapi_krb5.so.2.2 -Dsun.security.jgss.native=true -Dsun.security.nativegss.debug=true -Dsun.security.krb5.debug=true -Dsun.security.jgss.debug=true" bin/standalone.sh{code} > Investigate Elytron and gssproxy interoperability > ------------------------------------------------- > > Key: ELY-283 > URL: https://issues.jboss.org/browse/ELY-283 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Reporter: Peter Skopek > Assignee: Jan Kalina > Fix For: 2.0.0.Alpha1 > > > Investigate Elytron and gssproxy interoperability. > https://fedorahosted.org/gss-proxy/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9593) Add clustering externalizers for InetAddress and InetSocketAddress

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9593?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-9593: ------------------------------- Issue Type: Enhancement (was: Feature Request) > Add clustering externalizers for InetAddress and InetSocketAddress > ------------------------------------------------------------------ > > Key: WFLY-9593 > URL: https://issues.jboss.org/browse/WFLY-9593 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 11.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > InetAddress can be marshalled as a fixed sized array depending on whether the address is IPv4 or IPv6, which can be determined by the implementation class. > InetSocketAddress can marshal its address using the InetAddress externalizer, and its port as an unsigned short. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9509) Default SFSB Lifecycle methods transaction attribute causing warnings

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-9509?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-9509: ----------------------------------------------- Aurel Pintea <apintea(a)redhat.com> changed the Status of [bug 1508105|https://bugzilla.redhat.com/show_bug.cgi?id=1508105] from MODIFIED to ON_QA > Default SFSB Lifecycle methods transaction attribute causing warnings > --------------------------------------------------------------------- > > Key: WFLY-9509 > URL: https://issues.jboss.org/browse/WFLY-9509 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 11.0.0.Final > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: 12.0.0.Alpha1 > > Attachments: warning-reproducer.zip > > > EJB 2 deployment that does not specify transaction attribute for lifecycle methods such as: ejbActivate, ejbRemove, ejbPassivate are logging this warning. > JBAS014279: Invalid transaction attribute type REQUIRED on SFSB lifecyle method Method ejbRemove(), valid types are REQUIRES_NEW and NOT_SUPPORTED. Method will be treated as NOT_SUPPORTED. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-212) Automation Testcase

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-212: ----------------------------------------- Summary: Automation Testcase Key: HAWKULARQE-212 URL: https://issues.jboss.org/browse/HAWKULARQE-212 Project: Hawkular QE Issue Type: Sub-task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8954) Wildfly 10 with eclipselink Onscucess observer gets stale entity

by Tomas Kraus (JIRA)

[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ] Tomas Kraus commented on WFLY-8954: ----------------------------------- I made changes to implement JTA 1.1 TransactionSynchronizationRegistry in EclipseLink master branch, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=526419 for details. It would be good if you can test next http://www.eclipse.org/eclipselink/downloads/nightly.php (7th dec 2017 and later) and give us feedback. Also, if we'll make backport into 2.7. and 2.6 branches, you can base your changes on extending org.eclipse.persistence.transaction.JTA11TransactionController class instead of current JTATransactionController. > Wildfly 10 with eclipselink Onscucess observer gets stale entity > ---------------------------------------------------------------- > > Key: WFLY-8954 > URL: https://issues.jboss.org/browse/WFLY-8954 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.0.0.Final > Reporter: Nuno Godinho de Matos > Assignee: Scott Marlow > Fix For: 12.0.0.Alpha1 > > > Hi, > In widlfly there seems to be an important issue concerning CDI events and observing these events during onsuccess. At least while using eclipselink. > When using wildfly 10.0.0.Final together with eclipselink, if an application modifies an entity A, fires an event stating entity A has been modified, and an observer consumes this event during transaction success. > Then the observer will be working with stale entities that do not reflect the modifications done to the entity. > A sample application for this issue is available in: > https://github.com/99sono/wildfly10-observe-on-success-stale-entity > The widlfly configuration xml for the sample application, is available in the application itself, as can be seen in the readme documentation. > Many thanks for taking a look. > Kindest regards. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9598) Clustering Testsuite 2.0: no ant, CLI, 3-node DIST testing

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9598?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9598: --------------------------------- Description: For starters, move the testsuite away from using XSLT and just rely on the CLI scripts. > Clustering Testsuite 2.0: no ant, CLI, 3-node DIST testing > ---------------------------------------------------------- > > Key: WFLY-9598 > URL: https://issues.jboss.org/browse/WFLY-9598 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 12.0.0.Alpha1 > > > For starters, move the testsuite away from using XSLT and just rely on the CLI scripts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 December 2017