From what I see in the related JIRAs/Bugzillas/PRs, this should already be fixed in the Beta1 version you are using. Are you sure your client classpath is the using the new jboss-client.jar (or the equivalent new Maven co-ordinates)?
Yes it's picking up the new client jar, these are the product versions which come out :
11:16:13,607 INFO [xnio] XNIO Version 3.0.7.GA-redhat-1
11:16:13,607 INFO [nio] XNIO NIO Implementation Version 3.0.7.GA-redhat-1
11:16:13,607 INFO [remoting] JBoss Remoting version 3.2.15.GA-redhat-1
11:16:13,950 INFO [client] JBoss EJB Client version 1.0.17.Final-redhat-1
which are different than the versions I get when I swap the 6.1.0 Alpha client back in :
11:25:15,940 INFO [xnio] XNIO Version 3.0.7.GA
11:25:15,955 INFO [nio] XNIO NIO Implementation Version 3.0.7.GA
11:25:15,955 INFO [remoting] JBoss Remoting version 3.2.14.GA
11:25:16,345 INFO [client] JBoss EJB Client version 1.0.16.Final
Can you attach an application which reproduces this? By the way, I thought this was verified to be functional when you tested against a nightly snapshot? I am asking because, I want to figure out if we missed some commit or if this is something else.
Yes, we did do a build where this was working. You suggested we changed the following in our pom file :
1) Open the <JBoss AS source code home>/pom.xml in a text editor
2) Update the remote naming project version to 1.0.6.Final-SNAPSHOT. The correct line to update looks like:
... which we did, and the resulting client jar, which we built on 11 March, does not exhibit this problem.
I can certainly supply a test application, it isn't very big, just an ear and a jar, and if it would help I can also give you the client jar we built back in March. What's the best way to upload this to you ?
You can attach the application to this thread. When you hit reply, there's a "Use advanced editor" link on top right corner of the message editor window which will bring up the advanced editor. That advanced editor has a "Attach file" option which you can use.
Never mind, I just downloaded Beta1 and noticed that the remote naming module is at:
which means that the fix didn't make it to this version and will be available in next EAP 6.1 release.
OK that's great - thanks for clarifying that for us.