Hi,
We are trying to use an external RMI (on the localhost) for our connector but it will not work
 
the error we recieve is
 
Using OPENJMS_HOME: /home/zaelld/openjms
Using JAVA_HOME:    /usr/java/
OpenJMS 0.7.7-beta-1
The OpenJMS Group. (C) 1999-2007. All rights reserved.
http://openjms.sourceforge.net
org.exolab.jms.server.ServerException: org.exolab.jms.server.ServerException: java.rmi.server.ExportException: Failed to accept
connections on URI: rmi://myhost:1095/; nested exception is:
        org.exolab.jms.net.connector.ResourceException: Failed to bind connection factory
        at org.exolab.jms.net.orb.DefaultORB.accept(DefaultORB.java:458)
        at org.exolab.jms.net.orb.AbstractORB.doExport(AbstractORB.java:450)
        at org.exolab.jms.net.orb.AbstractORB.exportObject(AbstractORB.java:296)
        at org.exolab.jms.net.orb.AbstractORB.exportObject(AbstractORB.java:258)
        at org.exolab.jms.net.orb.RegistryService.<init>(RegistryService.java:82)
        at org.exolab.jms.net.orb.DefaultORB.getRegistry(DefaultORB.java:258)
        at org.exolab.jms.server.net.RemoteServerConnector.init(RemoteServerConnector.java:208)
        at org.exolab.jms.server.ConnectorService.initConnector(ConnectorService.java:258)
        at org.exolab.jms.server.ConnectorService.initConnectors(ConnectorService.java:196)
        at org.exolab.jms.server.ConnectorService.doStart(ConnectorService.java:164)
        at org.exolab.jms.service.Service.start(Service.java:97)
        at org.exolab.jms.service.ServiceManager.doStart(ServiceManager.java:176)
        at org.exolab.jms.service.Service.start(Service.java:97)
        at org.exolab.jms.server.JmsServer.init(JmsServer.java:146)
        at org.exolab.jms.server.JmsServer.main(JmsServer.java:178)
Caused by: org.exolab.jms.net.connector.ResourceException: Failed to bind connection factory
        at org.exolab.jms.net.rmi.RegistryHelper.bind(RegistryHelper.java:97)
        at org.exolab.jms.net.rmi.RMIManagedConnectionAcceptor.accept(RMIManagedConnectionAcceptor.java:164)
        at org.exolab.jms.net.connector.AbstractConnectionManager.accept(AbstractConnectionManager.java:160)
        at org.exolab.jms.net.connector.AbstractConnectionFactory.accept(AbstractConnectionFactory.java:205)
        at org.exolab.jms.net.connector.AbstractConnectionManager.accept(AbstractConnectionManager.java:251)
        at org.exolab.jms.net.orb.DefaultORB.accept(DefaultORB.java:456)
        ... 14 more
 
 
Our openjms.xml is as follows
 
 
<?xml version="1.0"?>
 
<Configuration>
 
  <!-- Optional. This represents the default configuration  -->
  <ServerConfiguration host="localhost" embeddedJNDI="true" />
 
  <Connectors>
    <Connector scheme="rmi">
      <ConnectionFactories>
        <QueueConnectionFactory name="JMSQueueConnectionFactory" />
        <TopicConnectionFactory name="JMSSTopicConnectionFactory" />
      </ConnectionFactories>
    </Connector>
  </Connectors>
 
  <RmiConfiguration embeddedRegistry="false"
                    registryHost="myhost"
                    registryPort="1099">
  </RmiConfiguration>
   
  <!-- Required  -->
  <DatabaseConfiguration>
    <RdbmsDatabaseConfiguration
      driver="oracle.jdbc.driver.OracleDriver"
      url="jdbc:oracle:thin:@myhost:1521:db1"
      user="openjms"
      password="secret1"/>
  </DatabaseConfiguration>
 
  <!-- Required -->   
  <AdminConfiguration script="${openjms.home}\bin\startup.bat" />
 
</Configuration>
 
 
when using an embeddedRegistry it works fine, but that isnt possible in our running environment, and we would prefer not to allocate more ports of http/tcp when we can just use RMI (provided it works)
 
Thanks,
 
DKE
 




NOTICE - This message and any attached files may contain information that is confidential and intended only for use by the intended recipient. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, be advised that you have received this message in error and that any dissemination, copying or use of this message or attachment is strictly forbidden, as is the disclosure of the information therein. If you have received this message in error please notify the sender immediately and delete the message.