Re: 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