EAP 6.1.0 Beta - Using home interfaces in different threads

[millsp]

Hi

We noticed this problem in earlier releases of 7 and also in EAP 6.1.0 Alpha.  It still seems to be present in 6.1.0 Beta, this is the version we're using :

JBAS015899: JBoss EAP 6.1.0.Beta1 (AS 7.2.0.Final-redhat-4) starting

The essence is that when a client program looks up EJBs using Remoting, it can't use initial contexts or home interfaces in a different thread than the thread they were acquired in.  There is some correspondence at :

https://community.jboss.org/thread/222724

https://community.jboss.org/thread/221913

https://issues.jboss.org/browse/JBEAP-4

My question is, can you tell me which release of EAP 6.1.0 is going to have the fix for this ?

Thanks -

Phil

[jaikiran]

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)?

[millsp]

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

[jaikiran]

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.

[millsp]

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:

<version.org.jboss.remote-naming>1.0.6.Final-SNAPSHOT</version.org.jboss.remote-naming>

... 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 ?

[jaikiran]

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.

[jaikiran]

Never mind, I just downloaded Beta1 and noticed that the remote naming module is at:

<resource-root path="jboss-remote-naming-1.0.5.Final-redhat-1.jar"/>

which means that the fix didn't make it to this version and will be available in next EAP 6.1 release.

[millsp]

OK that's great - thanks for clarifying that for us.