[JBoss JIRA] (WFLY-10736) Server in cluster hangs during start after previous kill
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFLY-10736?page=com.atlassian.jira.plugin... ]
Miroslav Novak commented on WFLY-10736:
---------------------------------------
[~pferraro] I've tried your build which was used in [1]: https://www.dropbox.com/s/z90ba1tj9xy90cl/jboss-eap.zip?dl=0 and cannot reproduce this issue again.
[1] https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messag...
> Server in cluster hangs during start after previous kill
> --------------------------------------------------------
>
> Key: WFLY-10736
> URL: https://issues.jboss.org/browse/WFLY-10736
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Miroslav Novak
> Assignee: Paul Ferraro
> Priority: Blocker
> Labels: blocker-WF14
> Fix For: 15.0.0.Alpha1
>
> Attachments: Lodh2TestCase.testRemoteJcaInboundOnly-traces.zip, Lodh2TestCase.testRemoteJcaInboundOnly.zip, Lodh2TestCase.testRemoteJcaInboundOnly2.zip, clusterKilTest.zip, logs-traces.zip, logs-traces2.zip, logs-traces3.zip, logs-traces4.zip, logs-with-workaround.zip, node-1-thread-dump-before-kill-shutdown-sequence.txt, server-with-mdb.log, standalone-full-ha-1.xml, standalone-full-ha-2.xml
>
>
> There is regression in JGroups or Infinispan in one of our tests for fault tolerance of JMS bridges. However work on JMS bridge appears to be unrelated. Issue was hit in WF weekly run.
> Test Scenario:
> * There are two servers. InQueue is deployed on Node 1,
> * OutQueue is deployed on Node 2. Both servers are started.
> * Large byte messages are sent to InQueue deployed on Node 1. Bridge between servers/queues transfers messages from node 1 to node 2.
> * Node 1 is killed and started again.
> * All messages are received from OutQueue deployed on Node 2.
> Result:
> Node 1 does not start after kill and hangs. There is following exception logged in node 2:
> {code}
> :26:17,894 INFO [org.infinispan.CLUSTER] (thread-12,ejb,node-2) ISPN100000: Node node-1 joined the cluster
> 09:26:18,520 INFO [org.infinispan.CLUSTER] (thread-12,ejb,node-2) ISPN000094: Received new cluster view for channel ejb: [node-2|7] (2) [node-2, node-1]
> 09:26:18,521 INFO [org.infinispan.CLUSTER] (thread-12,ejb,node-2) ISPN100001: Node node-1 left the cluster
> 09:26:18,521 INFO [org.infinispan.CLUSTER] (thread-12,ejb,node-2) ISPN000094: Received new cluster view for channel ejb: [node-2|7] (2) [node-2, node-1]
> 09:26:18,522 INFO [org.infinispan.CLUSTER] (thread-12,ejb,node-2) ISPN100001: Node node-1 left the cluster
> 09:26:18,522 INFO [org.infinispan.CLUSTER] (thread-12,ejb,node-2) ISPN000094: Received new cluster view for channel ejb: [node-2|7] (2) [node-2, node-1]
> 09:26:18,522 INFO [org.infinispan.CLUSTER] (thread-12,ejb,node-2) ISPN100001: Node node-1 left the cluster
> 09:26:18,522 INFO [org.infinispan.CLUSTER] (thread-12,ejb,node-2) ISPN000094: Received new cluster view for channel ejb: [node-2|7] (2) [node-2, node-1]
> 09:26:18,523 INFO [org.infinispan.CLUSTER] (thread-12,ejb,node-2) ISPN100001: Node node-1 left the cluster
> 09:26:18,868 INFO [org.infinispan.CLUSTER] (remote-thread--p5-t2) ISPN000310: Starting cluster-wide rebalance for cache default, topology CacheTopology{id=17, phase=READ_OLD_WRITE_ALL, rebalanceId=6, currentCH=ReplicatedConsistentHash{ns = 256, owners = (2)[node-2: 122, node-1: 134]}, pendingCH=ReplicatedConsistentHash{ns = 256, owners = (3)[node-2: 84, node-1: 90, node-1: 82]}, unionCH=null, actualMembers=[node-2, node-1, node-1], persistentUUIDs=[12443bfb-e88a-46f3-919e-9213bf38ce19, 2873237f-d881-463f-8a5a-940bf1d764e5, a05ea8af-a83b-42a9-b937-dc2da1cae6d1]}
> 09:26:18,869 INFO [org.infinispan.CLUSTER] (remote-thread--p5-t2) [Context=default][Scope=node-2]ISPN100002: Started rebalance with topology id 17
> 09:26:18,870 INFO [org.infinispan.CLUSTER] (transport-thread--p14-t5) [Context=default][Scope=node-2]ISPN100003: Node node-2 finished rebalance phase with topology id 17
> 09:26:18,981 INFO [org.infinispan.CLUSTER] (remote-thread--p5-t2) [Context=default][Scope=node-1]ISPN100003: Node node-1 finished rebalance phase with topology id 17
> 09:27:18,530 WARN [org.infinispan.topology.ClusterTopologyManagerImpl] (transport-thread--p15-t4) ISPN000197: Error updating cluster member list: org.infinispan.util.concurrent.TimeoutException: ISPN000476: Timed out waiting for responses for request 4 from node-1
> at org.infinispan.remoting.transport.impl.MultiTargetRequest.onTimeout(MultiTargetRequest.java:167)
> at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:87)
> at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:22)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_131]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [rt.jar:1.8.0_131]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [rt.jar:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_131]
> Suppressed: java.util.concurrent.ExecutionException: org.infinispan.util.concurrent.TimeoutException: ISPN000476: Timed out waiting for responses for request 4 from node-1
> at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) [rt.jar:1.8.0_131]
> at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1915) [rt.jar:1.8.0_131]
> at org.infinispan.util.concurrent.CompletableFutures.await(CompletableFutures.java:82)
> at org.infinispan.remoting.transport.Transport.invokeRemotely(Transport.java:71)
> at org.infinispan.topology.ClusterTopologyManagerImpl.confirmMembersAvailable(ClusterTopologyManagerImpl.java:540)
> at org.infinispan.topology.ClusterTopologyManagerImpl.updateCacheMembers(ClusterTopologyManagerImpl.java:523)
> at org.infinispan.topology.ClusterTopologyManagerImpl.handleClusterView(ClusterTopologyManagerImpl.java:334)
> at org.infinispan.topology.ClusterTopologyManagerImpl.access$500(ClusterTopologyManagerImpl.java:85)
> at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener.lambda$handleViewChange$0(ClusterTopologyManagerImpl.java:745)
> at org.infinispan.executors.LimitedExecutor.runTasks(LimitedExecutor.java:144)
> at org.infinispan.executors.LimitedExecutor.access$100(LimitedExecutor.java:33)
> at org.infinispan.executors.LimitedExecutor$Runner.run(LimitedExecutor.java:174)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_131]
> at org.wildfly.clustering.service.concurrent.ClassLoaderThreadFactory.lambda$newThread$0(ClassLoaderThreadFactory.java:47)
> ... 1 more
> Caused by: org.infinispan.util.concurrent.TimeoutException: ISPN000476: Timed out waiting for responses for request 4 from node-1
> at org.infinispan.remoting.transport.impl.MultiTargetRequest.onTimeout(MultiTargetRequest.java:167)
> at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:87)
> at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:22)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_131]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [rt.jar:1.8.0_131]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [rt.jar:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_131]
> ... 1 more
> [CIRCULAR REFERENCE:java.util.concurrent.ExecutionException: org.infinispan.util.concurrent.TimeoutException: ISPN000476: Timed out waiting for responses for request 4 from node-1]
> 09:27:18,530 WARN [org.infinispan.topology.ClusterTopologyManagerImpl] (transport-thread--p16-t4) ISPN000197: Error updating cluster member list: org.infinispan.util.concurrent.TimeoutException: ISPN000476: Timed out waiting for responses for request 4 from node-1
> at org.infinispan.remoting.transport.impl.MultiTargetRequest.onTimeout(MultiTargetRequest.java:167)
> at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:87)
> at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:22)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_131]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [rt.jar:1.8.0_131]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [rt.jar:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_131]
> Suppressed: java.util.concurrent.ExecutionException: org.infinispan.util.concurrent.TimeoutException: ISPN000476: Timed out waiting for responses for request 4 from node-1
> at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) [rt.jar:1.8.0_131]
> at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1915) [rt.jar:1.8.0_131]
> at org.infinispan.util.concurrent.CompletableFutures.await(CompletableFutures.java:82)
> at org.infinispan.remoting.transport.Transport.invokeRemotely(Transport.java:71)
> at org.infinispan.topology.ClusterTopologyManagerImpl.confirmMembersAvailable(ClusterTopologyManagerImpl.java:540)
> at org.infinispan.topology.ClusterTopologyManagerImpl.updateCacheMembers(ClusterTopologyManagerImpl.java:523)
> at org.infinispan.topology.ClusterTopologyManagerImpl.handleClusterView(ClusterTopologyManagerImpl.java:334)
> at org.infinispan.topology.ClusterTopologyManagerImpl.access$500(ClusterTopologyManagerImpl.java:85)
> at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener.lambda$handleViewChange$0(ClusterTopologyManagerImpl.java:745)
> at org.infinispan.executors.LimitedExecutor.runTasks(LimitedExecutor.java:144)
> at org.infinispan.executors.LimitedExecutor.access$100(LimitedExecutor.java:33)
> at org.infinispan.executors.LimitedExecutor$Runner.run(LimitedExecutor.java:174)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_131]
> at org.wildfly.clustering.service.concurrent.ClassLoaderThreadFactory.lambda$newThread$0(ClassLoaderThreadFactory.java:47)
> ... 1 more
> Caused by: org.infinispan.util.concurrent.TimeoutException: ISPN000476: Timed out waiting for responses for request 4 from node-1
> at org.infinispan.remoting.transport.impl.MultiTargetRequest.onTimeout(MultiTargetRequest.java:167)
> at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:87)
> at org.infinispan.remoting.transport.AbstractRequest.call(AbstractRequest.java:22)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_131]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [rt.jar:1.8.0_131]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [rt.jar:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_131]
> ... 1 more
> [CIRCULAR REFERENCE:java.util.concurrent.ExecutionException: org.infinispan.util.concurrent.TimeoutException: ISPN000476: Timed out waiting for responses for request 4 from node-1]
> {code}
> There is default JGroups udp stack configured which is used by Infinispan. Both of the servers (jgroups udp) are bound to 127.0.0.1. Node 2 has port offset 1000.
> Attaching thread dump from node 1 when it hangs during start.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11033) "'module' isn't an allowed attribute for the 'custom-load-metric'" - it should be
by Jan Kašík (JIRA)
[ https://issues.jboss.org/browse/WFLY-11033?page=com.atlassian.jira.plugin... ]
Jan Kašík updated WFLY-11033:
-----------------------------
Priority: Critical (was: Major)
> "'module' isn't an allowed attribute for the 'custom-load-metric'" - it should be
> ---------------------------------------------------------------------------------
>
> Key: WFLY-11033
> URL: https://issues.jboss.org/browse/WFLY-11033
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 14.0.0.Final
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
> Priority: Critical
>
> This message shows up if I try to define module attribute for 'custom-load-metric'. It doesn't make sense, since it says both, that 'module' attribute is and isn't allowed.
> {code}
> OPVDX001: Validation error in standalone-ha.xml --------------------------------
> |
> | 448: <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" listener="ajp">
> | 449: <dynamic-load-provider>
> | 450: <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" module="org.jboss.mod_cluster" weight="1" capacity="1000.0">
> | ^^^^ 'module' isn't an allowed attribute for the 'custom-load-metric'
> | element
> |
> | Attributes allowed here are: capacity, class, module, weight
> |
> | 451: <property name="parseexpression" value="^LOAD: ([0-9]*)$"/>
> | 452: <property name="loadfile" value="/home/virtual/mod_cluster_workspace/loadfileA"/>
> | 453: </custom-load-metric>
> |
> | 'module' is allowed on elements:
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > object-factory
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > external-context
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > minimum-set > permission
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > maximum-set > permission
> | - server > profile > {urn:jboss:domain:datasources:5.0}subsystem > datasources > drivers > driver
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source > class
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source-provider > class
> | - server > extensions > extension
> | - server > vault
> | - server > management > security-realms > security-realm > plug-ins > plug-in
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container > local-cache
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > remote-cache-container
> | - server > profile > {urn:jboss:domain:modcluster:4.0}subsystem > proxy > dynamic-load-provider > custom-load-metric
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > login-module-stack > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > auth-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authorization > policy-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > acl > acl-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > mapping > mapping-module
> | (and 26 more)
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[450,21]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11033) "'module' isn't an allowed attribute for the 'custom-load-metric'" - it should be
by Jan Kašík (JIRA)
[ https://issues.jboss.org/browse/WFLY-11033?page=com.atlassian.jira.plugin... ]
Jan Kašík updated WFLY-11033:
-----------------------------
Steps to Reproduce:
# Start Wildfly
# Add custom load metrics with 'module' defined
# Reload
was:
# Start Wildfly
# Add custom load metrics with 'module'defined
# Reload
> "'module' isn't an allowed attribute for the 'custom-load-metric'" - it should be
> ---------------------------------------------------------------------------------
>
> Key: WFLY-11033
> URL: https://issues.jboss.org/browse/WFLY-11033
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 14.0.0.Final
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
>
> This message shows up if I try to define module attribute for 'custom-load-metric'. It doesn't make sense, since it says both, that 'module' attribute is and isn't allowed.
> {code}
> OPVDX001: Validation error in standalone-ha.xml --------------------------------
> |
> | 448: <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" listener="ajp">
> | 449: <dynamic-load-provider>
> | 450: <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" module="org.jboss.mod_cluster" weight="1" capacity="1000.0">
> | ^^^^ 'module' isn't an allowed attribute for the 'custom-load-metric'
> | element
> |
> | Attributes allowed here are: capacity, class, module, weight
> |
> | 451: <property name="parseexpression" value="^LOAD: ([0-9]*)$"/>
> | 452: <property name="loadfile" value="/home/virtual/mod_cluster_workspace/loadfileA"/>
> | 453: </custom-load-metric>
> |
> | 'module' is allowed on elements:
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > object-factory
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > external-context
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > minimum-set > permission
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > maximum-set > permission
> | - server > profile > {urn:jboss:domain:datasources:5.0}subsystem > datasources > drivers > driver
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source > class
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source-provider > class
> | - server > extensions > extension
> | - server > vault
> | - server > management > security-realms > security-realm > plug-ins > plug-in
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container > local-cache
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > remote-cache-container
> | - server > profile > {urn:jboss:domain:modcluster:4.0}subsystem > proxy > dynamic-load-provider > custom-load-metric
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > login-module-stack > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > auth-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authorization > policy-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > acl > acl-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > mapping > mapping-module
> | (and 26 more)
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[450,21]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11033) "'module' isn't an allowed attribute for the 'custom-load-metric'" - it should be
by Jan Kašík (JIRA)
[ https://issues.jboss.org/browse/WFLY-11033?page=com.atlassian.jira.plugin... ]
Jan Kašík updated WFLY-11033:
-----------------------------
Description:
This message shows up if I try to define module attribute for 'custom-load-metric'. It doesn't make sense, since it says both, that 'module' attribute is and isn't allowed.
{code}
OPVDX001: Validation error in standalone-ha.xml --------------------------------
|
| 448: <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" listener="ajp">
| 449: <dynamic-load-provider>
| 450: <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" module="org.jboss.mod_cluster" weight="1" capacity="1000.0">
| ^^^^ 'module' isn't an allowed attribute for the 'custom-load-metric'
| element
|
| Attributes allowed here are: capacity, class, module, weight
|
| 451: <property name="parseexpression" value="^LOAD: ([0-9]*)$"/>
| 452: <property name="loadfile" value="/home/virtual/mod_cluster_workspace/loadfileA"/>
| 453: </custom-load-metric>
|
| 'module' is allowed on elements:
| - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > object-factory
| - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > external-context
| - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > minimum-set > permission
| - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > maximum-set > permission
| - server > profile > {urn:jboss:domain:datasources:5.0}subsystem > datasources > drivers > driver
| - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source > class
| - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source-provider > class
| - server > extensions > extension
| - server > vault
| - server > management > security-realms > security-realm > plug-ins > plug-in
| - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container
| - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container > local-cache
| - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > remote-cache-container
| - server > profile > {urn:jboss:domain:modcluster:4.0}subsystem > proxy > dynamic-load-provider > custom-load-metric
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication > login-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > login-module-stack > login-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > auth-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authorization > policy-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > acl > acl-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > mapping > mapping-module
| (and 26 more)
|
| The primary underlying error message was:
| > ParseError at [row,col]:[450,21]
{code}
was:
This message shows up if I try to define module attribute for 'custom-load-metric'. It doesn't make sense, since it says both, that 'module' attribute is and isn't allowed.
{code}
OPVDX001: Validation error in standalone-ha.xml --------------------------------
|
| 448: <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" listener="ajp">
| 449: <dynamic-load-provider>
| 450: <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" module="org.jboss.mod_cluster" weight="1" capacity="1000.0">
| ^^^^ 'module' isn't an allowed attribute for the 'custom-load-metric'
| element
|
| Attributes allowed here are: capacity, class, module, weight
|
| 451: <property name="parseexpression" value="^LOAD: ([0-9]*)$"/>
| 452: <property name="loadfile" value="/home/virtual/mod_cluster_workspace/loadfileA"/>
| 453: </custom-load-metric>
|
| 'module' is allowed on elements:
| - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > object-factory
| - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > external-context
| - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > minimum-set > permission
| - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > maximum-set > permission
| - server > profile > {urn:jboss:domain:datasources:5.0}subsystem > datasources > drivers > driver
| - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source > class
| - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source-provider > class
| - server > extensions > extension
| - server > vault
| - server > management > security-realms > security-realm > plug-ins > plug-in
| - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container
| - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container > local-cache
| - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > remote-cache-container
| - server > profile > {urn:jboss:domain:modcluster:4.0}subsystem > proxy > dynamic-load-provider > custom-load-metric
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication > login-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > login-module-stack > login-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > auth-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authorization > policy-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > acl > acl-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > mapping > mapping-module
| (and 26 more)
|
| The primary underlying error message was:
| > ParseError at [row,col]:[450,21]
{code]
> "'module' isn't an allowed attribute for the 'custom-load-metric'" - it should be
> ---------------------------------------------------------------------------------
>
> Key: WFLY-11033
> URL: https://issues.jboss.org/browse/WFLY-11033
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 14.0.0.Final
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
>
> This message shows up if I try to define module attribute for 'custom-load-metric'. It doesn't make sense, since it says both, that 'module' attribute is and isn't allowed.
> {code}
> OPVDX001: Validation error in standalone-ha.xml --------------------------------
> |
> | 448: <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" listener="ajp">
> | 449: <dynamic-load-provider>
> | 450: <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" module="org.jboss.mod_cluster" weight="1" capacity="1000.0">
> | ^^^^ 'module' isn't an allowed attribute for the 'custom-load-metric'
> | element
> |
> | Attributes allowed here are: capacity, class, module, weight
> |
> | 451: <property name="parseexpression" value="^LOAD: ([0-9]*)$"/>
> | 452: <property name="loadfile" value="/home/virtual/mod_cluster_workspace/loadfileA"/>
> | 453: </custom-load-metric>
> |
> | 'module' is allowed on elements:
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > object-factory
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > external-context
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > minimum-set > permission
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > maximum-set > permission
> | - server > profile > {urn:jboss:domain:datasources:5.0}subsystem > datasources > drivers > driver
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source > class
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source-provider > class
> | - server > extensions > extension
> | - server > vault
> | - server > management > security-realms > security-realm > plug-ins > plug-in
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container > local-cache
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > remote-cache-container
> | - server > profile > {urn:jboss:domain:modcluster:4.0}subsystem > proxy > dynamic-load-provider > custom-load-metric
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > login-module-stack > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > auth-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authorization > policy-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > acl > acl-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > mapping > mapping-module
> | (and 26 more)
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[450,21]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11033) "'module' isn't an allowed attribute for the 'custom-load-metric'" - it should be
by Jan Kašík (JIRA)
Jan Kašík created WFLY-11033:
--------------------------------
Summary: "'module' isn't an allowed attribute for the 'custom-load-metric'" - it should be
Key: WFLY-11033
URL: https://issues.jboss.org/browse/WFLY-11033
Project: WildFly
Issue Type: Bug
Components: mod_cluster
Affects Versions: 14.0.0.Final
Reporter: Jan Kašík
Assignee: Radoslav Husar
This message shows up if I try to define module attribute for 'custom-load-metric'. It doesn't make sense, since it says both, that 'module' attribute is and isn't allowed.
{code}
OPVDX001: Validation error in standalone-ha.xml --------------------------------
|
| 448: <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" listener="ajp">
| 449: <dynamic-load-provider>
| 450: <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" module="org.jboss.mod_cluster" weight="1" capacity="1000.0">
| ^^^^ 'module' isn't an allowed attribute for the 'custom-load-metric'
| element
|
| Attributes allowed here are: capacity, class, module, weight
|
| 451: <property name="parseexpression" value="^LOAD: ([0-9]*)$"/>
| 452: <property name="loadfile" value="/home/virtual/mod_cluster_workspace/loadfileA"/>
| 453: </custom-load-metric>
|
| 'module' is allowed on elements:
| - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > object-factory
| - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > external-context
| - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > minimum-set > permission
| - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > maximum-set > permission
| - server > profile > {urn:jboss:domain:datasources:5.0}subsystem > datasources > drivers > driver
| - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source > class
| - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source-provider > class
| - server > extensions > extension
| - server > vault
| - server > management > security-realms > security-realm > plug-ins > plug-in
| - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container
| - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container > local-cache
| - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > remote-cache-container
| - server > profile > {urn:jboss:domain:modcluster:4.0}subsystem > proxy > dynamic-load-provider > custom-load-metric
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication > login-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > login-module-stack > login-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > auth-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authorization > policy-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > acl > acl-module
| - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > mapping > mapping-module
| (and 26 more)
|
| The primary underlying error message was:
| > ParseError at [row,col]:[450,21]
{code]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2819) [DMN Designer] [IE11] Expression type change throws an Error
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2819?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-2819:
-------------------------------------
[~dadossan] no problem, however I am not going to build one more time it locally. I will wait until DROOLS-2818 is merged and then recheck.
> [DMN Designer] [IE11] Expression type change throws an Error
> ------------------------------------------------------------
>
> Key: DROOLS-2819
> URL: https://issues.jboss.org/browse/DROOLS-2819
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Environment: IE11
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Labels: drools-tools
>
> When user tries to change expression type the Unexpected error appears: *Uncaught exception: Exception caught: Exception caught: (TypeError) : Object doesn't support property or method 'startsWith' Caused by: Exception caught: (TypeError) : Object doesn't support property or method 'startsWith' Caused by: (TypeError) : Object doesn't support property or method 'startsWith'*
> h2. Manual Acceptance Test
> With DROOLS-2818 check steps to reproduce
> - IE (?)
> - Chrome (?)
> - Firefox (?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2819) [DMN Designer] [IE11] Expression type change throws an Error
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2819?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2819:
--------------------------------
Description:
When user tries to change expression type the Unexpected error appears: *Uncaught exception: Exception caught: Exception caught: (TypeError) : Object doesn't support property or method 'startsWith' Caused by: Exception caught: (TypeError) : Object doesn't support property or method 'startsWith' Caused by: (TypeError) : Object doesn't support property or method 'startsWith'*
h2. Manual Acceptance Test
With DROOLS-2818 check steps to reproduce
- IE (?)
- Chrome (?)
- Firefox (?)
was:
When user tries to change expression type the Unexpected error appears: *Uncaught exception: Exception caught: Exception caught: (TypeError) : Object doesn't support property or method 'startsWith' Caused by: Exception caught: (TypeError) : Object doesn't support property or method 'startsWith' Caused by: (TypeError) : Object doesn't support property or method 'startsWith'*
h2. Manual Acceptance Test
With DROOLS-2820 check steps to reproduce
- IE (x)
- Chrome (/)
- Firefox (/)
> [DMN Designer] [IE11] Expression type change throws an Error
> ------------------------------------------------------------
>
> Key: DROOLS-2819
> URL: https://issues.jboss.org/browse/DROOLS-2819
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Environment: IE11
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Labels: drools-tools
>
> When user tries to change expression type the Unexpected error appears: *Uncaught exception: Exception caught: Exception caught: (TypeError) : Object doesn't support property or method 'startsWith' Caused by: Exception caught: (TypeError) : Object doesn't support property or method 'startsWith' Caused by: (TypeError) : Object doesn't support property or method 'startsWith'*
> h2. Manual Acceptance Test
> With DROOLS-2818 check steps to reproduce
> - IE (?)
> - Chrome (?)
> - Firefox (?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2819) [DMN Designer] [IE11] Expression type change throws an Error
by Daniel José dos Santos (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2819?page=com.atlassian.jira.plugi... ]
Daniel José dos Santos commented on DROOLS-2819:
------------------------------------------------
[~jomarko], sorry, I did a mistake. Is [DROOLS-2818|https://issues.jboss.org/browse/DROOLS-2818] and not 2820. Sorry.
> [DMN Designer] [IE11] Expression type change throws an Error
> ------------------------------------------------------------
>
> Key: DROOLS-2819
> URL: https://issues.jboss.org/browse/DROOLS-2819
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Environment: IE11
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Labels: drools-tools
>
> When user tries to change expression type the Unexpected error appears: *Uncaught exception: Exception caught: Exception caught: (TypeError) : Object doesn't support property or method 'startsWith' Caused by: Exception caught: (TypeError) : Object doesn't support property or method 'startsWith' Caused by: (TypeError) : Object doesn't support property or method 'startsWith'*
> h2. Manual Acceptance Test
> With DROOLS-2820 check steps to reproduce
> - IE (x)
> - Chrome (/)
> - Firefox (/)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2993) Can't enable reason code in the guided scorecard
by Toni Rikkola (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2993?page=com.atlassian.jira.plugi... ]
Toni Rikkola commented on DROOLS-2993:
--------------------------------------
Hi,
Can you give some steps on how to reproduce with the example?
Starting from the moment where I have imported the project in.
> Can't enable reason code in the guided scorecard
> ------------------------------------------------
>
> Key: DROOLS-2993
> URL: https://issues.jboss.org/browse/DROOLS-2993
> Project: Drools
> Issue Type: Bug
> Components: Guided Score Card Editor
> Affects Versions: 7.11.0.Final
> Environment: All in one jbpm server
> Reporter: yi gong
> Assignee: Toni Rikkola
> Priority: Blocker
> Attachments: sandbox1.zip
>
>
> Can't enable the reason code in the guided scorecard editor even the data object has a filed which is string list.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months