The original exceptin is misleading ;-)
Your are doing the JNDI lookup with HTTP because you want to pass through your firewall. This is ok. But then you are receiving the wrong stub (to use jboss terminology: you get the rmi invoker), which tries to call JBoss using RMI again. I think your firewall won't let you do this ;-)
Search the forum (and JBoss examples) for an invoker using rmi over ssl. This should do the trick using JBoss from a client behind a firewall in a performant manner and opening only one specific port on your firewall. I think this is even mentioned in the JBoss doco.
thank you for the answer,
but havn't I the same problem with external address? I found an example with ssl. This also use the RMPInvoker. Have I set there the external serveraddress? And when I set
there the address, what is with the servlets (form the
web-client), which also invoke the same bean? Get they the wrong adresse? They need the internal address, I think. Questions over questions....
And if I can set two different Invokers for one bean,which is selected then?
You don't have to mess around with any adress. You only need to configure an adress when you are looking for the InitialContext.
With SSL you are using a special RMI Invoker, the RMI over SSL, which needs one port for SSL, not one dynamic (and optional one object) port.
I really think the exception is kind of misleading.
You can access the same bean with different invokers (if configured like this) by using different JNDI names when you do the bean lookup. You can configure this name with the invoker configuration.