[JBoss JIRA] (WFLY-258) Redesign mod_cluster subsystem
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-258?page=com.atlassian.jira.plugin.s... ]
Radoslav Husar updated WFLY-258:
--------------------------------
Affects Version/s: JBoss AS7 7.1.1.Final
> Redesign mod_cluster subsystem
> ------------------------------
>
> Key: WFLY-258
> URL: https://issues.jboss.org/browse/WFLY-258
> Project: WildFly
> Issue Type: Feature Request
> Components: mod_cluster
> Affects Versions: JBoss AS7 7.1.1.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> Changes to the schema
> * simplified names and sync in line with scheme recommendations
> * remove redundant <mod-cluster-config .. /> for good, everything should be element of the subsystem
> * fix load factor enum: no pool metric supported
> * make load-balancers configurable via socket-outbuound-group mechanism
> * add missing load-balancer properties to <proxies/>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-258) Redesign mod_cluster subsystem
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-258?page=com.atlassian.jira.plugin.s... ]
Radoslav Husar updated WFLY-258:
--------------------------------
Summary: Redesign mod_cluster subsystem (was: mod_cluster schema 2.0)
> Redesign mod_cluster subsystem
> ------------------------------
>
> Key: WFLY-258
> URL: https://issues.jboss.org/browse/WFLY-258
> Project: WildFly
> Issue Type: Feature Request
> Components: mod_cluster
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> Changes to the schema
> * simplified names and sync in line with scheme recommendations
> * remove redundant <mod-cluster-config .. /> for good, everything should be element of the subsystem
> * fix load factor enum: no pool metric supported
> * make load-balancers configurable via socket-outbuound-group mechanism
> * add missing load-balancer properties to <proxies/>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-5239) XSiteSimpleTestCase.testPutRelayedToBackups intermittently fails in ~5% cases with "no physical address for"
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5239?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-5239:
--------------------------------------
You can easily set node0/1 to one address and node2/3 to the other one..
> XSiteSimpleTestCase.testPutRelayedToBackups intermittently fails in ~5% cases with "no physical address for"
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-5239
> URL: https://issues.jboss.org/browse/WFLY-5239
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, Test Suite
> Affects Versions: 10.0.0.Beta2
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 11.0.0.Alpha1
>
>
> I have done some work to stabilize this test a little more by switching both stacks (default stack and the bridge stack) to tcp. This does not help the test completely, it still fails with the well known:
> {noformat}
> rhusar &#27;[0m&#27;[0m15:14:52,808 INFO [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "xsite.war" (runtime-name : "xsite.war")
> &#27;[0mExecuting HTTP request: http://[::1]:8080/xsite/cache?operation=put&key=a&value=100
> &#27;[33m15:14:53,513 WARNING [org.jgroups.protocols.TCP] (TransferQueueBundler,ee,LON-1) JGRP000032: LON-1: no physical address for a9d43ee2-698a-fbab-2ed8-fb54009f7af4, dropping message
> &#27;[0m&#27;[33m15:14:55,581 WARNING [org.jgroups.protocols.TCP] (TransferQueueBundler,ee,LON-1) JGRP000032: LON-1: no physical address for a9d43ee2-698a-fbab-2ed8-fb54009f7af4, dropping message
> &#27;[0m&#27;[33m15:14:57,583 WARNING [org.jgroups.protocols.TCP] (TransferQueueBundler,ee,LON-1) JGRP000032: LON-1: no physical address for a9d43ee2-698a-fbab-2ed8-fb54009f7af4, dropping message
> &#27;[0m&#27;[33m15:14:59,584 WARNING [org.jgroups.protocols.TCP] (TransferQueueBundler,ee,LON-1) JGRP000032: LON-1: no physical address for a9d43ee2-698a-fbab-2ed8-fb54009f7af4, dropping message
> &#27;[0m&#27;[33m15:15:01,585 WARNING [org.jgroups.protocols.TCP] (TransferQueueBundler,ee,LON-1) JGRP000032: LON-1: no physical address for a9d43ee2-698a-fbab-2ed8-fb54009f7af4, dropping message
> &#27;[0m&#27;[33m15:15:03,277 WARN [org.infinispan.xsite.BackupSenderImpl] (default task-1) ISPN000202: Problems backing up data for cache dist to site NYC: org.infinispan.util.concurrent.TimeoutException: Timed out after 10 seconds waiting for a response from NYC (sync, timeout=10000)
> &#27;[0mExecuted HTTP request
> &#27;[33m15:15:03,586 WARNING [org.jgroups.protocols.TCP] (TransferQueueBundler,ee,LON-1) JGRP000032: LON-1: no physical address for a9d43ee2-698a-fbab-2ed8-fb54009f7af4, dropping message
> &#27;[0m&#27;[33m15:15:05,591 WARNING [org.jgroups.protocols.TCP] (TransferQueueBundler,ee,LON-1) JGRP000032: LON-1: no physical address for a9d43ee2-698a-fbab-2ed8-fb54009f7af4, dropping message 17:02
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JGRP-2108) TCP_NIO2: make default
by Bela Ban (JIRA)
Bela Ban created JGRP-2108:
------------------------------
Summary: TCP_NIO2: make default
Key: JGRP-2108
URL: https://issues.jboss.org/browse/JGRP-2108
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 4.1
This requires the following things:
* performance of {{TCP_NIO2}} must be better than {{TCP}}
* (possibly) use multiple selectors: each selector handles only a max number of connections; create more selectors when the number of connections per selector exceeds a certain value
* (possibly) get rid of the reader thread and let the above selector do the read (the write is already done by the selector thread)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFCORE-848) "XNIO001001: No XNIO provider found" by some tests running with security manager
by Ingo Weiss (JIRA)
[ https://issues.jboss.org/browse/WFCORE-848?page=com.atlassian.jira.plugin... ]
Ingo Weiss commented on WFCORE-848:
-----------------------------------
Hi [~jcacek], I talked about this with Brian and it seems there might be a need to get {{subsystem=security-manager}} into wildfly-core. WDYT?
> "XNIO001001: No XNIO provider found" by some tests running with security manager
> --------------------------------------------------------------------------------
>
> Key: WFCORE-848
> URL: https://issues.jboss.org/browse/WFCORE-848
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 2.0.0.Alpha11
> Reporter: Petr Kremensky
> Assignee: Ingo Weiss
>
> Some tests in wildfly-core fails due to "XNIO001001: No XNIO provider found" while run with security manager enabled.
> {noformat}
> mvn test -Dtest=SuspendResumeTestCase -Dsecurity.manager -DtestLogToFile=false
> 10:27:16,814 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.test-undertow-server: org.jboss.msc.service.StartException in service jboss.test-undertow-server: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalArgumentException: XNIO001001: No XNIO provider found
> at org.xnio.Xnio.doGetInstance(Xnio.java:238)
> at org.xnio.Xnio.getInstance(Xnio.java:181)
> at io.undertow.Undertow.start(Undertow.java:97)
> at org.wildfly.test.suspendresumeendpoint.TestUndertowService.start(TestUndertowService.java:94)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> ... 3 more
> 10:27:16,816 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "web-suspend.jar")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.test-undertow-server" => "org.jboss.msc.service.StartException in service jboss.test-undertow-server: Failed to start service
> Caused by: java.lang.IllegalArgumentException: XNIO001001: No XNIO provider found"}}
> 10:27:16,817 ERROR [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0021: Deploy of deployment "web-suspend.jar" was rolled back with the following failure message:
> {"WFLYCTL0080: Failed services" => {"jboss.test-undertow-server" => "org.jboss.msc.service.StartException in service jboss.test-undertow-server: Failed to start service
> Caused by: java.lang.IllegalArgumentException: XNIO001001: No XNIO provider found"}}
> {noformat}
> Affected tests found so far:
> * org.wildfly.core.test.standalone.suspend.web.SuspendResumeTestCase
> * org.jboss.as.test.integration.domain.suspendresume.DomainGracefulShutdownTestCase
> * org.jboss.as.test.integration.domain.suspendresume.DomainSuspendResumeTestCase
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months