<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><tt>WildFly upstream no longer uses
4447 port for remote communication. Undertow now supports
http-upgrade which means that the communication happens on the
http port which by default is 8080.</tt><tt><br>
</tt><tt><br>
</tt><tt>-Jaikiran</tt><tt><br>
</tt><tt>On Wednesday 17 July 2013 03:31 PM, Wolf-Dieter Fink
wrote:</tt><tt><br>
</tt></div>
<blockquote cite="mid:51E66B74.1090808@redhat.com" type="cite"><tt>I
try to run my quickstart (ejb-multi-server) with WildFly.
</tt><tt><br>
</tt><tt>Configuration and deployment work.
</tt><tt><br>
</tt>
<tt><br>
</tt><tt>But the (remote) EJB invocation failed. Neither
standalone nor client inside the server works.
</tt><tt><br>
</tt><tt>If I use an older WildFly pulled at the 07/11 (don't know
the exact commit) everything works fine.
</tt><tt><br>
</tt>
<tt><br>
</tt><tt>I retest with the ejb-remote QS, here the same issue.
</tt><tt><br>
</tt>
<tt><br>
</tt><tt>To avoid any maven issue I've used plain java command and
include the correct jboss-client.jar
</tt><tt><br>
</tt>
<tt><br>
</tt><tt>I've attached the logfiles from a working and non-working
attempt.
</tt><tt><br>
</tt><tt>The only difference I see is that the ejb-client library
is new (moved from 1.x => 2.x.Beta), remoting is unkown and
XNIO 3.1.0.CR3.
</tt><tt><br>
</tt>
<tt><br>
</tt><tt>- Wolf
</tt><tt><br>
</tt>
<tt><br>
</tt>
<tt><br>
</tt><tt><br>
</tt>
<fieldset class="mimeAttachmentHeader"></fieldset>
<tt><br>
</tt>
<pre wrap="">_______________________________________________
wildfly-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a>
</pre>
</blockquote>
<tt><br>
</tt>
</body>
</html>