RE: JVM Bind error when starting Tomcat 3.2.4
Hi Carl, The error is simply telling you the address/port that it is attempting to connect to is in use. Possibly see what ports your using in the server.xml, and maybe compare that to a netstat -a command listing of the ports. Hope that helps some. Jeremy Davis Senior Support Analyst BPI Marketplace Integration 614.760.8941 1.800.436.8726 - Support Line -Original Message- From: Iddings, Carl (SAA) [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 25, 2003 11:03 AM To: [EMAIL PROTECTED] Subject: JVM Bind error when starting Tomcat 3.2.4 I'm running Tomcat 3.2.4 on a Windows 2000 Server using IIS 5.0. I received the following error when issuing the batch command "tomcat.bat run": FATAL:java.net.BindException: Address in use: JVM_Bind java.net.BindException: Address in use: JVM_Bind at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:447) at java.net.ServerSocket.(ServerSocket.java:165) at java.net.ServerSocket.(ServerSocket.java:116) at org.apache.tomcat.net.DefaultServerSocketFactory.createSocket(DefaultSer verSocketFactory.java:97) at org.apache.tomcat.service.PoolTcpEndpoint.startEndpoint(PoolTcpEndpoint. java:239) at org.apache.tomcat.service.PoolTcpConnector.start(PoolTcpConnector.java:1 88) at org.apache.tomcat.core.ContextManager.start(ContextManager.java:527) at org.apache.tomcat.startup.Tomcat.execute(Tomcat.java:207) at org.apache.tomcat.startup.Tomcat.main(Tomcat.java:240) I'm quite new at Tomcat, so I would appreciate any help in explaining what this error means and how I can avoid it in the future. Thanks. Carl Iddings Information Technology Manager U. S. Senate Technology Development Services - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Too many processes
Supposedly, to the best of my knowledge, the JVM is suppose to begin garbage collection once it nears the max memory allotted. Though if there is not enough memory to recover..yet, I guess it would be possible that this would occur, or maybe it is taking so long to run the garbage collection, that in the meantime, your hanging up the box? You could try the -Xincgc to increment garbage collection, so that it does not wait till the near end of the heap size before doing GC, and it does it in small increments reducing pauses. Another suggestion is to do something like -Xms1024m -Xmx1024m -XX:NewSize=512m -XX:MaxNewSize=512m Supposedly, this will set the short lived objects to be cleaned up a bit more efficiently? Would need to do more research to really explain that any further... Jeremy Davis Senior Support Analyst BPI Marketplace Integration 614.760.8941 1.800.436.8726 - Support Line -Original Message- From: Ryan Chambers [mailto:[EMAIL PROTECTED] Sent: Monday, March 24, 2003 2:11 PM To: Tomcat Users List Subject: RE: Too many processes Has anybody noticed that as you increase the -mx while running tomcat on linux, the maximum number of threads decreases? We have run tomcat on Debian linux with 2GB of real memory and we set a run-time flag of -mx1024m. In this configuration, once the java process reaches a certain number of threads (it's always the same number, I think it's around 468), then it can't create any new threads. When this happens it doesn't respond to any requests and requires a re-start. Reducing the mx value increases the number of threads allowed before the java process craps out, but then we get OutOfMemory exceptions, so we need that extra memory. Does anybody know how to explain this? This problem isn't limited to just tomcat, it affects any java process on linux, I've checked. Ryan -----Original Message- From: Davis, Jeremy [mailto:[EMAIL PROTECTED] Sent: Monday, March 24, 2003 11:01 AM To: 'Tomcat Users List' Subject: RE: Too many processes He is referring to the JVM parameters to limit the amount of memory the JVM is allotted. They are java command line parameters. That will atleast give you the direction for documentation. java.sun.com search should result in more detail for you. Jeremy Davis Senior Support Analyst BPI Marketplace Integration 614.760.8941 1.800.436.8726 - Support Line -Original Message- From: Gaston Escobar [mailto:[EMAIL PROTECTED] Sent: Monday, March 24, 2003 1:20 PM To: Tomcat Users List Subject: RE: Too many processes I couldn't find those parameters. Can you be a little bit more specific with what you mean? Thanks a lot -Mensaje original- De: Filip Hanik [mailto:[EMAIL PROTECTED] Enviado el: Lunes, 24 de Marzo de 2003 03:04 p.m. Para: Tomcat Users List Asunto: RE: Too many processes I believe on Linux, each process is a thread. So tomcat only starts one process, but the PS command will list all the threads as separate processes. So there is nothing to worry about. If you want tomcat to use less memory, you can always configure the -ms -mx parameters in catalina.sh Filip > -Original Message- > From: Gaston Escobar [mailto:[EMAIL PROTECTED] > Sent: Monday, March 24, 2003 9:59 AM > To: [EMAIL PROTECTED] > Subject: Too many processes > > > I'm running tomcat in a Red Hat 7.2. It works well when it is > started, but > it starts too many concurrent processes and it starts using > more and more > memory until it reaches 31% of my computer's memory. > How can I configure Tomcat to run less concurrent processes > and without > using so much memory? > > > This is the output of ps -aux > > root 21983 27.2 15.6 243620 39724 pts/0 S14:39 0:19 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 21984 0.0 15.6 243620 39724 pts/0 S14:39 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 21985 4.6 15.6 243620 39724 pts/0 S14:39 0:03 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 21986 0.0 15.6 243620 39724 pts/0 S14:39 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 21987 0.0 15.6 243620 39724 pts/0 S14:39 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 21988 0.0 15.6 243620 39724 pts/0 S14:39 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 21989 0.0 15.6 243620 39724 pts/0 S14:39 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 21990 0.0 15.6 243620 39724 pts/0 S14:39 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 21991 5.6 15.6 243620 39724 pts/0 S14:39 0:03 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tom
RE: Too many processes
He is referring to the JVM parameters to limit the amount of memory the JVM is allotted. They are java command line parameters. That will atleast give you the direction for documentation. java.sun.com search should result in more detail for you. Jeremy Davis Senior Support Analyst BPI Marketplace Integration 614.760.8941 1.800.436.8726 - Support Line -Original Message- From: Gaston Escobar [mailto:[EMAIL PROTECTED] Sent: Monday, March 24, 2003 1:20 PM To: Tomcat Users List Subject: RE: Too many processes I couldn't find those parameters. Can you be a little bit more specific with what you mean? Thanks a lot -Mensaje original- De: Filip Hanik [mailto:[EMAIL PROTECTED] Enviado el: Lunes, 24 de Marzo de 2003 03:04 p.m. Para: Tomcat Users List Asunto: RE: Too many processes I believe on Linux, each process is a thread. So tomcat only starts one process, but the PS command will list all the threads as separate processes. So there is nothing to worry about. If you want tomcat to use less memory, you can always configure the -ms -mx parameters in catalina.sh Filip > -Original Message- > From: Gaston Escobar [mailto:[EMAIL PROTECTED] > Sent: Monday, March 24, 2003 9:59 AM > To: [EMAIL PROTECTED] > Subject: Too many processes > > > I'm running tomcat in a Red Hat 7.2. It works well when it is > started, but > it starts too many concurrent processes and it starts using > more and more > memory until it reaches 31% of my computer's memory. > How can I configure Tomcat to run less concurrent processes > and without > using so much memory? > > > This is the output of ps -aux > > root 21983 27.2 15.6 243620 39724 pts/0 S14:39 0:19 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 21984 0.0 15.6 243620 39724 pts/0 S14:39 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 21985 4.6 15.6 243620 39724 pts/0 S14:39 0:03 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 21986 0.0 15.6 243620 39724 pts/0 S14:39 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 21987 0.0 15.6 243620 39724 pts/0 S14:39 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 21988 0.0 15.6 243620 39724 pts/0 S14:39 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 21989 0.0 15.6 243620 39724 pts/0 S14:39 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 21990 0.0 15.6 243620 39724 pts/0 S14:39 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 21991 5.6 15.6 243620 39724 pts/0 S14:39 0:03 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 21993 0.0 15.6 243620 39724 pts/0 S14:39 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 21994 0.0 15.6 243620 39724 pts/0 S14:39 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 21995 0.0 15.6 243620 39724 pts/0 S14:39 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 21996 0.0 15.6 243620 39724 pts/0 S14:39 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 22002 0.0 15.6 243620 39724 pts/0 S14:40 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 22003 0.0 15.6 243620 39724 pts/0 S14:40 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 22004 0.0 15.6 243620 39724 pts/0 S14:40 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 22005 0.0 15.6 243620 39724 pts/0 S14:40 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 22006 0.0 15.6 243620 39724 pts/0 S14:40 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 22007 0.0 15.6 243620 39724 pts/0 S14:40 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 22008 0.0 15.6 243620 39724 pts/0 S14:40 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 22009 0.0 15.6 243620 39724 pts/0 S14:40 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 22010 0.0 15.6 243620 39724 pts/0 S14:40 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 22011 0.0 15.6 243620 39724 pts/0 S14:40 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 22012 0.0 15.6 243620 39724 pts/0 S14:40 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 22013 0.0 15.6 243620 39724 pts/0 S14:40 0:00 > /usr/java/j2sdk1.4.1_01/bin/java -Djava.endorsed.dirs=/usr/Tomc > root 22014 0.0 15.6 243620 39724 pts/0 S14:40 0:00 > /usr/java/j2sdk1.4.1_01/bin/
RE: tomcat responds with localhost, but refuses the connection w/ mach inename
Ahhh, found that I wasn't completely starting, it was hanging looking for the keystore file, which had the wrong path, so shutting down was not happening, cause it was not up and listening on that port yet. Jeremy Davis Senior Support Analyst BPI Marketplace Integration 614.760.8941 1.800.436.8726 - Support Line -Original Message- From: John Turner [mailto:[EMAIL PROTECTED] Sent: Friday, March 21, 2003 4:21 PM To: Tomcat Users List Subject: Re: tomcat responds with localhost, but refuses the connection w/ mach inename Don't know...I've never seen that command before. "Connection Refused" typically means there's nothing listening on that port, in this case 8007. John On Fri, 21 Mar 2003 16:16:42 -0500, Davis, Jeremy <[EMAIL PROTECTED]> wrote: > Maybe you can give me some insight into why I am having problems with the > tomcat.sh stop command. When I do "./tomcat.sh stop -host localhost" the > ajp12 connector returns "Error stopping Tomcat with Ajp12 on > localhost.localdomain/127.0.0.1:8007 java.net.ConnectException: > Connection > Refused". > > Jeremy Davis > Senior Support Analyst > BPI Marketplace Integration > 614.760.8941 > 1.800.436.8726 - Support Line > > > -Original Message- > From: John Turner [mailto:[EMAIL PROTECTED] > Sent: Friday, March 21, 2003 4:00 PM > To: Tomcat Users List > Subject: Re: tomcat responds with localhost, but refuses the connection > w/ mach inename > > > > Cool. Tomcat still has its own resolution rules, though. > > John > > On Fri, 21 Mar 2003 15:53:40 -0500, Davis, Jeremy > <[EMAIL PROTECTED]> wrote: > >> Thanks, I have found that it was not tomcat at all, the issue is a >> networking mismatch between the dns name, and the real ip address are >> completely different. Using the machinename was having dns point me to >> a >> box that was not mine, so of course the connection was refused. Thanks >> for >> the help though. >> >> Jeremy Davis >> Senior Support Analyst >> BPI Marketplace Integration >> 614.760.8941 >> 1.800.436.8726 - Support Line >> >> >> -Original Message- >> From: John Turner [mailto:[EMAIL PROTECTED] >> Sent: Friday, March 21, 2003 2:52 PM >> To: Tomcat Users List >> Subject: Re: tomcat responds with localhost, but refuses the connection >> w/ mach inename >> >> >> >> That's one way. It pretty much comes down to how you want to handle >> Contexts. If you want a particular Context to be available for a >> particular domain/host and that domain/host only, you would use a >> separate Host container. >> >> John >> >> On Fri, 21 Mar 2003 14:39:39 -0500, Davis, Jeremy >> <[EMAIL PROTECTED]> wrote: >> >>> I was wondering, I saw the virtual host configuration documentation, >>> and was >>> about to attempt such a thing. So I should add an Alias tag, under a >>> host >>> tag in the server.xml? >>> >>> Jeremy Davis >>> Senior Support Analyst >>> BPI Marketplace Integration >>> 614.760.8941 >>> 1.800.436.8726 - Support Line >>> >>> >>> -Original Message- >>> From: John Turner [mailto:[EMAIL PROTECTED] >>> Sent: Friday, March 21, 2003 2:37 PM >>> To: Tomcat Users List >>> Subject: Re: tomcat responds with localhost, but refuses the connection >>> w/mach inename >>> >>> >>> >>> Did you configure a virtual host for machinename in server.xml, or just >>> leave it with localhost? Tomcat is literal, there is no catch-all like >>> there is with Apache. That is, unless you have a Host container for >>> your hostname or an Alias directive for an already existing virtual >>> host, Tomcat will not answer the request. >>> >>> - will only take requests for localhost >>> and none other >>> >>> >>> machinename - will take requests for localhost + >>> machinename >>> >>> - will take requests for machinename but >>> not localhost >>> >>> John >>> >>> On Fri, 21 Mar 2003 14:32:17 -0500, Davis, Jeremy >>> <[EMAIL PROTECTED]> wrote: >>> >>>> I got red hat 8.0, jdk 1.3.1_07, and tomcat 3.3.1a installed. If on >>>> the >>>> server, I do localhost:8080, it works ok and comes up with the welcome >>>> page, >>>> but when I do machinename:8080 it comes back telling me the connection >>>> was >>>> refused? >>>> >>>> Thanks, >>>> >>>> Jeremy Davis >>>> Senior Support Analyst >>>> BPI Marketplace Integration >>>> 614.760.8941 >>>> 1.800.436.8726 - Support Line >>>> >>>> >>>> - >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>> >>>> >>> >>> >>> >> >> >> > > > -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tomcat responds with localhost, but refuses the connection w/ mach inename
Maybe you can give me some insight into why I am having problems with the tomcat.sh stop command. When I do "./tomcat.sh stop -host localhost" the ajp12 connector returns "Error stopping Tomcat with Ajp12 on localhost.localdomain/127.0.0.1:8007 java.net.ConnectException: Connection Refused". Jeremy Davis Senior Support Analyst BPI Marketplace Integration 614.760.8941 1.800.436.8726 - Support Line -Original Message- From: John Turner [mailto:[EMAIL PROTECTED] Sent: Friday, March 21, 2003 4:00 PM To: Tomcat Users List Subject: Re: tomcat responds with localhost, but refuses the connection w/ mach inename Cool. Tomcat still has its own resolution rules, though. John On Fri, 21 Mar 2003 15:53:40 -0500, Davis, Jeremy <[EMAIL PROTECTED]> wrote: > Thanks, I have found that it was not tomcat at all, the issue is a > networking mismatch between the dns name, and the real ip address are > completely different. Using the machinename was having dns point me to a > box that was not mine, so of course the connection was refused. Thanks > for > the help though. > > Jeremy Davis > Senior Support Analyst > BPI Marketplace Integration > 614.760.8941 > 1.800.436.8726 - Support Line > > > -Original Message- > From: John Turner [mailto:[EMAIL PROTECTED] > Sent: Friday, March 21, 2003 2:52 PM > To: Tomcat Users List > Subject: Re: tomcat responds with localhost, but refuses the connection > w/ mach inename > > > > That's one way. It pretty much comes down to how you want to handle > Contexts. If you want a particular Context to be available for a > particular domain/host and that domain/host only, you would use a > separate Host container. > > John > > On Fri, 21 Mar 2003 14:39:39 -0500, Davis, Jeremy > <[EMAIL PROTECTED]> wrote: > >> I was wondering, I saw the virtual host configuration documentation, and >> was >> about to attempt such a thing. So I should add an Alias tag, under a >> host >> tag in the server.xml? >> >> Jeremy Davis >> Senior Support Analyst >> BPI Marketplace Integration >> 614.760.8941 >> 1.800.436.8726 - Support Line >> >> >> -Original Message- >> From: John Turner [mailto:[EMAIL PROTECTED] >> Sent: Friday, March 21, 2003 2:37 PM >> To: Tomcat Users List >> Subject: Re: tomcat responds with localhost, but refuses the connection >> w/mach inename >> >> >> >> Did you configure a virtual host for machinename in server.xml, or just >> leave it with localhost? Tomcat is literal, there is no catch-all like >> there is with Apache. That is, unless you have a Host container for >> your hostname or an Alias directive for an already existing virtual >> host, Tomcat will not answer the request. >> >> - will only take requests for localhost and >> none other >> >> >> machinename - will take requests for localhost + >> machinename >> >> - will take requests for machinename but >> not localhost >> >> John >> >> On Fri, 21 Mar 2003 14:32:17 -0500, Davis, Jeremy >> <[EMAIL PROTECTED]> wrote: >> >>> I got red hat 8.0, jdk 1.3.1_07, and tomcat 3.3.1a installed. If on >>> the >>> server, I do localhost:8080, it works ok and comes up with the welcome >>> page, >>> but when I do machinename:8080 it comes back telling me the connection >>> was >>> refused? >>> >>> Thanks, >>> >>> Jeremy Davis >>> Senior Support Analyst >>> BPI Marketplace Integration >>> 614.760.8941 >>> 1.800.436.8726 - Support Line >>> >>> >>> - >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> >> >> > > > -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tomcat responds with localhost, but refuses the connection w/ mach inename
Thanks, I have found that it was not tomcat at all, the issue is a networking mismatch between the dns name, and the real ip address are completely different. Using the machinename was having dns point me to a box that was not mine, so of course the connection was refused. Thanks for the help though. Jeremy Davis Senior Support Analyst BPI Marketplace Integration 614.760.8941 1.800.436.8726 - Support Line -Original Message- From: John Turner [mailto:[EMAIL PROTECTED] Sent: Friday, March 21, 2003 2:52 PM To: Tomcat Users List Subject: Re: tomcat responds with localhost, but refuses the connection w/ mach inename That's one way. It pretty much comes down to how you want to handle Contexts. If you want a particular Context to be available for a particular domain/host and that domain/host only, you would use a separate Host container. John On Fri, 21 Mar 2003 14:39:39 -0500, Davis, Jeremy <[EMAIL PROTECTED]> wrote: > I was wondering, I saw the virtual host configuration documentation, and > was > about to attempt such a thing. So I should add an Alias tag, under a > host > tag in the server.xml? > > Jeremy Davis > Senior Support Analyst > BPI Marketplace Integration > 614.760.8941 > 1.800.436.8726 - Support Line > > > -Original Message- > From: John Turner [mailto:[EMAIL PROTECTED] > Sent: Friday, March 21, 2003 2:37 PM > To: Tomcat Users List > Subject: Re: tomcat responds with localhost, but refuses the connection > w/mach inename > > > > Did you configure a virtual host for machinename in server.xml, or just > leave it with localhost? Tomcat is literal, there is no catch-all like > there is with Apache. That is, unless you have a Host container for your > hostname or an Alias directive for an already existing virtual host, > Tomcat will not answer the request. > > - will only take requests for localhost and > none other > > > machinename - will take requests for localhost + > machinename > > - will take requests for machinename but > not localhost > > John > > On Fri, 21 Mar 2003 14:32:17 -0500, Davis, Jeremy > <[EMAIL PROTECTED]> wrote: > >> I got red hat 8.0, jdk 1.3.1_07, and tomcat 3.3.1a installed. If on the >> server, I do localhost:8080, it works ok and comes up with the welcome >> page, >> but when I do machinename:8080 it comes back telling me the connection >> was >> refused? >> >> Thanks, >> >> Jeremy Davis >> Senior Support Analyst >> BPI Marketplace Integration >> 614.760.8941 >> 1.800.436.8726 - Support Line >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tomcat responds with localhost, but refuses the connection w/mach inename
I was wondering, I saw the virtual host configuration documentation, and was about to attempt such a thing. So I should add an Alias tag, under a host tag in the server.xml? Jeremy Davis Senior Support Analyst BPI Marketplace Integration 614.760.8941 1.800.436.8726 - Support Line -Original Message- From: John Turner [mailto:[EMAIL PROTECTED] Sent: Friday, March 21, 2003 2:37 PM To: Tomcat Users List Subject: Re: tomcat responds with localhost, but refuses the connection w/mach inename Did you configure a virtual host for machinename in server.xml, or just leave it with localhost? Tomcat is literal, there is no catch-all like there is with Apache. That is, unless you have a Host container for your hostname or an Alias directive for an already existing virtual host, Tomcat will not answer the request. - will only take requests for localhost and none other machinename - will take requests for localhost + machinename - will take requests for machinename but not localhost John On Fri, 21 Mar 2003 14:32:17 -0500, Davis, Jeremy <[EMAIL PROTECTED]> wrote: > I got red hat 8.0, jdk 1.3.1_07, and tomcat 3.3.1a installed. If on the > server, I do localhost:8080, it works ok and comes up with the welcome > page, > but when I do machinename:8080 it comes back telling me the connection > was > refused? > > Thanks, > > Jeremy Davis > Senior Support Analyst > BPI Marketplace Integration > 614.760.8941 > 1.800.436.8726 - Support Line > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
tomcat responds with localhost, but refuses the connection w/machinename
I got red hat 8.0, jdk 1.3.1_07, and tomcat 3.3.1a installed. If on the server, I do localhost:8080, it works ok and comes up with the welcome page, but when I do machinename:8080 it comes back telling me the connection was refused? Thanks, Jeremy Davis Senior Support Analyst BPI Marketplace Integration 614.760.8941 1.800.436.8726 - Support Line - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: no Tomcat process & error stopping service (Red Hat 8.0)
Do you have a webserver already up and listening on port 80? I don't know for sure, but that would be my first guess, if that helps. Jeremy Davis Senior Support Analyst BPI Marketplace Integration 614.760.8941 1.800.436.8726 - Support Line -Original Message- From: Lisa Foister [mailto:[EMAIL PROTECTED] Sent: Friday, March 21, 2003 12:17 PM To: 'Tomcat Users List' Subject: RE: no Tomcat process & error stopping service (Red Hat 8.0) hmm... ok, here's what's in the log (this should be exactly one start and stop -- the first 2 or 3 entries are from the start, the rest from the stop). I don't seem to be getting any errors at all on startup. No clue what "Error initializing endpoint" means, but it seems to be my first actual error. Mar 21, 2003 11:59:04 AM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Mar 21, 2003 11:59:04 AM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Mar 21, 2003 11:59:05 AM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Mar 21, 2003 11:59:07 AM org.apache.coyote.http11.Http11Protocol init SEVERE: Error initializing endpoint java.net.BindException: Permission denied:80 at org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoi nt.java:270) at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java) at org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteCo nnector. java) at org.apache.catalina.core.StandardService.initialize(StandardService.j ava:579) at org.apache.catalina.core.StandardServer.initialize(StandardServer.jav a:2245) at org.apache.catalina.startup.Catalina.start(Catalina.java:511) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) Catalina.start: LifecycleException: Protocol handler initialization failed: jav a.net.BindException: Permission denied:80 LifecycleException: Protocol handler initialization failed: java.net.BindExcept ion: Permission denied:80 at org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteConnector. java) at org.apache.catalina.core.StandardService.initialize(StandardService.j ava:579) at org.apache.catalina.core.StandardServer.initialize(StandardServer.jav a:2245) at org.apache.catalina.startup.Catalina.start(Catalina.java:511) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) Catalina.stop: LifecycleException: This server has not yet been started LifecycleException: This server has not yet been started at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2212 ) at org.apache.catalina.startup.Catalina.start(Catalina.java:543) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) On Friday, March 21, 2003 12:08 PM, Tim Funk [SMTP:[EMAIL PROTECTED] wrote: > Look for /var/tomcat4/logs/catalina.out. There will be an error message > in there of what went wrong. > > -Tim > > Lisa Foister wrote: > > I'm very much a Linux newbie, so I may be missing something obvious here, > > but I think I've got the J2SDK set up right, and I thought I had Tomcat set > > up right. I've completely shut down my Apache server so I don't have to > > deal with the interactions, and although I would prefer to be running > > Tomcat on port 80, at the moment I'd be happy to have it running on any > > port. > > > > Every time I try to start Tomcat as a service (logged in as root, if it > > makes a difference) I get "Starting tomcat4: OK ]" as if
RE: Need help with tomcat running as service with ajp13
There is an issue with the JDK 1.3.x and NT running as a service? Maybe try and upgrade the jdk to 1.4? Jeremy Davis Senior Support Analyst BPI Marketplace Integration 614.760.8941 1.800.436.8726 - Support Line -Original Message- From: Strecker, Mark [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2003 4:15 PM To: Tomcat Users List Subject: Need help with tomcat running as service with ajp13 Hello All, I have Tomcat 4.1.18 running as a service on an NT4.0 machine with Java 1.3.1 ... also it is getting requests via ajp13 from an apache server. It starts and works fine, but I am seeing a problem where it gets "stuck" and pegs the cpu. I can still connect to the administration page and connect to applications in a reasonable amount of time, but I am concerned about why it is using 100% cpu to do nothing. Has anyone experienced this or have a suggestion as to what I can log to figure out what is happening? (I have tried to log everything with no success.) TIA, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problem with my aplication
You may want to try some JVM tweaks to play with the memory heap size, the garbage collection size and such? Jeremy Davis Senior Support Analyst BPI Marketplace Integration 614.760.8941 1.800.436.8726 - Support Line -Original Message- From: Claudio Pimentel Modesto [mailto:[EMAIL PROTECTED] Sent: Thursday, March 20, 2003 3:42 PM To: '[EMAIL PROTECTED]' Subject: Problem with my aplication Hello there, I´m using Tomcat 4.1.12 for a while and I'm very happy with it. Congratulations. Today I had a problem like this, it's happening sometimes. There are about 80 browser accessing it and my server has 2GB of RAM and 2 xeon processor at 2GHz. I'm using java 1.4.0 Take a look at tomcat's log file. 2003-03-20 17:09:42 StandardWrapperValve[ATMDemo]: Servlet.service() for servlet ATMDemo threw exception javax.servlet.ServletException: Servlet execution threw an exception at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2396) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 ) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:405) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne ction(Http11Protocol.java:380) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:508) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:533) at java.lang.Thread.run(Thread.java:536) - Root Cause - java.lang.OutOfMemoryError Is there a hint to solve this problem? I apreciate your help. Thanks a lot. Cláudio Pimentel Modesto System analist Bank of Brasília - Brazil Cartão BRB - DEINF/GERAS *362-3414 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SSL Handshake failure
I setup a tomcat 3.3.1 system, with the ssl connector, JSSE, generated cert and keystore, per documentation. Every time I attempt to hit https://theserver:8443/ we get the below in the console window for tomcat... PoolTcpEndpoint: Handshake failed javax.net.ssl.SSLException: bad handshake record MAC at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275) at com.sun.net.ssl.internal.ssl.AppOutputStream.write(DashoA6275) at java.io.OutputStream.write(OutputStream.java:56) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(DashoA6275) at org.apache.tomcat.util.net.JSSESocketFactory.handshake(JSSESocketFactory.jav a:270) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:479) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:516) at java.lang.Thread.run(Thread.java:479) ThreadPool: Caught exception executing [EMAIL PROTECTED], terminating thread java.lang.NullPointerException at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:498) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:516) at java.lang.Thread.run(Thread.java:479) Jeremy Davis Senior Support Analyst BPI Marketplace Integration 614.760.8941 1.800.436.8726 - Support Line - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
