[JBoss JIRA] Created: (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address
8:43 a.m.
mod_cluster should use hostname provided in address instead a IP address
------------------------------------------------------------------------
Key: MODCLUSTER-168
URL: https://jira.jboss.org/browse/MODCLUSTER-168
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR3
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Jean-Frederic Clere
The CONFIG message contains something like:
JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp
Even if the Connector is defined like:
<Connector port="8009" address= "jfcpc"
protocol="AJP/1.3" redirectPort="8443" />
There are 2 ways to fix:
- Use the String (Change the Connector.java in mod_cluster).
- Use parameters.put("Host", connector.getAddress().getHostName()); when
building the CONFIG message.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:05 a.m.
New subject: [JBoss JIRA] Updated: (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address
[
https://jira.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.plug...
]
Jean-Frederic Clere updated MODCLUSTER-168:
-------------------------------------------
Fix Version/s: 1.1.0.Final
mod_cluster should use hostname provided in address instead a IP
address
------------------------------------------------------------------------
Key: MODCLUSTER-168
URL: https://jira.jboss.org/browse/MODCLUSTER-168
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR3
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Jean-Frederic Clere
Fix For: 1.1.0.Final
The CONFIG message contains something like:
JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp
Even if the Connector is defined like:
<Connector port="8009" address= "jfcpc"
protocol="AJP/1.3" redirectPort="8443" />
There are 2 ways to fix:
- Use the String (Change the Connector.java in mod_cluster).
- Use parameters.put("Host", connector.getAddress().getHostName()); when
building the CONFIG message.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:22 a.m.
New subject: [JBoss JIRA] Assigned: (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address
[
https://jira.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.plug...
]
Paul Ferraro reassigned MODCLUSTER-168:
---------------------------------------
Assignee: Paul Ferraro (was: Jean-Frederic Clere)
mod_cluster should use hostname provided in address instead a IP
address
------------------------------------------------------------------------
Key: MODCLUSTER-168
URL: https://jira.jboss.org/browse/MODCLUSTER-168
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR3
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Paul Ferraro
Fix For: 1.1.0.Final
The CONFIG message contains something like:
JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp
Even if the Connector is defined like:
<Connector port="8009" address= "jfcpc"
protocol="AJP/1.3" redirectPort="8443" />
There are 2 ways to fix:
- Use the String (Change the Connector.java in mod_cluster).
- Use parameters.put("Host", connector.getAddress().getHostName()); when
building the CONFIG message.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:58 a.m.
New subject: [JBoss JIRA] Commented: (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address
[
https://jira.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.plug...
]
Paul Ferraro commented on MODCLUSTER-168:
-----------------------------------------
We don't want to use InetAddress.getHostName() since this may perform unwanted reverse
dns lookup if the host was specified as an address.
mod_cluster should use hostname provided in address instead a IP
address
------------------------------------------------------------------------
Key: MODCLUSTER-168
URL: https://jira.jboss.org/browse/MODCLUSTER-168
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR3
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Paul Ferraro
Fix For: 1.1.0.Final
The CONFIG message contains something like:
JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp
Even if the Connector is defined like:
<Connector port="8009" address= "jfcpc"
protocol="AJP/1.3" redirectPort="8443" />
There are 2 ways to fix:
- Use the String (Change the Connector.java in mod_cluster).
- Use parameters.put("Host", connector.getAddress().getHostName()); when
building the CONFIG message.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 a.m.
New subject: [JBoss JIRA] Resolved: (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address
[
https://jira.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.plug...
]
Paul Ferraro resolved MODCLUSTER-168.
-------------------------------------
Resolution: Done
Parse host name from InetAddress.toString() if it exists, otherwise use address portion -
since toString() does not perform reverse dns lookup.
mod_cluster should use hostname provided in address instead a IP
address
------------------------------------------------------------------------
Key: MODCLUSTER-168
URL: https://jira.jboss.org/browse/MODCLUSTER-168
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR3
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Paul Ferraro
Fix For: 1.1.0.Final
The CONFIG message contains something like:
JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp
Even if the Connector is defined like:
<Connector port="8009" address= "jfcpc"
protocol="AJP/1.3" redirectPort="8443" />
There are 2 ways to fix:
- Use the String (Change the Connector.java in mod_cluster).
- Use parameters.put("Host", connector.getAddress().getHostName()); when
building the CONFIG message.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:19 a.m.
New subject: [JBoss JIRA] (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address
3:28 a.m.
New subject: [JBoss JIRA] (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address
10:53 a.m.
New subject: [JBoss JIRA] (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address
[
https://issues.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere commented on MODCLUSTER-168:
------------------------------------------------
-Dorg.jboss.modcluster.USE_HOST_NAME true / false as in 1.0.x
mod_cluster should use hostname provided in address instead a IP
address
------------------------------------------------------------------------
Key: MODCLUSTER-168
URL: https://issues.jboss.org/browse/MODCLUSTER-168
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR3
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Paul Ferraro
Fix For: 1.1.0.Final
The CONFIG message contains something like:
JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp
Even if the Connector is defined like:
<Connector port="8009" address= "jfcpc"
protocol="AJP/1.3" redirectPort="8443" />
There are 2 ways to fix:
- Use the String (Change the Connector.java in mod_cluster).
- Use parameters.put("Host", connector.getAddress().getHostName()); when
building the CONFIG message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:55 a.m.
New subject: [JBoss JIRA] (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address
[
https://issues.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere updated MODCLUSTER-168:
-------------------------------------------
Fix Version/s: 1.2.2.Beta1
Forum Reference: http://community.jboss.org/message/548324#548324 (was:
http://community.jboss.org/message/548324#548324)
mod_cluster should use hostname provided in address instead a IP
address
------------------------------------------------------------------------
Key: MODCLUSTER-168
URL: https://issues.jboss.org/browse/MODCLUSTER-168
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR3
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Paul Ferraro
Fix For: 1.1.0.Final, 1.2.2.Beta1
The CONFIG message contains something like:
JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp
Even if the Connector is defined like:
<Connector port="8009" address= "jfcpc"
protocol="AJP/1.3" redirectPort="8443" />
There are 2 ways to fix:
- Use the String (Change the Connector.java in mod_cluster).
- Use parameters.put("Host", connector.getAddress().getHostName()); when
building the CONFIG message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:55 a.m.
New subject: [JBoss JIRA] (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address
[
https://issues.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere reopened MODCLUSTER-168:
--------------------------------------------
mod_cluster should use hostname provided in address instead a IP
address
------------------------------------------------------------------------
Key: MODCLUSTER-168
URL: https://issues.jboss.org/browse/MODCLUSTER-168
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR3
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Paul Ferraro
Fix For: 1.1.0.Final, 1.2.2.Beta1
The CONFIG message contains something like:
JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp
Even if the Connector is defined like:
<Connector port="8009" address= "jfcpc"
protocol="AJP/1.3" redirectPort="8443" />
There are 2 ways to fix:
- Use the String (Change the Connector.java in mod_cluster).
- Use parameters.put("Host", connector.getAddress().getHostName()); when
building the CONFIG message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:57 a.m.
New subject: [JBoss JIRA] (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address
[
https://issues.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.pl...
]
Aleksandar Kostadinov commented on MODCLUSTER-168:
--------------------------------------------------
Thank you, Jean, do you know which release versions this switch will be available in?
mod_cluster should use hostname provided in address instead a IP
address
------------------------------------------------------------------------
Key: MODCLUSTER-168
URL: https://issues.jboss.org/browse/MODCLUSTER-168
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR3
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Paul Ferraro
Fix For: 1.1.0.Final, 1.2.2.Beta1
The CONFIG message contains something like:
JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp
Even if the Connector is defined like:
<Connector port="8009" address= "jfcpc"
protocol="AJP/1.3" redirectPort="8443" />
There are 2 ways to fix:
- Use the String (Change the Connector.java in mod_cluster).
- Use parameters.put("Host", connector.getAddress().getHostName()); when
building the CONFIG message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:59 a.m.
New subject: [JBoss JIRA] (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address
[
https://issues.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.pl...
]
Aleksandar Kostadinov edited comment on MODCLUSTER-168 at 7/9/12 11:57 AM:
---------------------------------------------------------------------------
Thank you, Jean, do you know which release versions this switch will be available in? I
mean 1.1.?
was (Author: akostadinov):
Thank you, Jean, do you know which release versions this switch will be available in?
mod_cluster should use hostname provided in address instead a IP
address
------------------------------------------------------------------------
Key: MODCLUSTER-168
URL: https://issues.jboss.org/browse/MODCLUSTER-168
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR3
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Paul Ferraro
Fix For: 1.1.0.Final, 1.2.2.Beta1
The CONFIG message contains something like:
JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp
Even if the Connector is defined like:
<Connector port="8009" address= "jfcpc"
protocol="AJP/1.3" redirectPort="8443" />
There are 2 ways to fix:
- Use the String (Change the Connector.java in mod_cluster).
- Use parameters.put("Host", connector.getAddress().getHostName()); when
building the CONFIG message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:11 a.m.
New subject: [JBoss JIRA] (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address
[
https://issues.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere updated MODCLUSTER-168:
-------------------------------------------
Fix Version/s: (was: 1.1.0.Final)
Forum Reference: http://community.jboss.org/message/548324#548324 (was:
http://community.jboss.org/message/548324#548324)
mod_cluster should use hostname provided in address instead a IP
address
------------------------------------------------------------------------
Key: MODCLUSTER-168
URL: https://issues.jboss.org/browse/MODCLUSTER-168
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR3
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Paul Ferraro
Fix For: 1.2.2.Beta1
The CONFIG message contains something like:
JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp
Even if the Connector is defined like:
<Connector port="8009" address= "jfcpc"
protocol="AJP/1.3" redirectPort="8443" />
There are 2 ways to fix:
- Use the String (Change the Connector.java in mod_cluster).
- Use parameters.put("Host", connector.getAddress().getHostName()); when
building the CONFIG message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:11 a.m.
New subject: [JBoss JIRA] (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address
[
https://issues.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere commented on MODCLUSTER-168:
------------------------------------------------
1.2.2.Beta1
mod_cluster should use hostname provided in address instead a IP
address
------------------------------------------------------------------------
Key: MODCLUSTER-168
URL: https://issues.jboss.org/browse/MODCLUSTER-168
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR3
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Paul Ferraro
Fix For: 1.2.2.Beta1
The CONFIG message contains something like:
JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp
Even if the Connector is defined like:
<Connector port="8009" address= "jfcpc"
protocol="AJP/1.3" redirectPort="8443" />
There are 2 ways to fix:
- Use the String (Change the Connector.java in mod_cluster).
- Use parameters.put("Host", connector.getAddress().getHostName()); when
building the CONFIG message.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:18 a.m.
New subject: [JBoss JIRA] (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address
[
https://issues.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere commented on MODCLUSTER-168:
------------------------------------------------
the fix for MOD_CLUSTER_1_0_10_GA_CP is r892
mod_cluster should use hostname provided in address instead a IP
address
------------------------------------------------------------------------
Key: MODCLUSTER-168
URL: https://issues.jboss.org/browse/MODCLUSTER-168
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR3
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Paul Ferraro
Fix For: 1.2.2.Beta1
The CONFIG message contains something like:
JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp
Even if the Connector is defined like:
<Connector port="8009" address= "jfcpc"
protocol="AJP/1.3" redirectPort="8443" />
There are 2 ways to fix:
- Use the String (Change the Connector.java in mod_cluster).
- Use parameters.put("Host", connector.getAddress().getHostName()); when
building the CONFIG message.
--
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
9:32 a.m.
New subject: [JBoss JIRA] (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address
[
https://issues.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere updated MODCLUSTER-168:
-------------------------------------------
Fix Version/s: 1.2.3.Beta1
(was: 1.2.2.Final)
mod_cluster should use hostname provided in address instead a IP
address
------------------------------------------------------------------------
Key: MODCLUSTER-168
URL: https://issues.jboss.org/browse/MODCLUSTER-168
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR3
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Paul Ferraro
Fix For: 1.2.3.Beta1
The CONFIG message contains something like:
JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp
Even if the Connector is defined like:
<Connector port="8009" address= "jfcpc"
protocol="AJP/1.3" redirectPort="8443" />
There are 2 ways to fix:
- Use the String (Change the Connector.java in mod_cluster).
- Use parameters.put("Host", connector.getAddress().getHostName()); when
building the CONFIG message.
--
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
6:12 a.m.
New subject: [JBoss JIRA] (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address
[
https://issues.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere updated MODCLUSTER-168:
-------------------------------------------
Fix Version/s: 1.2.4.Final
(was: 1.2.3.Final)
mod_cluster should use hostname provided in address instead a IP
address
------------------------------------------------------------------------
Key: MODCLUSTER-168
URL: https://issues.jboss.org/browse/MODCLUSTER-168
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR3
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Paul Ferraro
Fix For: 1.2.4.Final
The CONFIG message contains something like:
JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp
Even if the Connector is defined like:
<Connector port="8009" address= "jfcpc"
protocol="AJP/1.3" redirectPort="8443" />
There are 2 ways to fix:
- Use the String (Change the Connector.java in mod_cluster).
- Use parameters.put("Host", connector.getAddress().getHostName()); when
building the CONFIG message.
--
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
6:24 a.m.
New subject: [JBoss JIRA] (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address
[
https://issues.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere edited comment on MODCLUSTER-168 at 10/18/12 7:22 AM:
--------------------------------------------------------------------------
1.2.4.Final
was (Author: jfclere):
1.2.2.Beta1
mod_cluster should use hostname provided in address instead a IP
address
------------------------------------------------------------------------
Key: MODCLUSTER-168
URL: https://issues.jboss.org/browse/MODCLUSTER-168
Project: mod_cluster
Issue Type: Feature Request
Affects Versions: 1.1.0.CR3
Environment: any
Reporter: Jean-Frederic Clere
Assignee: Paul Ferraro
Fix For: 1.2.4.Final
The CONFIG message contains something like:
JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp
Even if the Connector is defined like:
<Connector port="8009" address= "jfcpc"
protocol="AJP/1.3" redirectPort="8443" />
There are 2 ways to fix:
- Use the String (Change the Connector.java in mod_cluster).
- Use parameters.put("Host", connector.getAddress().getHostName()); when
building the CONFIG message.
--
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
4447
days inactive
5301
days old
mod_cluster-issues@lists.jboss.org
17 comments
3 participants
participants (3)
-
Aleksandar Kostadinov (JIRA) -
Jean-Frederic Clere (JIRA)
-
Paul Ferraro (JIRA)