[JBoss JIRA] Created: (EJBTHREE-853) Partial StringProperty replacement in ejb 3 container
by Roland R?z (JIRA)
Partial StringProperty replacement in ejb 3 container
-----------------------------------------------------
Key: EJBTHREE-853
URL: http://jira.jboss.com/jira/browse/EJBTHREE-853
Project: EJB 3.0
Issue Type: Feature Request
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Roland R?z
I tried to change the messageSelector in an EJB 3.0 MDB in the ejb.jar.xml containing partial System Property references (aaa${xyz}bbb). Sadly this didn't work as with ejb 2.1.
I think fully supporting system property replacement as with ejb 2.x in EJB 3.0 would be a nice feature.
The method org.jboss.ejb3.metamodel.EjbJarDDObjectFactory.getValue(String name, String value)
could be changed to
{
value = org.jboss.util.StringPropertyReplacer.replaceProperties(value);
}
I would suggest, to implement the string property replacement even better in the class org.jboss.metamodel.descriptor.DDObjectFactory.getValue()
and remove the getValue method from JBossDDObjectFactory and EjbJarDDObjectFactory.
The idea of using an MBean abstraction to replace system properties is fine but the nice syntax of the StringPropertyReplacer should be still supported (${v1,v2:default}). Returning always the replaced property is one possibility (currently it is not done this way) but probably a new method "getReplaced" would be less surprising.
--
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
16 years, 11 months
[JBoss JIRA] Created: (JGRP-375) Paralellize discovery phase
by Bela Ban (JIRA)
Paralellize discovery phase
---------------------------
Key: JGRP-375
URL: http://jira.jboss.com/jira/browse/JGRP-375
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.4
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.6
With TCPPING, if we have 10 servers defined in the list, we sequentially send a GET_MBRS_REQ to each. However, if that server is not reachable, we will timeout out on the socket connect call. Also, DNS lookup might take some time, so we might time out if we cannot contact all servers. Example: servers 1 - 10. 1-9 are down or not reachable, plus we have a slow DNS, 10 is running. So before we get to 10, the discovery will timeout and we will become a singleton node.
SOLUTION: use threads from the common (global) thread pool in JGroups to parallelize the sending of requests to all 10 servers.
--
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
16 years, 11 months