That's for messaging not for remoting.

Andy

On Wed, Jun 29, 2016 at 11:33 AM, Marlow, Andrew <Andrew.Marlow@fisglobal.com> wrote:

The connectors section of the config file is:

        <subsystem xmlns="urn:jboss:domain:messaging:3.0">
            <hornetq-server>
                <security-enabled>false</security-enabled>
                <statistics-enabled>true</statistics-enabled>
                <journal-file-size>102400</journal-file-size>

                <connectors>
                    <http-connector name="http-connector" socket-binding="http">
                        <param key="http-upgrade-endpoint" value="http-acceptor"/>
                    </http-connector>
                    <http-connector name="http-connector-throughput" socket-binding="http">
                        <param key="http-upgrade-endpoint" value="http-acceptor-throughput"/>
                        <param key="batch-delay" value="50"/>
                    </http-connector>
                    <in-vm-connector name="in-vm" server-id="0"/>
                </connectors>

                <acceptors>
                    <http-acceptor http-listener="default" name="http-acceptor"/>
                    <http-acceptor http-listener="default" name="http-acceptor-throughput">
                        <param key="batch-delay" value="50"/>
                        <param key="direct-deliver" value="false"/>
                    </http-acceptor>
                    <in-vm-acceptor name="in-vm" server-id="0"/>
                </acceptors>

-----Original Message-----
From: wildfly-dev-bounces@lists.jboss.org [mailto:wildfly-dev-bounces@lists.jboss.org] On Behalf Of David M. Lloyd
Sent: 29 June 2016 18:15
To: wildfly-dev@lists.jboss.org
Subject: Re: [wildfly-dev] JBREM000200 error: XNI0000804: Received an invalid message length of 1195725856

This is just the socket bindings; it's the connectors that determine what the protocol is.

On 06/29/2016 12:07 PM, Marlow, Andrew wrote:
> Apologies for top-posting, I am forced to use LookOut!
>
> I never knew about HTTP Upgrade. I knew that wildfly multiplexed all
> the old jboss ports onto one http port but didn’t know this was how it was done.
>
> The client is most definately using http-remoting. I thought wildfly
> was as well, here is the end of the config file:
>
>      <socket-binding-group name="standard-sockets"
> default-interface="public"
> port-offset="${jboss.socket.binding.port-offset:0}">

[snip]


_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.

_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev