June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10645) Unable to obtain CDI 1.1 utilities for Mojarra

by tommaso borgato (JIRA)

tommaso borgato created WFLY-10645: -------------------------------------- Summary: Unable to obtain CDI 1.1 utilities for Mojarra Key: WFLY-10645 URL: https://issues.jboss.org/browse/WFLY-10645 Project: WildFly Issue Type: Bug Components: Clustering, JSF Reporter: tommaso borgato Assignee: Paul Ferraro Affected job is eap-7x-failover-ejb-ejbservlet-undeploy-repl-sync. Every time the server is stated or re-started, we observed these SEVERE logs just after clusterbench is deployed (clusterbench also uses JSF): {noformat} 2018-06-27 02:47:07,439 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 72) WFLYCLINF0002: Started clusterbench-ee7.ear.clusterbench-ee7-web-granular.war cache from web container 2018-06-27 02:47:07,440 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 75) WFLYCLINF0002: Started client-mappings cache from ejb container 2018-06-27 02:47:07,440 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 73) WFLYCLINF0002: Started clusterbench-ee7.ear.clusterbench-ee7-web-default.war cache from web container 2018-06-27 02:47:07,440 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 74) WFLYCLINF0002: Started default-server cache from web container 2018-06-27 02:47:07,439 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 76) WFLYCLINF0002: Started clusterbench-ee7.ear.clusterbench-ee7-web-passivating.war cache from web container 2018-06-27 02:47:07,578 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 75) WFLYCLINF0002: Started clusterbench-ee7.ear/clusterbench-ee7-ejb.jar cache from ejb container 2018-06-27 02:47:07,673 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.jberet.creation.BatchBeanProducer is deprecated from CDI 1.1! 2018-06-27 02:47:07,713 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor is deprecated from CDI 1.1! 2018-06-27 02:47:07,739 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.sun.faces.flow.FlowDiscoveryCDIHelper is deprecated from CDI 1.1! 2018-06-27 02:47:08,149 SEVERE [javax.enterprise.resource.webcontainer.jsf.flow] (MSC service thread 1-7) Unable to obtain CDI 1.1 utilities for Mojarra 2018-06-27 02:47:08,163 SEVERE [javax.enterprise.resource.webcontainer.jsf.application.view] (MSC service thread 1-7) Unable to obtain CDI 1.1 utilities for Mojarra 2018-06-27 02:47:08,586 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 76) Initializing Mojarra 2.2.13.SP5 for context '/clusterbench-granular' 2018-06-27 02:47:08,586 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 72) Initializing Mojarra 2.2.13.SP5 for context '/clusterbench' 2018-06-27 02:47:08,587 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 78) Initializing Mojarra 2.2.13.SP5 for context '/clusterbench-passivating' 2018-06-27 02:47:09,860 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 76) WFLYUT0021: Registered web context: '/clusterbench-granular' for server 'default-server' 2018-06-27 02:47:09,863 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0021: Registered web context: '/clusterbench' for server 'default-server' 2018-06-27 02:47:09,863 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 78) WFLYUT0021: Registered web context: '/clusterbench-passivating' for server 'default-server' 2018-06-27 02:47:09,889 INFO [org.jboss.as.server] (ServerService Thread Pool -- 42) WFLYSRV0010: Deployed "clusterbench-ee7.ear" (runtime-name : "clusterbench-ee7.ear") 2018-06-27 02:47:09,989 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server {noformat} Complete log [here|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2658) PMML - tests in class ScorecardReasonCodeTest fail randomly

by Tibor Zimányi (JIRA)

Tibor Zimányi created DROOLS-2658: ------------------------------------- Summary: PMML - tests in class ScorecardReasonCodeTest fail randomly Key: DROOLS-2658 URL: https://issues.jboss.org/browse/DROOLS-2658 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.7.0.Final Reporter: Tibor Zimányi Assignee: Lance Leverich Priority: Critical When the ScorecardReasonCodeTest.testPointsBelow is run repeatedly, it sometimes fail with following assertion fail [1]. Setting this as critical, because the random fail causes build problems in the CI environment. Same applies for testPointsAbove, testReasonCodesCombination and probably others (I tested those 3 mentioned). [1] https://gist.github.com/baldimir/4c8ac4563fd17d13e4646fd60dd3a357 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10619) Add version 7 of the management model for the Undertow subsystem

by Jan Stourac (JIRA)

[ https://issues.jboss.org/browse/WFLY-10619?page=com.atlassian.jira.plugin... ] Jan Stourac commented on WFLY-10619: ------------------------------------ Thank you Kabir and Darran for the explanation! Link to the jira also helped :) > Add version 7 of the management model for the Undertow subsystem > ---------------------------------------------------------------- > > Key: WFLY-10619 > URL: https://issues.jboss.org/browse/WFLY-10619 > Project: WildFly > Issue Type: Task > Components: Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 14.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10619) Add version 7 of the management model for the Undertow subsystem

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-10619?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFLY-10619: ----------------------------------------- Hello yes this is required for WFLY-10614 which will be following up later. The reason I submitted this part of the changes early was in-case anyone else is also working on Undertow subsystem changes as we end up with duplicated work and conflicts if multiple engineers all need to bump the model simultaneously. > Add version 7 of the management model for the Undertow subsystem > ---------------------------------------------------------------- > > Key: WFLY-10619 > URL: https://issues.jboss.org/browse/WFLY-10619 > Project: WildFly > Issue Type: Task > Components: Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 14.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10619) Add version 7 of the management model for the Undertow subsystem

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-10619?page=com.atlassian.jira.plugin... ] Kabir Khan commented on WFLY-10619: ----------------------------------- [~jstourac] we frequently bump the version when other changes are planned to avoid conflicts if e.g. two features would both need to do that. [~dlofthouse] or [~swd847] will have to confirm exactly what is coming, but I think https://issues.jboss.org/browse/WFLY-10614 looks like a candidate. > Add version 7 of the management model for the Undertow subsystem > ---------------------------------------------------------------- > > Key: WFLY-10619 > URL: https://issues.jboss.org/browse/WFLY-10619 > Project: WildFly > Issue Type: Task > Components: Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 14.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10644) Remove the EE8 Preview section from Getting_Started_Guide.adoc

by Kabir Khan (JIRA)

Kabir Khan created WFLY-10644: --------------------------------- Summary: Remove the EE8 Preview section from Getting_Started_Guide.adoc Key: WFLY-10644 URL: https://issues.jboss.org/browse/WFLY-10644 Project: WildFly Issue Type: Task Components: Build System Reporter: Kabir Khan Assignee: Kabir Khan Priority: Critical These *-addendum.html files contain licenses for modules brought in for the dual EE8/EE7 support. Once we've removed this support, we should remove these files. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10644) Remove the EE8 Preview section from Getting_Started_Guide.adoc

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-10644?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFLY-10644: ------------------------------ Description: This highlights the dual EE8/EE7 support. Once we've removed this support, we should remove this section. (was: These *-addendum.html files contain licenses for modules brought in for the dual EE8/EE7 support. Once we've removed this support, we should remove these files.) > Remove the EE8 Preview section from Getting_Started_Guide.adoc > -------------------------------------------------------------- > > Key: WFLY-10644 > URL: https://issues.jboss.org/browse/WFLY-10644 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Kabir Khan > Assignee: Kabir Khan > Priority: Critical > > This highlights the dual EE8/EE7 support. Once we've removed this support, we should remove this section. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10643) Remove the *-licenses-addendum.html files

by Kabir Khan (JIRA)

Kabir Khan created WFLY-10643: --------------------------------- Summary: Remove the *-licenses-addendum.html files Key: WFLY-10643 URL: https://issues.jboss.org/browse/WFLY-10643 Project: WildFly Issue Type: Task Components: Build System Reporter: Kabir Khan Assignee: Kabir Khan Priority: Critical These *-addendum.html files contain licenses for modules brought in for the dual EE8/EE7 support. Once we've removed this support, we should remove these files. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2281) MERGE3 blocks unnecessarily in discovery when non-multicast transport is used

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2281?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2281: -------------------------------- Results with {{min_interval=5000}} and {{max_interval=10000}}: {noformat} Results for TCP Min merge time=16031 Max merge time=16091 Avg merge time=16057.0 =================================================================== Results for UDP Min merge time=16022 Max merge time=16107 Avg merge time=16055.0 =================================================================== {noformat} > MERGE3 blocks unnecessarily in discovery when non-multicast transport is used > ----------------------------------------------------------------------------- > > Key: JGRP-2281 > URL: https://issues.jboss.org/browse/JGRP-2281 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.0.13 > > > When MERGE3 uses TCP, it cannot multicast its INFO message, and therefore uses the discovery protocol (e.g. MPING) to fetch the targets to send the INFO message to. > Since we don't know how many responses to expect, we simply block for {{(min_interval + max_interval /2) ms}}. This is bad, as it delays the sending of INFO messages, which results in a partial merge as we're likely not to get responses from *all* members. This delays a full merge, e.g. when we have many singleton subclusters. A heavily split cluster will therefore likely require more merge rounds than necessary when using TCP, compared to (e.g.) UDP. > h4. Solution: > * The discovery process should be _reactive_ rather than blocking: instead of waiting for N seconds, we simply pass a function to the discovery protocol that gets invoked whenever a response has been received > * When the function gets invoked, it sends an INFO to the respective member > * This prevents 1 thread from blocking for N seconds > See \[1\] for details. > \[1\] https://github.com/belaban/JGroups/pull/389 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10640) driver-datasource-class-name and driver-xa-datasource-class-name need to be validated when updating

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-10640?page=com.atlassian.jira.plugin... ] Lin Gao commented on WFLY-10640: -------------------------------- [~maeste] Do you see any problem if only valid +javax.sql.DataSource+ / +javax.sql.XADataSource+ implementation can be specified when updating the JDBC driver or adding the datasource? For now, I can see that the smoke test [DataSourceOperationsUnitTestCase#testAddXaDsWithProperties|https://github...] will fail. > driver-datasource-class-name and driver-xa-datasource-class-name need to be validated when updating > --------------------------------------------------------------------------------------------------- > > Key: WFLY-10640 > URL: https://issues.jboss.org/browse/WFLY-10640 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Lin Gao > Assignee: Lin Gao > Priority: Minor > > Download oracle jdbc driver at http://www.oracle.com/technetwork/database/features/jdbc/jdbc-ucp-122-311... > Install the driver as a module and add the JDBC driver: > {code:bash} > module add --name=com.oracle.jdbc --resources=/opt/Downloads/ojdbc8.jar --dependencies=[javax.api, javax.transaction.api] > /subsystem=datasources/jdbc-driver=oracle:add(driver-name=oracle, driver-module-name=com.oracle.jdbc, driver-datasource-class-name=oracle.jdbc.datasource.OracleDataSource, driver-xa-datasource-class-name=oracle.jdbc.xa.client.OracleXADataSource, driver-class-name=oracle.jdbc.OracleDriver) > {code} > It should fail because the configuraiton: > {code:java} > driver-datasource-class-name=oracle.jdbc.datasource.OracleDataSource > {code} > is wrong, +oracle.jdbc.datasource.OracleDataSource+ is an interface, not a concrete class. > It should be the same for the data-source creation when specifying the datasource-class. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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 2018