Problem remoting connection with wildfly 10.0.0.CR4

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Problem remoting connection with wildfly 10.0.0.CR4

Thomas Frühbeck
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
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Problem remoting connection with wildfly 10.0.0.CR4

Eduardo Sant´Ana da Silva
Maybe this could help:



2015-11-24 20:33 GMT-02:00 Thomas Frühbeck <[hidden email]>:
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
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev



--
__________________________
Eduardo Sant'Ana da Silva - Dr.
Pesquisador / Consultor de TI


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Problem remoting connection with wildfly 10.0.0.CR4

Thomas Frühbeck
you nailed it, thanks!
unfortunate though :-/

Am 25.11.2015 um 01:30 schrieb Eduardo Sant´Ana da Silva:
Maybe this could help:



2015-11-24 20:33 GMT-02:00 Thomas Frühbeck <[hidden email]>:
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
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev



--
__________________________
Eduardo Sant'Ana da Silva - Dr.
Pesquisador / Consultor de TI



_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Problem remoting connection with wildfly 10.0.0.CR4

Eduardo Sant´Ana da Silva
Could you send your client pom.xml?

Thx

2015-11-24 22:34 GMT-02:00 Thomas Frühbeck <[hidden email]>:
you nailed it, thanks!
unfortunate though :-/


Am 25.11.2015 um 01:30 schrieb Eduardo Sant´Ana da Silva:
Maybe this could help:



2015-11-24 20:33 GMT-02:00 Thomas Frühbeck <[hidden email]>:
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
[hidden email]
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
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Problem remoting connection with wildfly 10.0.0.CR4

Eduardo Sant´Ana da Silva
In reply to this post by Thomas Frühbeck
Jason G. commented out XNIO-222 to see the spec about the content-lenght.

I found this:


   Each SIP message MUST be carried within a single WebSocket message,
   and a WebSocket message MUST NOT contain more than one SIP message.
   Because the WebSocket transport preserves message boundaries, the use
   of the Content-Length header in SIP messages is not necessary when
   they are transported using the WebSocket subprotocol.

      This simplifies the parsing of SIP messages for both clients and
      servers.  There is no need to establish message boundaries using
      Content-Length headers between messages.  Other SIP transports,
      such as UDP and the Stream Control Transmission Protocol (SCTP)
      [RFC4168], also provide this benefit.

It was fixed, so the previous problem it is not present anymore:

This was replaced:

335         private void handleUpgrade(final HttpUpgradeParser parser) {
336             final String contentLength = parser.getHeaders().get("content-length");
337             if (!"0".equals(contentLength)) {
338                 future.setException(new IOException("For now upgrade responses must have a content length of zero."));
339                 return;
340             }

by that:
       private void handleUpgrade(final HttpUpgradeParser parser) {
            Map<String, String> simpleHeaders = new HashMap<>();
            for(Map.Entry<String, List<String>> e : parser.getHeaders().entrySet()) {
                simpleHeaders.put(e.getKey(), e.getValue().get(0));
            }
            final String contentLength = simpleHeaders.get("content-length");
            if (contentLength != null) {
                if (!"0".equals(contentLength)) {
                    future.setException(new IOException("Upgrade responses must have a content length of zero."));
                    return;
                }
}

Seems to me that the content length should not be informed in your case, or if it is in the header the value should be 0 to the upgrade operation.

Thx
Eduardo Sant'Ana da Silva


On Nov 24, 2015, at 10:34 PM, Thomas Frühbeck <[hidden email]> wrote:

you nailed it, thanks!
unfortunate though :-/

Am 25.11.2015 um 01:30 schrieb Eduardo Sant´Ana da Silva:
Maybe this could help:



2015-11-24 20:33 GMT-02:00 Thomas Frühbeck <[hidden email]>:
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
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev



--
__________________________
Eduardo Sant'Ana da Silva - Dr.
Pesquisador / Consultor de TI




_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Problem remoting connection with wildfly 10.0.0.CR4

Eduardo Sant´Ana da Silva
In reply to this post by Thomas Frühbeck
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 <[hidden email]> wrote:

you nailed it, thanks!
unfortunate though :-/

Am 25.11.2015 um 01:30 schrieb Eduardo Sant´Ana da Silva:
Maybe this could help:



2015-11-24 20:33 GMT-02:00 Thomas Frühbeck <[hidden email]>:
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
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev



--
__________________________
Eduardo Sant'Ana da Silva - Dr.
Pesquisador / Consultor de TI




_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Problem remoting connection with wildfly 10.0.0.CR4

Thomas Frühbeck
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 <[hidden email]> wrote:

you nailed it, thanks!
unfortunate though :-/

Am 25.11.2015 um 01:30 schrieb Eduardo Sant´Ana da Silva:
Maybe this could help:



2015-11-24 20:33 GMT-02:00 Thomas Frühbeck <[hidden email]>:
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
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev



--
__________________________
Eduardo Sant'Ana da Silva - Dr.
Pesquisador / Consultor de TI





_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Problem remoting connection with wildfly 10.0.0.CR4

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 <[hidden email]>:
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 <[hidden email][hidden email]> wrote:

you nailed it, thanks!
unfortunate though :-/

Am 25.11.2015 um 01:30 schrieb Eduardo Sant´Ana da Silva:
Maybe this could help:



2015-11-24 20:33 GMT-02:00 Thomas Frühbeck <[hidden email][hidden email]>:
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
[hidden email]
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
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Problem remoting connection with wildfly 10.0.0.CR4

Thomas Frühbeck
Eduardo, thank you very much for your support, evidently I did not look close enough :-)
Quickest fix was to move dependency of XNIO _before_ jboss-client.
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 <[hidden email]>:
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 <[hidden email]> wrote:

you nailed it, thanks!
unfortunate though :-/

Am 25.11.2015 um 01:30 schrieb Eduardo Sant´Ana da Silva:
Maybe this could help:



2015-11-24 20:33 GMT-02:00 Thomas Frühbeck <[hidden email]>:
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
[hidden email]
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
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Problem remoting connection with wildfly 10.0.0.CR4

Ladislav Thon
> 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 <[hidden email]
>> <mailto:[hidden email]>>:
>>
>>     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 <[hidden email]
>>>     <mailto:[hidden email]>> 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:[hidden email]>[hidden email]>:
>>>>>
>>>>>         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
>>>>>         [hidden email]
>>>>>         <mailto:[hidden email]>
>>>>>         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
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Problem remoting connection with wildfly 10.0.0.CR4

Thomas Frühbeck
absolutely right!

  I thougt jboss-client is the all-in-one jar like in
<JBOSS_HOME>/bin/client/jboss-client.jar  which evidently contains XNIO:

jar tfv /work/java/wildfly-10.0.0.CR4/bin/client/jboss-client.jar |grep xnio
      0 Fri Oct 23 13:49:00 CEST 2015 org/xnio/

.. but I didnt check first place :-/

Exclusion works perfectly here though, thanks for notice!
          <dependency>
             <groupId>jboss</groupId>
             <artifactId>jboss-client</artifactId>
             <version>4.0.2</version>
             <exclusions>
                <exclusion>
                   <groupId>org.jboss.xnio</groupId>
                   <artifactId>xnio-nio</artifactId>
                </exclusion>
             </exclusions>

Regards,
thomas

Am 26.11.2015 um 08:02 schrieb Ladislav Thon:

>> 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 <[hidden email]
>>> <mailto:[hidden email]>>:
>>>
>>>      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 <[hidden email]
>>>>      <mailto:[hidden email]>> 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:[hidden email]>[hidden email]>:
>>>>>>
>>>>>>          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
>>>>>>          [hidden email]
>>>>>>          <mailto:[hidden email]>
>>>>>>          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
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev