I was trying to start the Jboss and was getting these error all of a sudden. I checked my code it was ok. Deleting temp folder and restarting jboss was not resolving the issue.
Work around – Check if you have multiple wireless network connected, if so close all the network connection just work with one, you will not get this error in your windows machine.
The error log are as below
12:02:34,022 INFO [SessionFactoryImpl] building session factory
12:02:34,163 WARN [CacheConfiguration] Cache ‘persistence.unit:unitName=cloudmatrix.ear/bms.jar#bts.org.hibernate.cache.UpdateTimestampsCache’ is set to eternal but also has TTI/TTL set. To avoid this warning, clean up the config removing conflicting values of eternal, TTI and TTL. Effective configuration for Cache ‘persistence.unit:unitName=cloudmatrix.ear/bms.jar#bts.org.hibernate.cache.UpdateTimestampsCache’ will be eternal=’true’, timeToIdleSeconds=’0′, timeToLiveSeconds=’0′.
12:02:34,262 ERROR [MulticastRMICacheManagerPeerProvider] Error starting heartbeat. Error was: IP_ADD_MEMBERSHIP failed (out of hardware filters?)
java.net.SocketException: IP_ADD_MEMBERSHIP failed (out of hardware filters?)
at java.net.PlainDatagramSocketImpl.join(Native Method)
Let me fix it
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To prevent the network adapter from detecting a link state, follow these steps.
Note The NetBEUI protocol and the IPX protocol do not support Media Sensing.
- Start Registry Editor.
- Locate the following registry subkey:
- Add the following registry entry to the
Data type: REG_DWORD (Boolean)
Note This entry controls the behavior of Media Sensing. By default, Media Sensing events trigger a DHCP client to take an action. For example, when a connect event occurs, the client tries to obtain a lease. When a disconnect event occurs, the client may invalidate the interface and routes. If you set this value data to 1, DHCP clients and non-DHCP clients ignore Media Sensing events.
- Restart the computer.