[
https://jira.jboss.org/jira/browse/JBCLUSTER-220?page=com.atlassian.jira....
]
Brian Stansberry commented on JBCLUSTER-220:
--------------------------------------------
Yes, these can be ignored. Better yet, remove the attributes mentioned from the channel
configurations in the AS so the WARNs will go away.
The standard configurations in AS 4.x are not optimized for JGroups 2.6; perhaps you would
be better off replacing them with ones based on the "udp" or "tcp"
protocol stack configs in AS 5's ChannelFactory (see
http://www.jboss.org/community/docs/DOC-13186 for discussion of where that is in AS 5).
This would be a cut-and-paste exercise + changing the mcast_port (to make the port unique
for each channel) and removing the singleton_name attribute from UDP/TCP.
If you have more questions about this move, please start a thread on the "Clustering
User" forum, rather than mixing the discussion in here.
HAPartition.callMethodOnCluster() is not reentrant
--------------------------------------------------
Key: JBCLUSTER-220
URL:
https://jira.jboss.org/jira/browse/JBCLUSTER-220
Project: JBoss Clustering
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: HA-Server-API
Reporter: Fol de Rol
Assignee: Brian Stansberry
An RPC handler of callMethodOnCluster() cannot in its turn call callMethodOnCluster()
querying other services. The second call blocks until timeout is reached and returns
without results.
The same relates to facilities based on this method like Distributed Replicant Manager.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira