[JBoss JIRA] (ISPN-12060) WildFly modules integration tests do not work on WildFly 19
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-12060?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-12060:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/8515
> WildFly modules integration tests do not work on WildFly 19
> -----------------------------------------------------------
>
> Key: ISPN-12060
> URL: https://issues.redhat.com/browse/ISPN-12060
> Project: Infinispan
> Issue Type: Bug
> Components: WildFly modules
> Affects Versions: 11.0.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.1.Final
>
>
> The modules build with the version of microprofile-config components from WildFly 19.0.0: microprofile-config-api 1.4 and smallrye-config 1.6.2. But the wildfly-modules integration tests run on WildFly 18.0.0, which has microprofile-config-api 1.3 and [smallrye-config 1.3.4|https://github.com/wildfly/wildfly/blob/18.0.x/pom.xml#L278].
> This happens if I change {{appserver.version}} to 19.0.0:
> {noformat}
> 09:23:15.051 [ERROR] org.infinispan.test.integration.as.cdi.GreetingCacheManagerIT Time elapsed: 0.009 s <<< ERROR!
> org.jboss.arquillian.container.spi.client.container.DeploymentException:
> Cannot deploy cdi-cm.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"cdi-cm.war\".WeldStartService" => "Failed to start service
> Caused by: org.jboss.weld.exceptions.DeploymentException: No ConfigProviderResolver implementation found!
> Caused by: java.lang.IllegalStateException: No ConfigProviderResolver implementation found!"}}}}
> {noformat}
> The full exception is
> {noformat}
> 2020-06-29 09:42:15,083 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."cdi-cm.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.u
> nit."cdi-cm.war".WeldStartService: Failed to start service
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: org.jboss.weld.exceptions.DeploymentException: No ConfigProviderResolver implementation found!
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.events.AbstractDeploymentContainerEvent.fire(AbstractDeploymentContainerEvent.java:38)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.events.AfterDeploymentValidationImpl.fire(AfterDeploymentValidationImpl.java:28)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.WeldStartup.validateBeans(WeldStartup.java:505)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:93)
> at org.jboss.as.weld@19.1.0.Final//org.jboss.as.weld.WeldStartService.start(WeldStartService.java:98)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> ... 6 more
> Caused by: java.lang.IllegalStateException: No ConfigProviderResolver implementation found!
> at org.eclipse.microprofile.config.api//org.eclipse.microprofile.config.spi.ConfigProviderResolver.loadSpi(ConfigProviderResolver.java:125)
> at org.eclipse.microprofile.config.api//org.eclipse.microprofile.config.spi.ConfigProviderResolver.instance(ConfigProviderResolver.java:110)
> at org.eclipse.microprofile.config.api//org.eclipse.microprofile.config.ConfigProvider.getConfig(ConfigProvider.java:91)
> at io.smallrye.config//io.smallrye.config.inject.ConfigExtension.validate(ConfigExtension.java:93)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:95)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:85)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.injection.MethodInvocationStrategy$SimpleMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:168)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:330)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:123)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:308)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:286)
> at javax.enterprise.api//javax.enterprise.inject.spi.ObserverMethod.notify(ObserverMethod.java:124)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.util.Observers.notify(Observers.java:166)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:285)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:273)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:177)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:171)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:53)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.events.AbstractDeploymentContainerEvent.fire(AbstractDeploymentContainerEvent.java:35)
> ... 12 more
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 10 months
[JBoss JIRA] (ISPN-7842) Declarative indexed entity mapping
by Yoann Rodière (Jira)
[ https://issues.redhat.com/browse/ISPN-7842?page=com.atlassian.jira.plugin... ]
Yoann Rodière commented on ISPN-7842:
-------------------------------------
Just a heads-up: the programmatic mapping API is different in Hibernate Search 6 is different, down to some concepts that are quite different (e.g. there's not just one type of field but multiple types: FullTextField, KeywordField, ScaledNumberField; FieldBridge was split into multiple different classes; the concept of Binder was introduced, etc.).
If we introduce an XML schema for declarative mapping, we might want to model it after the Search 6 concepts rather than the Search 5 concepts currently exposed in Infinispan. Or better, model it after Infinispan-specific concepts that are a subset of Search 6 concepts (e.g. annotations in infinispan packages); but those don't exist yet.
> Declarative indexed entity mapping
> ----------------------------------
>
> Key: ISPN-7842
> URL: https://issues.redhat.com/browse/ISPN-7842
> Project: Infinispan
> Issue Type: Enhancement
> Components: Configuration, Embedded Querying
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Minor
>
> We need a way to list annotation-less indexed entities in the infinispan XML.
> The
> {noformat}
> <indexed-entities>
> {noformat}
> element schema will need to be extended as follows:
> {code:xml}
> <indexed-entities>
> <!-- annotated entity -->
> <indexed-entity>org.infinispan.query.queries.faceting.Car</indexed-entity>
> <!-- non-annotated entity -->
> <indexed-entity-mapping>
> <!-- the FQN of the class to index -->
> <class>my.domain.model.Author</class>
> <!-- optional -->
> <spatial name="place" mode="HASH"/>
> <!-- list of indexed properties -->
> <property name="name" type="method">
> <field store="true" index="true" analyze="true" norms="true" term-vector="yes" boost="0.5"/>
> </property>
> <property name="title" type="method">
> <field store="true" index="true" analyze="true" norms="true" term-vector="yes" boost="0.5" analyzer="titleanalyzer"/>
> </property>
> <property type="method" name="birthdate">
> <field store="true" index="true" analyze="true" norms="true" term-vector="yes" boost="0.5"/>
> <date-bridge resolution="DAY"/>
> </property>
>
> <property type="method" name="city">
> <spatial name="name" store="true" boost="0.5" spatial-mode="RANGE" />
> </property>
> </indexed-entity-mapping>
> </indexed-entities>
>
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 10 months
[JBoss JIRA] (ISPN-12060) WildFly modules do not work on WildFly 19
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-12060?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-12060:
--------------------------------
Status: Open (was: New)
> WildFly modules do not work on WildFly 19
> -----------------------------------------
>
> Key: ISPN-12060
> URL: https://issues.redhat.com/browse/ISPN-12060
> Project: Infinispan
> Issue Type: Bug
> Components: WildFly modules
> Affects Versions: 11.0.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.1.Final
>
>
> The modules build with the version of microprofile-config components from WildFly 19.0.0: microprofile-config-api 1.4 and smallrye-config 1.6.2. But the wildfly-modules integration tests run on WildFly 18.0.0, which has microprofile-config-api 1.3 and [smallrye-config 1.3.4|https://github.com/wildfly/wildfly/blob/18.0.x/pom.xml#L278].
> This happens if I change {{appserver.version}} to 19.0.0:
> {noformat}
> 09:23:15.051 [ERROR] org.infinispan.test.integration.as.cdi.GreetingCacheManagerIT Time elapsed: 0.009 s <<< ERROR!
> org.jboss.arquillian.container.spi.client.container.DeploymentException:
> Cannot deploy cdi-cm.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"cdi-cm.war\".WeldStartService" => "Failed to start service
> Caused by: org.jboss.weld.exceptions.DeploymentException: No ConfigProviderResolver implementation found!
> Caused by: java.lang.IllegalStateException: No ConfigProviderResolver implementation found!"}}}}
> {noformat}
> The full exception is
> {noformat}
> 2020-06-29 09:42:15,083 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."cdi-cm.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.u
> nit."cdi-cm.war".WeldStartService: Failed to start service
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: org.jboss.weld.exceptions.DeploymentException: No ConfigProviderResolver implementation found!
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.events.AbstractDeploymentContainerEvent.fire(AbstractDeploymentContainerEvent.java:38)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.events.AfterDeploymentValidationImpl.fire(AfterDeploymentValidationImpl.java:28)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.WeldStartup.validateBeans(WeldStartup.java:505)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:93)
> at org.jboss.as.weld@19.1.0.Final//org.jboss.as.weld.WeldStartService.start(WeldStartService.java:98)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> ... 6 more
> Caused by: java.lang.IllegalStateException: No ConfigProviderResolver implementation found!
> at org.eclipse.microprofile.config.api//org.eclipse.microprofile.config.spi.ConfigProviderResolver.loadSpi(ConfigProviderResolver.java:125)
> at org.eclipse.microprofile.config.api//org.eclipse.microprofile.config.spi.ConfigProviderResolver.instance(ConfigProviderResolver.java:110)
> at org.eclipse.microprofile.config.api//org.eclipse.microprofile.config.ConfigProvider.getConfig(ConfigProvider.java:91)
> at io.smallrye.config//io.smallrye.config.inject.ConfigExtension.validate(ConfigExtension.java:93)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:95)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:85)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.injection.MethodInvocationStrategy$SimpleMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:168)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:330)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:123)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:308)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:286)
> at javax.enterprise.api//javax.enterprise.inject.spi.ObserverMethod.notify(ObserverMethod.java:124)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.util.Observers.notify(Observers.java:166)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:285)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:273)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:177)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:171)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:53)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.events.AbstractDeploymentContainerEvent.fire(AbstractDeploymentContainerEvent.java:35)
> ... 12 more
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 10 months
[JBoss JIRA] (ISPN-12060) WildFly modules integration tests do not work on WildFly 19
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-12060?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-12060:
--------------------------------
Summary: WildFly modules integration tests do not work on WildFly 19 (was: WildFly modules do not work on WildFly 19)
> WildFly modules integration tests do not work on WildFly 19
> -----------------------------------------------------------
>
> Key: ISPN-12060
> URL: https://issues.redhat.com/browse/ISPN-12060
> Project: Infinispan
> Issue Type: Bug
> Components: WildFly modules
> Affects Versions: 11.0.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.1.Final
>
>
> The modules build with the version of microprofile-config components from WildFly 19.0.0: microprofile-config-api 1.4 and smallrye-config 1.6.2. But the wildfly-modules integration tests run on WildFly 18.0.0, which has microprofile-config-api 1.3 and [smallrye-config 1.3.4|https://github.com/wildfly/wildfly/blob/18.0.x/pom.xml#L278].
> This happens if I change {{appserver.version}} to 19.0.0:
> {noformat}
> 09:23:15.051 [ERROR] org.infinispan.test.integration.as.cdi.GreetingCacheManagerIT Time elapsed: 0.009 s <<< ERROR!
> org.jboss.arquillian.container.spi.client.container.DeploymentException:
> Cannot deploy cdi-cm.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"cdi-cm.war\".WeldStartService" => "Failed to start service
> Caused by: org.jboss.weld.exceptions.DeploymentException: No ConfigProviderResolver implementation found!
> Caused by: java.lang.IllegalStateException: No ConfigProviderResolver implementation found!"}}}}
> {noformat}
> The full exception is
> {noformat}
> 2020-06-29 09:42:15,083 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."cdi-cm.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.u
> nit."cdi-cm.war".WeldStartService: Failed to start service
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: org.jboss.weld.exceptions.DeploymentException: No ConfigProviderResolver implementation found!
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.events.AbstractDeploymentContainerEvent.fire(AbstractDeploymentContainerEvent.java:38)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.events.AfterDeploymentValidationImpl.fire(AfterDeploymentValidationImpl.java:28)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.WeldStartup.validateBeans(WeldStartup.java:505)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:93)
> at org.jboss.as.weld@19.1.0.Final//org.jboss.as.weld.WeldStartService.start(WeldStartService.java:98)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> ... 6 more
> Caused by: java.lang.IllegalStateException: No ConfigProviderResolver implementation found!
> at org.eclipse.microprofile.config.api//org.eclipse.microprofile.config.spi.ConfigProviderResolver.loadSpi(ConfigProviderResolver.java:125)
> at org.eclipse.microprofile.config.api//org.eclipse.microprofile.config.spi.ConfigProviderResolver.instance(ConfigProviderResolver.java:110)
> at org.eclipse.microprofile.config.api//org.eclipse.microprofile.config.ConfigProvider.getConfig(ConfigProvider.java:91)
> at io.smallrye.config//io.smallrye.config.inject.ConfigExtension.validate(ConfigExtension.java:93)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:95)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:85)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.injection.MethodInvocationStrategy$SimpleMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:168)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:330)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:123)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:308)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:286)
> at javax.enterprise.api//javax.enterprise.inject.spi.ObserverMethod.notify(ObserverMethod.java:124)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.util.Observers.notify(Observers.java:166)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:285)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:273)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:177)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:171)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:53)
> at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.events.AbstractDeploymentContainerEvent.fire(AbstractDeploymentContainerEvent.java:35)
> ... 12 more
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 10 months
[JBoss JIRA] (ISPN-12060) WildFly modules do not work on WildFly 19
by Dan Berindei (Jira)
Dan Berindei created ISPN-12060:
-----------------------------------
Summary: WildFly modules do not work on WildFly 19
Key: ISPN-12060
URL: https://issues.redhat.com/browse/ISPN-12060
Project: Infinispan
Issue Type: Bug
Components: WildFly modules
Affects Versions: 11.0.0.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 11.0.1.Final
The modules build with the version of microprofile-config components from WildFly 19.0.0: microprofile-config-api 1.4 and smallrye-config 1.6.2. But the wildfly-modules integration tests run on WildFly 18.0.0, which has microprofile-config-api 1.3 and [smallrye-config 1.3.4|https://github.com/wildfly/wildfly/blob/18.0.x/pom.xml#L278].
This happens if I change {{appserver.version}} to 19.0.0:
{noformat}
09:23:15.051 [ERROR] org.infinispan.test.integration.as.cdi.GreetingCacheManagerIT Time elapsed: 0.009 s <<< ERROR!
org.jboss.arquillian.container.spi.client.container.DeploymentException:
Cannot deploy cdi-cm.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"cdi-cm.war\".WeldStartService" => "Failed to start service
Caused by: org.jboss.weld.exceptions.DeploymentException: No ConfigProviderResolver implementation found!
Caused by: java.lang.IllegalStateException: No ConfigProviderResolver implementation found!"}}}}
{noformat}
The full exception is
{noformat}
2020-06-29 09:42:15,083 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."cdi-cm.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.u
nit."cdi-cm.war".WeldStartService: Failed to start service
at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731)
at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: org.jboss.weld.exceptions.DeploymentException: No ConfigProviderResolver implementation found!
at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.events.AbstractDeploymentContainerEvent.fire(AbstractDeploymentContainerEvent.java:38)
at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.events.AfterDeploymentValidationImpl.fire(AfterDeploymentValidationImpl.java:28)
at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.WeldStartup.validateBeans(WeldStartup.java:505)
at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:93)
at org.jboss.as.weld@19.1.0.Final//org.jboss.as.weld.WeldStartService.start(WeldStartService.java:98)
at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
... 6 more
Caused by: java.lang.IllegalStateException: No ConfigProviderResolver implementation found!
at org.eclipse.microprofile.config.api//org.eclipse.microprofile.config.spi.ConfigProviderResolver.loadSpi(ConfigProviderResolver.java:125)
at org.eclipse.microprofile.config.api//org.eclipse.microprofile.config.spi.ConfigProviderResolver.instance(ConfigProviderResolver.java:110)
at org.eclipse.microprofile.config.api//org.eclipse.microprofile.config.ConfigProvider.getConfig(ConfigProvider.java:91)
at io.smallrye.config//io.smallrye.config.inject.ConfigExtension.validate(ConfigExtension.java:93)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:95)
at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:85)
at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.injection.MethodInvocationStrategy$SimpleMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:168)
at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:330)
at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:123)
at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:308)
at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:286)
at javax.enterprise.api//javax.enterprise.inject.spi.ObserverMethod.notify(ObserverMethod.java:124)
at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.util.Observers.notify(Observers.java:166)
at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:285)
at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:273)
at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:177)
at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:171)
at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:53)
at org.jboss.weld.core@3.1.3.Final//org.jboss.weld.bootstrap.events.AbstractDeploymentContainerEvent.fire(AbstractDeploymentContainerEvent.java:35)
... 12 more
{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 10 months
[JBoss JIRA] (ISPN-12043) Shared stores should not have (add|remove)Segments methods invoked
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-12043?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-12043:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Shared stores should not have (add|remove)Segments methods invoked
> ------------------------------------------------------------------
>
> Key: ISPN-12043
> URL: https://issues.redhat.com/browse/ISPN-12043
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 11.0.0.Final
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
> Fix For: 12.0.0.Final, 11.0.1.Final
>
>
> A shared store should never have its remove or add segments methods invoked as the store should always own all segments at all times. We should add this check in the PeristenceManagerImpl and technically we should only invoke these methods if the store is also configured as being segmented.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 10 months
[JBoss JIRA] (ISPN-11974) Remove GenericJbossMarshaller automatic configuration
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-11974?page=com.atlassian.jira.plugi... ]
Will Burns reopened ISPN-11974:
-------------------------------
> Remove GenericJbossMarshaller automatic configuration
> -----------------------------------------------------
>
> Key: ISPN-11974
> URL: https://issues.redhat.com/browse/ISPN-11974
> Project: Infinispan
> Issue Type: Task
> Components: Configuration, Hot Rod
> Affects Versions: 11.0.0.CR1
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> Currently if the {{infinispan-jboss-marshalling}} module is on the client classpath we automatically configure the client marshaller to be {{GenericJBossMarshaller}}. This causes issues with our testsuite, as the module is often on the classpath. Furthermore, we want users to start transitioning away from JBoss Marshalling. Therefore, from Infinispan -12- 11 we should no automatically configure this marshaller if the module is present.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 10 months