June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10655) SEVERE error on deploy of ear: "Unable to obtain CDI 1.1 utilities for Mojarra"

by Patrick Menagé (Jira)

[ https://issues.jboss.org/browse/WFLY-10655?page=com.atlassian.jira.plugin... ] Patrick Menagé commented on WFLY-10655: --------------------------------------- [~NOTiFY] I solved the problem by adding file beans.xml in webcontent>web-inf, the content of the file being <beans></beans> > SEVERE error on deploy of ear: "Unable to obtain CDI 1.1 utilities for Mojarra" > ------------------------------------------------------------------------------- > > Key: WFLY-10655 > URL: https://issues.jboss.org/browse/WFLY-10655 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, JSF > Affects Versions: 13.0.0.Final > Reporter: Tommasso Borgato > Assignee: Dmitrii Tikhomirov > Priority: Major > Labels: downstream_dependency > Fix For: 14.0.0.Beta2 > > Attachments: clusterbench-ee7-bugged.ear, clusterbench-ee7.ear > > > Affected scenario is [eap-7x-failover-ejb-ejbservlet-undeploy-repl-sync|https://jenkins.hosts.m...]. > Every time the server is stated or re-started, we observed the following SEVERE logs just after clusterbench is deployed (clusterbench is an ear that uses JSF); we observed them systematically on each of the 4 nodes composing the cluster: > {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...] > Already observed a very long time ago: https://issues.jboss.org/browse/WFLY-1946 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12226) IJ020017: Invalid archive: file://RaActivatoractivemq-ra WARN during start with standalone-full*.xml

by Ondrej Kotek (Jira)

[ https://issues.jboss.org/browse/WFLY-12226?page=com.atlassian.jira.plugin... ] Ondrej Kotek updated WFLY-12226: -------------------------------- Description: There is a warning during start with standalone-full*.xml: {noformat} 12:19:04,432 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007: Registered connection factory java:/JmsXA 12:19:04,440 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 84) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory 12:19:04,441 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 83) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory 12:19:04,441 WARN [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020017: Invalid archive: file://RaActivatoractivemq-ra 12:19:04,486 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-3) AMQ151007: Resource adaptor started 12:19:04,486 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatoractivemq-ra 12:19:04,492 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] 12:19:04,493 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory {noformat} For an automation checking the server log for issues, this WARN causes false positive. Hence, I set the Priority to Critical. was: There is a warning during start with standalone-full*.xml: {noformat} 12:19:04,432 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007: Registered connection factory java:/JmsXA 12:19:04,440 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 84) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory 12:19:04,441 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 83) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory 12:19:04,441 WARN [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020017: Invalid archive: file://RaActivatoractivemq-ra 12:19:04,486 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-3) AMQ151007: Resource adaptor started 12:19:04,486 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatoractivemq-ra 12:19:04,492 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] 12:19:04,493 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory {noformat} for an automation checking the server log for issues, this WARN causes false positive. Hence, I set the Priority to Critical. > IJ020017: Invalid archive: file://RaActivatoractivemq-ra WARN during start with standalone-full*.xml > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-12226 > URL: https://issues.jboss.org/browse/WFLY-12226 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 18.0.0.Beta1 > Reporter: Ondrej Kotek > Assignee: Stefano Maestri > Priority: Critical > > There is a warning during start with standalone-full*.xml: > {noformat} > 12:19:04,432 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007: Registered connection factory java:/JmsXA > 12:19:04,440 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 84) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > 12:19:04,441 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 83) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory > 12:19:04,441 WARN [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020017: Invalid archive: file://RaActivatoractivemq-ra > 12:19:04,486 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-3) AMQ151007: Resource adaptor started > 12:19:04,486 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatoractivemq-ra > 12:19:04,492 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] > 12:19:04,493 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory > {noformat} > For an automation checking the server log for issues, this WARN causes false positive. Hence, I set the Priority to Critical. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12226) IJ020017: Invalid archive: file://RaActivatoractivemq-ra WARN during start with standalone-full*.xml

by Ondrej Kotek (Jira)

Ondrej Kotek created WFLY-12226: ----------------------------------- Summary: IJ020017: Invalid archive: file://RaActivatoractivemq-ra WARN during start with standalone-full*.xml Key: WFLY-12226 URL: https://issues.jboss.org/browse/WFLY-12226 Project: WildFly Issue Type: Bug Components: JCA Affects Versions: 18.0.0.Beta1 Reporter: Ondrej Kotek Assignee: Stefano Maestri There is a warning during start with standalone-full*.xml: {noformat} 12:19:04,432 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007: Registered connection factory java:/JmsXA 12:19:04,440 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 84) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory 12:19:04,441 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 83) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory 12:19:04,441 WARN [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020017: Invalid archive: file://RaActivatoractivemq-ra 12:19:04,486 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-3) AMQ151007: Resource adaptor started 12:19:04,486 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatoractivemq-ra 12:19:04,492 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] 12:19:04,493 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory {noformat} for an automation checking the server log for issues, this WARN causes false positive. Hence, I set the Priority to Critical. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1303) WildFly Elytron Tool, Vault command should support set security provider to convert vaults to custom credential store implementation.

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1303?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1303: ---------------------------------- Fix Version/s: 1.9.0.CR1 > WildFly Elytron Tool, Vault command should support set security provider to convert vaults to custom credential store implementation. > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: ELY-1303 > URL: https://issues.jboss.org/browse/ELY-1303 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Reporter: Hynek Švábek > Assignee: Ilia Vassilev > Priority: Major > Fix For: 1.9.0.CR1 > > > WildFly Elytron Tool, Vault command should support set security provider to convert vaults to custom credential store implementation. > Something similar to credential-store command. > http://undertheelytron.blogspot.cz/2017/07/custom-test-credential-store.html -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4204) DMN optimize DT evaluation

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-4204: -------------------------------------- Summary: DMN optimize DT evaluation Key: DROOLS-4204 URL: https://issues.jboss.org/browse/DROOLS-4204 Project: Drools Issue Type: Enhancement Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12225) Document missing discovery capabilities

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-12225: ------------------------------------- Summary: Document missing discovery capabilities Key: WFLY-12225 URL: https://issues.jboss.org/browse/WFLY-12225 Project: WildFly Issue Type: Sub-task Reporter: Radoslav Husar Assignee: Radoslav Husar namely https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/d... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10594) Document missing clustering capabilities

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-10594?page=com.atlassian.jira.plugin... ] Radoslav Husar edited comment on WFLY-10594 at 6/21/19 7:12 AM: ---------------------------------------------------------------- Singleton is missing these https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/c... https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/c... https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/c... was (Author: rhusar): Singleton is missing these https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/c... https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/c... > Document missing clustering capabilities > ---------------------------------------- > > Key: WFLY-10594 > URL: https://issues.jboss.org/browse/WFLY-10594 > Project: WildFly > Issue Type: Sub-task > Components: Clustering > Reporter: Jeff Mesnil > Assignee: Paul Ferraro > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10594) Document missing clustering capabilities

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-10594?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFLY-10594: --------------------------------------- Singleton is missing this one https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/c... > Document missing clustering capabilities > ---------------------------------------- > > Key: WFLY-10594 > URL: https://issues.jboss.org/browse/WFLY-10594 > Project: WildFly > Issue Type: Sub-task > Components: Clustering > Reporter: Jeff Mesnil > Assignee: Paul Ferraro > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10594) Document missing clustering capabilities

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-10594?page=com.atlassian.jira.plugin... ] Radoslav Husar edited comment on WFLY-10594 at 6/21/19 7:11 AM: ---------------------------------------------------------------- Singleton is missing these https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/c... https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/c... was (Author: rhusar): Singleton is missing this one https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/c... > Document missing clustering capabilities > ---------------------------------------- > > Key: WFLY-10594 > URL: https://issues.jboss.org/browse/WFLY-10594 > Project: WildFly > Issue Type: Sub-task > Components: Clustering > Reporter: Jeff Mesnil > Assignee: Paul Ferraro > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10594) Document missing clustering capabilities

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-10594?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFLY-10594: --------------------------------------- JGroups is missing these https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/c... https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/c... https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/c... https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/c... > Document missing clustering capabilities > ---------------------------------------- > > Key: WFLY-10594 > URL: https://issues.jboss.org/browse/WFLY-10594 > Project: WildFly > Issue Type: Sub-task > Components: Clustering > Reporter: Jeff Mesnil > Assignee: Paul Ferraro > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 June 2019