[JBoss JIRA] Commented: (JGRP-105) GossipRouter should additionally listen on IP multicast group and bridge traffic
by Galder Zamarreno (JIRA)
[ http://jira.jboss.com/jira/browse/JGRP-105?page=comments#action_12371759 ]
Galder Zamarreno commented on JGRP-105:
---------------------------------------
Looking at JBCACHE-816, I spotted some potential requirements
for JGRP-105 as explained in:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073104#4073104
Note: DC refers to Data Centre as indicated in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheAcrossDataCentres
Summarised requirements:
- be able to filter which traffic get's propagated to DCs, i.e. only JBC
CRUD methods (put, remove...etc). JGroups could define an interface
for that, which JBC would implement based on its requirements.
- configurable (sync/async) communications for in DC (typically IP multicast and
synchronous) and inter DC (inter GR - typically TCP based and asynchronous)
- GR failover. We need to support failover of a GR so that another node in the
local DC takes over.
> GossipRouter should additionally listen on IP multicast group and bridge traffic
> --------------------------------------------------------------------------------
>
> Key: JGRP-105
> URL: http://jira.jboss.com/jira/browse/JGRP-105
> Project: JGroups
> Issue Type: Feature Request
> Affects Versions: 2.2.8
> Reporter: Bela Ban
> Assigned To: Vladimir Blagojevic
> Fix For: 2.6
>
>
> GossipRouter should be augmented to not just route traffic between TCP endpoints, but also between an IP multicast group and all TCP endpoints.
> It should be configured with the properties for a (multicast-based) group X, and then forward messages from X to all of its attached endpoints, and vice versa.
> In the future, this concept could be extended to generic bridging functionality, which will allow to construct hierarchical messaging trees, similar to the MBone
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 11 months
[JBoss JIRA] Created: (JBAS-4602) org.jboss.deployment.DeploymentException is thrown when configuring the ServerSocketFactory attribute of the NamingService
by Roland Räz (JIRA)
org.jboss.deployment.DeploymentException is thrown when configuring the ServerSocketFactory attribute of the NamingService
--------------------------------------------------------------------------------------------------------------------------
Key: JBAS-4602
URL: http://jira.jboss.com/jira/browse/JBAS-4602
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Other
Affects Versions: JBossAS-4.2.1.GA
Reporter: Roland Räz
The following exception is thrown when the ServerSocketFactory attribute is configured in the org.jboss.naming.NamingService MBean is configured:
16:09:01,948 INFO [ServiceConfigurator] Problem configuring service jboss:service=Naming
org.jboss.deployment.DeploymentException: No property editor for attribute: ServerSocketFactory; type=interface java.rmi.server.RMIServerSocketFactory
at org.jboss.system.ServiceConfigurator.parseTextSerialData(ServiceConfigurator.java:554)
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:329)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:460)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
at org.jboss.system.ServiceController.install(ServiceController.java:226)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
...
Reason:
The file conf/xmdesc/NamingService-xmbean.xml contains a second definition of the ServerSocketFactory attribute ServerSocketFactory. The second definition should be ServerSocketFactoryBean.
Snippet from NamingService-xmbean.xml:
<attribute access="read-write" getMethod="getServerSocketFactory" setMethod="setServerSocketFactory">
<description>The RMI service java.rmi.server.RMIServerSocketFactory class name</description>
<name>ServerSocketFactory</name>
<type>java.lang.String</type>
</attribute>
<attribute access="read-write" getMethod="getServerSocketFactoryBean" setMethod="setServerSocketFactoryBean">
<description>The RMI service java.rmi.server.RMIServerSocketFactory instance</description>
<name>ServerSocketFactory</name>
<type>java.rmi.server.RMIServerSocketFactory</type>
</attribute>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 11 months
[JBoss JIRA] Created: (JBPORTAL-1231) Management beans initialized too many times
by Ryszard Kozmik (JIRA)
Management beans initialized too many times
-------------------------------------------
Key: JBPORTAL-1231
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1231
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Core
Affects Versions: 2.6.Alpha1, 2.6.Alpha2
Environment: AS 4.0.5
Portal 2.6Alpha1 or Alpha2 from svn tag
Reporter: Ryszard Kozmik
Assigned To: Julien Viet
Priority: Minor
Fix For: 2.6.Beta1
10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'portalobjectmgr' - only keeping the last
10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'portalAction' - only keeping the last
10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'addPageAction' - only keeping the last
10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'addWindowAction' - only keeping the last
10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'themePropertyAction' - only keeping the last
10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'instancemgr' - only keeping the last
10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'preferenceAction' - only keeping the last
10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'portletmgr' - only keeping the last
10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'createInstanceAction' - only keeping the
Those warnings are harmless and are caused by newer myfaces libraries in AS 4.0.5. Please look at forum link included in this task for sollution. However, this sollution might not fully work as Portal has quite old Facelets libraries.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 11 months