[jboss-user] [Remoting] - Re: Setting codebase in jboss ejb3 application has no efffec

[ron.sigal@jboss.com]

Hi Emil,

Your question isn't related to Remoting, so I'm going to suggest you try the "Installation, Configuration & DEPLOYMENT" forum at http://www.jboss.com/index.html?module=bb&op=viewforum&f=61.

For what it's worth, I can point you to the $JBOSS/server/$CONFIG/conf/jboss-service.xml file, where you'll find the MBean configurations


  |    <!-- ==================================================================== -->
  |    <!-- Class Loading                                                        -->
  |    <!-- ==================================================================== -->
  | 
  |    <!-- A mini webserver used for dynamic and class and resource loading --> 
  |    <mbean code="org.jboss.web.WebService"
  |       name="jboss:service=WebService">
  |       <!-- The Bind address and Port -->
  |       <attribute name="BindAddress">${jboss.bind.address}</attribute>      
  |       <attribute name="Port">8083</attribute>
  |       <!--  The address to use for the host portion of the RMI codebase URL -->
  |       <attribute name="Host">${java.rmi.server.hostname}</attribute>
  |       <!-- Should non-EJB .class files be downloadable -->
  |       <attribute name="DownloadServerClasses">true</attribute>
  |       <!-- Should resources other than .class files be downloadable. Both
  |          DownloadServerClasses and DownloadResources must be true for resources
  |          to be downloadable. This is false by default because its generally a
  |          bad idea as server configuration files that container security
  |          information can be accessed.
  |        -->
  |       <attribute name="DownloadResources">false</attribute>
  | 
  |       <!-- Use the default thread pool for dynamic class loading -->
  |       <depends optional-attribute-name="ThreadPool"
  |          proxy-type="attribute">jboss.system:service=ThreadPool</depends>
  |    </mbean>
  | 
  |    <!-- ==================================================================== -->
  |    <!-- JBoss RMI Classloader - only install when available                  -->
  |    <!-- ==================================================================== -->
  |    <mbean code="org.jboss.util.property.jmx.SystemPropertyClassValue"
  |       name="jboss.rmi:type=RMIClassLoader">
  |       <attribute name="Property">java.rmi.server.RMIClassLoaderSpi</attribute>
  |       <attribute name="ClassName">org.jboss.system.JBossRMIClassLoader</attribute>
  |    </mbean>
  | 

Good luck, and if you solve your problem, it would be great if you could come back and post the solution.

-Ron

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

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