jboss – Error was: IP_ADD_MEMBERSHIP failed (out of hardware filters?)

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)
    at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:181)

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.

  1. Start Registry Editor.
  2. Locate the following registry subkey:


  3. Add the following registry entry to the



    Name: DisableDHCPMediaSense
    Data type: REG_DWORD (Boolean)
    Value: 1

    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.

  4. Restart the computer.

Errors : Wicket RuntimeException “No get method defined for class–upload”

In a recent Wicket migration 1.3 to 1.6, my application was giving me trouble whenever used uploads an image.

Main exception

org.apache.wicket.WicketRuntimeException: No get method defined for class: class com.ptc.fusion.web.pages.admin.ManageCustomizationPage expression: upload
     at org.apache.wicket.core.util.lang.PropertyResolver.getGetAndSetter(PropertyResolver.java:499)
     at org.apache.wicket.core.util.lang.PropertyResolver.getObjectAndGetSetter(PropertyResolver.java:341)
     at org.apache.wicket.core.util.lang.PropertyResolver.getObjectAndGetSetter(PropertyResolver.java:244)
     at org.apache.wicket.core.util.lang.PropertyResolver.getValue(PropertyResolver.java:97)
     at org.apache.wicket.model.AbstractPropertyModel.getObject(AbstractPropertyModel.java:86)
     at org.apache.wicket.Component.getDefaultModelObject(Component.java:1616)


I spent several hours on this issue, and once again, I figured it out 20 minutes after I posted to SO about it. The fix is to turn the upload field declaration into one that provides a model, like this:

fuf = new FileUploadField("DocumentUpload", new Model<FileUpload>());

EDIT: It turns out this was related to 1.3 -> 1.4 migration. Per the migration guide,

FileUploadField – now requires model

The FileUploadField now REQUIRES a model. This means that if you previously used the ID-only >constructor (i.e. new FileUploadField(“myFileField”)), you will need to change it to include >a model (i.e. new FileUploadField(“myFileField”, new Model())).


Previously constructor was like :

final FileUploadField uploadField = new FileUploadField(“upload”);


The problem got resolved just by using the new constructor mentioned below :

        IModel uploadModel = new Model<FileUpload>();

    public IModel getUploadModel() {
        return uploadModel;

    public void setUploadModel(IModel uploadModel) {
        this.uploadModel = uploadModel;
    final FileUploadField uploadField = new FileUploadField(“upload”, uploadModel);


I found solution here :

Error Handling : java.lang.VerifyError: Expecting a stackmap frame

If you are struggling with the following kind of error

java.lang.VerifyError: Expecting a stackmap frame at branch target 6 bla bla bla …

then a simple solution is to add the following default JVM argument -XX:-UseSplitVerifier

If you are doing it in eclipse, like i was, then goto Window -> Preferences -> Installed JREs -> and add the default parameter.

If may want to add it to the sure fire plugin in pom.xml

                        <argLine>-Xms512m -Xmx512m -XX:-UseSplitVerifier</argLine>


Detailed stack trace :                
Running TestSuite

Total tests run: 0, Failures: 0, Skips: 0

org.apache.maven.surefire.util.SurefireReflectionException: java.lang.reflect.In
vocationTargetException; nested exception is java.lang.reflect.InvocationTargetE
xception: null
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
        at java.lang.reflect.Method.invoke(Method.java:601)
        at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(
        at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke
        at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(Provi
        at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(Fork
        at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:
Caused by: java.lang.VerifyError: Expecting a stackmap frame at branch target 24
in method com.ptc.fusion.model.learningitem.AbstractLearningItem.JiBX_LearningI
fusion/model/learningitem/AbstractLearningItem; at offset 16
        at java.lang.Class.getDeclaredMethods0(Native Method)
        at java.lang.Class.privateGetDeclaredMethods(Class.java:2442)
        at java.lang.Class.privateGetPublicMethods(Class.java:2562)
        at java.lang.Class.getMethods(Class.java:1427)
        at org.testng.internal.TestNGClassFinder.<init>(TestNGClassFinder.java:5
        at org.testng.TestRunner.initMethods(TestRunner.java:289)
        at org.testng.TestRunner.init(TestRunner.java:235)
        at org.testng.TestRunner.init(TestRunner.java:197)
        at org.testng.TestRunner.<init>(TestRunner.java:141)
        at org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRu
        at org.testng.SuiteRunner.privateRun(SuiteRunner.java:250)
        at org.testng.SuiteRunner.run(SuiteRunner.java:204)
        at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:877)
        at org.testng.TestNG.runSuitesLocally(TestNG.java:842)
        at org.testng.TestNG.run(TestNG.java:751)
        at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.ja
        at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXml
        at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider
        … 9 more

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[INFO] ————————————————————————
[INFO] ————————————————————————
[INFO] Total time: 1:04.074s
[INFO] Finished at: Wed Mar 13 11:40:05 IST 2013
[INFO] Final Memory: 39M/295M
[INFO] ————————————————————————
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.
12.4:test (default-test) on project fusion-service: Execution default-test of go
al org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test failed: The forked
VM terminated without saying properly goodbye. VM crash or System.exit called ?
-> [Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions, please rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutio
[ERROR] After correcting the problems, you can resume the build with the command

[ERROR]   mvn <goals> -rf :fusion-service