<div dir="ltr">Other option would be that you are just using old version of client libs, <br>they should be updated to match ones used in WildFly<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 29, 2016 at 5:15 PM, David M. Lloyd <span dir="ltr"><<a href="mailto:david.lloyd@redhat.com" target="_blank">david.lloyd@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">JBoss Remoting uses a feature called "HTTP Upgrade", which basically<br>
allows a client to connect to an HTTP port and then send a special HTTP<br>
request which allows an "upgrade" to another arbitrary protocol. Later<br>
versions of WildFly use this feature by default to reduce the count of<br>
bound ports.<br>
<br>
What is probably happening is that you are connecting to a port that has<br>
a plain Remoting listener on it, but the client is using "http-remoting"<br>
which means "JBoss Remoting over HTTP Upgrade". So the client sends an<br>
HTTP request, but the server interprets it as garbage because it is<br>
expecting a Remoting framed packet instead.<br>
<br>
The fix is to either change the client from "http-remoting" to just<br>
"remoting", or to change your server to use HTTP upgrade instead.<br>
Information on this should be in the user docs.<br>
<div><div class="h5"><br>
On 06/29/2016 10:08 AM, Marlow, Andrew wrote:<br>
> Hello everyone,<br>
><br>
> This is an appeal for help to resolve the error JBREM000200 that I get<br>
> when a process connects to wildfly to do some JMS work. Details follow:-<br>
><br>
> I am trying to switch from JBoss-as-7.1.1.Final to Wildfly 9.0.1.Final.<br>
> My project runs on Microsoft Windows and Red Hat Linux (RHEL 5.11). I am<br>
> using java jdk 1.8.0_60. The switch to wildfly worked fine on Windows,<br>
> once I found out what the config file changes were, especially the<br>
> switch from remote port 4777 to undertow http port 8080. However, on<br>
> linux the wildfly server get an error as soon as one of my processes<br>
> connects to it. The wildfly log is not very busy. Wildfly starts with<br>
> not much logged then I get a one line error report for every connection<br>
> attempt:<br>
><br>
> 2016-06-29 15:09:09,555 ERROR [org.jboss.remoting.remote.connection]<br>
> (default I/O-6) JBREM000200: Remote connection failed:<br>
> java.io.IOException: XNIO000804: Received an invalid message length of<br>
> 1195725856<br>
><br>
> The log of the process that connects contains a bit more detail:<br>
><br>
> Error: NamingException detected during EndPointFactory JMS Server queue<br>
> initialisation: Failed to connect to any server. Servers tried:<br>
> [http-remoting://<myIpAddress>:8180 (java.io.EOFException: XNIO000812:<br>
> Connection closed unexpectedly)] : Failed to connect to any server.<br>
> Servers tried: [http-remoting://<myIpAddress>:8180<br>
> (java.io.EOFException: XNIO000812: Connection closed unexpectedly)]<br>
> Cause unknown. : Stack trace: javax.naming.CommunicationException:<br>
> Failed to connect to any server. Servers tried:<br>
> [http-remoting://<myIpAddress>:8180 (java.io.EOFException: XNIO000812:<br>
> Connection closed unexpectedly)]<br>
><br>
> at<br>
> org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:244)<br>
><br>
> at<br>
> org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:149)<br>
><br>
> at<br>
> org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:130)<br>
><br>
> at<br>
> org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272)<br>
><br>
> at<br>
> org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104)<br>
><br>
> at<br>
> org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93)<br>
><br>
> at<br>
> org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146)<br>
><br>
> at javax.naming.InitialContext.lookup(InitialContext.java:417)<br>
><br>
> I am using port 8180 because port 8080 is already taken (jenkins).<br>
><br>
> I have googled for this causes of this error. I found several hits that<br>
> suggested various “solutions”. I tried them all. None of them worked.<br>
> Here’s what I have tried:<br>
><br>
> ·I ensured that no other process was using 8180. Some wildfly users have<br>
> been in environments where a rogue process was writing to the undertow<br>
> port. I used netstat in a loop to monitor any process using 8180. It<br>
> just showed wildfly listening on it until my app made the connection<br>
> attempt. Then it showed my app as well. No other apps.<br>
><br>
> ·I tried using the port number offset feature. This used different port<br>
> numbers but the problem remained.<br>
><br>
> ·xml config, disable section security-realm-name=”ApplicationRealm”.<br>
> This made no difference.<br>
><br>
> ·In the interfaces section, interface name=”public” replace inet-address<br>
> value=${jboss.bind.address:0.0.0.0} with value =<br>
> “<myIpAddressAsADottedQuad>”. This did make a difference – I lost<br>
> connectivity completely. This was fixed by me changing localhost in my<br>
> remoting URL to the ip address as a dotted quad. Then I got the invalid<br>
> message length error back.<br>
><br>
> This seems like a very deep mystery to me. It might force me to abandon<br>
> using wildfly on linux and say that it is only supported on windows. Any<br>
> help will be much appreciated.<br>
><br>
> Regards,<br>
><br>
> Andrew Marlow.<br>
><br>
> <a href="http://www.andrewpetermarlow.co.uk" rel="noreferrer" target="_blank">http://www.andrewpetermarlow.co.uk</a><br>
><br>
> _____________<br>
> The information contained in this message is proprietary and/or<br>
> confidential. If you are not the intended recipient, please: (i) delete<br>
> the message and all copies; (ii) do not disclose, distribute or use the<br>
> message in any manner; and (iii) notify the sender immediately. In<br>
> addition, please be aware that any message addressed to our domain is<br>
> subject to archiving and review by persons other than the intended<br>
> recipient. Thank you.<br>
><br>
><br>
</div></div>> _______________________________________________<br>
> wildfly-dev mailing list<br>
> <a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
><br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
- DML<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></font></span></blockquote></div><br></div>