[JBoss JIRA] (WFLY-11933) Error when accessing metrics with RBAC enabled
by Claudio Weiler (Jira)
[ https://issues.redhat.com/browse/WFLY-11933?page=com.atlassian.jira.plugi... ]
Claudio Weiler updated WFLY-11933:
----------------------------------
Description:
When RBAC is enabled for management in Wildfly, metrics throws exception:
java.lang.IllegalStateException: WFLYMETRICS0003: Unable to read attribute XAForgetAverageTime on [
("subsystem" => "datasources"),
("data-source" => "ExampleDS"),
("statistics" => "pool")
]: "WFLYCTL0216: Management resource '[
(\"subsystem\" => \"datasources\"),
(\"data-source\" => \"ExampleDS\"),
(\"statistics\" => \"pool\")
]' not found".
was:
When RBAC is enabled for management in Wildfly 16, metrics throws exception:
java.lang.IllegalStateException: WFLYMETRICS0003: Unable to read attribute XAForgetAverageTime on [
("subsystem" => "datasources"),
("data-source" => "ExampleDS"),
("statistics" => "pool")
]: "WFLYCTL0216: Management resource '[
(\"subsystem\" => \"datasources\"),
(\"data-source\" => \"ExampleDS\"),
(\"statistics\" => \"pool\")
]' not found".
> Error when accessing metrics with RBAC enabled
> ----------------------------------------------
>
> Key: WFLY-11933
> URL: https://issues.redhat.com/browse/WFLY-11933
> Project: WildFly
> Issue Type: Bug
> Components: Management, MP Metrics
> Affects Versions: 16.0.0.Final, 17.0.0.Final, 17.0.1.Final
> Reporter: Claudio Weiler
> Assignee: Jeff Mesnil
> Priority: Major
>
> When RBAC is enabled for management in Wildfly, metrics throws exception:
> java.lang.IllegalStateException: WFLYMETRICS0003: Unable to read attribute XAForgetAverageTime on [
> ("subsystem" => "datasources"),
> ("data-source" => "ExampleDS"),
> ("statistics" => "pool")
> ]: "WFLYCTL0216: Management resource '[
> (\"subsystem\" => \"datasources\"),
> (\"data-source\" => \"ExampleDS\"),
> (\"statistics\" => \"pool\")
> ]' not found".
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (JGRP-2454) Documentation is wrong for ForkChannel creation / Initial messages on fork channel are lost
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2454?page=com.atlassian.jira.plugin... ]
Bela Ban resolved JGRP-2454.
----------------------------
Resolution: Done
> Documentation is wrong for ForkChannel creation / Initial messages on fork channel are lost
> -------------------------------------------------------------------------------------------
>
> Key: JGRP-2454
> URL: https://issues.redhat.com/browse/JGRP-2454
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.1.8
> Reporter: Mirko Streckenbach
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 5.0, 4.2.1
>
>
> The documentation at
> http://www.jgroups.org/manual/html/user-advanced.html#ForkChannelCreation
> has the following example:
> {code}
> JChannel main_ch=new JChannel("/home/bela/udp.xml").name("A");
> ForkChannel fork_ch=new ForkChannel(main_ch, "lock", "fork-ch4",
> new CENTRAL_LOCK(), new STATS());
> fork_ch.connect("bla");
> main_ch.connect("cluster");
> {code}
> This does not work as "fork_ch.connect" will throw an IllegalStateException because the main channel is not connected at that point.
> But if the connects are reversed, messages for the fork channel may arrive before the fork channel is fully established and cause warnings like
> {code}
> Feb 20, 2020 6:15:37 PM org.jgroups.protocols.FORK$1 handleUnknownForkChannel
> WARNING: marian-20309: fork-channel for id=fork-ch4 not found; discarding message
> {code}
> My application will send a message to every new member in the cluster on a specific fork channel (in ReceiverAdapter.viewAccepted). These message usually get lost. Is there an alternate pattern for that?
> I can provide example code if required.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (JGRP-2454) Documentation is wrong for ForkChannel creation / Initial messages on fork channel are lost
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2454?page=com.atlassian.jira.plugin... ]
Bela Ban commented on JGRP-2454:
--------------------------------
I changed the manual for 4.x and 5. The main channel must be connected when connecting the ForkChannel, so I reversed the 2 lines in question. Note that ForkChannelTest does this correctly.
Sending messages in {{viewAccepted()}} is not really an anti-pattern, but not recommended, either. Say you're installing view \{\{A,B,C,D\}\}: not everybody may install this new view at exactly the same time, e.g. if C install it with a delay, then the message from D will be discarded as D is not yet a member of C's (old) view. This applies to both regular and fork channels.
> Documentation is wrong for ForkChannel creation / Initial messages on fork channel are lost
> -------------------------------------------------------------------------------------------
>
> Key: JGRP-2454
> URL: https://issues.redhat.com/browse/JGRP-2454
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.1.8
> Reporter: Mirko Streckenbach
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 5.0, 4.2.1
>
>
> The documentation at
> http://www.jgroups.org/manual/html/user-advanced.html#ForkChannelCreation
> has the following example:
> {code}
> JChannel main_ch=new JChannel("/home/bela/udp.xml").name("A");
> ForkChannel fork_ch=new ForkChannel(main_ch, "lock", "fork-ch4",
> new CENTRAL_LOCK(), new STATS());
> fork_ch.connect("bla");
> main_ch.connect("cluster");
> {code}
> This does not work as "fork_ch.connect" will throw an IllegalStateException because the main channel is not connected at that point.
> But if the connects are reversed, messages for the fork channel may arrive before the fork channel is fully established and cause warnings like
> {code}
> Feb 20, 2020 6:15:37 PM org.jgroups.protocols.FORK$1 handleUnknownForkChannel
> WARNING: marian-20309: fork-channel for id=fork-ch4 not found; discarding message
> {code}
> My application will send a message to every new member in the cluster on a specific fork channel (in ReceiverAdapter.viewAccepted). These message usually get lost. Is there an alternate pattern for that?
> I can provide example code if required.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-13215) Upgrade Apache Artemis to 2.11.0
by Emmanuel Hugonnet (Jira)
Emmanuel Hugonnet created WFLY-13215:
----------------------------------------
Summary: Upgrade Apache Artemis to 2.11.0
Key: WFLY-13215
URL: https://issues.redhat.com/browse/WFLY-13215
Project: WildFly
Issue Type: Component Upgrade
Components: JMS
Affects Versions: 20.0.0.Beta1
Reporter: Emmanuel Hugonnet
Assignee: Emmanuel Hugonnet
Upgrade apache Artemis to the latest stable version: 2.11.0
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (JGRP-2451) FD_ALL3: improvements over FD_ALL
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2451?page=com.atlassian.jira.plugin... ]
Bela Ban resolved JGRP-2451.
----------------------------
Resolution: Done
Implemented on master and backported to 4.x
> FD_ALL3: improvements over FD_ALL
> ---------------------------------
>
> Key: JGRP-2451
> URL: https://issues.redhat.com/browse/JGRP-2451
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 5.0, 4.2.1
>
>
> Improvements to {{FD_ALL}}.
> * Messages should count as heartbeats ({{msg_counts_as_heartbeat}} should be *default*, and as such, deprecated/removed).
> * When a multicast message is sent before {{interval}} elapsed, we suppress sending a heartbeat
> It is crucial that setting the timestamp in the map is quick, especially since this is done on every message. This should not be an issue, as we fetch the current time from the time service, which does *not* call {{System.nanoTime()}} or {{System.currentTimeMillis()}} every time.
> The advantage is that we only send heartbeats when there is no (multicast) traffic, and we don't suspect a member P when heartbeats have been missing despite receiving traffic from P.
> We need to think about whether to consider unicast messages, too, on the sender side: we could populate a bit map with messages sent to members: on a unicast message to P, P's bit would be set in the bit. On a multicast message, all bits would be set. Then, we could selectively send heartbeats only to members with bits set to 0.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (JGRP-2451) FD_ALL3: improvements over FD_ALL
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2451?page=com.atlassian.jira.plugin... ]
Bela Ban updated JGRP-2451:
---------------------------
Fix Version/s: 4.2.1
> FD_ALL3: improvements over FD_ALL
> ---------------------------------
>
> Key: JGRP-2451
> URL: https://issues.redhat.com/browse/JGRP-2451
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 5.0, 4.2.1
>
>
> Improvements to {{FD_ALL}}.
> * Messages should count as heartbeats ({{msg_counts_as_heartbeat}} should be *default*, and as such, deprecated/removed).
> * When a multicast message is sent before {{interval}} elapsed, we suppress sending a heartbeat
> It is crucial that setting the timestamp in the map is quick, especially since this is done on every message. This should not be an issue, as we fetch the current time from the time service, which does *not* call {{System.nanoTime()}} or {{System.currentTimeMillis()}} every time.
> The advantage is that we only send heartbeats when there is no (multicast) traffic, and we don't suspect a member P when heartbeats have been missing despite receiving traffic from P.
> We need to think about whether to consider unicast messages, too, on the sender side: we could populate a bit map with messages sent to members: on a unicast message to P, P's bit would be set in the bit. On a multicast message, all bits would be set. Then, we could selectively send heartbeats only to members with bits set to 0.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-11792) Error creating server pooled-connection-factory
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFLY-11792?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet commented on WFLY-11792:
------------------------------------------
Now the operation will fail with a /subsystem=messaging-activemq/server=srv-foo/discovery-group=dg1:add
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0155: 'socket-binding' may not be null",
"rolled-back" => true
} so closing it
> Error creating server pooled-connection-factory
> -----------------------------------------------
>
> Key: WFLY-11792
> URL: https://issues.redhat.com/browse/WFLY-11792
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Claudio Miranda
> Assignee: Emmanuel Hugonnet
> Priority: Major
> Fix For: 19.0.0.Beta3
>
>
> Try to add a pooled-connection-factory, it returns as failure caused by a NullPointerException.
> To reproduce:
> {code}
> batch
> /subsystem=messaging-activemq/server=srv-foo:add
> /subsystem=messaging-activemq/server=srv-foo/path=bindings-directory:add(path=byhmzspzrcxq)
> /subsystem=messaging-activemq/server=srv-foo/path=journal-directory:add(path=yghaapgbokdd)
> /subsystem=messaging-activemq/server=srv-foo/path=large-messages-directory:add(path=qjaagiljbwjh)
> /subsystem=messaging-activemq/server=srv-foo/path=paging-directory:add(path=sbxvhqytamqe)
> run-batch
> /subsystem=messaging-activemq/server=srv-foo/discovery-group=dg1:add
> /subsystem=messaging-activemq/server=srv-foo/pooled-connection-factory=pool1:add(discovery-group=dg1,entries=[foobar])
> {code}
> {code}
> 19:21:20,772 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.messaging-activemq.srv-update-wwavjsiodinh.jms.pooled-connection-factory.pool1: org.jboss.msc.service.StartException in service jboss.messaging-activemq.srv-update-wwavjsiodinh.jms.pooled-connection-factory.pool1: WFLYMSGAMQ0028: Failed to create resource adapter
> at org.wildfly.extension.messaging.activemq.jms.PooledConnectionFactoryService.start(PooledConnectionFactoryService.java:328)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
> 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)
> Caused by: java.lang.NullPointerException
> at org.wildfly.extension.messaging.activemq.jms.PooledConnectionFactoryService.createService(PooledConnectionFactoryService.java:381)
> at org.wildfly.extension.messaging.activemq.jms.PooledConnectionFactoryService.start(PooledConnectionFactoryService.java:325)
> ... 8 more
> 19:21:20,773 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "srv-update-wwavjsiodinh"),
> ("pooled-connection-factory" => "pool1")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.messaging-activemq.srv-update-wwavjsiodinh.jms.pooled-connection-factory.pool1" => "WFLYMSGAMQ0028: Failed to create resource adapter
> Caused by: java.lang.NullPointerException"}}
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-11792) Error creating server pooled-connection-factory
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFLY-11792?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet resolved WFLY-11792.
--------------------------------------
Resolution: Out of Date
> Error creating server pooled-connection-factory
> -----------------------------------------------
>
> Key: WFLY-11792
> URL: https://issues.redhat.com/browse/WFLY-11792
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Claudio Miranda
> Assignee: Emmanuel Hugonnet
> Priority: Major
> Fix For: 19.0.0.Beta3
>
>
> Try to add a pooled-connection-factory, it returns as failure caused by a NullPointerException.
> To reproduce:
> {code}
> batch
> /subsystem=messaging-activemq/server=srv-foo:add
> /subsystem=messaging-activemq/server=srv-foo/path=bindings-directory:add(path=byhmzspzrcxq)
> /subsystem=messaging-activemq/server=srv-foo/path=journal-directory:add(path=yghaapgbokdd)
> /subsystem=messaging-activemq/server=srv-foo/path=large-messages-directory:add(path=qjaagiljbwjh)
> /subsystem=messaging-activemq/server=srv-foo/path=paging-directory:add(path=sbxvhqytamqe)
> run-batch
> /subsystem=messaging-activemq/server=srv-foo/discovery-group=dg1:add
> /subsystem=messaging-activemq/server=srv-foo/pooled-connection-factory=pool1:add(discovery-group=dg1,entries=[foobar])
> {code}
> {code}
> 19:21:20,772 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.messaging-activemq.srv-update-wwavjsiodinh.jms.pooled-connection-factory.pool1: org.jboss.msc.service.StartException in service jboss.messaging-activemq.srv-update-wwavjsiodinh.jms.pooled-connection-factory.pool1: WFLYMSGAMQ0028: Failed to create resource adapter
> at org.wildfly.extension.messaging.activemq.jms.PooledConnectionFactoryService.start(PooledConnectionFactoryService.java:328)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
> 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)
> Caused by: java.lang.NullPointerException
> at org.wildfly.extension.messaging.activemq.jms.PooledConnectionFactoryService.createService(PooledConnectionFactoryService.java:381)
> at org.wildfly.extension.messaging.activemq.jms.PooledConnectionFactoryService.start(PooledConnectionFactoryService.java:325)
> ... 8 more
> 19:21:20,773 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "srv-update-wwavjsiodinh"),
> ("pooled-connection-factory" => "pool1")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.messaging-activemq.srv-update-wwavjsiodinh.jms.pooled-connection-factory.pool1" => "WFLYMSGAMQ0028: Failed to create resource adapter
> Caused by: java.lang.NullPointerException"}}
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (WFLY-11792) Error creating server pooled-connection-factory
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFLY-11792?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet updated WFLY-11792:
-------------------------------------
Fix Version/s: 19.0.0.Beta3
> Error creating server pooled-connection-factory
> -----------------------------------------------
>
> Key: WFLY-11792
> URL: https://issues.redhat.com/browse/WFLY-11792
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Claudio Miranda
> Assignee: Emmanuel Hugonnet
> Priority: Major
> Fix For: 19.0.0.Beta3
>
>
> Try to add a pooled-connection-factory, it returns as failure caused by a NullPointerException.
> To reproduce:
> {code}
> batch
> /subsystem=messaging-activemq/server=srv-foo:add
> /subsystem=messaging-activemq/server=srv-foo/path=bindings-directory:add(path=byhmzspzrcxq)
> /subsystem=messaging-activemq/server=srv-foo/path=journal-directory:add(path=yghaapgbokdd)
> /subsystem=messaging-activemq/server=srv-foo/path=large-messages-directory:add(path=qjaagiljbwjh)
> /subsystem=messaging-activemq/server=srv-foo/path=paging-directory:add(path=sbxvhqytamqe)
> run-batch
> /subsystem=messaging-activemq/server=srv-foo/discovery-group=dg1:add
> /subsystem=messaging-activemq/server=srv-foo/pooled-connection-factory=pool1:add(discovery-group=dg1,entries=[foobar])
> {code}
> {code}
> 19:21:20,772 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.messaging-activemq.srv-update-wwavjsiodinh.jms.pooled-connection-factory.pool1: org.jboss.msc.service.StartException in service jboss.messaging-activemq.srv-update-wwavjsiodinh.jms.pooled-connection-factory.pool1: WFLYMSGAMQ0028: Failed to create resource adapter
> at org.wildfly.extension.messaging.activemq.jms.PooledConnectionFactoryService.start(PooledConnectionFactoryService.java:328)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
> 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)
> Caused by: java.lang.NullPointerException
> at org.wildfly.extension.messaging.activemq.jms.PooledConnectionFactoryService.createService(PooledConnectionFactoryService.java:381)
> at org.wildfly.extension.messaging.activemq.jms.PooledConnectionFactoryService.start(PooledConnectionFactoryService.java:325)
> ... 8 more
> 19:21:20,773 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "messaging-activemq"),
> ("server" => "srv-update-wwavjsiodinh"),
> ("pooled-connection-factory" => "pool1")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.messaging-activemq.srv-update-wwavjsiodinh.jms.pooled-connection-factory.pool1" => "WFLYMSGAMQ0028: Failed to create resource adapter
> Caused by: java.lang.NullPointerException"}}
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months