[wildfly-dev] JBREM000200 error: XNI0000804: Received an invalid message length of 1195725856
David M. Lloyd
david.lloyd at redhat.com
Wed Jun 29 14:12:48 EDT 2016
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>
>
> -----Original Message-----
> From: wildfly-dev-bounces at lists.jboss.org
> <mailto:wildfly-dev-bounces at lists.jboss.org>
> [mailto: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 18:15
> To: wildfly-dev at lists.jboss.org <mailto:wildfly-dev at 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 at lists.jboss.org <mailto:wildfly-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.jboss.org_mailman_listinfo_wildfly-2Ddev&d=BQMFaQ&c=3BfiSO86x5iKjpl2b39jud9R1NrKYqPq2js90dwBswk&r=r8WgofSOL-7GXl-9C8d8UegYRA2PCrzVWlsJKTyAwJY&m=AL3vsANNamMHTm6l-fICaur1p-ih_yDj4AmhgiM-fb0&s=f3JPU-y40_bnocVu-_XM9Z0M8BEBM8Q2GSBt-ZSI9gE&e=>
>
>
>
>
> --
>
> Andrig (Andy) T. Miller
>
> Global Platform Director, Middleware
>
> Red Hat, Inc.
>
> _____________
> 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.
>
> _____________
> 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
--
- DML
More information about the wildfly-dev
mailing list