Re: Running Openjms with Servlet Runner Server Other Than Tomcat..

amit godbole wrote:
> Hi All,
>
> We want to run openjms-0.7.7-alpha-1 server with
> Servlet Runner Server other than Tomcat.
>
> The steps we followed were:
>
> 1. Firstly, we deployed
> openjms-tunnel-0.7.7-alpha-1.war on tomcat.
>
> 2. Started the tomcat. - 
>
> 3. We created the Jar file of the classes present in
> the directory -	
> 	
>
> jakarta-tomcat-4.1.12/webapps/openjms-tunnel-0.7.7-alpha-1/WEB-INF/classes
> 	
> 4. We deployed this jar into Servlet Runner Server in
> its classpath.
>
> 5. We deployed required Jars for OpenJms into
> CLASSPATH of Servlet Runner Server.
>
> 6. We also deployed the file
> openjms-common-0.7.7-alpha-1.jar present in
> (openjms-tunnel-0.7.7-alpha-1/WEB-INF/lib)
> 	
>    into Servlet Runner Server in its classpath.
>
> 7. We changed the openjms.xml file as follows:
>
> 	 <HttpConfiguration port="3030" 
>                      webServerHost="192.168.1.11"
> webServerPort="8080" maxThreads="50"
>                      servlet="/tunnel"/>
>
> 8. We made the changes into Configuration file of our
> Servlet Runner Server according to web.xml file.
> 	     
> 9. We tried to run openjms-0.7.7-alpha-1 server with
> the above configuration.
>
>
>
>
> But with this we are getting the exception as follows:
>
> Using JAVA_HOME:    /usr/java/j2sdk1.4.2_03/
> OpenJMS: JMS 0.7.7-alpha-1
> The OpenJMS Group. (C) 1999-2005. All rights reserved.
> http://openjms.sourceforge.net
> org.exolab.jms.server.ServerException:
> java.rmi.server.ExportException: Failed to accept
> connections on URI: http-server://192.168.1.11:3030/;
> nested exception is:
>        
> org.exolab.jms.net.connector.ResourceException: Failed
> to create server socket for
> URI=http-server://192.168.1.11:3030/
>         at
> org.exolab.jms.net.orb.DefaultORB.accept(DefaultORB.java:369)
>         at
> org.exolab.jms.net.orb.AbstractORB.doExport(AbstractORB.java:441)
>         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:201)
>         at
> org.exolab.jms.server.net.RemoteServerConnector.init(RemoteServerConnector.java:149)
>         at
> org.exolab.jms.server.ConnectorService.initConnector(ConnectorService.java:202)
>         at
> org.exolab.jms.server.ConnectorService.initConnectors(ConnectorService.java:143)
>         at
> org.exolab.jms.server.ConnectorService.start(ConnectorService.java:109)
>         at
> org.exolab.jms.server.JmsServer.init(JmsServer.java:162)
>         at
> org.exolab.jms.server.JmsServer.main(JmsServer.java:195)
> Caused by:
> org.exolab.jms.net.connector.ResourceException: Failed
> to create server socket for
> URI=http-server://192.168.1.11:3030/
>         at
> org.exolab.jms.net.socket.SocketManagedConnectionAcceptor.<init>(SocketManagedConnectionAcceptor.java:160)
>         at
> org.exolab.jms.net.http.HTTPManagedConnectionAcceptor.<init>(HTTPManagedConnectionAcceptor.java:90)
>         at
> org.exolab.jms.net.http.HTTPManagedConnectionFactory.createManagedConnectionAcceptor(HTTPManagedConnectionFactory.java:117)
>         at
> org.exolab.jms.net.connector.DefaultConnectionPool.createManagedConnectionAcceptor(DefaultConnectionPool.java:217)
>        
> 	at
> org.exolab.jms.net.connector.AbstractConnectionManager.accept(AbstractConnectionManager.java:158)
>         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:367)
>         ... 11 more
>
> [6]   Exit 255                sh openjms.sh start
>
>
>
> Please let me know where we are going wrong.
>
> Thanks in Advance.
>
> With Regards,
>
> Amit Godbole.
>
>   
That's a particularly convoluted way to deploy the tunnel to servlet runner,
but its probably not the cause the problem.

The server is trying to create a socket to accept connections on port 3030.
Its failing, probably because another  process is using that  port.

Try running
 > netstat -a
to determine if the port is in use

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