EJB3 over SSL in NAT environment (JBoss 4.0.5)

[clnw8346]

Has anyone been able to configure SSL for EJB3 in a NAT environment?
I have followed the lower 2 posts and have successfully configured a server for EJB3 over SSL and configured regular EJB3 in a NAT environment, but not combined.

(Problems with bean-lookup in NAT environment, EJB3RC5)
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=79325

(stateless-ssl-invoker for EJB3)
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=74475

My EJB has the following annotations:

@RemoteBindings({
 @RemoteBinding(clientBindUrl="sslsocket://0.0.0.0:3843", jndiBinding="ejb/TestBean/ssl"),
 @RemoteBinding(jndiBinding="ejb/TestBean/remote")
 })
 public class TestBean implements TestInterface
 {
 ...
 }

The regular remote call, "ejb/TestBean/remote", works in NAT if I setup the ej3 deployer with a remoting configuration (similar to the ssl version) and specify a "clientConnectAddress"

An example here:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=63821

Since I have to specify a remote binding annotation to bind "ejb/TestBean/ssl" to the ssl socket, the clientConnectAddress in the service file is never used, it is overridden by the annotated value.

Any ideas would be greatly appreciated. The server version used is 4.0.5 prod.

[ovidiu.feodorov]

For reference, in case anyone else is having the same problem.

The misbehavior of EJB3 in a NAT/SSL environment is caused by a combination of two bugs:

http://jira.jboss.com/jira/browse/EJBTHREE-1190
http://jira.jboss.com/jira/browse/EJBTHREE-1191

The bugs have been fixed around Feb 16 2008 (I don't know the SVN tags, the EJB3 team may add clarifications here). The patch have been tested and it works.

[bdecoste]

SVN tag is EJB3_RC9_Patch_1_EJBTHREE1-1091

[bdecoste]

Sorry, EJB3_RC9_Patch_1_EJBTHREE1-1191

[ofridler]

The subject here and the 2 jira issues mentioned above on jira.jboss.com specify the bug fix is applicable to versions JBoss4.0.5-GA, JBoss-4.2.2-GA and JBoss-5.0.0-Beta3.

How can I verify the applicability of this patch to JBoss4.2.0-GA?

Any idea would be highly appreciated