Wildfly 8

How to use JConsole (link of source)

JConsole now has the ability to dump to the current working directory.

1. Connect to your JMX enabled instance
2. Navigate to com.sun.management >HotspotDiagnostic >Operations
3. Fill in p0 to name the Heap Dump (please see the related errors you can have)
4. press the heapDump button

JConsole | java.io.IOException: File exists or Unable to invoke invoke(), status=WAITING

JConsole | java.io.IOException: Unable to invoke invoke(), status=WAITING

Normally this is related to the default path you give and if you have permissions to create the pretended file. Please give a correct file path and try again.

Example:

If you have the Wildfly running on Solarias just put a file path to the log folder like:

><full path>/standalone/log/test.hprof

Other problems related go to this link

Jboss7 to Wildfly 8 - What has changed? from Jean Pereira

Connection terminated as request was larger than 10485760?

Just had for example:

<http-listener name="default" socket-binding="http" max-post-size="104857600"/>

on 

<subsystem xmlns="urn:jboss:domain:undertow:1.2">
            <buffer-cache name="default"/>
            <server name="default-server">
                <http-listener name="default" socket-binding="http" max-post-size="104857600"/>
                <https-listener name="https" socket-binding="https" security-realm="ssl-realm"/>
                <host name="default-host" alias="localhost">
                    <location name="/" handler="welcome-content"/>
                    <filter-ref name="server-header"/>
                    <filter-ref name="x-powered-by-header"/>
                </host>
            </server>
            <servlet-container name="default">
                <jsp-config/>
                <websockets/>
            </servlet-container>
            <handlers>
                <file name="welcome-content" path="${jboss.home.dir}/welcome-content"/>
            </handlers>
            <filters>
                <response-header name="server-header" header-name="Server" header-value="WildFly/8"/>
                <response-header name="x-powered-by-header" header-name="X-Powered-By" header-value="Undertow/1"/>
            </filters>
        </subsystem>

This example is allow POST with 100 megabytes size.

java.lang.RuntimeException: javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms

Caused by: java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling...combination for invocation context

Normally this exceptions are related to the security-realm. It's enabled for the subsystem remoting (see standalone*.xml or domain.xml) by default. 

You have two options:

- Add the user using the command bin/add-user.sh (or.bat) and add remote.connection.default.username/remote.connection.default.password to client properties;

- Remove the attribute security-realm in the configuration

  Before

        <subsystem xmlns="urn:jboss:domain:remoting:2.0">
            <endpoint worker="default"/>
            <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/>
        </subsystem>

  After
        <subsystem xmlns="urn:jboss:domain:remoting:2.0">            
           <endpoint worker="default"/>            
           <http-connector name="http-remoting-connector" connector-ref="default"/>      
        </subsystem>

see more about this here!