Thx,
setting -Djava.net.preferIPv4Stack=true helped:
| 09:38:50,561 INFO [vakuum] Fetching state (will wait for 3
milliseconds):
| 09:38:50,651 INFO [HANamingService] Started ha-jndi bootstrap
jnpPort=1100, backlog=50, bindAddress=/0.0.0.0
| 09:38:50,660 INFO [DetachedHANamingServ
Ok, not the AutoDiscoveryAddress seems to be relevant but the
AutoDiscoveryBindAddress. This defaults to jboss.bind.address which defaults to
0.0.0.0. Setting this to some "real" value makes AutoDiscovery work.
I read some thread in the forum in respect to problems with the wildcard
address.
Fo
I saw the same (since 4.0.3sp1 - used 4.0.2 before) without binding only to
loopback.
Configuration says
| 230.0.0.4
|
| 08:18:05,687 INFO [vakuum] I am (172.17.12.57:1099) received
membershipChanged event:
| 08:18:05,687 INFO [vakuum] Dead members: 0 ([])
| 08:18:05,688 INFO [v
Hi,
I searched a while until I discovered the following problem:
scenario:
JDBCStateManager on MySQL with existing tables (so CREATE_TABLES_ON_STARTUP =
FALSE).
Starting JBoss lead to OutOfMemory-Exceptions after a while and no
error-message about the cause.
solution:
After enabling full logg
