[JBoss JIRA] (WFLY-13186) Multiple @PostLoad in @MappedSuperclass
by Cheng Fang (Jira)
[ https://issues.redhat.com/browse/WFLY-13186?page=com.atlassian.jira.plugi... ]
Cheng Fang reassigned WFLY-13186:
---------------------------------
Assignee: Scott Marlow (was: Cheng Fang)
> Multiple @PostLoad in @MappedSuperclass
> ---------------------------------------
>
> Key: WFLY-13186
> URL: https://issues.redhat.com/browse/WFLY-13186
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 18.0.1.Final
> Reporter: Stefan Lindner
> Assignee: Scott Marlow
> Priority: Major
>
> Using {{@PostLoad}} in a {{@MappedSuperclass}} does not work it the annotated method has the same name as in {{@Entity}} class.
> I did not find any hints in the specs about the behavior in this case. Is it allowed?
> h3. This does not work
> {code:title=SuperClass.java|borderStyle=solid}
> @MappedSuperclass
> public abstract Superclass {
> @PostLoad
> public void postLoad() {
> System.out.println("Superclass.postLoad");
> }
> }
> {code}
> {code:title=EntityClass.java|borderStyle=solid}
> @Entity
> public class EntityClass extends SuperClass {
> @PostLoad
> public void postLoad() {
> System.out.println("Superclass.postLoad");
> }
> }
> {code}
> h3. This works
> {code:title=SuperClass.java|borderStyle=solid}
> @MappedSuperclass
> public abstract Superclass {
> @PostLoad
> public void otherPostLoad() {
> System.out.println("Superclass.postLoad");
> }
> }
> {code}
> {code:title=EntityClass.java|borderStyle=solid}
> @Entity
> public class EntityClass extends SuperClass {
> @PostLoad
> public void postLoad() {
> System.out.println("Superclass.postLoad");
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13186) Multiple @PostLoad in @MappedSuperclass
by Cheng Fang (Jira)
[ https://issues.redhat.com/browse/WFLY-13186?page=com.atlassian.jira.plugi... ]
Cheng Fang updated WFLY-13186:
------------------------------
Component/s: (was: EJB)
> Multiple @PostLoad in @MappedSuperclass
> ---------------------------------------
>
> Key: WFLY-13186
> URL: https://issues.redhat.com/browse/WFLY-13186
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 18.0.1.Final
> Reporter: Stefan Lindner
> Assignee: Cheng Fang
> Priority: Major
>
> Using {{@PostLoad}} in a {{@MappedSuperclass}} does not work it the annotated method has the same name as in {{@Entity}} class.
> I did not find any hints in the specs about the behavior in this case. Is it allowed?
> h3. This does not work
> {code:title=SuperClass.java|borderStyle=solid}
> @MappedSuperclass
> public abstract Superclass {
> @PostLoad
> public void postLoad() {
> System.out.println("Superclass.postLoad");
> }
> }
> {code}
> {code:title=EntityClass.java|borderStyle=solid}
> @Entity
> public class EntityClass extends SuperClass {
> @PostLoad
> public void postLoad() {
> System.out.println("Superclass.postLoad");
> }
> }
> {code}
> h3. This works
> {code:title=SuperClass.java|borderStyle=solid}
> @MappedSuperclass
> public abstract Superclass {
> @PostLoad
> public void otherPostLoad() {
> System.out.println("Superclass.postLoad");
> }
> }
> {code}
> {code:title=EntityClass.java|borderStyle=solid}
> @Entity
> public class EntityClass extends SuperClass {
> @PostLoad
> public void postLoad() {
> System.out.println("Superclass.postLoad");
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13186) Multiple @PostLoad in @MappedSuperclass
by Cheng Fang (Jira)
[ https://issues.redhat.com/browse/WFLY-13186?page=com.atlassian.jira.plugi... ]
Cheng Fang updated WFLY-13186:
------------------------------
Component/s: JPA / Hibernate
> Multiple @PostLoad in @MappedSuperclass
> ---------------------------------------
>
> Key: WFLY-13186
> URL: https://issues.redhat.com/browse/WFLY-13186
> Project: WildFly
> Issue Type: Bug
> Components: EJB, JPA / Hibernate
> Affects Versions: 18.0.1.Final
> Reporter: Stefan Lindner
> Assignee: Cheng Fang
> Priority: Major
>
> Using {{@PostLoad}} in a {{@MappedSuperclass}} does not work it the annotated method has the same name as in {{@Entity}} class.
> I did not find any hints in the specs about the behavior in this case. Is it allowed?
> h3. This does not work
> {code:title=SuperClass.java|borderStyle=solid}
> @MappedSuperclass
> public abstract Superclass {
> @PostLoad
> public void postLoad() {
> System.out.println("Superclass.postLoad");
> }
> }
> {code}
> {code:title=EntityClass.java|borderStyle=solid}
> @Entity
> public class EntityClass extends SuperClass {
> @PostLoad
> public void postLoad() {
> System.out.println("Superclass.postLoad");
> }
> }
> {code}
> h3. This works
> {code:title=SuperClass.java|borderStyle=solid}
> @MappedSuperclass
> public abstract Superclass {
> @PostLoad
> public void otherPostLoad() {
> System.out.println("Superclass.postLoad");
> }
> }
> {code}
> {code:title=EntityClass.java|borderStyle=solid}
> @Entity
> public class EntityClass extends SuperClass {
> @PostLoad
> public void postLoad() {
> System.out.println("Superclass.postLoad");
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13186) Multiple @PostLoad in @MappedSuperclass
by Stefan Lindner (Jira)
[ https://issues.redhat.com/browse/WFLY-13186?page=com.atlassian.jira.plugi... ]
Stefan Lindner commented on WFLY-13186:
---------------------------------------
Just one more note: The SUperClass is part of aanotehr module than the EntityClass
> Multiple @PostLoad in @MappedSuperclass
> ---------------------------------------
>
> Key: WFLY-13186
> URL: https://issues.redhat.com/browse/WFLY-13186
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 18.0.1.Final
> Reporter: Stefan Lindner
> Assignee: Cheng Fang
> Priority: Major
>
> Using {{@PostLoad}} in a {{@MappedSuperclass}} does not work it the annotated method has the same name as in {{@Entity}} class.
> I did not find any hints in the specs about the behavior in this case. Is it allowed?
> h3. This does not work
> {code:title=SuperClass.java|borderStyle=solid}
> @MappedSuperclass
> public abstract Superclass {
> @PostLoad
> public void postLoad() {
> System.out.println("Superclass.postLoad");
> }
> }
> {code}
> {code:title=EntityClass.java|borderStyle=solid}
> @Entity
> public class EntityClass extends SuperClass {
> @PostLoad
> public void postLoad() {
> System.out.println("Superclass.postLoad");
> }
> }
> {code}
> h3. This works
> {code:title=SuperClass.java|borderStyle=solid}
> @MappedSuperclass
> public abstract Superclass {
> @PostLoad
> public void otherPostLoad() {
> System.out.println("Superclass.postLoad");
> }
> }
> {code}
> {code:title=EntityClass.java|borderStyle=solid}
> @Entity
> public class EntityClass extends SuperClass {
> @PostLoad
> public void postLoad() {
> System.out.println("Superclass.postLoad");
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13150) Create a Galleon layer for distributable web
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13150?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFLY-13150:
-----------------------------------------
https://github.com/wildfly/wildfly/pull/13015/files#diff-ecd1b3234e2ba2d0... is a prototype of this, added in test-feature-pack. I think it has the correct content. Whether the name of the layer is good, I don't know.
> Create a Galleon layer for distributable web
> --------------------------------------------
>
> Key: WFLY-13150
> URL: https://issues.redhat.com/browse/WFLY-13150
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering, Web (Undertow)
> Reporter: Brian Stansberry
> Assignee: Paul Ferraro
> Priority: Major
> Fix For: 20.0.0.Beta1
>
>
> We have a web-clustering layer that provides the distributable-web subsystem and the related infinispan web session caching resources, configured for multi-server distributed sessions.
> We need a variant of this with infinispan configured for local caching.
> The WFLY-13099 standalone-microprofile.xml config should have this kind of setup; otherwise session sharing does not work . (A failure in org.jboss.as.test.clustering.cluster.web.shared.SharedSessionTestCase if the server uses a config without it shows this.) For WFLY-13099 I can work around this by adding the needed config stuff without a layer, but as everything else needed for those configs are from layers, it's better to use a layer in WF 20.
> Besides it's a good layer to have anyway. :)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13185) Rest-client can't be used without opentracing subsystem present in config
by Jean Francois Denise (Jira)
[ https://issues.redhat.com/browse/WFLY-13185?page=com.atlassian.jira.plugi... ]
Jean Francois Denise commented on WFLY-13185:
---------------------------------------------
I Have attached a reproducer. Unzip it and follow the README.
> Rest-client can't be used without opentracing subsystem present in config
> -------------------------------------------------------------------------
>
> Key: WFLY-13185
> URL: https://issues.redhat.com/browse/WFLY-13185
> Project: WildFly
> Issue Type: Bug
> Components: MP REST Client
> Reporter: Jean Francois Denise
> Assignee: Alessio Soldano
> Priority: Critical
> Attachments: rest-reproducer.zip
>
>
> Trying to provision the following set of galleon layers:
> jaxrs ==> for jaxrs and rest-client
> microprofile-config
> I am getting an NPE. If open-tracing is provisioned along with jaxrs, no NPE and client injection works fine.
> java.lang.NullPointerException
> at org.jboss.resteasy.microprofile.client.RestClientExtension.extractBaseUri(RestClientExtension.java:40)
> at org.jboss.resteasy.microprofile.client.RestClientExtension.registerRestClient(RestClientExtension.java:29)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:95)
> at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:85)
> at org.jboss.weld.injection.MethodInvocationStrategy$SimpleMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:168)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:330)
> at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:123)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:308)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:286)
> at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessAnnotatedType(ContainerLifecycleEvents.java:207)
> at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessAnnotatedType(ContainerLifecycleEvents.java:176)
> at org.jboss.weld.bootstrap.BeanDeployer.processAnnotatedTypes(BeanDeployer.java:166)
> at org.jboss.weld.bootstrap.BeanDeployment.createTypes(BeanDeployment.java:219)
> at org.jboss.weld.bootstrap.WeldStartup.startInitialization(WeldStartup.java:421)
> at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:79)
> at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:96)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:748)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13185) Rest-client can't be used without opentracing subsystem present in config
by Jean Francois Denise (Jira)
[ https://issues.redhat.com/browse/WFLY-13185?page=com.atlassian.jira.plugi... ]
Jean Francois Denise updated WFLY-13185:
----------------------------------------
Attachment: rest-reproducer.zip
> Rest-client can't be used without opentracing subsystem present in config
> -------------------------------------------------------------------------
>
> Key: WFLY-13185
> URL: https://issues.redhat.com/browse/WFLY-13185
> Project: WildFly
> Issue Type: Bug
> Components: MP REST Client
> Reporter: Jean Francois Denise
> Assignee: Alessio Soldano
> Priority: Critical
> Attachments: rest-reproducer.zip
>
>
> Trying to provision the following set of galleon layers:
> jaxrs ==> for jaxrs and rest-client
> microprofile-config
> I am getting an NPE. If open-tracing is provisioned along with jaxrs, no NPE and client injection works fine.
> java.lang.NullPointerException
> at org.jboss.resteasy.microprofile.client.RestClientExtension.extractBaseUri(RestClientExtension.java:40)
> at org.jboss.resteasy.microprofile.client.RestClientExtension.registerRestClient(RestClientExtension.java:29)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:95)
> at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:85)
> at org.jboss.weld.injection.MethodInvocationStrategy$SimpleMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:168)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:330)
> at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:123)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:308)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:286)
> at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessAnnotatedType(ContainerLifecycleEvents.java:207)
> at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessAnnotatedType(ContainerLifecycleEvents.java:176)
> at org.jboss.weld.bootstrap.BeanDeployer.processAnnotatedTypes(BeanDeployer.java:166)
> at org.jboss.weld.bootstrap.BeanDeployment.createTypes(BeanDeployment.java:219)
> at org.jboss.weld.bootstrap.WeldStartup.startInitialization(WeldStartup.java:421)
> at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:79)
> at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:96)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:748)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13188) Exception while exporting metrics during WildFly initialization
by Ehsan Zaery Moghaddam (Jira)
[ https://issues.redhat.com/browse/WFLY-13188?page=com.atlassian.jira.plugi... ]
Ehsan Zaery Moghaddam updated WFLY-13188:
-----------------------------------------
Affects Version/s: 19.0.0.Beta2
> Exception while exporting metrics during WildFly initialization
> ---------------------------------------------------------------
>
> Key: WFLY-13188
> URL: https://issues.redhat.com/browse/WFLY-13188
> Project: WildFly
> Issue Type: Bug
> Components: MP Metrics
> Affects Versions: 18.0.1.Final, 19.0.0.Beta2
> Reporter: Ehsan Zaery Moghaddam
> Assignee: Jeff Mesnil
> Priority: Major
> Labels: Microprofile
>
> When the open tracing system is enabled and some metrics are exposed, if when the WildFly is in the startup process, the Prometheus server calls the /metrics endpoint, WildFly prints a stacktrace for each metrics that is has detected (i.e. more than thousands) with the following message:
> *WFLYCTL0379: System boot is in process; execution of remote management operations is not currently available
> *
> In some cases the error persists, even after the server startup is done and we need to restart the WildFly; but we couldn't find the exact scenario for that.
> Here is an example for wildfly_jpa_second_level_cache_size_in_memory metric:
> 2020-03-02 09:38:06,739 WARN [management I/O-2] [metrics] Unable to export metric wildfly_jpa_second_level_cache_size_in_memory: java.lang.IllegalStateException: WFLYMETRICS0003: Unable to read attribute second-level-cache-size-in-memory on [
> ("deployment" => "application.ear"),
> ("subdeployment" => "application-persistence.jar"),
> ("subsystem" => "jpa"),
> ("hibernate-persistence-unit" => "application.ear/application-persistence.jar#app"),
> ("entity-cache" => "com.app.persistence.entity.Country")
> ]: "WFLYCTL0379: System boot is in process; execution of remote management operations is not currently available".
> at org.wildfly.extension.microprofile.metrics.MetricCollector.readAttributeValue(MetricCollector.java:303)
> at org.wildfly.extension.microprofile.metrics.MetricCollector.access$200(MetricCollector.java:70)
> at org.wildfly.extension.microprofile.metrics.MetricCollector$2.getValue(MetricCollector.java:174)
> at org.wildfly.extension.microprofile.metrics.MetricCollector$2.getValue(MetricCollector.java:171)
> at io.smallrye.metrics.exporters.OpenMetricsExporter.createSimpleValueLine(OpenMetricsExporter.java:445)
> at io.smallrye.metrics.exporters.OpenMetricsExporter.exposeEntries(OpenMetricsExporter.java:178)
> at io.smallrye.metrics.exporters.OpenMetricsExporter.getEntriesForScope(OpenMetricsExporter.java:150)
> at io.smallrye.metrics.exporters.OpenMetricsExporter.exportAllScopes(OpenMetricsExporter.java:101)
> at io.smallrye.metrics.MetricsRequestHandler.handleRequest(MetricsRequestHandler.java:116)
> at io.smallrye.metrics.MetricsRequestHandler.handleRequest(MetricsRequestHandler.java:73)
> at org.wildfly.extension.microprofile.metrics.MetricsContextService$1.handleRequest(MetricsContextService.java:81)
> at org.jboss.as.domain.http.server.security.RealmReadinessHandler.handleRequest(RealmReadinessHandler.java:51)
> at org.jboss.as.domain.http.server.security.ServerErrorReadinessHandler.handleRequest(ServerErrorReadinessHandler.java:35)
> at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:91)
> at io.undertow.server.handlers.ChannelUpgradeHandler.handleRequest(ChannelUpgradeHandler.java:211)
> at io.undertow.server.handlers.cache.CacheHandler.handleRequest(CacheHandler.java:92)
> at io.undertow.server.handlers.error.SimpleErrorPageHandler.handleRequest(SimpleErrorPageHandler.java:78)
> at io.undertow.server.handlers.CanonicalPathHandler.handleRequest(CanonicalPathHandler.java:49)
> at org.jboss.as.domain.http.server.ManagementHttpRequestHandler.handleRequest(ManagementHttpRequestHandler.java:57)
> at org.jboss.as.domain.http.server.cors.CorsHttpHandler.handleRequest(CorsHttpHandler.java:75)
> at org.jboss.as.domain.http.server.ManagementHttpServer$UpgradeFixHandler.handleRequest(ManagementHttpServer.java:666)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:376)
> at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:255)
> at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:136)
> at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:59)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13188) Exception while exporting metrics during WildFly initialization
by Ehsan Zaery Moghaddam (Jira)
Ehsan Zaery Moghaddam created WFLY-13188:
--------------------------------------------
Summary: Exception while exporting metrics during WildFly initialization
Key: WFLY-13188
URL: https://issues.redhat.com/browse/WFLY-13188
Project: WildFly
Issue Type: Bug
Components: MP Metrics
Affects Versions: 18.0.1.Final
Reporter: Ehsan Zaery Moghaddam
Assignee: Jeff Mesnil
When the open tracing system is enabled and some metrics are exposed, if when the WildFly is in the startup process, the Prometheus server calls the /metrics endpoint, WildFly prints a stacktrace for each metrics that is has detected (i.e. more than thousands) with the following message:
*WFLYCTL0379: System boot is in process; execution of remote management operations is not currently available
*
In some cases the error persists, even after the server startup is done and we need to restart the WildFly; but we couldn't find the exact scenario for that.
Here is an example for wildfly_jpa_second_level_cache_size_in_memory metric:
2020-03-02 09:38:06,739 WARN [management I/O-2] [metrics] Unable to export metric wildfly_jpa_second_level_cache_size_in_memory: java.lang.IllegalStateException: WFLYMETRICS0003: Unable to read attribute second-level-cache-size-in-memory on [
("deployment" => "application.ear"),
("subdeployment" => "application-persistence.jar"),
("subsystem" => "jpa"),
("hibernate-persistence-unit" => "application.ear/application-persistence.jar#app"),
("entity-cache" => "com.app.persistence.entity.Country")
]: "WFLYCTL0379: System boot is in process; execution of remote management operations is not currently available".
at org.wildfly.extension.microprofile.metrics.MetricCollector.readAttributeValue(MetricCollector.java:303)
at org.wildfly.extension.microprofile.metrics.MetricCollector.access$200(MetricCollector.java:70)
at org.wildfly.extension.microprofile.metrics.MetricCollector$2.getValue(MetricCollector.java:174)
at org.wildfly.extension.microprofile.metrics.MetricCollector$2.getValue(MetricCollector.java:171)
at io.smallrye.metrics.exporters.OpenMetricsExporter.createSimpleValueLine(OpenMetricsExporter.java:445)
at io.smallrye.metrics.exporters.OpenMetricsExporter.exposeEntries(OpenMetricsExporter.java:178)
at io.smallrye.metrics.exporters.OpenMetricsExporter.getEntriesForScope(OpenMetricsExporter.java:150)
at io.smallrye.metrics.exporters.OpenMetricsExporter.exportAllScopes(OpenMetricsExporter.java:101)
at io.smallrye.metrics.MetricsRequestHandler.handleRequest(MetricsRequestHandler.java:116)
at io.smallrye.metrics.MetricsRequestHandler.handleRequest(MetricsRequestHandler.java:73)
at org.wildfly.extension.microprofile.metrics.MetricsContextService$1.handleRequest(MetricsContextService.java:81)
at org.jboss.as.domain.http.server.security.RealmReadinessHandler.handleRequest(RealmReadinessHandler.java:51)
at org.jboss.as.domain.http.server.security.ServerErrorReadinessHandler.handleRequest(ServerErrorReadinessHandler.java:35)
at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:91)
at io.undertow.server.handlers.ChannelUpgradeHandler.handleRequest(ChannelUpgradeHandler.java:211)
at io.undertow.server.handlers.cache.CacheHandler.handleRequest(CacheHandler.java:92)
at io.undertow.server.handlers.error.SimpleErrorPageHandler.handleRequest(SimpleErrorPageHandler.java:78)
at io.undertow.server.handlers.CanonicalPathHandler.handleRequest(CanonicalPathHandler.java:49)
at org.jboss.as.domain.http.server.ManagementHttpRequestHandler.handleRequest(ManagementHttpRequestHandler.java:57)
at org.jboss.as.domain.http.server.cors.CorsHttpHandler.handleRequest(CorsHttpHandler.java:75)
at org.jboss.as.domain.http.server.ManagementHttpServer$UpgradeFixHandler.handleRequest(ManagementHttpServer.java:666)
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:376)
at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:255)
at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:136)
at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:59)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months