[wildfly-dev] Problem remoting connection with wildfly 10.0.0.CR4

Wed Nov 25 17:58:13 EST 2015

thanks for the input, yet I am using following artifacts:

          <dependency>
             <groupId>org.jboss.xnio</groupId>
             <artifactId>xnio-nio</artifactId>
             <version>3.3.2.Final</version>
          </dependency>

The full source is available at: 
https://github.com/shadogray/securefs/tree/master/securefs-master/securefs-client-test 

And, just to make sure, the full command line reads: 
xnio-nio-3.3.2.Final.jar

[DEBUG] Executing command line: [java, -classpath,
/raid/home/thomas/workspace-sec/securefs/securefs-master/securefs-client-test/target/classes:\
/home/thomas/.m2/repository/at/tfr/securefs/securefs-client/1.1.0-SNAPSHOT/securefs-client-1.1.0-SNAPSHOT.jar:\
/home/thomas/.m2/repository/at/tfr/securefs/securefs-api/1.1.0-SNAPSHOT/securefs-api-1.1.0-SNAPSHOT.jar:\
/home/thomas/.m2/repository/org/jboss/logging/jboss-logging/3.1.4.GA/jboss-logging-3.1.4.GA.jar:\
/home/thomas/.m2/repository/commons-io/commons-io/2.4/commons-io-2.4.jar:\
/home/thomas/.m2/repository/commons-lang/commons-lang/2.6/commons-lang-2.6.jar:\
/home/thomas/.m2/repository/javax/javaee-api/7.0/javaee-api-7.0.jar:\
/home/thomas/.m2/repository/com/sun/mail/javax.mail/1.5.0/javax.mail-1.5.0.jar:\
/home/thomas/.m2/repository/javax/activation/activation/1.1/activation-1.1.jar:\
/home/thomas/.m2/repository/jboss/jboss-client/4.0.2/jboss-client-4.0.2.jar:\
/home/thomas/.m2/repository/org/jboss/jboss-remote-naming/2.0.4.Final/jboss-remote-naming-2.0.4.Final.jar:\
/home/thomas/.m2/repository/org/jboss/jboss-ejb-client/2.0.0.Final/jboss-ejb-client-2.0.0.Final.jar:\
/home/thomas/.m2/repository/org/jboss/marshalling/jboss-marshalling/1.4.3.Final/jboss-marshalling-1.4.3.Final.jar:\
/home/thomas/.m2/repository/org/jboss/marshalling/jboss-marshalling-river/1.4.3.Final/jboss-marshalling-river-1.4.3.Final.jar:\
/home/thomas/.m2/repository/org/jboss/xnio/xnio-api/3.2.0.Final/xnio-api-3.2.0.Final.jar:\
/home/thomas/.m2/repository/org/jboss/remoting/jboss-remoting/4.0.0.Final/jboss-remoting-4.0.0.Final.jar:\
/home/thomas/.m2/repository/org/jboss/sasl/jboss-sasl/1.0.4.Final/jboss-sasl-1.0.4.Final.jar:\
/home/thomas/.m2/repository/commons-cli/commons-cli/1.3.1/commons-cli-1.3.1.jar:\
/home/thomas/.m2/repository/org/jboss/xnio/xnio-nio/3.3.2.Final/xnio-nio-3.3.2.Final.jar:\
/home/thomas/.m2/repository/joda-time/joda-time/2.9/joda-time-2.9.jar, \
at.tfr.securefs.client.SecurefsClient, -b, 
sec:///raid/home/thomas/workspace-sec/securefs/securefs-master/securefs-client-test/target/, 
-a, false, -t, 10, -f, data/test/test.txt,data/test/test_main.txt]

I am really looking forward to Wilfly 10.0.0 - especially clusterd 
deployment,  and  would appreciate to find anything blocking early.

Am 25.11.2015 um 02:14 schrieb Eduardo Sant'Ana da Silva:
> In my opinion, you should upgrade your client xnio version to one 
> later or equals to 3.2.1.Final.
>
>
> On Nov 24, 2015, at 10:34 PM, Thomas Frühbeck <fruehbeck at aon.at 
> <mailto:fruehbeck at aon.at>> wrote:
>
>> you nailed it, thanks!
>> unfortunate though :-/
>>
>> Am 25.11.2015 um 01:30 schrieb Eduardo Sant´Ana da Silva:
>>> Maybe this could help:
>>>
>>> https://issues.jboss.org/browse/XNIO-222
>>>
>>>
>>> 2015-11-24 20:33 GMT-02:00 Thomas Frühbeck <fruehbeck at aon.at 
>>> <mailto:fruehbeck at aon.at>>:
>>>
>>>     Hi,
>>>     I wanted to experiment with Wildfly 10.0.0.CR4 and Remoting and
>>>     got the
>>>     followin error on client side. I know, that my client works
>>>     perfectly
>>>     with 9.0.2.Final.
>>>     Can you guide me to the relevant changes, is this a known problem?
>>>
>>>     WARN: Could not register a EJB receiver for connection to
>>>     localhost:8080
>>>     java.lang.RuntimeException: java.io.IOException: For now upgrade
>>>     responses must have a content length of zero.
>>>              at
>>>     org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:92)
>>>              at
>>>     org.jboss.ejb.client.remoting.ConnectionPool.getConnection(ConnectionPool.java:77)
>>>              at
>>>     org.jboss.ejb.client.remoting.RemotingConnectionManager.getConnection(RemotingConnectionManager.java:51)
>>>              at
>>>     org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.setupEJBReceivers(ConfigBasedEJBClientContextSelector.java:155)
>>>              at
>>>     org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.getCurrent(ConfigBasedEJBClientContextSelector.java:115)
>>>              at
>>>     org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.getCurrent(ConfigBasedEJBClientContextSelector.java:47)
>>>              at
>>>     org.jboss.ejb.client.EJBClientContext.getCurrent(EJBClientContext.java:271)
>>>              at
>>>     org.jboss.ejb.client.EJBClientContext.requireCurrent(EJBClientContext.java:281)
>>>              at
>>>     org.jboss.ejb.client.EJBClient.createSession(EJBClient.java:200)
>>>              at
>>>     org.jboss.ejb.client.naming.ejb.EjbNamingContext.doCreateProxy(EjbNamingContext.java:216)
>>>              at
>>>     org.jboss.ejb.client.naming.ejb.EjbNamingContext.createEjbProxy(EjbNamingContext.java:193)
>>>              at
>>>     org.jboss.ejb.client.naming.ejb.EjbNamingContext.lookup(EjbNamingContext.java:176)
>>>              at
>>>     javax.naming.InitialContext.lookup(InitialContext.java:417)
>>>
>>>     Thanks,
>>>     Thomas
>>>     _______________________________________________
>>>     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
>>>
>>>
>>>
>>>
>>> -- 
>>> __________________________
>>> Eduardo Sant'Ana da Silva - Dr.
>>> Pesquisador / Consultor de TI
>>>
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20151125/80dec425/attachment-0001.html 