tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arion Yu <ario...@i-stt.com.hk>
Subject Re: ANYONE gotten tomcat3.1 stand-alone to work with linux ?
Date Fri, 20 Oct 2000 08:25:34 GMT
Hi!

Are you sure your a/c can open the port 8080?

Arion

Phil_Hedley@Mitel.COM wrote:

> From:  Phil Hedley@MITEL on 10/20/2000 09:13 AM GDT
> Hi Jacob,
> Yes, I have Tomcat 3.1 working with RedHat Linux 6.2.
> I have no idea why you are getting the first error.
> The 2nd error is obviously occuring because of the Ist error.
>
> The only problems I have encountered whilst starting up Tomcat is when I have
> not had su permissions. But the errors are different.
>
> Sorry I can't offer you anything else.
>
> Phil Hedley
>
> Jacob Nowicki <jacob.nowicki@kineticconcepts.com> on 20/10/2000 07:42:01
>
> Please respond to tomcat-user@jakarta.apache.org
>
> To:   tomcat-user@jakarta.apache.org
> cc:    (bcc: Phil Hedley/Cal/Mitel)
>
> Subject:  ANYONE gotten tomcat3.1 stand-alone to work with linux ?
>
>   ------------------------------------------------------------------------
>
> I am just trying to get tomcat3.1 running on my linux box in stand-alone
> mode
> but I am getting the "infamous" errors...
>
> #1 after startup
> java.net.SocketException: Interrupted system call
>         at java.net.PlainSocketImpl.socketAccept(Native Method)
>         at java.net.PlainSocketImpl.accept(Compiled Code)
>         at java.net.ServerSocket.implAccept(Compiled Code)
>         at java.net.ServerSocket.accept(Compiled Code)
>         at
> org.apache.tomcat.service.SimpleTcpEndpoint.acceptSocket(Compiled Code)
>         at
> org.apache.tomcat.service.SimpleTcpEndpoint.acceptConnections(Compiled
> Code)
>         at org.apache.tomcat.service.TcpListenerThread.run(Compiled
> Code)
>         at java.lang.Thread.run(Compiled Code)
> Endpoint ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8080]
> shutdown due to exception: java.net.SocketException: Interrupted system
> call
>
> #2 during shutdown
> java.net.ConnectException: Connection refused
>         at java.net.PlainSocketImpl.socketConnect(Native Method)
>         at java.net.PlainSocketImpl.doConnect(Compiled Code)
>         at java.net.PlainSocketImpl.connectToAddress(Compiled Code)
>         at java.net.PlainSocketImpl.connect(Compiled Code)
>         at java.net.Socket.<init>(Compiled Code)
>         at java.net.Socket.<init>(Compiled Code)
>         at org.apache.tomcat.startup.Tomcat.stopTomcat(Compiled Code)
>         at org.apache.tomcat.startup.Tomcat.execute(Compiled Code)
>         at org.apache.tomcat.startup.Tomcat.main(Compiled Code)
>
> HELP ANYONE!!!!
>
> Jake
>
> Ralph Einfeldt wrote:
> >
> > - The servlet spec is not completely backwards compatible.
> >   Some methods and a class have been deprecated
> >   see:
> > http://www.javaworld.com/javaworld/jw-12-1998/jw-12-servletapi_p.html
> >
> >   But to change that shouldn'be be a big task.
> >
> > - The biggest effort (acccording to the traffic in this list) is
> >   to convert the configuration.
> >
> > > -----Urspr√ľngliche Nachricht-----
> > > Von: Christian Rauh [mailto:christian@rauh.net]
> > > Gesendet: Donnerstag, 19. Oktober 2000 20:40
> > > An: tomcat-user@jakarta.apache.org
> > > Betreff: Re: Why there are two apache servlets projects?
> > <snip/>
> > > The next question I pose is: how hard it is to eventually port the
> > > applications from JServ to Apache? I believe none due to backward
> > > compatibility, but is this really happening?
> > <snip/>

--
[This email and any files transmitted with it are confidential and may contain
information that is legally privileged. They are intended solely for the
addressee(s). Access to this email by anyone else is unauthorized. If you are not
the intended recipient, please delete it and notify the sender by email
immediately; you should not copy or use it for any purpose, nor disclose its
contents to any other person. Thank you.]



Mime
View raw message