RE: [JBoss-user] Using RMI / JNDI over HTTPS

[Sebastian H. <seb...@sk...>]

Hi Jeremy,


> -----Original Message-----
> From: Jeremy Rempel [mailto:jr...@ec...]=20
> Sent: Monday, March 10, 2003 12:27 PM
> To: jbo...@li...
> Subject: [JBoss-user] Using RMI / JNDI over HTTPS
>=20
>=20
> I have recently modified my existing application to use JNDI=20
> / RMI over=20
> HTTPS as explained in the (non-free) JBoss Admin manual. I have port=20
> 8443 open on the server and thats what it references in my=20
> jndi.properties.
>=20
> It works on the same machine but when I try and run it through the=20
> internet it gives me this error :
>=20
> javax.naming.NamingException: Failed to retrieve Naming=20
> interface.  Root=20
> exception is java.net.SocketException: Connection reset by=20
> peer: connect
>=20
> Is there any additional steps I need to do to make JNDI / RMI=20
> work over=20
> HTTPS ?

Yes,

Check your:
deploy/http-invoker/META-INF/jboss-service.xml file:
And check whether your have an entry like this:

   <!-- Expose the Naming service interface via HTTP -->
   <mbean code=3D"org.jboss.invocation.http.server.HttpProxyFactory"
      name=3D"jboss:service=3Dinvoker,type=3Dhttp,target=3DNaming">
      <!-- The Naming service we are proxying -->
      <attribute name=3D"InvokerName">jboss:service=3DNaming</attribute>
      <!-- Compose the invoker URL from the cluster node address -->
      <attribute name=3D"InvokerURLPrefix">https://</attribute>
      <attribute
name=3D"InvokerURLSuffix">:8443/invoker/JMXInvokerServlet</attribute>
      <attribute name=3D"UseHostName">false</attribute>
      <attribute
name=3D"ExportedInterface">org.jnp.interfaces.Naming</attribute>
      <attribute name=3D"JndiName"></attribute>
   </mbean>

Now this is just for the naming interface you will also need to do this
for the other stuff, like EJB invoker service.
If you are using want to use HTTPS with JDK 1.3.x you might also have to
register the JSSE protocol handler with the VM before you can open the
connection.

Sebastian=20