[wildfly-dev] Problem remoting connection with wildfly 10.0.0.CR4
Ladislav Thon
lthon at redhat.com
Thu Nov 26 02:02:25 EST 2015
> Quickest fix was to move dependency of XNIO _before_ jboss-client.
Or use a dependency exclusion. I think it's more clear, personally.
LT
> That settles it, best regards,
> thomas
>
> Am 26.11.2015 um 00:29 schrieb Eduardo Sant´Ana da Silva:
>> I've made the deployment of your application and I've got the same error.
>>
>>
>> You can see that the log of your test contains the XNIO version...
>>
>> -------------------------------------------------------
>>
>> T E S T S
>>
>> -------------------------------------------------------
>>
>> Running at.tfr.securefs.client.TestFileSystem
>>
>> Nov 25, 2015 9:18:47 PM org.xnio.Xnio <clinit>
>>
>> INFO: XNIO version 3.2.0.Final
>>
>> Nov 25, 2015 9:18:48 PM org.xnio.nio.NioXnio <clinit>
>>
>> INFO: XNIO NIO Implementation Version 3.3.2.Final
>>
>> Nov 25, 2015 9:18:48 PM org.jboss.remoting3.EndpointImpl <clinit>
>>
>> INFO: JBoss Remoting version 4.0.0.Final
>>
>> Nov 25, 2015 9:18:49 PM org.jboss.ejb.client.EJBClient <clinit>
>>
>> INFO: JBoss EJB Client version 2.0.0.Final
>>
>> Nov 25, 2015 9:18:51 PM
>> org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector
>> setupEJBReceivers
>>
>> 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.
>>
>>
>>
>> .m2/repository/./org/jboss/jboss-ejb-client/2.1.3.Final/jboss-ejb-client-2.1.3.Final.pom
>>
>>
>> Here is the problem, the latest version of the jboss-ejb-client (at
>> least what I have here) is using a xnio version that does not contain
>> the fix:
>>
>> <version.org.jboss.xnio>3.2.0.Final</version.org.jboss.xnio>
>>
>>
>>
>> 2015-11-25 20:58 GMT-02:00 Thomas Frühbeck <fruehbeck at aon.at
>> <mailto:fruehbeck at aon.at>>:
>>
>> 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>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
>> <http://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
>>>>> <<mailto:fruehbeck at aon.at>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
>>>>>
>>>>
>>>
>>
>>
>>
>>
>> --
>> __________________________
>> Eduardo Sant'Ana da Silva - Dr.
>> Pesquisador / Consultor de TI
>>
>
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
More information about the wildfly-dev
mailing list