|
If you were logged in you would be able to see more operations.
|
|
|
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
4.3.0.GA
|
|
Security Level:
|
Public
(Everyone can see)
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
In */deploy/jboss-messaging.sar/hsqldb-persistence-service.xml there bind_to_all_interfaces attribute set to TRUE. This is not a bug, but is this really intended? It is incosistent with other services relying on JGroups, since non of them overrides this parameter and it defaults to FALSE.
<MPING timeout="4000"
bind_to_all_interfaces="true"
mcast_addr="${jboss.messaging.datachanneludpaddress:228.6.6.6}"
mcast_port="${jboss.messaging.datachanneludpport:45567}"
ip_ttl="${jboss.messaging.ipttl:8}"
num_initial_members="2"
num_ping_requests="1"/>
|
|
Description
|
In */deploy/jboss-messaging.sar/hsqldb-persistence-service.xml there bind_to_all_interfaces attribute set to TRUE. This is not a bug, but is this really intended? It is incosistent with other services relying on JGroups, since non of them overrides this parameter and it defaults to FALSE.
<MPING timeout="4000"
bind_to_all_interfaces="true"
mcast_addr="${jboss.messaging.datachanneludpaddress:228.6.6.6}"
mcast_port="${jboss.messaging.datachanneludpport:45567}"
ip_ttl="${jboss.messaging.ipttl:8}"
num_initial_members="2"
num_ping_requests="1"/>
|
Show » |
|
|
Bug
Resolved
Minor
bind_to_all attribute set to true for MPING protocol of messaging data chanel JGroups stack configuration