[JBoss JIRA] (DROOLS-2399) [Guided Decision Table] ValidationWebWorkerServlet fails to load web worker
by Jozef Marko (JIRA)
Jozef Marko created DROOLS-2399:
-----------------------------------
Summary: [Guided Decision Table] ValidationWebWorkerServlet fails to load web worker
Key: DROOLS-2399
URL: https://issues.jboss.org/browse/DROOLS-2399
Project: Drools
Issue Type: Sub-task
Components: Guided Decision Table Editor
Affects Versions: 7.0.0.Beta4
Reporter: Jozef Marko
Assignee: Toni Rikkola
Priority: Minor
The guided decision tables are not validated. After user clicks on the _Validate_ button, the error [1] appears in the server log.
Steps to reproduce:
# Create new Guided Decision Table
# Add simple Condition column into the table
# Insert new empty row into the table
# Click Validate button
** Panel with validation results won't appear
** The error in server log appear
[1]
{code:log}
10:32:00,313 ERROR [org.drools.workbench.services.verifier.plugin.backend.VerifierWebWorkerServlet] (default task-43) Failed to load verifier web worker.
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10046) Cannot create cluster with JGroups Gossip router
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFLY-10046?page=com.atlassian.jira.plugin... ]
Miroslav Novak commented on WFLY-10046:
---------------------------------------
[~rhusar] This config worked in EAP 7.1. I've tried to use 127.0.0.1 instead of 0.0.0.0 in WF12 and it still does not work.
> Cannot create cluster with JGroups Gossip router
> ------------------------------------------------
>
> Key: WFLY-10046
> URL: https://issues.jboss.org/browse/WFLY-10046
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 12.0.0.Final
> Reporter: Miroslav Novak
> Assignee: Paul Ferraro
> Priority: Blocker
> Attachments: standalone-full-ha-gosship1.xml, standalone-full-ha-gosship2.xml
>
>
> I've used config from EAP 7.1.0/WF11 where gossip router was configured in udp stack like:
> {code}
> <stack name="udp">
> <transport type="UDP" shared="false" socket-binding="jgroups-udp"/>
> <protocol type="PING"/>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD_ALL"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG2"/>
> <protocol type="TUNNEL">
> <property name="gossip_router_hosts">
> 0.0.0.0[12001]
> </property>
> </protocol>
> </stack>
> {code}
> Gossip router was started on localhost:
> {{java -cp $JBOSS_HOME//bin/client/jboss-client.jar org.jgroups.stack.GossipRouter -port 12001 -bindaddress 0.0.0.0}}
> but cluster does not form up. The same configuration works in EAP 7.1.
> Attaching xml config files for both of the servers.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10047) OOM caused by jgroups objects UNICAST3$SenderEntry#1
by Erich Duda (JIRA)
[ https://issues.jboss.org/browse/WFLY-10047?page=com.atlassian.jira.plugin... ]
Erich Duda commented on WFLY-10047:
-----------------------------------
Here is the start up configuration which was logged by the test. The servers should be bound to {{127.0.0.1}}.
{code}
INFO: Manual starting of a server instance with overridden configuration. New configuration: {managementAddress=127.0.0.1, adminOnly=false, javaVmArguments=-Xms64m -Xmx788m -XX:MaxPermSize=256m
-Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000
-Dorg.jboss.byteman.transform.all
-Dsun.rmi.dgc.server.gcInterval=3600000
-javaagent:/home/hudson/hudson_workspace/workspace/early-testing-messaging-weekly-common-cluster/.repository/org/jboss/byteman/byteman/3.0.5/byteman-3.0.5.jar=prop:org.jboss.byteman.verbose=t
rue,address:127.0.0.1,port:9091
-Djboss.modules.system.pkgs=org.jboss.byteman -Xbootclasspath/a:/home/hudson/hudson_workspace/workspace/early-testing-messaging-weekly-common-cluster/.repository/org/jboss/byteman/byteman/3.0
.5/byteman-3.0.5.jar:/home/hudson/hudson_workspace/workspace/early-testing-messaging-weekly-common-cluster/.repository/org/jboss/byteman/byteman-submit/3.0.5/byteman-submit-3.0.5.jar
-Djboss.bind.address=127.0.0.1
-Djboss.bind.address.management=127.0.0.1
-Djboss.bind.address.unsecure=127.0.0.1
-Djboss.bind.address.private=127.0.0.1
-XX:+HeapDumpOnOutOfMemoryError
-Djava.net.preferIPv4Stack=true
-Djboss.modules.policy-permissions=true
-Djboss.node.name=node-1
-Dxnio.nio.selector.main=sun.nio.ch.DevPollSelectorImpl
-Djboss.socket.binding.port-offset=0 -Djboss.messaging.group.address=237.47.146.238 -Djboss.default.multicast.address=237.47.146.238, password=minono532/20, startupTimeoutInSeconds=300, managementPort=9990, jbossHome=/home/hudson/hudson_workspace/workspace/early-testing-messaging-weekly-common-cluster/server1/jboss-eap, serverConfig=standalone-full-ha.xml, username=admin}
{code}
> OOM caused by jgroups objects UNICAST3$SenderEntry#1
> ----------------------------------------------------
>
> Key: WFLY-10047
> URL: https://issues.jboss.org/browse/WFLY-10047
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 13.0.0.Beta1
> Reporter: Erich Duda
> Assignee: Paul Ferraro
> Priority: Blocker
> Attachments: heapdump.png
>
>
> JGroups objects UNICAST3$SenderEntry#1 caused OOM on Wildfly server during the boot. See attached picture. !heapdump.png|thumbnail!
> *User impact:* If users use JGroups for clustering, the server may get OOM what can cause undefined behavior.
> The *blocker* priority was set, because this is regression against previous versions of Wildfly and the OOM is serious error which prevents server to work properly.
> The issue was hit in following scenario.
> # start two servers (nodes) in cluster with one queue
> # producer starts to send messages to queue to node-1
> # node-2 is killed and restarted during sending messages <---- *Here the test failed, when the node-2 was started after that it had been killed.*
> # start consumer on node-2 which reads messages from queue
> # servers are stopped
> The Wildfly was built from following source code:
> repo: https://github.com/jmesnil/wildfly
> branch: WFLY-9407_upgrade_artemis_2.5.0
> commit SHA: 06c878a313d3cad323889d017e60fd5533204d1a
> JGroups version: 4.0.10.Final
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10047) OOM caused by jgroups objects UNICAST3$SenderEntry#1
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-10047?page=com.atlassian.jira.plugin... ]
Paul Ferraro commented on WFLY-10047:
-------------------------------------
If I had to guess, this looks like someone configured "0.0.0.0" as the bind address on each node, hence there is is no physical address to which to send messages.
> OOM caused by jgroups objects UNICAST3$SenderEntry#1
> ----------------------------------------------------
>
> Key: WFLY-10047
> URL: https://issues.jboss.org/browse/WFLY-10047
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 13.0.0.Beta1
> Reporter: Erich Duda
> Assignee: Paul Ferraro
> Priority: Blocker
> Attachments: heapdump.png
>
>
> JGroups objects UNICAST3$SenderEntry#1 caused OOM on Wildfly server during the boot. See attached picture. !heapdump.png|thumbnail!
> *User impact:* If users use JGroups for clustering, the server may get OOM what can cause undefined behavior.
> The *blocker* priority was set, because this is regression against previous versions of Wildfly and the OOM is serious error which prevents server to work properly.
> The issue was hit in following scenario.
> # start two servers (nodes) in cluster with one queue
> # producer starts to send messages to queue to node-1
> # node-2 is killed and restarted during sending messages <---- *Here the test failed, when the node-2 was started after that it had been killed.*
> # start consumer on node-2 which reads messages from queue
> # servers are stopped
> The Wildfly was built from following source code:
> repo: https://github.com/jmesnil/wildfly
> branch: WFLY-9407_upgrade_artemis_2.5.0
> commit SHA: 06c878a313d3cad323889d017e60fd5533204d1a
> JGroups version: 4.0.10.Final
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10031) Scripts throws "illegal reflective access" warning on JDK9
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-10031?page=com.atlassian.jira.plugin... ]
Tomaz Cerar commented on WFLY-10031:
------------------------------------
In that case, please add --illegal-access=permit to the scripts in QE.
This way it should not print warning to stderr
> Scripts throws "illegal reflective access" warning on JDK9
> ----------------------------------------------------------
>
> Key: WFLY-10031
> URL: https://issues.jboss.org/browse/WFLY-10031
> Project: WildFly
> Issue Type: Bug
> Components: Scripts, Security
> Reporter: Marek Kopecký
> Assignee: James Perkins
> Priority: Blocker
>
> *Description of the issue:*
> Scripts throws "illegal reflective access" warning on JDK9/10/11.
> *How reproducible:*
> Always with JDK9, 10 and 11
> *Steps to Reproduce:*
> * ./jboss-cli.sh "echo test"
> * ./add-user.sh -u test4 -p Test123* -s
> * ./appclient.sh -v
> * ./wsconsume.sh
> * ./wsprovide.sh
> * ./domain.sh
> * ./standalone.sh
> *Actual results:*
> {noformat}
> [hudson@rhel7-large-9887 bin]$ java --version
> java 9.0.4
> Java(TM) SE Runtime Environment (build 9.0.4+11)
> Java HotSpot(TM) 64-Bit Server VM (build 9.0.4+11, mixed mode)
> [hudson@rhel7-large-9887 bin]$
> {noformat}
> {noformat}
> [hudson@rhel7-large-9887 bin]$ ./jboss-cli.sh "echo test"
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
> WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> test
> [hudson@rhel7-large-9887 bin]$
> {noformat}
> {noformat}
> [hudson@rhel7-large-9887 bin]$ ./add-user.sh -u test4 -p Test123* -s
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
> WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [hudson@rhel7-large-9887 bin]$ cat ../standalone/configuration/mgmt-users.properties | tail -n 1
> test4=a95aa9d159b7afe0cc9d3795061551ad
> [hudson@rhel7-large-9887 bin]$
> {noformat}
> {noformat}
> [hudson@rhel7-large-9887 bin]$ ./appclient.sh -v
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
> WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> 06:11:52,205 INFO [org.jboss.modules] (main) JBoss Modules version 1.7.0.Final
> WildFly Full 13.0.0.Alpha1-SNAPSHOT (WildFly Core 4.0.0.Final)
> [hudson@rhel7-large-9887 bin]$
> {noformat}
> *Expected results:*
> No warnings
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10044) enable_bundling property causes boot to fail
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-10044?page=com.atlassian.jira.plugin... ]
Paul Ferraro closed WFLY-10044.
-------------------------------
Resolution: Done
The "enable_bundling" protocol property has been deprecated since AS 7.2 (JGroups 3.2.7.FInal).
[1] https://github.com/belaban/JGroups/commit/89440e0e179b83186b6d0c04e7b944b...
> enable_bundling property causes boot to fail
> --------------------------------------------
>
> Key: WFLY-10044
> URL: https://issues.jboss.org/browse/WFLY-10044
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 12.0.0.Final
> Reporter: Miroslav Novak
> Assignee: Paul Ferraro
> Priority: Critical
>
> When configuring JGroups udp stack then it no longer takes property {{enable_bundling}}:
> {code}
> <stack name="udp">
> <transport type="UDP" shared="false" socket-binding="jgroups-udp">
> <property name="enable_bundling">
> false
> </property>
> </transport>
> <protocol type="PING"/>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD_ALL"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG3"/>
> <protocol type="TUNNEL">
> <property name="gossip_router_hosts">
> 0.0.0.0[12001]
> </property>
> </protocol>
> </stack>
> {code}
> If it's used then server does not boot and logs error:
> {code}
> 10:15:24,324 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 74) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.activemq-cluster: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.activemq-cluster: java.lang.IllegalArgumentException: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized UDP properties: [enable_bundling]
> at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:103)
> at org.wildfly.clustering.service.AsynchronousServiceBuilder.lambda$start$0(AsynchronousServiceBuilder.java:99) [wildfly-clustering-service-12.0.0.Final.jar:12.0.0.Final]
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) [jboss-threads-2.3.1.Final.jar:2.3.1.Final]
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) [jboss-threads-2.3.1.Final.jar:2.3.1.Final]
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) [jboss-threads-2.3.1.Final.jar:2.3.1.Final]
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) [jboss-threads-2.3.1.Final.jar:2.3.1.Final]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_131]
> at org.jboss.threads.JBossThread.run(JBossThread.java:485) [jboss-threads-2.3.1.Final.jar:2.3.1.Final]
> Caused by: java.lang.IllegalArgumentException: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized UDP properties: [enable_bundling]
> at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationBuilder.createProtocol(AbstractProtocolConfigurationBuilder.java:119)
> at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:102)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:101)
> ... 7 more
> Caused by: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized UDP properties: [enable_bundling]
> at org.wildfly.security.manager.WildFlySecurityManager.doUnchecked(WildFlySecurityManager.java:852) [wildfly-elytron-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationBuilder.createProtocol(AbstractProtocolConfigurationBuilder.java:114)
> ... 9 more
> Caused by: java.lang.IllegalArgumentException: Unrecognized UDP properties: [enable_bundling]
> at org.jgroups.stack.Protocol.setProperties(Protocol.java:144)
> at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationBuilder.lambda$createProtocol$0(AbstractProtocolConfigurationBuilder.java:108)
> at org.wildfly.security.manager.WildFlySecurityManager.doUnchecked(WildFlySecurityManager.java:850) [wildfly-elytron-1.2.2.Final.jar:1.2.2.Final]
> ... 10 more
> {code}
> This is change and backward compatibility issue against EAP 7.1/WF11.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10044) enable_bundling property causes boot to fail
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-10044?page=com.atlassian.jira.plugin... ]
Paul Ferraro updated WFLY-10044:
--------------------------------
Comment: was deleted
(was: To better handle legacy configuration, we can log a WARNing instead of throwing an IAE in the case that a specified protocol property is invalid.)
> enable_bundling property causes boot to fail
> --------------------------------------------
>
> Key: WFLY-10044
> URL: https://issues.jboss.org/browse/WFLY-10044
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 12.0.0.Final
> Reporter: Miroslav Novak
> Assignee: Paul Ferraro
> Priority: Critical
>
> When configuring JGroups udp stack then it no longer takes property {{enable_bundling}}:
> {code}
> <stack name="udp">
> <transport type="UDP" shared="false" socket-binding="jgroups-udp">
> <property name="enable_bundling">
> false
> </property>
> </transport>
> <protocol type="PING"/>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD_ALL"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG3"/>
> <protocol type="TUNNEL">
> <property name="gossip_router_hosts">
> 0.0.0.0[12001]
> </property>
> </protocol>
> </stack>
> {code}
> If it's used then server does not boot and logs error:
> {code}
> 10:15:24,324 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 74) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.activemq-cluster: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.activemq-cluster: java.lang.IllegalArgumentException: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized UDP properties: [enable_bundling]
> at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:103)
> at org.wildfly.clustering.service.AsynchronousServiceBuilder.lambda$start$0(AsynchronousServiceBuilder.java:99) [wildfly-clustering-service-12.0.0.Final.jar:12.0.0.Final]
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) [jboss-threads-2.3.1.Final.jar:2.3.1.Final]
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) [jboss-threads-2.3.1.Final.jar:2.3.1.Final]
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) [jboss-threads-2.3.1.Final.jar:2.3.1.Final]
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) [jboss-threads-2.3.1.Final.jar:2.3.1.Final]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_131]
> at org.jboss.threads.JBossThread.run(JBossThread.java:485) [jboss-threads-2.3.1.Final.jar:2.3.1.Final]
> Caused by: java.lang.IllegalArgumentException: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized UDP properties: [enable_bundling]
> at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationBuilder.createProtocol(AbstractProtocolConfigurationBuilder.java:119)
> at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:102)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:101)
> ... 7 more
> Caused by: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized UDP properties: [enable_bundling]
> at org.wildfly.security.manager.WildFlySecurityManager.doUnchecked(WildFlySecurityManager.java:852) [wildfly-elytron-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationBuilder.createProtocol(AbstractProtocolConfigurationBuilder.java:114)
> ... 9 more
> Caused by: java.lang.IllegalArgumentException: Unrecognized UDP properties: [enable_bundling]
> at org.jgroups.stack.Protocol.setProperties(Protocol.java:144)
> at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationBuilder.lambda$createProtocol$0(AbstractProtocolConfigurationBuilder.java:108)
> at org.wildfly.security.manager.WildFlySecurityManager.doUnchecked(WildFlySecurityManager.java:850) [wildfly-elytron-1.2.2.Final.jar:1.2.2.Final]
> ... 10 more
> {code}
> This is change and backward compatibility issue against EAP 7.1/WF11.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10047) OOM caused by jgroups objects UNICAST3$SenderEntry#1
by Erich Duda (JIRA)
[ https://issues.jboss.org/browse/WFLY-10047?page=com.atlassian.jira.plugin... ]
Erich Duda edited comment on WFLY-10047 at 3/19/18 8:51 AM:
------------------------------------------------------------
In the log I can see several messages \[1\], before the OOM happend. I suspected that they are expected since the node-2 was killed.
Both servers are running on single node and communicate over localhost. Do you know what could cause that these warnings were logged?
\[1\]
{code}
13:31:33,794 WARN [org.jgroups.protocols.UDP] (TQ-Bundler-4,ejb,node-2) JGRP000032: node-2: no physical address for bb5fc2e1-deb1-30b6-0f2d-90a2b5239c6c, dropping message
13:31:35,804 WARN [org.jgroups.protocols.UDP] (TQ-Bundler-4,ejb,node-2) JGRP000032: node-2: no physical address for bb5fc2e1-deb1-30b6-0f2d-90a2b5239c6c, dropping message
13:31:37,804 WARN [org.jgroups.protocols.UDP] (TQ-Bundler-4,ejb,node-2) JGRP000032: node-2: no physical address for bb5fc2e1-deb1-30b6-0f2d-90a2b5239c6c, dropping message
13:31:39,804 WARN [org.jgroups.protocols.UDP] (TQ-Bundler-4,ejb,node-2) JGRP000032: node-2: no physical address for bb5fc2e1-deb1-30b6-0f2d-90a2b5239c6c, dropping message
13:31:41,804 WARN [org.jgroups.protocols.UDP] (TQ-Bundler-4,ejb,node-2) JGRP000032: node-2: no physical address for bb5fc2e1-deb1-30b6-0f2d-90a2b5239c6c, dropping message
13:31:43,804 WARN [org.jgroups.protocols.UDP] (TQ-Bundler-4,ejb,node-2) JGRP000032: node-2: no physical address for bb5fc2e1-deb1-30b6-0f2d-90a2b5239c6c, dropping message
{code}
bq. The analysis is very likely incorrect – the SenderEntry are entries kept for retransmit – none of this is indicative of a leak (note that this size can be adjusted with xmit_table_msgs_per_row and xmit_table_num_rows).
If the OOM was caused by "cache" for retransmits, shouldn't be the default size of the cache lowered to not to cause OOM?
was (Author: eduda):
In the log I can see several messages \[1\], before the OOM happend. I suspected that they are expected since the node-2 was killed.
Both servers are running on single node and communicate over localhost. Do you know what could cause that these warning were logged?
\[1\]
{code}
13:31:33,794 WARN [org.jgroups.protocols.UDP] (TQ-Bundler-4,ejb,node-2) JGRP000032: node-2: no physical address for bb5fc2e1-deb1-30b6-0f2d-90a2b5239c6c, dropping message
13:31:35,804 WARN [org.jgroups.protocols.UDP] (TQ-Bundler-4,ejb,node-2) JGRP000032: node-2: no physical address for bb5fc2e1-deb1-30b6-0f2d-90a2b5239c6c, dropping message
13:31:37,804 WARN [org.jgroups.protocols.UDP] (TQ-Bundler-4,ejb,node-2) JGRP000032: node-2: no physical address for bb5fc2e1-deb1-30b6-0f2d-90a2b5239c6c, dropping message
13:31:39,804 WARN [org.jgroups.protocols.UDP] (TQ-Bundler-4,ejb,node-2) JGRP000032: node-2: no physical address for bb5fc2e1-deb1-30b6-0f2d-90a2b5239c6c, dropping message
13:31:41,804 WARN [org.jgroups.protocols.UDP] (TQ-Bundler-4,ejb,node-2) JGRP000032: node-2: no physical address for bb5fc2e1-deb1-30b6-0f2d-90a2b5239c6c, dropping message
13:31:43,804 WARN [org.jgroups.protocols.UDP] (TQ-Bundler-4,ejb,node-2) JGRP000032: node-2: no physical address for bb5fc2e1-deb1-30b6-0f2d-90a2b5239c6c, dropping message
{code}
> OOM caused by jgroups objects UNICAST3$SenderEntry#1
> ----------------------------------------------------
>
> Key: WFLY-10047
> URL: https://issues.jboss.org/browse/WFLY-10047
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 13.0.0.Beta1
> Reporter: Erich Duda
> Assignee: Paul Ferraro
> Priority: Blocker
> Attachments: heapdump.png
>
>
> JGroups objects UNICAST3$SenderEntry#1 caused OOM on Wildfly server during the boot. See attached picture. !heapdump.png|thumbnail!
> *User impact:* If users use JGroups for clustering, the server may get OOM what can cause undefined behavior.
> The *blocker* priority was set, because this is regression against previous versions of Wildfly and the OOM is serious error which prevents server to work properly.
> The issue was hit in following scenario.
> # start two servers (nodes) in cluster with one queue
> # producer starts to send messages to queue to node-1
> # node-2 is killed and restarted during sending messages <---- *Here the test failed, when the node-2 was started after that it had been killed.*
> # start consumer on node-2 which reads messages from queue
> # servers are stopped
> The Wildfly was built from following source code:
> repo: https://github.com/jmesnil/wildfly
> branch: WFLY-9407_upgrade_artemis_2.5.0
> commit SHA: 06c878a313d3cad323889d017e60fd5533204d1a
> JGroups version: 4.0.10.Final
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10044) enable_bundling property causes boot to fail
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-10044?page=com.atlassian.jira.plugin... ]
Paul Ferraro commented on WFLY-10044:
-------------------------------------
To better handle legacy configuration, we can log a WARNing instead of throwing an IAE in the case that a specified protocol property is invalid.
> enable_bundling property causes boot to fail
> --------------------------------------------
>
> Key: WFLY-10044
> URL: https://issues.jboss.org/browse/WFLY-10044
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 12.0.0.Final
> Reporter: Miroslav Novak
> Assignee: Paul Ferraro
> Priority: Critical
>
> When configuring JGroups udp stack then it no longer takes property {{enable_bundling}}:
> {code}
> <stack name="udp">
> <transport type="UDP" shared="false" socket-binding="jgroups-udp">
> <property name="enable_bundling">
> false
> </property>
> </transport>
> <protocol type="PING"/>
> <protocol type="MERGE3"/>
> <protocol type="FD_SOCK"/>
> <protocol type="FD_ALL"/>
> <protocol type="VERIFY_SUSPECT"/>
> <protocol type="pbcast.NAKACK2"/>
> <protocol type="UNICAST3"/>
> <protocol type="pbcast.STABLE"/>
> <protocol type="pbcast.GMS"/>
> <protocol type="UFC"/>
> <protocol type="MFC"/>
> <protocol type="FRAG3"/>
> <protocol type="TUNNEL">
> <property name="gossip_router_hosts">
> 0.0.0.0[12001]
> </property>
> </protocol>
> </stack>
> {code}
> If it's used then server does not boot and logs error:
> {code}
> 10:15:24,324 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 74) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.activemq-cluster: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.activemq-cluster: java.lang.IllegalArgumentException: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized UDP properties: [enable_bundling]
> at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:103)
> at org.wildfly.clustering.service.AsynchronousServiceBuilder.lambda$start$0(AsynchronousServiceBuilder.java:99) [wildfly-clustering-service-12.0.0.Final.jar:12.0.0.Final]
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) [jboss-threads-2.3.1.Final.jar:2.3.1.Final]
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) [jboss-threads-2.3.1.Final.jar:2.3.1.Final]
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) [jboss-threads-2.3.1.Final.jar:2.3.1.Final]
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) [jboss-threads-2.3.1.Final.jar:2.3.1.Final]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_131]
> at org.jboss.threads.JBossThread.run(JBossThread.java:485) [jboss-threads-2.3.1.Final.jar:2.3.1.Final]
> Caused by: java.lang.IllegalArgumentException: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized UDP properties: [enable_bundling]
> at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationBuilder.createProtocol(AbstractProtocolConfigurationBuilder.java:119)
> at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:102)
> at org.jboss.as.clustering.jgroups.subsystem.ChannelBuilder.start(ChannelBuilder.java:101)
> ... 7 more
> Caused by: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized UDP properties: [enable_bundling]
> at org.wildfly.security.manager.WildFlySecurityManager.doUnchecked(WildFlySecurityManager.java:852) [wildfly-elytron-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationBuilder.createProtocol(AbstractProtocolConfigurationBuilder.java:114)
> ... 9 more
> Caused by: java.lang.IllegalArgumentException: Unrecognized UDP properties: [enable_bundling]
> at org.jgroups.stack.Protocol.setProperties(Protocol.java:144)
> at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationBuilder.lambda$createProtocol$0(AbstractProtocolConfigurationBuilder.java:108)
> at org.wildfly.security.manager.WildFlySecurityManager.doUnchecked(WildFlySecurityManager.java:850) [wildfly-elytron-1.2.2.Final.jar:1.2.2.Final]
> ... 10 more
> {code}
> This is change and backward compatibility issue against EAP 7.1/WF11.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10047) OOM caused by jgroups objects UNICAST3$SenderEntry#1
by Erich Duda (JIRA)
[ https://issues.jboss.org/browse/WFLY-10047?page=com.atlassian.jira.plugin... ]
Erich Duda commented on WFLY-10047:
-----------------------------------
In the log I can see several messages \[1\], before the OOM happend. I suspected that they are expected since the node-2 was killed.
Both servers are running on single node and communicate over localhost. Do you know what could cause that these warning were logged?
\[1\]
{code}
13:31:33,794 WARN [org.jgroups.protocols.UDP] (TQ-Bundler-4,ejb,node-2) JGRP000032: node-2: no physical address for bb5fc2e1-deb1-30b6-0f2d-90a2b5239c6c, dropping message
13:31:35,804 WARN [org.jgroups.protocols.UDP] (TQ-Bundler-4,ejb,node-2) JGRP000032: node-2: no physical address for bb5fc2e1-deb1-30b6-0f2d-90a2b5239c6c, dropping message
13:31:37,804 WARN [org.jgroups.protocols.UDP] (TQ-Bundler-4,ejb,node-2) JGRP000032: node-2: no physical address for bb5fc2e1-deb1-30b6-0f2d-90a2b5239c6c, dropping message
13:31:39,804 WARN [org.jgroups.protocols.UDP] (TQ-Bundler-4,ejb,node-2) JGRP000032: node-2: no physical address for bb5fc2e1-deb1-30b6-0f2d-90a2b5239c6c, dropping message
13:31:41,804 WARN [org.jgroups.protocols.UDP] (TQ-Bundler-4,ejb,node-2) JGRP000032: node-2: no physical address for bb5fc2e1-deb1-30b6-0f2d-90a2b5239c6c, dropping message
13:31:43,804 WARN [org.jgroups.protocols.UDP] (TQ-Bundler-4,ejb,node-2) JGRP000032: node-2: no physical address for bb5fc2e1-deb1-30b6-0f2d-90a2b5239c6c, dropping message
{code}
> OOM caused by jgroups objects UNICAST3$SenderEntry#1
> ----------------------------------------------------
>
> Key: WFLY-10047
> URL: https://issues.jboss.org/browse/WFLY-10047
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 13.0.0.Beta1
> Reporter: Erich Duda
> Assignee: Paul Ferraro
> Priority: Blocker
> Attachments: heapdump.png
>
>
> JGroups objects UNICAST3$SenderEntry#1 caused OOM on Wildfly server during the boot. See attached picture. !heapdump.png|thumbnail!
> *User impact:* If users use JGroups for clustering, the server may get OOM what can cause undefined behavior.
> The *blocker* priority was set, because this is regression against previous versions of Wildfly and the OOM is serious error which prevents server to work properly.
> The issue was hit in following scenario.
> # start two servers (nodes) in cluster with one queue
> # producer starts to send messages to queue to node-1
> # node-2 is killed and restarted during sending messages <---- *Here the test failed, when the node-2 was started after that it had been killed.*
> # start consumer on node-2 which reads messages from queue
> # servers are stopped
> The Wildfly was built from following source code:
> repo: https://github.com/jmesnil/wildfly
> branch: WFLY-9407_upgrade_artemis_2.5.0
> commit SHA: 06c878a313d3cad323889d017e60fd5533204d1a
> JGroups version: 4.0.10.Final
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month