Re: Error - org.exolab.jms.server.ServerException

If you add the following to $OPENJMS_HOME/config/log4j.xml:
  <category name="org.exolab.jms.net.rmi.RMIManagedConnectionAcceptor" 
additivity="false">
    <priority value="DEBUG"/>
    <appender-ref ref="STDOUT"/>
    <appender-ref ref="openjms"/>
  </category>
does anything get logged?

Can you start the server using the startup scripts with the default rmi 
configuration?


Thuy-Linh Chu wrote:
>
> (Please notice that the port number changes because we assign dynamic 
> port, but the problem is the same).
>
>
> 2006-08-28 12:51:58,765 ERROR [Thread-42] 
> org.exolab.jms.server.EmbeddedJmsServer - 
> org.exolab.jms.server.ServerException: Failed to start services
> org.exolab.jms.server.ServerException:
> org.exolab.jms.server.ServerException:
> java.rmi.server.ExportException: Failed to accept connections on URI: 
> rmi://10.0.0.187:15067/; nested exception is:
>         org.exolab.jms.net.connector.ResourceException: Failed to 
> export object
>         at org.exolab.jms.net.orb.DefaultORB.accept(DefaultORB.java:440)
>         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:240)
>         at 
> org.exolab.jms.server.net.RemoteServerConnector.init(RemoteServerConnector.java:195)
>         at 
> org.exolab.jms.server.ConnectorService.initConnector(ConnectorService.java:246)
>         at 
> org.exolab.jms.server.ConnectorService.initConnectors(ConnectorService.java:186)
>         at 
> org.exolab.jms.server.ConnectorService.doStart(ConnectorService.java:154)
>         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:145)
>         at 
> org.exolab.jms.server.EmbeddedJmsServer.run(EmbeddedJmsServer.java:105)
>         at java.lang.Thread.run(Thread.java:534)
> Caused by: org.exolab.jms.net.connector.ResourceException: Failed to 
> export object
>         at 
> org.exolab.jms.net.rmi.RMIManagedConnectionAcceptor.accept(RMIManagedConnectionAcceptor.java:160)
>         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:438)
>         ... 15 more
>
>
> -----Original Message-----
> From: openjms-user-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org on behalf of Tim Anderson
> Sent: Mon 8/28/2006 2:46 PM
> To: [email protected]
> Subject: Re: [openjms-user] Error - org.exolab.jms.server.ServerException
>
> What's the stack trace?
>
> Thuy-Linh Chu wrote:
> >
> > I tried both embedded and non-embedded, the same error occured.
> >
> > Thuy-Linh Chu
> >
> >
> > -----Original Message-----
> > From: openjms-user-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org on behalf of Tim 
> Anderson
> > Sent: Mon 8/28/2006 5:28 AM
> > To: [email protected]
> > Subject: Re: [openjms-user] Error - 
> org.exolab.jms.server.ServerException
> >
> > Try running with an embedded registry:
> >
> >   <RmiConfiguration embeddedRegistry="true"
> >                     registryHost="127.0.0.1"
> >                     registryPort="18221" >
> >   </RmiConfiguration>
> >
> > It looks like support for external registries is currently broken.
> >
> > -Tim
> >
> > Thuy-Linh Chu wrote:
> > >
> > > I got the same error.  This occurs right after I upgraded from 0.7.6.1
> > > to 0.7.7.
> > >  When I did a netstat after this error (with server still running), I
> > > got the
> > > following:
> > >
> > >   TCP    mymachine:4954             mymachine.company.com:18221
> > > ESTABLISHED
> > >   TCP    mymachine:18221            mymachine.company.com:0    
> > LISTENING
> > >   TCP    mymachine:18221            mymachine.company.com:4954
> > > ESTABLISHED
> > >
> > > where 18221 is my RMI port.  Below is my connector and RMI
> > configuration:
> > >
> > >   <Connectors>
> > >     <Connector scheme="rmi">
> > >       <ConnectionFactories>
> > >         <ConnectionFactory name="RMIConnectionFactory"/>
> > >       </ConnectionFactories>
> > >     </Connector>
> > >   </Connectors>
> > >
> > >   <!-- Optional. This represents the default configuration  -->
> > >   <RmiConfiguration embeddedRegistry="false"
> > >                     registryHost="127.0.0.1"
> > >                     registryPort="18221" >
> > >   </RmiConfiguration>
> > >
> > > Your help is appreciated.
> > >
> > > Thuy-Linh Chu
> > >
> > > Tim Anderson <tma@...> writes:
> > >
> > > >
> > > >
> > > > Make sure you haven't configured openjms.xml to use port 1099 
> for more
> > > > than one connector.
> > > > Failing that, pull apart the exception to find the root cause of the
> > > > problem.
> > > > -Tim
> > > > Alexis Rocha wrote:
> > > >
> > > >   Thanks Tim.
> > > > 
> > > >   But I used this command and nothing was listening port 1099. I
> > > > restarted my machine and still couldn´t connect due to the same
> > error.
> > > >   Any other ideas ?
> > > > 
> > > >   Thanks,
> > > >   Alexis
> > > >
> > > >
> > > > On 7/3/06, Tim
> > > > Anderson <tma-ooduxAEi7gXtt0EhB6fy4g-XMD5yJDbdMReXY1tMh2IBg@public.gmane.org>
> > > > wrote:
> > > >   Alexis
> > > > Rocha wrote:
> > > > > Hi all,
> > > > >
> > > > >   When I try to initialize OpenJms in my machine, sometimes, I get
> > > > the
> > > >  
> > > > > error:
> > > > >
> > > > >   org.exolab.jms.server.ServerException:
> > > > > java.rmi.server.ExportException: Failed accept connections on URI:
> > > > > rmi://my_machine_ip:1099/
> > > > >
> > > > >   Does anyone can help me with this ?
> > > >  
> > > > >
> > > > > Thanks,
> > > > > Alexis
> > > > It usually means that something is already listening on port 1099.
> > > > You can check by running:
> > > > > netstat -a
> > > > from the command line.
> > > > -Tim
> > >
> >
>

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642