[JBoss JIRA] (JGRP-1635) RELAY2: Allow for load balancing for received messages among the local cluster
by Erik Salter (JIRA)
Erik Salter created JGRP-1635:
---------------------------------
Summary: RELAY2: Allow for load balancing for received messages among the local cluster
Key: JGRP-1635
URL: https://issues.jboss.org/browse/JGRP-1635
Project: JGroups
Issue Type: Feature Request
Affects Versions: 3.2.9
Reporter: Erik Salter
Assignee: Bela Ban
I've prototyped a configuration option that load-balances applying the changes from a remote SiteMaster across all local nodes in a cluster.
There is still a single SiteMaster (thereby not breaking the existing JGroups model); the difference is that the messages are now forwarded to other nodes in the local cluster and delivered to the application layer there for unmarshalling and processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (WFLY-1380) Undertow: Error initialize the net.jawr.web.servlet.JawrServlet with undertow
by Igor Shulika (JIRA)
[ https://issues.jboss.org/browse/WFLY-1380?page=com.atlassian.jira.plugin.... ]
Igor Shulika commented on WFLY-1380:
------------------------------------
Do I need to create a separate bug for the null: java.lang.reflect.UndeclaredThrowableException
> Undertow: Error initialize the net.jawr.web.servlet.JawrServlet with undertow
> -----------------------------------------------------------------------------
>
> Key: WFLY-1380
> URL: https://issues.jboss.org/browse/WFLY-1380
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Alpha1
> Reporter: Igor Shulika
> Assignee: Stuart Douglas
> Fix For: 8.0.0.Alpha2
>
>
> I'm deploying a OSGi WAB file on the latest WildFly 8.0.0.Alpha2-SNAPSHOT server. Can not initialize the JavascriptServlet from JAWR Bundle. Note: When I used the <extension module="org.jboss.as.web"/> insted of <extension module="org.wildfly.extension.undertow"/> it works.
> Please see error trace below.
> Thanks!
> 12:20:41,629 FATAL [net.jawr.web.servlet.JawrServlet] (MSC service thread 1-7) Jawr servlet with name JavascriptServlet failed to initialize properly.
> 12:20:41,629 FATAL [net.jawr.web.servlet.JawrServlet] (MSC service thread 1-7) Cause:
> 12:20:41,629 FATAL [net.jawr.web.servlet.JawrServlet] (MSC service thread 1-7) Illegal char <:> at index 3: dwr:WebServiceDocService: java.nio.file.InvalidPathException: Illegal char <:> at index 3: dwr:WebServiceDocService
> at sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182) [rt.jar:1.7.0_21]
> at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153) [rt.jar:1.7.0_21]
> at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77) [rt.jar:1.7.0_21]
> at sun.nio.fs.WindowsPath.parse(WindowsPath.java:94) [rt.jar:1.7.0_21]
> at sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255) [rt.jar:1.7.0_21]
> at sun.nio.fs.AbstractPath.resolve(AbstractPath.java:53) [rt.jar:1.7.0_21]
> at io.undertow.server.handlers.resource.FileResourceManager.getResource(FileResourceManager.java:57) [undertow-core-1.0.0.Alpha15.jar:1.0.0.Alpha15]
> at io.undertow.server.handlers.resource.CachingResourceManager.getResource(CachingResourceManager.java:68) [undertow-core-1.0.0.Alpha15.jar:1.0.0.Alpha15]
> at io.undertow.servlet.spec.ServletContextImpl.getResourceAsStream(ServletContextImpl.java:175) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15]
> at net.jawr.web.resource.handler.reader.ServletContextResourceReader.getResource(ServletContextResourceReader.java:70) [ServletContextResourceReader.class:]
> at net.jawr.web.resource.handler.reader.ServletContextResourceReaderHandler.getResource(ServletContextResourceReaderHandler.java:192) [ServletContextResourceReaderHandler.class:]
> at net.jawr.web.resource.bundle.handler.ResourceBundlesHandlerImpl.joinAndPostprocessBundle(ResourceBundlesHandlerImpl.java:892) [ResourceBundlesHandlerImpl.class:]
> at net.jawr.web.resource.bundle.handler.ResourceBundlesHandlerImpl.joinAndPostProcessBundle(ResourceBundlesHandlerImpl.java:835) [ResourceBundlesHandlerImpl.class:]
> at net.jawr.web.resource.bundle.handler.ResourceBundlesHandlerImpl.joinAndStoreBundle(ResourceBundlesHandlerImpl.java:766) [ResourceBundlesHandlerImpl.class:]
> at net.jawr.web.resource.bundle.handler.ResourceBundlesHandlerImpl.initAllBundles(ResourceBundlesHandlerImpl.java:542) [ResourceBundlesHandlerImpl.class:]
> at net.jawr.web.resource.bundle.handler.CachedResourceBundlesHandler.initAllBundles(CachedResourceBundlesHandler.java:126) [CachedResourceBundlesHandler.class:]
> at net.jawr.web.resource.bundle.factory.BundlesHandlerFactory.buildResourceBundlesHandler(BundlesHandlerFactory.java:233) [BundlesHandlerFactory.class:]
> at net.jawr.web.resource.bundle.factory.PropertiesBasedBundlesHandlerFactory.buildResourceBundlesHandler(PropertiesBasedBundlesHandlerFactory.java:204) [PropertiesBasedBundlesHandlerFactory.class:]
> at net.jawr.web.servlet.JawrRequestHandler.initializeJawrConfig(JawrRequestHandler.java:349) [JawrRequestHandler.class:]
> at net.jawr.web.servlet.JawrRequestHandler.initRequestHandler(JawrRequestHandler.java:262) [JawrRequestHandler.class:]
> at net.jawr.web.servlet.JawrRequestHandler.<init>(JawrRequestHandler.java:184) [JawrRequestHandler.class:]
> at net.jawr.web.servlet.JawrServlet.init(JawrServlet.java:56) [JawrServlet.class:]
> at javax.servlet.GenericServlet.init(GenericServlet.java:244) [jboss-servlet-api_3.1_spec-1.0.0.Alpha1.jar:1.0.0.Alpha1]
> at io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:145) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15]
> at io.undertow.servlet.core.ManagedServlet.start(ManagedServlet.java:62) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15]
> at io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:599) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15]
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:77)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (WFLY-1416) Cross site replication requires totally connected graph of sites/routes
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-1416?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz edited comment on WFLY-1416 at 5/29/13 12:37 PM:
---------------------------------------------------------------------
Bela is looking to see if there is a non-performance impacting solution to this at the JGroups level.
One AS level option would be to either:
(i) require a totally connected graph
(ii) if not totally connected, allow specifying site indices in XML with the remote-site element
was (Author: rachmato):
Bela is looking to see if there is a non-performance impacting solution to this at the JGroups level.
One option would be to either:
(i) require a totally connected graph
(ii) if not totally connected, allow specifying site indices in XML with the remote-site element
> Cross site replication requires totally connected graph of sites/routes
> ------------------------------------------------------------------------
>
> Key: WFLY-1416
> URL: https://issues.jboss.org/browse/WFLY-1416
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 8.0.0.Alpha2
> Reporter: Richard Achmatowicz
> Assignee: Paul Ferraro
>
> Cross site replication is configured using JGroups subsystem <relay/> and <remote-site/> elements to define sites and multicast relay routes between sites.
> Looking at a site/route configuration as a graph of nodes and edges, xsite only works if this graph is totally connected (i.e. every site has a defined direct route to every other site). This is because <site name> -> <site id> mappings are assigned per node, with no agreement on what is happening at other nodes.
> For example, this configuration works:
> <relay site="LON">
> <remote-site name="NYC" .../>
> <remote-site name="SFO" .../>
> </relay>
> <relay site="NYC">
> <remote-site name="LON" .../>
> <remote-site name="SFO" .../>
> </relay>
> <relay site="SFO">
> <remote-site name="NYC" .../>
> <remote-site name="LON" .../>
> </relay>
> but this configuration does not:
> <relay site="LON">
> <remote-site name="NYC" .../>
> <remote-site name="SFO" .../>
> </relay>
> <relay site="NYC">
> <remote-site name="LON" .../>
> </relay>
> <relay site="SFO">
> <remote-site name="LON" .../>
> </relay>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (WFLY-1416) Cross site replication requires totally connected graph of sites/routes
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-1416?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz edited comment on WFLY-1416 at 5/29/13 12:36 PM:
---------------------------------------------------------------------
Bela is looking to see if there is a non-performance impacting solution to this at the JGroups level.
One option would be to either:
(i) require a totally connected graph
(ii) if not totally connected, allow specifying site indices in XML with the remote-site element
was (Author: rachmato):
Bela is looking to see if there is a non-performance impacting solution to this.
> Cross site replication requires totally connected graph of sites/routes
> ------------------------------------------------------------------------
>
> Key: WFLY-1416
> URL: https://issues.jboss.org/browse/WFLY-1416
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 8.0.0.Alpha2
> Reporter: Richard Achmatowicz
> Assignee: Paul Ferraro
>
> Cross site replication is configured using JGroups subsystem <relay/> and <remote-site/> elements to define sites and multicast relay routes between sites.
> Looking at a site/route configuration as a graph of nodes and edges, xsite only works if this graph is totally connected (i.e. every site has a defined direct route to every other site). This is because <site name> -> <site id> mappings are assigned per node, with no agreement on what is happening at other nodes.
> For example, this configuration works:
> <relay site="LON">
> <remote-site name="NYC" .../>
> <remote-site name="SFO" .../>
> </relay>
> <relay site="NYC">
> <remote-site name="LON" .../>
> <remote-site name="SFO" .../>
> </relay>
> <relay site="SFO">
> <remote-site name="NYC" .../>
> <remote-site name="LON" .../>
> </relay>
> but this configuration does not:
> <relay site="LON">
> <remote-site name="NYC" .../>
> <remote-site name="SFO" .../>
> </relay>
> <relay site="NYC">
> <remote-site name="LON" .../>
> </relay>
> <relay site="SFO">
> <remote-site name="LON" .../>
> </relay>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (WFLY-1416) Cross site replication requires totally connected graph of sites/routes
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-1416?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz commented on WFLY-1416:
-------------------------------------------
Bela is looking to see if there is a non-performance impacting solution to this.
> Cross site replication requires totally connected graph of sites/routes
> ------------------------------------------------------------------------
>
> Key: WFLY-1416
> URL: https://issues.jboss.org/browse/WFLY-1416
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 8.0.0.Alpha2
> Reporter: Richard Achmatowicz
> Assignee: Paul Ferraro
>
> Cross site replication is configured using JGroups subsystem <relay/> and <remote-site/> elements to define sites and multicast relay routes between sites.
> Looking at a site/route configuration as a graph of nodes and edges, xsite only works if this graph is totally connected (i.e. every site has a defined direct route to every other site). This is because <site name> -> <site id> mappings are assigned per node, with no agreement on what is happening at other nodes.
> For example, this configuration works:
> <relay site="LON">
> <remote-site name="NYC" .../>
> <remote-site name="SFO" .../>
> </relay>
> <relay site="NYC">
> <remote-site name="LON" .../>
> <remote-site name="SFO" .../>
> </relay>
> <relay site="SFO">
> <remote-site name="NYC" .../>
> <remote-site name="LON" .../>
> </relay>
> but this configuration does not:
> <relay site="LON">
> <remote-site name="NYC" .../>
> <remote-site name="SFO" .../>
> </relay>
> <relay site="NYC">
> <remote-site name="LON" .../>
> </relay>
> <relay site="SFO">
> <remote-site name="LON" .../>
> </relay>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (WFLY-1416) Cross site replication requires totally connected graph of sites/routes
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/WFLY-1416?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz commented on WFLY-1416:
-------------------------------------------
The results of running probe.sh on the first example above:
{noformat}
[nrla@lenovo bin]$ ./probe.sh -addr 224.0.75.75 op=RELAY2.printRoutes
-- send probe on /224.0.75.75:7500
#1 (211 bytes):
local_addr=LON-1/web [54877f5a-7378-f542-fec5-8b89af0b6d89]
cluster=web
RELAY2.printRoutes=n/a (not site master)
physical_addr=127.0.0.1:55300
view=[LON-0/web|1] [LON-0/web, LON-1/web]
version=3.3.0.Final
#2 (274 bytes):
local_addr=LON-0/web [a033d27d-6af1-3ec7-7ee2-3241e4e62978]
cluster=web
RELAY2.printRoutes=LON --> _LON-0/web:LON [UP]
NYC --> _NYC-0/web:NYC [UP]
SFO --> _SFO-0/web:SFO [UP]
physical_addr=127.0.0.1:55200
view=[LON-0/web|1] [LON-0/web, LON-1/web]
version=3.3.0.Final
#3 (263 bytes):
local_addr=NYC-0/web [b287afd9-70a6-81cd-65ca-561838aaa51f]
cluster=web
RELAY2.printRoutes=LON --> _LON-0/web:LON [UP]
NYC --> _NYC-0/web:NYC [UP]
SFO --> _SFO-0/web:SFO [UP]
physical_addr=127.0.0.1:55400
view=[NYC-0/web|0] [NYC-0/web]
version=3.3.0.Final
#4 (263 bytes):
local_addr=SFO-0/web [b8e9a2ce-72b7-7c14-e420-9276912f827b]
cluster=web
RELAY2.printRoutes=LON --> _LON-0/web:LON [UP]
NYC --> _NYC-0/web:NYC [UP]
SFO --> _SFO-0/web:SFO [UP]
physical_addr=127.0.0.1:55500
view=[SFO-0/web|0] [SFO-0/web]
version=3.3.0.Final
4 responses (4 matches, 0 non matches)
{noformat}
> Cross site replication requires totally connected graph of sites/routes
> ------------------------------------------------------------------------
>
> Key: WFLY-1416
> URL: https://issues.jboss.org/browse/WFLY-1416
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 8.0.0.Alpha2
> Reporter: Richard Achmatowicz
> Assignee: Paul Ferraro
>
> Cross site replication is configured using JGroups subsystem <relay/> and <remote-site/> elements to define sites and multicast relay routes between sites.
> Looking at a site/route configuration as a graph of nodes and edges, xsite only works if this graph is totally connected (i.e. every site has a defined direct route to every other site). This is because <site name> -> <site id> mappings are assigned per node, with no agreement on what is happening at other nodes.
> For example, this configuration works:
> <relay site="LON">
> <remote-site name="NYC" .../>
> <remote-site name="SFO" .../>
> </relay>
> <relay site="NYC">
> <remote-site name="LON" .../>
> <remote-site name="SFO" .../>
> </relay>
> <relay site="SFO">
> <remote-site name="NYC" .../>
> <remote-site name="LON" .../>
> </relay>
> but this configuration does not:
> <relay site="LON">
> <remote-site name="NYC" .../>
> <remote-site name="SFO" .../>
> </relay>
> <relay site="NYC">
> <remote-site name="LON" .../>
> </relay>
> <relay site="SFO">
> <remote-site name="LON" .../>
> </relay>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month