Hello,

is it possible to configure jboss to support access to beans with and without SSL in 
the same server ?
One Client may access the beans using SSL an other client may access without SSL.

I deploy the beans for the Client in 2 jar-files, one with JNDINames , the other 
configured for SSL and with JNDINames ssl/.

My jboss-service.xml configuration is:



   <!-- JAAS security manager and realm mapping -->
   
      
         org.jboss.security.plugins.JaasSecurityManager
      
   

  <!-- The SSL domain setup -->
  
    
       
    
    test.keystore
    passw
  



   <!-- RMI/JRMP invoker -->
   
      4444
      ${jboss.bind.address}
      <!--
      custom
      custom
      ssl-domain-name
      -->

      jboss:service=TransactionManager
   

  
    8443
    
      org.jboss.security.ssl.RMISSLClientSocketFactory
    
    
      org.jboss.security.ssl.RMISSLServerSocketFactory
    
    java:/jaas/RMI+SSL
    jboss.security:service=JaasSecurityDomain,domain=RMI+SSL
    jboss:service=TransactionManager
  



It seems to work.
How can I verify that SSL is really used ?

But during jboss shutdown the follwing exception occurs:

2004-09-15 13:25:06,203 INFO  [org.jboss.invocation.jrmp.server.JRMPInvoker] Stopping 
jboss:service=invoker,type=jrmp
2004-09-15 13:25:06,218 ERROR [org.jboss.invocation.jrmp.server.JRMPInvoker] Stopping 
failed
javax.naming.NameNotFoundException: jrmp not bound
  at org.jnp.server.NamingServer.getBinding(NamingServer.java:495)
  at org.jnp.server.NamingServer.getBinding(NamingServer.java:503)
  at org.jnp.server.NamingServer.unbind(NamingServer.java:228)
  at org.jnp.server.NamingServer.unbind(NamingServer.java:201)
  at org.jnp.server.NamingServer.unbind(NamingServer.java:201)
  at org.jnp.interfaces.NamingContext.unbind(NamingContext.java:673)
  at org.jnp.interfaces.NamingContext.unbind(NamingContext.java:661)
  at javax.naming.InitialContext.unbind(InitialContext.java:371)
  at org.jboss.invocation.jrmp.server.JRMPInvoker.stopService(JRMPInvoker.java:328)
  at org.jboss.invocation.jrmp.server.JRMPInvoker$1.stopService(JRMPInvoker.java:112)
  at org.jboss.system.ServiceMBeanSupport.stop(ServiceMBeanSupport.java:240)
  at org.jboss.invocation.jrmp.server.JRMPInvoker.stop(JRMPInvoker.java:571)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:324)
  at 
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
  at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)
  at $Proxy0.stop(Unknown Source)
  at org.jboss.system.ServiceController.stop(ServiceController.java:471)
  at sun.reflect.GeneratedMethodAccessor41.invoke(Unknown Source)
  at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:324)
  at 
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
  at $Proxy4.stop(Unknown Source)
  at org.jboss.deployment.SARDeployer.stop(SARDeployer.java:373)
  at org.jboss.deployment.MainDeployer.stop(MainDeployer.java:489)
  at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:472)
  at org.jboss.deployment.MainDeployer.shutdown(MainDeployer.java:359)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:324)
  at 
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
  at 
org.jboss.system.server.ServerImpl$ShutdownHook.shutdownDeployments(ServerImpl.java:849)
  at org.jboss.system.server.ServerImpl$ShutdownHook.shutdown(ServerImpl.java:824)
  at org.jboss.system.server.ServerImpl$ShutdownHook.run(ServerImpl.java:812)

What does this mean ?
I looked in the jboss sourcecode and found out that each JRMPInvoker binds "invokers/" 
+ InetAddress.getLocalHost().getHostName() + "/jrmp".
Is it not possible to configure more than one JRMPInvoker ?
When I look in the jmx-console I can see both JRMPInvoker configurations.

Any idea ?

Annegret


View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3848302#3848302

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3848302


-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to