[wildfly-dev] JBREM000200 error: XNI0000804: Received an invalid message length of 1195725856

[Marlow, Andrew]

Thankyou to David for identifying the problem. It is indeed a mystery why this works on windows. Never mind, once I've got the config working on linux I will try the config on windows. If Windows continues to work then that will be my new config file.

Now I just need to know how to change the config. Sorry I'm being a bit slow here but I don't quite see how to say that I want http-remoting instead of remoting. When I change "remoting" to "http-remoting" in the 
socket-binding-group section wildfly complains that it doesn't like it. The error is:-

19:23:43,096 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
    ("subsystem" => "remoting"),
    ("connector" => "remoting-connector")
]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.remoting-connector is missing [jboss.binding.remoting]"]}

Maybe I need to add something to my global modules list. Here is what it is right now:

      <global-modules>
                <module name="org.apache.log4j" slot="main"/>
                <module name="org.jboss.as.jmx" slot="main"/>
                <module name="org.jboss.as.naming" slot="main"/>
                <module name="org.jboss.msc" slot="main"/>
                <module name="org.jboss.remote-naming" slot="main"/>
                <module name="org.jboss.logging" slot="main"/>
                <module name="org.jboss.xnio" slot="main"/>
                <module name="org.jboss.xnio.nio" slot="main"/>
                <module name="org.jboss.remoting3" slot="main"/>
                <module name="org.jboss.remoting3.remoting-jmx" slot="main"/>
                <module name="org.jboss.marshalling" slot="main"/>
                <module name="org.jboss.marshalling.river" slot="main"/>
                <module name="org.jboss.sasl" slot="main"/>
                <module name="javax.jms.api" slot="main"/>
                <module name="org.hornetq" slot="main"/>
            </global-modules>

Please note: I am reluctant to post the entire config because the project is proprietary and contains proprietary bits.

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

So in this case your "connector" is using the regular Remoting protocol and it's using the "remoting" socket binding, which you have defined as port 8180.  Then you connect with http-remoting and it blows up.

If you want to connect with http-remoting then you need to make sure that your http-connector is referencing the connector which is listening on the port you're connecting to.

On 06/29/2016 12:41 PM, Marlow, Andrew wrote:
> Ah yes, so it is. How about this:
>
>         <subsystem xmlns="urn:jboss:domain:remoting:3.0">
>
>              <endpoint worker="default"/>
>
>              <connector name="remoting-connector"
> socket-binding="remoting"/>
>
>              <http-connector name="http-remoting-connector"
> connector-ref="default"/>
>
>          </subsystem>
>
> *From:*Andrig Miller [mailto:anmiller at redhat.com]
> *Sent:* 29 June 2016 18:38
> *To:* Marlow, Andrew <Andrew.Marlow at fisglobal.com>
> *Cc:* wildfly-dev <wildfly-dev at lists.jboss.org>
> *Subject:* Re: [wildfly-dev] JBREM000200 error: XNI0000804: Received 
> an invalid message length of 1195725856
>
> That's for messaging not for remoting.
>
> Andy
>
> On Wed, Jun 29, 2016 at 11:33 AM, Marlow, Andrew 
> <Andrew.Marlow at fisglobal.com <mailto:Andrew.Marlow at 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>

[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.