[JBoss JIRA] Created: (JBAS-7779) Provide a node name mechanism
by David Lloyd (JIRA)
Provide a node name mechanism
-----------------------------
Key: JBAS-7779
URL: https://jira.jboss.org/jira/browse/JBAS-7779
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Other
Reporter: David Lloyd
Assignee: David Lloyd
Fix For: JBossAS-6.0.0.M3
"Today, we configure clustered JBossAS instances with a "jboss.partition.name" which represents the identity of the cluster of which it is a part. However as far as I've been able to figure out, we do not have a hard-and-fast concept of a node name. I would like to propose a system property "jboss.node.name" which represents the identity of the node itself. This property would have a sensible default but would also be modifiable just as partition name is today.
In terms of implementation, my few minutes of research on the topic indicate that the best way to calculate a default node name at boot would be as follows.
1. Define a system property, "jboss.host.qualified.name" or just "host.qualified.name", which, if unspecified, defaults to the value of:
1. the HOSTNAME env var, or if that is not specified,
2. the COMPUTERNAME env var, or if that is not specified,
3. the value of InetAddress.getLocalHost().getHostName(), or if that does not turn up anything,
4. a default value such as "unknown-host.unknown-domain"
2. Define a system property, "jboss.host.name" or just "host.name", which, if unspecified, defaults to host portion of the above property
3. Define a system property, "jboss.node.name" which, if unspecified, defaults to the value of the above property
--
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
14 years, 2 months
[JBoss JIRA] Created: (JBREFLECT-99) AbstractIsLocalResourcePlugin.isSameInParent relies on ClassLoader.getResource instead of ClassPool.find
by Flavia Rainone (JIRA)
AbstractIsLocalResourcePlugin.isSameInParent relies on ClassLoader.getResource instead of ClassPool.find
--------------------------------------------------------------------------------------------------------
Key: JBREFLECT-99
URL: https://jira.jboss.org/jira/browse/JBREFLECT-99
Project: JBoss Reflection
Issue Type: Bug
Components: Class Pool
Affects Versions: JBossReflection.2.2.0-Alpha3
Reporter: Flavia Rainone
Assignee: Flavia Rainone
Fix For: JBossReflection.2.2.0-Alpha4
This bug has been covered by the old vfs (version 2):
rotected boolean isSameInParent(String classResourceName, URL foundURL)
{
ClassPool parent = pool.getParent();
if (parent != null)
{
ClassLoader parentLoader = parent.getClassLoader();
URL parentURL = parentLoader.getResource(classResourceName);
if (parentURL == null)
{
return false;
}
URI parentURI = URI.create(parentURL.toString());
URI foundURI = URI.create(foundURL.toString());
if (parentURI.equals(foundURI))
{
return true;
}
}
return false;
}
The lines that try to create a URI from the URL fail, since the URL would return a vfs:// file. With VFS 3, the URL contains file:// instead, thus affecting the result of the method and uncovering the error.
--
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
14 years, 2 months