date:20100213


Hi.

Does anyone else experience problems accessing the Apache websites right 
now ?

I am getting Invalid Encoding errors in Firefox 3.5.

Content Encoding Error
The page you are trying to view cannot be shown because it uses an 
invalid or unsupported form of compression.


I would suspect a local problem, but Google, IBM and other pages seems 
to load fine.  IE also is unable to access the Apache pages.


At further inspection, it seems to be due to an invalid gzip-encoded 
response.



Example, captured using HttpFox browser plugin :

Request :
(Request-Line)  GET /tomcat-6.0-doc/index.html HTTP/1.1
Hosttomcat.apache.org
User-Agent	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.3) 
Gecko/20090824 Firefox/3.5.3

Accept  text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language en-gb,en;q=0.5
Accept-Encoding gzip,deflate
Accept-Charset  ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive  300
Connection  keep-alive
Range   bytes=1-
If-Ranged10ded-31ff-47d84a38e2700-gzip
Cache-Control   max-age=0

Response :
(Status-Line)   HTTP/1.1 200 OK
DateSat, 13 Feb 2010 14:23:13 GMT
Server  Apache/2.3.5 (Unix) mod_ssl/2.3.5 OpenSSL/0.9.7d mod_fcgid/2.3.2-dev
Last-Modified   Tue, 19 Jan 2010 13:42:20 GMT
Etagd10ded-31ff-47d84a38e2700-gzip
Accept-Ranges   bytes
VaryAccept-Encoding
Content-Encodinggzip
Content-Range   bytes 1-12798/12799
Content-Length  12798
Keep-Alive  timeout=30, max=100
Connection  Keep-Alive
Content-Typetext/html

Status line in HttpFox plugin :

00:02:23.326	0.179	483	13101	GET	200	text/html 
(NS_ERROR_INVALID_CONTENT_ENCODING) 
http://tomcat.apache.org/tomcat-6.0-doc/index.html



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat dies suddenly

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

André,

On 2/12/2010 7:29 PM, André Warnier wrote:
 I would just like to mention that in 90% of the cases where I have seen
 a Seg Fault, it was due to the attempted execution of a piece of binary
 code not meant for the current platform.
 (It's been a while since I've seen one though.)

In a Java context, for me it's always been either misbehaving native
code (/not/ from Sun... this would be application code), or bad
hardware. Maybe another run through memtest86+ would be a good idea.

I'd love to see a stack trace from a few crashes, though.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkt2u18ACgkQ9CaO5/Lv0PBGsQCgvhnXtIby1uP47o3BmjN8Hlyh
USAAn1P/xLbv3tDhsTto6lWXDfwd4lM7
=xovn
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: digest algorithm in BASIC auth

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Antonio,

On 2/13/2010 3:01 AM, banto wrote:
 I was confused because in the HTTP message exchanges between the browser and
 tomcat i saw that tomcat sent back to the browser the realm value. for that
 i thought was involved some kind of digest.

The realm name is present in both BASIC and DIGEST authentication
mechanisms.

Were you able to get things working?

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkt2u5cACgkQ9CaO5/Lv0PDxlACfQeCnbfzDtGaK02LwdKwjzh3a
tu4An2QCo/tCLUAWQNLJzy8GKQV0q49J
=cKxS
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: How to configure tomcat server.xml....

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Munirathinavel,

One post is sufficient: we all got a copy.

On 2/13/2010 8:48 AM, Munirathinavel wrote:
 I'm using Tomcat 6.0.18  apache2.2 server  I need to know configure my
 server.xml  context.xml for high performance  heavy traffic.

It's always best to have the most up-to-date version of your software.
Tomcat 6.0.24 is available: you might want to consider using that in
your testing environment from here on out.

How do you connect Apache httpd to Tomcat? What purpose does httpd serve?

   GlobalNamingResources
 Resource name=UserDatabase auth=Container
   type=org.apache.catalina.UserDatabase
   description=User database that can be updated and saved
   factory=org.apache.catalina.users.MemoryUserDatabaseFactory
   pathname=conf/tomcat-users.xml /
   /GlobalNamingResources

Do you need this UserDatabase in here? I wouldn't use that in production.

   Service name=Catalina
   Connector port=8009 debug=0 enableLookups=false 
 protocol=AJP/1.3
maxThreads=120 minSpareThreads=30 maxSpareThreads=60
 reloadable=false connectionTimeout=2  
 redirectPort=8443/ 

Here's where things get interesting:

Does 120 simultaneous connections sound like a reasonable load for your
webapp? What kinds of loads do you /want/ to be able to handle?

If you need to be able to handle huge amounts of traffic, you might want
to consider removing Apache httpd from your setup. You haven't said what
you use it for: some people use it work static content hosting, which
isn't a good enough reason. Others use it for load balancing, which you
haven't mentioned so I assume you aren't. Some folks, like me, use it to
direct traffic to more than one instance of Tomcat when a hardware
load-balancer isn't available. If you aren't doing any of these things,
then get rid of httpd: it's just slowing things down.

If you have a lot of keepalive requests, consider using the NIO
connector which doesn't tie up request processing threads while waiting
for the 3nd, 3rd, etc. request on the same connection. If you need to
send large static files, definitely consider using the APR connector
with sendFile=true. If you need SSL, also consider using the APR
connector, as the OpenSSL-based SSL implementation is faster than the
one you get with the Java provider.

Finally, the use of an Executor is usually recommended because those
thread pools can dynamically size themselves. The standard Connector
thread pools, for whatever reason, will only create new threads... they
won't take them out of service. An Executor can keep the thread pool
lean and mean.


 Engine name=Catalina defaultHost=***
 
 Realm className=org.apache.catalina.realm.UserDatabaseRealm
  resourceName=UserDatabase/

Yikes!

   Host name=***  appBase=gateway
 unpackWARs=true autoDeploy=true
 xmlValidation=false xmlNamespaceAware=false
 
   Listener className = 
 org.apache.jk.config.ApacheConfig
 workersConfig=conf/workers.properties
 mod_Jk=D:/Apache2.2/modules/mod_jk.so jkLog=logs/mod_jk.log
 jkDebug=info noRoot=false/
   /Host
   
   Listener className = org.apache.jk.config.ApacheConfig
 workersConfig=conf/workers.properties
 mod_Jk=D:/Apache2.2/modules/mod_jk.so jkLog=logs/mod_jk.log
 jkDebug=info noRoot=false/ 
 /Engine
   /Service
   Listener className = org.apache.jk.config.ApacheConfig
 workersConfig=conf/workers.properties
 mod_Jk=D:/Apache2.2/modules/mod_jk.so jkLog=logs/mod_jk.log
 jkDebug=info noRoot=false/

You probably don't want to use the ApacheConfig listener: just write
your own mod_jk configuration files. You certainly don't need /three/ of
them.

   Resource name=jdbc/vehrentDB auth=Container
   type=javax.sql.DataSource 
   maxActive=100

Only you can decide what settings are best for your webapp. Here are
some things to think about:

1. You have 120 max threads, meaning a maximum of 120 simultaneous
connections to handle. Your database connection pool is configured for
100 connections. What percentage of your requests do /not/ require
database access? If the answer is lower than about 20%, then you
probably want to make your maxThreads and maxActive closer to each
other. Otherwise, request threads will block waiting for database
connections.

There are good reasons to limit your database connection pool size: if
your database is not particularly high-performance, then you might want
users to wait. It's just something to think about.

   Resource name=jdbc/empowerDB auth=Container
   type=javax.sql.DataSource 
   maxActive=100

If you have 2 databases, I might think about the ratio of connections
used for each database: if the usage is roughly 50/50, maybe you want
only 60 connections in each database connection pool. Reducing from 100
to 60 connections to your database might

RE: Apache Tomcat/httpd websites problem ?

 From: André Warnier [mailto:a...@ice-sa.com]
 Subject: Apache Tomcat/httpd websites problem ?

 Does anyone else experience problems accessing the Apache websites
 right now ? I am getting Invalid Encoding errors in Firefox 3.5.

Same problem here on FF 3.5 and 3.6.  Not just the Tomcat portion, the entire 
site seems garbled.  Even the www.apache.org home page is oddly formatted.

 - Chuck

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

Re: Apache Tomcat/httpd websites problem ?

2010/2/13 André Warnier a...@ice-sa.com:
 Hi.

 Does anyone else experience problems accessing the Apache websites right now
 ?
 I am getting Invalid Encoding errors in Firefox 3.5.

 Content Encoding Error
 The page you are trying to view cannot be shown because it uses an invalid
 or unsupported form of compression.

 I would suspect a local problem, but Google, IBM and other pages seems to
 load fine.  IE also is unable to access the Apache pages.

 At further inspection, it seems to be due to an invalid gzip-encoded
 response.


 Example, captured using HttpFox browser plugin :

 Request :
 (Request-Line)  GET /tomcat-6.0-doc/index.html HTTP/1.1
 Host    tomcat.apache.org
 User-Agent      Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.3)
 Gecko/20090824 Firefox/3.5.3
 Accept  text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
 Accept-Language en-gb,en;q=0.5
 Accept-Encoding gzip,deflate
 Accept-Charset  ISO-8859-1,utf-8;q=0.7,*;q=0.7
 Keep-Alive      300
 Connection      keep-alive
 Range   bytes=1-
 If-Range        d10ded-31ff-47d84a38e2700-gzip
 Cache-Control   max-age=0

 Response :
 (Status-Line)   HTTP/1.1 200 OK
 Date    Sat, 13 Feb 2010 14:23:13 GMT
 Server  Apache/2.3.5 (Unix) mod_ssl/2.3.5 OpenSSL/0.9.7d mod_fcgid/2.3.2-dev
 Last-Modified   Tue, 19 Jan 2010 13:42:20 GMT
 Etag    d10ded-31ff-47d84a38e2700-gzip
 Accept-Ranges   bytes
 Vary    Accept-Encoding
 Content-Encoding        gzip
 Content-Range   bytes 1-12798/12799
 Content-Length  12798
 Keep-Alive      timeout=30, max=100
 Connection      Keep-Alive
 Content-Type    text/html

 Status line in HttpFox plugin :

 00:02:23.326    0.179   483     13101   GET     200     text/html
 (NS_ERROR_INVALID_CONTENT_ENCODING)
 http://tomcat.apache.org/tomcat-6.0-doc/index.html


Yes, I am also seeing this error. I am using Firefox 3.6.

It occurs only with EU mirror of the site. The US mirror is running fine.

http://tomcat.eu.apache.org/
http://tomcat.us.apache.org/

More than that, the error is intermittent: refreshing the page I get
a) Invalid Encoding error
b) misrendered page (site search box is aligned to the left border of
the screen) (probably the stylesheet failed to load)
c) correctly rendered page


From an error page footer I see that the EU server runs Apache/2.3.5,
while US one uses Apache/2.3.3

Apache/2.3.5 (Unix) mod_ssl/2.3.5 OpenSSL/0.9.7d mod_fcgid/2.3.2-dev
Server at tomcat.apache.org Port 80
Apache/2.3.3 (Unix) mod_ssl/2.3.3 OpenSSL/0.9.7d mod_fcgid/2.3.2-dev
Server at tomcat.us.apache.org Port 80


Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: performance problems with Tomcat 6 and JSF 1.2

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Michael,

On 2/12/2010 11:11 AM, Michael Heinen wrote:
 I noticed serious performance problems with JSF 1.2 and Tomcat which seems to 
 be caused by Tomcat.
 One major performace problem is  bug 
 https://issues.apache.org/bugzilla/show_bug.cgi?id=48600
 Setting metadata-complete=true in web.xml improved the speed significantly
 
 But there seems to be still another problem in Tomcat.
 I deployed the same apps to Jetty.
 Average results of 500 calls of a simple jsf page (jsp) with 1000 h:output 
 tags:
 
 JSF 1.1:
 Tomcat 6.0.24: 26ms
 Jetty 7.0.1: 35ms
 
 JSF 1.2:
 Tomcat 6.0.24: 72ms
 Jetty 7.0.1: 41ms
 
 Any ideas regarding the bad performance of Tomcat with JSF 1.2?
 
 The simple page does not contain any EL expressions,
 just 1000 simple tags: h:outputText value=1 style=z-index:29202;/.

You might want to check out the generated .java file to see if there is
anything suspicious in there. Can you post both the sample JSP and the
generated .java file?

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkt2xPQACgkQ9CaO5/Lv0PDaOwCgtJ4QWltYOpOv1wjzFcd1/EM4
M98An1IzBmOI38A6MZYrk9wOUE++xfqM
=mdSW
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat dies suddenly


Chris and Andre,

Andre's note that it was always code that was not meant for the platform 
triggered a thought that it might be remnants of the jre Slackware includes 
in their distribution.  Let me explain.  I have been installing  Slackware 
by just saying 'load everything'.  Then, I would remove the jre 'package' 
using the package manager.  My thought was what if the package manager is 
not removing everything?  So, I am rebuilding one of the servers eliminating 
unwanted packages before they are installed (take less than 30 minutes... 
not certain how I can get a 10 minute test to see if I accomplished 
anything.)


I agree with Chris that the only definitive way of finding the problem is to 
get a stack trace.  It seems to me we have two stack traces that we need to 
know about: 1) the jvm stack trace and 2) the java stack trace.  Running gdb 
against the core dump only tells me the problem was in the jvm because there 
is no debugging info in the jvm.  So, the only way to get the details would 
seem to be to build the jvm from source (I have downloaded the source but 
haven't built the jvm yet.)  I don't know how to force a java stack dump at 
point of failure, not even certain it is possible because it would seem the 
the failure in the C code in the jvm would mean the jvm would stop before it 
could give a stack trace.


Understand that this is my best guess and that this area is removed from my 
usual mundane Java application development.  If anyone has suggestions, I am 
open to them because I know I know very little.


Thanks,

Carl

- Original Message - 
From: Christopher Schultz ch...@christopherschultz.net

To: Tomcat Users List users@tomcat.apache.org
Sent: Saturday, February 13, 2010 9:46 AM
Subject: Re: Tomcat dies suddenly



-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

André,

On 2/12/2010 7:29 PM, André Warnier wrote:

I would just like to mention that in 90% of the cases where I have seen
a Seg Fault, it was due to the attempted execution of a piece of binary
code not meant for the current platform.
(It's been a while since I've seen one though.)


In a Java context, for me it's always been either misbehaving native
code (/not/ from Sun... this would be application code), or bad
hardware. Maybe another run through memtest86+ would be a good idea.

I'd love to see a stack trace from a few crashes, though.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkt2u18ACgkQ9CaO5/Lv0PBGsQCgvhnXtIby1uP47o3BmjN8Hlyh
USAAn1P/xLbv3tDhsTto6lWXDfwd4lM7
=xovn
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Tomcat dies suddenly

 From: Christopher Schultz [mailto:ch...@christopherschultz.net]
 Subject: Re: Tomcat dies suddenly

 Maybe another run through memtest86+ would be a good idea.

Does memtest86+ fire up enough threads to heat up all the cores?

 - Chuck

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

Re: tomcat 6 on solaris losing cookies

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Konstantin,

On 2/12/2010 5:32 PM, Konstantin Kolinko wrote:
 What connectors are you using? HTTP/AJP? Nio/Bio/Apr? (usually some
 org.apache.coyote.* class is mentioned in the startup log in a
 Starting Coyote .. message)   Do you have Apache HTTPD in front of
 Tomcat?   Do you have HTTP proxies around?  Are failing requests
 coming from some specific client? Are they coming from some specific
 browser?

One more question: how many webapps are we talking about, here, and what
are their deployment paths?

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkt2xgAACgkQ9CaO5/Lv0PCvpwCdGeyhx4lZUd0eEY0le57Wb0Uh
uFwAniNMuCClYqsAw/c4XtQid31hikPo
=JEm6
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Apache Tomcat/httpd websites problem ?

2010/2/13 André Warnier a...@ice-sa.com:
 Hi.

 Does anyone else experience problems accessing the Apache websites right now
 ?
 I am getting Invalid Encoding errors in Firefox 3.5.

 Content Encoding Error
 The page you are trying to view cannot be shown because it uses an invalid
 or unsupported form of compression.

 I would suspect a local problem, but Google, IBM and other pages seems to
 load fine.  IE also is unable to access the Apache pages.

 At further inspection, it seems to be due to an invalid gzip-encoded
 response.


 Example, captured using HttpFox browser plugin :

 Request :
 (Request-Line)  GET /tomcat-6.0-doc/index.html HTTP/1.1
 Host    tomcat.apache.org
 User-Agent      Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.3)
 Gecko/20090824 Firefox/3.5.3
 Accept  text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
 Accept-Language en-gb,en;q=0.5
 Accept-Encoding gzip,deflate
 Accept-Charset  ISO-8859-1,utf-8;q=0.7,*;q=0.7
 Keep-Alive      300
 Connection      keep-alive
 Range   bytes=1-
 If-Range        d10ded-31ff-47d84a38e2700-gzip
 Cache-Control   max-age=0

 Response :
 (Status-Line)   HTTP/1.1 200 OK
 Date    Sat, 13 Feb 2010 14:23:13 GMT
 Server  Apache/2.3.5 (Unix) mod_ssl/2.3.5 OpenSSL/0.9.7d mod_fcgid/2.3.2-dev
 Last-Modified   Tue, 19 Jan 2010 13:42:20 GMT
 Etag    d10ded-31ff-47d84a38e2700-gzip
 Accept-Ranges   bytes
 Vary    Accept-Encoding
 Content-Encoding        gzip
 Content-Range   bytes 1-12798/12799
 Content-Length  12798
 Keep-Alive      timeout=30, max=100
 Connection      Keep-Alive
 Content-Type    text/html

 Status line in HttpFox plugin :

 00:02:23.326    0.179   483     13101   GET     200     text/html
 (NS_ERROR_INVALID_CONTENT_ENCODING)
 http://tomcat.apache.org/tomcat-6.0-doc/index.html


(resending, as the original message didn't reach all the recipients)

Yes, I am also seeing this error. I am using Firefox 3.6.

It occurs only with EU mirror of the site. The US mirror is running fine.

http://tomcat.eu.apache.org/
http://tomcat.us.apache.org/

More than that, the error is intermittent: refreshing the page I get

a) Invalid Encoding error
b) misrendered page (site search box is aligned to the left border of
the screen) (probably the stylesheet failed to load)
c) correctly rendered page


From an error page footer I see that the EU server runs Apache/2.3.5,
while US one uses Apache/2.3.3

Apache/2.3.5 (Unix) mod_ssl/2.3.5 OpenSSL/0.9.7d mod_fcgid/2.3.2-dev
Server at tomcat.apache.org Port 80
Apache/2.3.3 (Unix) mod_ssl/2.3.3 OpenSSL/0.9.7d mod_fcgid/2.3.2-dev
Server at tomcat.us.apache.org Port 80


Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat dies suddenly


Chuck,

I don't know.  Memtest86 states that it has 'support for execution with 
multiple CPUs' but I recall that process froze when I tried it and the 
suggestion (from memtest86) was to use a different option.  I will revisit 
this after I have tried rebuilding the server sans jre and building the jvm 
from source (so I can use it with gdb.)


Thanks,

Carl

- Original Message - 
From: Caldarale, Charles R chuck.caldar...@unisys.com

To: Tomcat Users List users@tomcat.apache.org
Sent: Saturday, February 13, 2010 10:29 AM
Subject: RE: Tomcat dies suddenly



From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Subject: Re: Tomcat dies suddenly

Maybe another run through memtest86+ would be a good idea.


Does memtest86+ fire up enough threads to heat up all the cores?

- Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you 
received this in error, please contact the sender and delete the e-mail 
and its attachments from all computers.






-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Tomcat dies suddenly

 From: Carl [mailto:c...@etrak-plus.com]
 Subject: Re: Tomcat dies suddenly

 building the jvm from source

Just be aware that Sun is rather explicit about the specific versions of the 
compilers and libraries used to build the JVM - it can be a major hassle to get 
it all set up right.

 - Chuck

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

Re: digest algorithm in BASIC auth

2010-02-13 Thread banto


yes!! that´s base64 encoding, you are perfectly right!!!

thanks


Christopher Schultz-2 wrote:
 
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Antonio,
 
 On 2/13/2010 3:01 AM, banto wrote:
 I was confused because in the HTTP message exchanges between the browser
 and
 tomcat i saw that tomcat sent back to the browser the realm value. for
 that
 i thought was involved some kind of digest.
 
 The realm name is present in both BASIC and DIGEST authentication
 mechanisms.
 
 Were you able to get things working?
 
 - -chris
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.10 (MingW32)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
 
 iEYEARECAAYFAkt2u5cACgkQ9CaO5/Lv0PDxlACfQeCnbfzDtGaK02LwdKwjzh3a
 tu4An2QCo/tCLUAWQNLJzy8GKQV0q49J
 =cKxS
 -END PGP SIGNATURE-
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 
 
 

-- 
View this message in context: 
http://old.nabble.com/digest-algorithm-in-BASIC-auth-tp27562000p27576143.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Socket Error in tomcat, white screen in browser

I do not mean to insult your intelligence on the matter, but we are not
getting anywhere on the matter. I feel like we are going off on a tangent
and are just wasting time (because you don't know the solution). Everything
you have told me to do then I already know about and would like to correct
you on some of the things you told me. First of all, I know what
connections and sockets are and infact, a socket is a connection! (Don't
argue with the intricate details of whether a unconnected socket is a
connection or a dormant connection waiting to happen because anything
valuable do with a socket is a connection!) I have programmed large
concurrent/multithreading programming projects including torents and servers
that deal with all kinds of sockets in many different contexts in many
different languages. I know what a socket is! Anything valuable to do with
a socket is a connection! And how do you define a socket without its
port number and IPaddress? A socket is meaningless without this. If you
don't believe me then here are some references from Sun's documentation and
from RFC's (Request for comments from the internet):

---
Definition: A socket is one endpoint of a two-way communication link
between two programs running on the network. A socket is bound to a port
number so that the TCP layer can identify the application that data is
destined to be sent.

An endpoint is a combination of an IP address and a port number. Every TCP
connection can be uniquely identified by its two endpoints. That way you can
have multiple connections between your host and the server.

So don't get lost in technicalities that are meaningless to the situation.
I mean sure, there can be other connections besides sockets (subset of), but
dude, getting lost in these technicalities to try and show superiority does
nothing to help figure out the situation. Now I am sure you know more about
the architecture of Tomcat then I do(maybe not, but will give you the
benefit of the doubt), I am not disputing that. I am a masters student in
computer science with a bachelors in math and computer engineering and I
feel very insulted by the last two posts. I mean, the way they were
structured (especially the last one) have bothered me. My problem is not
the logists of the science, but the Tomcat application itself.

As far as the other replies then you say there is a problem since my windows
machine (windows 7 ultimate) isn't showing the other ports being listened on
(bound). Since they are redirect connections, then I wouldn't be surprised
if a socket (connection), only opens up when a page is redirecting so I
don't believe that is the problem. (Maybe it is, but I doubt it)

And then as far as Root and ROOT, then come on, you know what I am talking
about. Were not talking about case sensitive environmental operating system
features / registry files. I feel like the comment on this was more of an
insult then to inform me. (if you don't know what I am talking about then
maybe I need to talk to someone else)

And then as far as the other guy that posted:
read all of the other posts and not just half of them?
Yes, I did read the posts several times to see if I was missing something.
They tell me nothing useful that I already did not know. Is everyone on
your forums this stuck up. This is bullcrap!

Once again I am not insulting you on your expertise of Tomcat, but I regret
you cannot say the same for me. I feel like this forum is a waste of time
for newbies in the realm of computer science / networking to try and show
superiority over others because they know more on a specific applicaiton.
The people here are not willing to get in and help if it includes more than
the easy icing. What I am going to do next is either try another forum,
reinstall my tomcat and eclipse, or go meet with some professionals that
know tomcat. (my buddies up at the University). If there is anyone that is
willing to help me then let me know, otherwise good day to everyone and good
luck.
Good luck and good day to you.
--
View this message in context:
http://old.nabble.com/Socket-Error-in-tomcat%2C-white-screen-in-browser-tp27567722p27576522.html
Sent from the Tomcat - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Socket Error in tomcat, white screen in browser

--
View this message in context:
http://old.nabble.com/Socket-Error-in-tomcat%2C-white-screen-in-browser-tp27567722p27576555.html
Sent from the Tomcat - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Socket Error in tomcat, white screen in browser

2010/2/13 millerKiller smille8...@hotmail.com:

 And then as far as Root and ROOT, then come on, you know what I am talking
 about.  Were not talking about case sensitive environmental operating system
 features / registry files.  I feel like the comment on this was more of an
 insult then to inform me.  (if you don't know what I am talking about then
 maybe I need to talk to someone else)

Believe us, what was said about ROOT vs Root is important.



 They tell me nothing useful that I already did not know.  Is everyone on
 your forums this stuck up.  This is bullcrap!

Try this one:
http://www.catb.org/~esr/faqs/smart-questions.html#keepcool

And it is not a forum.  It is a mailing list, users @ tomcat.apache.org.


It might be that
1. You have already another instance of Tomcat running. On Windows
usually one Tomcat instance is installed as a service. If it is
already started, you won't be able to start another instance from
within Eclipse IDE using the same port numbers (There are three port
numbers used, all configured in server.xml).

2. There might be a firewall/security software that prevents listening
on that port. Thus the unusual Unrecognized Windows Sockets error.


Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Socket Error in tomcat, white screen in browser


Thanks for the reply.  I will look into closer and see what I come up with. 
When I figure out the solution, if I do, then I will let post a comment so
that it is available to everyone. 

-- 
View this message in context: 
http://old.nabble.com/Socket-Error-in-tomcat%2C-white-screen-in-browser-tp27567722p27576781.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat dies suddenly


Andre,

I tried this and 1) I am now permamently cross eyed and 2) didn't see 
anything that was out of place or looked like a binary that should not be 
there.


Thanks,

Carl

- Original Message - 
From: André Warnier a...@ice-sa.com

To: Tomcat Users List users@tomcat.apache.org
Sent: Saturday, February 13, 2010 11:49 AM
Subject: Re: Tomcat dies suddenly


Just a quick way to check if a rogue binary hasn't crept into some 
libraries directory :


find . -type f -print -exec file {} \; | more

That should give the same file type most of the time, except the rogue 
module.

(the -print may be superfluous)


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat dies suddenly

2010-02-13 Thread Tsirkin Evgeny

Carl ,
At this point it is probably would be much simpler for you to just move away
from Slackware .
Building jvm from source ,debugging with strace - this is a very hard path .
And once you find the bug - there is nothing that you can do with it.
You are not going to fix jvm/libc bugs ,right?
You could report it and wait for new release .
Probably your best bet would be use another distro and download Sun's jvm
from thier site.
Evgeny


  So, the only way to get the details would seem to be to build the jvm from
 source (I have downloaded the source but haven't built the jvm yet.)  I
 don't know how to force a java stack dump at point of failure, not even
 certain it is possible because it would seem the the failure in the C code
 in the jvm would mean the jvm would stop before it could give a stack trace.

 Understand that this is my best guess and that this area is removed from my
 usual mundane Java application development.  If anyone has suggestions, I am
 open to them because I know I know very little.


 Thanks,

 Carl

Re: Tomcat dies suddenly


Tsirkin,

I tried part of that.

I brought up a server with openSuse (64 bit), the latest Sun Java and the 
latest Tomcat.  Failed in about 15 minutes with the same indicators (no 
tracks in any log, didn't know to look for a core file at that time.)  Could 
try this again and check for the core file to see if the failure is the 
same.


I agree building from source and debugging is a very hard road.  Have been 
trying to find a solution for almost three months and everything I have 
tried has failed.


There appear to be only two moving parts: the operating system and the jvm 
(we now know the failure is when the jvm seg faults.)  Maybe I should try a 
different jvm but I have always believed Sun's was most likely the most 
stable and bug free.


Another option is to create a separate Tomcat for each application.  This 
would require reworking and rethinking the applications with no guarantee of 
success anyway.


It would seem that there is something wrong in my setup because I can't 
believe every 64 bit Slackware/Tomcat has failed as we would likely see that 
on this list.


I am certainly open to any suggestion and I appreciate your thoughts.

Thanks,

Carl

- Original Message - 
From: Tsirkin Evgeny tsir...@gmail.com

To: Tomcat Users List users@tomcat.apache.org
Sent: Saturday, February 13, 2010 1:24 PM
Subject: Re: Tomcat dies suddenly



Carl ,
At this point it is probably would be much simpler for you to just move 
away

from Slackware .
Building jvm from source ,debugging with strace - this is a very hard path 
.

And once you find the bug - there is nothing that you can do with it.
You are not going to fix jvm/libc bugs ,right?
You could report it and wait for new release .
Probably your best bet would be use another distro and download Sun's jvm
from thier site.
Evgeny


 So, the only way to get the details would seem to be to build the jvm 
from

source (I have downloaded the source but haven't built the jvm yet.)  I
don't know how to force a java stack dump at point of failure, not even
certain it is possible because it would seem the the failure in the C 
code
in the jvm would mean the jvm would stop before it could give a stack 
trace.


Understand that this is my best guess and that this area is removed from 
my
usual mundane Java application development.  If anyone has suggestions, I 
am

open to them because I know I know very little.


Thanks,

Carl







-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat dies suddenly



The oomParachute does not seem a likely candidate for solving the issue 
because 1) we have never seem the memory (from JConsole or VisualJVM) fill 
the heap or approach the max memory in the machine (never uses swap) or come 
close to blowing the permGem memory.  More and more it does not seem like a 
memory problem.


Thanks,

Carl


- Original Message - 
From: Christopher Schultz ch...@christopherschultz.net

To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, February 12, 2010 5:28 PM
Subject: Re: Tomcat dies suddenly



-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

André,

On 2/12/2010 3:34 PM, André Warnier wrote:

Carl wrote:

Andre,

Thanks for the response.

I have read almost all of your posts and realy enjoy the way to take
problems apart.

Keep on thinking.


I'm not quite sure how to take the above answer..
So, just in case, and maybe to my own ultimate embarassment, I want to
indicate that I was serious.  I seem to remember cases where an
application at the point of dying, would have very much liked to log a
last desperate message to indicate the situation, but did not even have
the resources left to be able to do so.


Are you talking about this?

http://tomcat.apache.org/tomcat-6.0-doc/config/http.html
(search for oomParachute)

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkt11hkACgkQ9CaO5/Lv0PA40gCfaqBCAz8wq2k6W3SH3gKIlF7q
xMQAnjnynEOuXlosG/v2jWHVx5akaQWo
=ODoh
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat dies suddenly


Chris,

This is the only thing I see from gdb:

r...@tomcat_liv:/# gdb -c core
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
http://gnu.org/licenses/gpl.html

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-slackware-linux.
(no debugging symbols found)
Core was generated by 
`/usr/local/java/bin/java -Djava.util.logging.config.file=/usr/local/tomcat/conf'.

Program terminated with signal 11, Segmentation fault.
[New process 3824]
[New process 4182]
[New process 3811]
[New process 3823]
[New process 3825]
[New process 4325]
[New process 3849]
[New process 3364]
[New process 3850]
[New process 3393]
[New process 3851]
[New process 3395]
[New process 3852]
[New process 3399]
[New process 3401]
[New process 3853]
[New process 3406]
[New process 3859]
[New process 3860]
[New process 3861]
[New process 3862]
[New process 3863]
[New process 3410]
[New process 3864]
[New process 3880]
[New process 3416]
[New process 3939]
[New process 3940]
[New process 3775]
[New process 3986]
[New process 3780]
[New process 3987]
[New process 3388]
[New process 4291]
[New process 3387]
[New process 3403]
[New process 3383]
[New process 3389]
[New process 3396]
[New process 3398]
[New process 3407]
[New process 3408]
[New process 3409]
[New process 3411]
[New process 3412]
[New process 3413]
[New process 3414]
[New process 3415]
[New process 3776]
[New process 3782]
[New process 3818]
[New process 3820]
#0  0x7fe01f9d359d in ?? ()

I have thought the reason I am seeing nothing beyond the JVM is that the JVM 
has no debugging symbols.  Did I miss something?


Thanks,

Carl



- Original Message - 
From: Christopher Schultz ch...@christopherschultz.net

To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, February 12, 2010 5:27 PM
Subject: Re: Tomcat dies suddenly



-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Carl,

On 2/12/2010 4:59 PM, Carl wrote:

Darn, I thought we were onto something here but, as you suspected, the
line contains a lot of parameters and was truncated.  So, now, I think
we know the JVM is seg faulting, we just don't know where or why.  I'm
guessing we have to somehow get a stack trace at the point of failure...
any idea how I can get one?  Or, is there a better way?


I believe you can do roughly this with gdb (from memory):

$ gdb core-file

gdb) where

(boom: your stack trace goes here)

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkt11bwACgkQ9CaO5/Lv0PBUCgCfbR2f2IXwFq7ile8biFNjsXOH
opEAnj7gYfb2jfQDtwIcl5atUpyYG8au
=im6P
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat dies suddenly


Chris,

I find it hard to believe two brand new machines with different processors, 
etc. would have a hardware problem that showed itself in exactly the same 
way.  Further, I have run memTest86 for 30 hours on one of the servers and 
it showed nothing (although, as Chuck pointed out, the test may not have 
handled the cores correctly or may not have changed the temperature 
sufficiently to cause the problem we are seeing.)  I have not found a mem 
test specifically for 64 bit processors.


Thanks,

Carl
- Original Message - 
From: Christopher Schultz ch...@christopherschultz.net

To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, February 12, 2010 5:26 PM
Subject: Re: Tomcat dies suddenly



-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Carl,

On 2/12/2010 4:44 PM, Carl wrote:

Now, this is embarrassing: I just checked the other server and it also
has a core file with the date and time of the last failure in the
tomcat/bin directory.  And, it shows a seg fault at exactly the same 
code.


This might be a winner... we certainly know it killed the java process.


So, this now, to me, narrows this down to two possibilities:

1. A JVM bug
2. A hardware problem

That is, if you really aren't running any native code.

But, if you were, it would be showing up in the code dump, right?!

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkt11YMACgkQ9CaO5/Lv0PC/ZwCcCdB3k1ARO5uhxneWilt3wkox
n/4AniRJb/t3Xd9FgKQecXHN7UyFP5RQ
=s/EK
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat dies suddenly


Donn,

It looks like the total files opened are less than 1,000 and the ulimit is 
set to 4,096 (this was increased as a way to check if ulimit was a 
problem... did not change the behavior of the system.)


We use jdbc with the commons pooling process.  We follow the number of open 
connections very closely (logging to catalina.out) because we have had 
connection leaks (still have a small one) in the past.


We do not use LDAP.

Thanks,

Carl
- Original Message - 
From: Donn Aiken donn.ai...@gmail.com

To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, February 12, 2010 4:00 PM
Subject: Re: Tomcat dies suddenly


Carl -

I did have something like this happen to me - not with Tomcat but with
another JEE container.  The container would run for a while, without
incident, then suddenly simply die, with nothing in any log, and not on any
apparent time schedule.

We had some code that was manipulating LDAP that had a leak in it.  For each
leaked connection, we had an open file descriptor that never went away,
until the process went away.  If memory serves, we finally found it by
looking at entries in /proc/{pid of jvm}/fd, doing a bunch of find . | wc
and watching that over time.

I hope this is of some help.  Good luck.

Donn

On Fri, Feb 12, 2010 at 3:46 PM, Carl c...@etrak-plus.com wrote:


Andre,

Take my comment as a compliment because that is the way it was meant... 
you
have helped a lot of people on this least and I, for one, really 
appreciate

that.

I was waiting to see if someone could give me an idea how to implement 
what

you remembered and, if not, then I would google around to see if I could
find it myself.

Thanks,

Carl


- Original Message - From: André Warnier a...@ice-sa.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, February 12, 2010 3:34 PM
Subject: Re: Tomcat dies suddenly


 Carl wrote:



Andre,

Thanks for the response.

I have read almost all of your posts and realy enjoy the way to take
problems apart.

Keep on thinking.

 I'm not quite sure how to take the above answer..

So, just in case, and maybe to my own ultimate embarassment, I want to
indicate that I was serious.  I seem to remember cases where an 
application

at the point of dying, would have very much liked to log a last desperate
message to indicate the situation, but did not even have the resources 
left

to be able to do so.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Tomcat dies suddenly

 From: Carl [mailto:c...@etrak-plus.com]
 Subject: Re: Tomcat dies suddenly

 We use jdbc with the commons pooling process.

Is your JDBC driver type 4, or does it utilize some native code?

 - Chuck

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat dies suddenly


Carl wrote:

Chris,

I find it hard to believe two brand new machines with different 
processors, etc. would have a hardware problem that showed itself in 
exactly the same way.  Further, I have run memTest86 for 30 hours on one 
of the servers and it showed nothing (although, as Chuck pointed out, 
the test may not have handled the cores correctly or may not have 
changed the temperature sufficiently to cause the problem we are 
seeing.)  I have not found a mem test specifically for 64 bit processors.



Right.
After rescanning your posts (and feel free to correct any 
discrepancies), here is a summary :


1) you never saw this issue under a previous JVM 1.5 and Tomcat version 
5.5.x


2) the problem happens on two separate servers, which seems to rule out 
a common server hardware issue


3) it happens under different versions of Linux, which seems to rule out 
a problem with one particular Linux distribution


4) it seems to be a SegFault in the JVM, leaving a core dump but no 
traces in the logs.
(which SegFaults in my experience happen usually when trying to execute 
something which is not valid executable code for the platform at hand)
Anyway, it does not seem to be due to running out of some resource, nor 
to a hidden call to system.exit().


5) not quite sure of this anymore, but it seems to happen also on 
different JVMs, which would tend to rule out a problem with a particular 
JVM port.


6) it does not happen immediately, not in any obvious way related to 
what is being processsed, except that it seems to happen more readily 
under load


7) it is obviously not a common problem with either JVM or Tomcat, or we 
would have had laments from others by now


8) I don't know how a Java/Tomcat webapp application could trigger a 
SegFault on its own, other than by having the JVM participate in it.
And apparently your apps are working fine up to the moment of the sudden 
death, so for once they do not appear as being among the usual suspects.


9) This, in one of your earlier posts, triggered my curiosity :
quote
This Tomcat is straight out of the box except for some modifications to 
JAVA_OPTS in tomcat/bin/catalina.sh (NDLR: canonically, a better place 
would be setenv.sh) and opening up ports and turning on SSL in 
tomcat/conf/server.xml.

unquote

So, maybe two suggestions, taking into account that I am just making 
wild guesses here (but that's pretty much what everyone by now is doing 
too, so I don't feel too bad) :


- have you tried running Tomcat from the command-line, with 
STDOUT/STDERR to the console ?  Maybe something shows up there which 
doesn't show up anywhere else ?


- what about this SSL ? that just seems to me a likely candidate for 
something that is maybe not used all the time, probably calls stuff 
which should be native code, and is usually provided separately from Tomcat.

Can you turn it off and still be operational ?
Also, if it is provided separately, it should probably be relatively 
grouped in some directory, making it easier to check if everything is 
as it should be.


Note also that apart from a direct hardware similarity between the 
servers on which it happens, another common element seems to be the 
place at which it happens, namely the server room.  This is a long shot, 
but a power supply issue may also provoke hardware failures.  Or if your 
server room is on top of a mountain, or near a particle accelerator ?

(re relativistic gamma rays, dark energy and all that stuff).
;-)


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat dies suddenly


Chris,

I will start the newly rebuilt server with strace tomorrow morning before 
anyone comes on.  Hopefully, strace will yield some useful information.


Thanks,

Carl
- Original Message - 
From: Christopher Schultz ch...@christopherschultz.net

To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, February 12, 2010 3:01 PM
Subject: Re: Tomcat dies suddenly



-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Carl,

On 2/12/2010 2:42 PM, Carl wrote:

Great ideas (did you see Chris's response with a way of testing the exit
code?)


[snip]


There is no native code in the application (used to do a lot of work in
C and I am familiar with mayhem of buffer overruns, pointer screwups, 
etc.)


If you get really desperate, you can also run the jvm inside of strace
and get ready for a huge log file. It's possible that you'll see the jvm
fail on the same function call every time, and you'll get more
information about the problem. strace will show you if a signal
terminated the process, or if some other call killed it (like exec(),
which would sure do a number on your JVM).

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkt1s58ACgkQ9CaO5/Lv0PB8YQCgq0kuu87WVbPy0P40vFFHyPJW
RUsAn1dzTKz2NTm7HAKAK7xeAWJS/2hd
=2HBr
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Tomcat dies suddenly

2010-02-13 Thread Anthony J. Biacco

If #1 is correct maybe you should just revert back until you can do more 
testing outside production.
Of course that's only if you're not using some tomcat 6/java 1.6 specific 
features for your apps

-Tony

Sent from my Windows® phone.

-Original Message-
From: André Warnier a...@ice-sa.com
Sent: Saturday, February 13, 2010 1:56 PM
To: Tomcat Users List users@tomcat.apache.org
Subject: Re: Tomcat dies suddenly

Carl wrote:
 Chris,
 
 I find it hard to believe two brand new machines with different 
 processors, etc. would have a hardware problem that showed itself in 
 exactly the same way.  Further, I have run memTest86 for 30 hours on one 
 of the servers and it showed nothing (although, as Chuck pointed out, 
 the test may not have handled the cores correctly or may not have 
 changed the temperature sufficiently to cause the problem we are 
 seeing.)  I have not found a mem test specifically for 64 bit processors.
 
Right.
After rescanning your posts (and feel free to correct any 
discrepancies), here is a summary :

1) you never saw this issue under a previous JVM 1.5 and Tomcat version 
5.5.x

2) the problem happens on two separate servers, which seems to rule out 
a common server hardware issue

3) it happens under different versions of Linux, which seems to rule out 
a problem with one particular Linux distribution

4) it seems to be a SegFault in the JVM, leaving a core dump but no 
traces in the logs.
(which SegFaults in my experience happen usually when trying to execute 
something which is not valid executable code for the platform at hand)
Anyway, it does not seem to be due to running out of some resource, nor 
to a hidden call to system.exit().

5) not quite sure of this anymore, but it seems to happen also on 
different JVMs, which would tend to rule out a problem with a particular 
JVM port.

6) it does not happen immediately, not in any obvious way related to 
what is being processsed, except that it seems to happen more readily 
under load

7) it is obviously not a common problem with either JVM or Tomcat, or we 
would have had laments from others by now

8) I don't know how a Java/Tomcat webapp application could trigger a 
SegFault on its own, other than by having the JVM participate in it.
And apparently your apps are working fine up to the moment of the sudden 
death, so for once they do not appear as being among the usual suspects.

9) This, in one of your earlier posts, triggered my curiosity :
quote
This Tomcat is straight out of the box except for some modifications to 
JAVA_OPTS in tomcat/bin/catalina.sh (NDLR: canonically, a better place 
would be setenv.sh) and opening up ports and turning on SSL in 
tomcat/conf/server.xml.
unquote

So, maybe two suggestions, taking into account that I am just making 
wild guesses here (but that's pretty much what everyone by now is doing 
too, so I don't feel too bad) :

- have you tried running Tomcat from the command-line, with 
STDOUT/STDERR to the console ?  Maybe something shows up there which 
doesn't show up anywhere else ?

- what about this SSL ? that just seems to me a likely candidate for 
something that is maybe not used all the time, probably calls stuff 
which should be native code, and is usually provided separately from Tomcat.
Can you turn it off and still be operational ?
Also, if it is provided separately, it should probably be relatively 
grouped in some directory, making it easier to check if everything is 
as it should be.

Note also that apart from a direct hardware similarity between the 
servers on which it happens, another common element seems to be the 
place at which it happens, namely the server room.  This is a long shot, 
but a power supply issue may also provoke hardware failures.  Or if your 
server room is on top of a mountain, or near a particle accelerator ?
(re relativistic gamma rays, dark energy and all that stuff).
;-)


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re:[OT] Tomcat dies suddenly




(re relativistic gamma rays, dark energy and all that stuff).


I'll take that back quickly before Chuck does me in. Gamma rays being 
photons, they are always relativistic. Read relativistic protons instead.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Re:[OT] Tomcat dies suddenly

 From: André Warnier [mailto:a...@ice-sa.com]
 Subject: Re:[OT] Tomcat dies suddenly

 Read relativistic protons instead.

Now you're talking about something that can do real damage.  (Unlike a WIMP, 
which seems to be too shy to even show up at the party.)

BTW, I was thinking that since the T105 and T110 were both from the same vendor 
and use the same case, there might be some common design factor causing these 
mysterious segfaults - but they're radically different on the inside (e.g., AMD 
vs. Intel, memory speed and type, slots).  Not much in common, except perhaps 
the power supply.

 - Chuck

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

Re: Tomcat dies suddenly


Andre,

You have the ability to boil things down to the bare essentials.

1) you never saw this issue under a previous JVM 1.5 and Tomcat version 
5.5.x


Correct.  (Running on a P4 with 32 bit Slackware.)

2) the problem happens on two separate servers, which seems to rule out a 
common server hardware issue


Correct.

3) it happens under different versions of Linux, which seems to rule out a 
problem with one particular Linux distribution


Correct... Slackware and openSuse.

4) it seems to be a SegFault in the JVM, leaving a core dump but no traces 
in the logs.
(which SegFaults in my experience happen usually when trying to execute 
something which is not valid executable code for the platform at hand)
Anyway, it does not seem to be due to running out of some resource, nor to 
a hidden call to system.exit().


Correct... might be some strange code someplace but I can't find any.

5) not quite sure of this anymore, but it seems to happen also on 
different JVMs, which would tend to rule out a problem with a particular 
JVM port.


No, I have only used Sun's 64 bit.  Started with 1.6.0_17 and am now using 
1.6.0_18.


6) it does not happen immediately, not in any obvious way related to what 
is being processsed, except that it seems to happen more readily under 
load


Correct although I am leaning more towards something related to accessing 
applications B, C and D.  Correct that it does not seem to have an issue at 
any particular point in the code or after some activity by a user.


7) it is obviously not a common problem with either JVM or Tomcat, or we 
would have had laments from others by now


Correct, I think it is something specific to my setup.

8) I don't know how a Java/Tomcat webapp application could trigger a 
SegFault on its own, other than by having the JVM participate in it.
And apparently your apps are working fine up to the moment of the sudden 
death, so for once they do not appear as being among the usual suspects.


Correct.  I can see no degradation of speed right up to the moment of 
failure.



9) This, in one of your earlier posts, triggered my curiosity :
quote
This Tomcat is straight out of the box except for some modifications to 
JAVA_OPTS in tomcat/bin/catalina.sh (NDLR: canonically, a better place 
would be setenv.sh) and opening up ports and turning on SSL in 
tomcat/conf/server.xml.

unquote

So, maybe two suggestions, taking into account that I am just making wild 
guesses here (but that's pretty much what everyone by now is doing too, so 
I don't feel too bad) :


- have you tried running Tomcat from the command-line, with STDOUT/STDERR 
to the console ?  Maybe something shows up there which doesn't show up 
anywhere else ?


I have been starting Tomcat from startup.sh which redirects STDOUT to 
catalina.out and STDERR to somewhere (I will have to look at it closer.) 
Starting tomorrow morning, the server which will be running production (I 
keep the other server in reserve for failures and the old server further 
back just in case I can't keep up with the failures) will be running under 
strace to see if that gives us anything (and I will be pounding on 
applications B, C and D just to see if I can force a failure.)




- what about this SSL ? that just seems to me a likely candidate for 
something that is maybe not used all the time, probably calls stuff which 
should be native code, and is usually provided separately from Tomcat.

Can you turn it off and still be operational ?
Also, if it is provided separately, it should probably be relatively 
grouped in some directory, making it easier to check if everything is as 
it should be.


We use SSL for all communications because most of the data we handle is 
personal data for children.  Can't really turn that off.


Note also that apart from a direct hardware similarity between the servers 
on which it happens, another common element seems to be the place at which 
it happens, namely the server room.  This is a long shot, but a power 
supply issue may also provoke hardware failures.  Or if your server room 
is on top of a mountain, or near a particle accelerator ?

(re relativistic gamma rays, dark energy and all that stuff).
;-)


I am not certain but I do know I don't have to use any lights at night, I 
provide enough glowing (light) to see where I am going.


All of servers are on UPS's which are tested periodically.

Thanks for your thoughts, you have such a great way of analyzing problems.

Carl 



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: [OT] Tomcat dies suddenly

Caldarale, Charles R wrote:

From: André Warnier [mailto:a...@ice-sa.com]
Subject: Re:[OT] Tomcat dies suddenly

Read relativistic protons instead.

Now you're talking about something that can do real damage.  (Unlike a WIMP, 
which seems to be too shy to even show up at the party.)

BTW, I was thinking that since the T105 and T110 were both from the same vendor 
and use the same case, there might be some common design factor causing these 
mysterious segfaults - but they're radically different on the inside (e.g., AMD 
vs. Intel, memory speed and type, slots).  Not much in common, except perhaps 
the power supply.

Since we must have by now exhausted all the normal  causes of such 
errors, maybe we should recommend
a) a visual inspection of the systems, to see if there are any pinsize 
holes, or paint flaking off or so
b) the installation of a surveilance camera, to check if the SegFaults 
are synchronous with any visible phenomenon (sparks, Cerenkow radiation, 
etc.)

c) moving the systems to the basement ?

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat dies suddenly


Anthony,

I have to get through this as quickly as possible and I have never been able 
to rig up a stress test that duplicates what I am seeing in production so I 
am basically using the production servers for working the problem out.  When 
a server fails, I just redirect the traffic to the other server and try to 
analyze what happened.  And, if I can't keep the new servers up, I just move 
back to the old server (thank goodness I didn't rebuild that one when the 
new ones seemed to work.)


Thanks,

Carl

- Original Message - 
From: Anthony J. Biacco abia...@formatdynamics.com

To: Tomcat Users List users@tomcat.apache.org
Sent: Saturday, February 13, 2010 4:08 PM
Subject: RE: Tomcat dies suddenly


If #1 is correct maybe you should just revert back until you can do more 
testing outside production.
Of course that's only if you're not using some tomcat 6/java 1.6 specific 
features for your apps


-Tony

Sent from my Windows® phone.

-Original Message-
From: André Warnier a...@ice-sa.com
Sent: Saturday, February 13, 2010 1:56 PM
To: Tomcat Users List users@tomcat.apache.org
Subject: Re: Tomcat dies suddenly

Carl wrote:

Chris,

I find it hard to believe two brand new machines with different
processors, etc. would have a hardware problem that showed itself in
exactly the same way.  Further, I have run memTest86 for 30 hours on one
of the servers and it showed nothing (although, as Chuck pointed out,
the test may not have handled the cores correctly or may not have
changed the temperature sufficiently to cause the problem we are
seeing.)  I have not found a mem test specifically for 64 bit processors.


Right.
After rescanning your posts (and feel free to correct any
discrepancies), here is a summary :

1) you never saw this issue under a previous JVM 1.5 and Tomcat version
5.5.x

2) the problem happens on two separate servers, which seems to rule out
a common server hardware issue

3) it happens under different versions of Linux, which seems to rule out
a problem with one particular Linux distribution

4) it seems to be a SegFault in the JVM, leaving a core dump but no
traces in the logs.
(which SegFaults in my experience happen usually when trying to execute
something which is not valid executable code for the platform at hand)
Anyway, it does not seem to be due to running out of some resource, nor
to a hidden call to system.exit().

5) not quite sure of this anymore, but it seems to happen also on
different JVMs, which would tend to rule out a problem with a particular
JVM port.

6) it does not happen immediately, not in any obvious way related to
what is being processsed, except that it seems to happen more readily
under load

7) it is obviously not a common problem with either JVM or Tomcat, or we
would have had laments from others by now

8) I don't know how a Java/Tomcat webapp application could trigger a
SegFault on its own, other than by having the JVM participate in it.
And apparently your apps are working fine up to the moment of the sudden
death, so for once they do not appear as being among the usual suspects.

9) This, in one of your earlier posts, triggered my curiosity :
quote
This Tomcat is straight out of the box except for some modifications to
JAVA_OPTS in tomcat/bin/catalina.sh (NDLR: canonically, a better place
would be setenv.sh) and opening up ports and turning on SSL in
tomcat/conf/server.xml.
unquote

So, maybe two suggestions, taking into account that I am just making
wild guesses here (but that's pretty much what everyone by now is doing
too, so I don't feel too bad) :

- have you tried running Tomcat from the command-line, with
STDOUT/STDERR to the console ?  Maybe something shows up there which
doesn't show up anywhere else ?

- what about this SSL ? that just seems to me a likely candidate for
something that is maybe not used all the time, probably calls stuff
which should be native code, and is usually provided separately from Tomcat.
Can you turn it off and still be operational ?
Also, if it is provided separately, it should probably be relatively
grouped in some directory, making it easier to check if everything is
as it should be.

Note also that apart from a direct hardware similarity between the
servers on which it happens, another common element seems to be the
place at which it happens, namely the server room.  This is a long shot,
but a power supply issue may also provoke hardware failures.  Or if your
server room is on top of a mountain, or near a particle accelerator ?
(re relativistic gamma rays, dark energy and all that stuff).
;-)


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: [OT] Tomcat dies suddenly

 From: André Warnier [mailto:a...@ice-sa.com]
 Subject: Re: [OT] Tomcat dies suddenly

 Since we must have by now exhausted all the normal  causes of such
 errors, maybe we should recommend
 a) a visual inspection of the systems, to see if there are any pinsize
 holes, or paint flaking off or so
 b) the installation of a surveilance camera, to check if the SegFaults
 are synchronous with any visible phenomenon (sparks, Cerenkow
 radiation, etc.)
 c) moving the systems to the basement ?

d) exorcism?

 - Chuck

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

Re: Re:[OT] Tomcat dies suddenly


Chuck,

The cases and even power supplies are very different.  The T105 is destined 
to be a backup server and the T110 is supposed to be the front line guy.


Thanks,

Carl

- Original Message - 
From: Caldarale, Charles R chuck.caldar...@unisys.com

To: Tomcat Users List users@tomcat.apache.org
Sent: Saturday, February 13, 2010 4:38 PM
Subject: RE: Re:[OT] Tomcat dies suddenly



From: André Warnier [mailto:a...@ice-sa.com]
Subject: Re:[OT] Tomcat dies suddenly

Read relativistic protons instead.


Now you're talking about something that can do real damage.  (Unlike a 
WIMP, which seems to be too shy to even show up at the party.)


BTW, I was thinking that since the T105 and T110 were both from the same 
vendor and use the same case, there might be some common design factor 
causing these mysterious segfaults - but they're radically different on 
the inside (e.g., AMD vs. Intel, memory speed and type, slots).  Not much 
in common, except perhaps the power supply.


- Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you 
received this in error, please contact the sender and delete the e-mail 
and its attachments from all computers.






-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat dies suddenly


Chuck,

I am using the mysql-connector/j version 3.1.12.  Interesting because the 
latest driver is version 5.1.11.  Is this worth a shot or is it likely to 
just miuddy the waters?  We typically have less than 20 open connections.


Thanks,

Carl
- Original Message - 
From: Caldarale, Charles R chuck.caldar...@unisys.com

To: Tomcat Users List users@tomcat.apache.org
Sent: Saturday, February 13, 2010 3:51 PM
Subject: RE: Tomcat dies suddenly



From: Carl [mailto:c...@etrak-plus.com]
Subject: Re: Tomcat dies suddenly

We use jdbc with the commons pooling process.


Is your JDBC driver type 4, or does it utilize some native code?

- Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Tomcat dies suddenly

 From: Carl [mailto:c...@etrak-plus.com]
 Subject: Re: Tomcat dies suddenly

  This Tomcat is straight out of the box except for some modifications
  to JAVA_OPTS in tomcat/bin/catalina.sh

Have you tried using the default GC mechanism, rather than CMS?  (Sorry if I'm 
repeating something you've already done.)

 - Chuck

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

RE: Tomcat dies suddenly

 From: Carl [mailto:c...@etrak-plus.com]
 Subject: Re: Tomcat dies suddenly

 I am using the mysql-connector/j version 3.1.12.  Interesting 
 because the latest driver is version 5.1.11.  Is this worth a 
 shot or is it likely to just miuddy the waters?

I think it would be muddying, since I'm pretty sure both are pure Java.

However, since we're way beyond the grasping at straws stage...

 - Chuck

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Socket Error in tomcat, white screen in browser


I accept your apology and owe you one to.  The post that threw me off the
rocker was the post that told me to look through all of the messages and not
just parts of.  I apologize...
,but now that we are on the same page and using the same terminology, would
you mind if I ask you some questions?  The last post was interesting and I
had some questions:

If so, here they are:
(1)  On startup, does Tomcat have to set up these dormant
sockets(inactive/listening/passive) or, does Tomcat create them upon a need
base?
(2)  This one might answer number (1). Why does Tomcat use the three
different sockets, doesn't it just need a single server listening socket?
(3)

   Proto  Local Address  Foreign AddressState   PID
  TCP0.0.0.0:80 0.0.0.0:0  LISTENING   6104
  TCP0.0.0.0:8009   0.0.0.0:0  LISTENING   6104
  TCP[::]:80[::]:0 LISTENING   6104
  TCP[::]:8009  [::]:0 LISTENING   6104
 The Foreign Address will always be 0.0.0.0 for passive open (LISTENING)
ports.

I am testing the server on localHost and am getting
Proto  Local Address  Foreign AddressState   PID
 TCP127.0.0.1:8005 0.0.0.0:0  LISTENING  
520
 
 
Is this valid since I using localHost?

(4)If nothing else is using the ports that I mentioned earlier when I use
netstat -ano,  then why does it think there is a bind somewhere?

Thanks


-- 
View this message in context: 
http://old.nabble.com/Socket-Error-in-tomcat%2C-white-screen-in-browser-tp27567722p27579336.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat dies suddenly


Chuck,

I started with the default (except for Xms, Xmx and the PermSize settings) 
and only added the others after the failures started piling up.  They are 
easy to remove and are not likely to be helping or hurting but may be 
muddying the waters.


Thanks,

Carl

- Original Message - 
From: Caldarale, Charles R chuck.caldar...@unisys.com

To: Tomcat Users List users@tomcat.apache.org
Sent: Saturday, February 13, 2010 5:39 PM
Subject: RE: Tomcat dies suddenly



From: Carl [mailto:c...@etrak-plus.com]
Subject: Re: Tomcat dies suddenly

 This Tomcat is straight out of the box except for some modifications
 to JAVA_OPTS in tomcat/bin/catalina.sh


Have you tried using the default GC mechanism, rather than CMS?  (Sorry if 
I'm repeating something you've already done.)


- Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you 
received this in error, please contact the sender and delete the e-mail 
and its attachments from all computers.







-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: [OT] Tomcat dies suddenly

Caldarale, Charles R wrote:

From: André Warnier [mailto:a...@ice-sa.com]
Subject: Re: [OT] Tomcat dies suddenly

Since we must have by now exhausted all the normal  causes of such
errors, maybe we should recommend
a) a visual inspection of the systems, to see if there are any pinsize
holes, or paint flaking off or so
b) the installation of a surveilance camera, to check if the SegFaults
are synchronous with any visible phenomenon (sparks, Cerenkow
radiation, etc.)
c) moving the systems to the basement ?

d) exorcism?

That makes me think about something, specially since Carl mentioned that 
there are children involved.

Maybe we should also investigate if the SegFaults are simultaneous with 
anyone specific entering the room where the servers are.  Like someone 
bringing coffee or pizzas or so ? I swear that I have seen some 
long-running applications mysteriously fail as soon as some specific 
end-users approached a keyboard.  They did not have to even touch the 
keyboard for this to happen.

There are programmers like that too, for that matter.

Surprise visits by big bosses are also among well-known triggering 
factors, as are demos to new users.  But I think in this case we can 
eliminate the first one, since the problem happens several times per 
day.  After the first couple of visits, the surprise element would tend 
to disappear.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Socket Error in tomcat, white screen in browser

 From: millerKiller [mailto:smille8...@hotmail.com]
 Subject: RE: Socket Error in tomcat, white screen in browser

 (1)  On startup, does Tomcat have to set up these dormant
 sockets(inactive/listening/passive) or, does Tomcat create
 them upon a need base?

They're established during Tomcat initialization.  They should appear in the 
netstat display by the time Tomcat logs its server startup message.  For 
example, here are the ones from my Vista system:

Feb 13, 2010 11:22:27 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Feb 13, 2010 11:22:27 AM org.apache.coyote.http11.Http11NioProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8081
Feb 13, 2010 11:22:27 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 3943 ms

 (2) This one might answer number (1). Why does Tomcat use the three
 different sockets, doesn't it just need a single server listening
 socket?

One for each configured port.  The shutdown port (default 8005) is established 
only on the standard IPv4 loopback address (127.0.0.1), whereas the others are 
on 0.0.0.0 ([::] for IPv6) - meaning all IP addresses - unless the address 
attribute is used on the Connector elements.

Your snippet of server.xml showed an HTTP Connector on port 80, and an AJP 
one on 8009, so there has to be a listener set up for each.  (BTW, unless 
you're front-ending Tomcat with IIS or httpd, you don't need the AJP 
Connector.)

 I am testing the server on localHost and am getting
 Proto  Local Address  Foreign AddressState
 PID
  TCP127.0.0.1:8005 0.0.0.0:0  LISTENING
 520

 Is this valid since I using localHost?

No - it shows that *something* is listening on 8005, but it's not likely to be 
Tomcat.  Use the Task Manager to find out what PID 520 is.  As I mentioned 
before, lots of products have Tomcat embedded in them, and at least one 
(VMware) leaves the shutdown port set to the default, creating difficulty for 
anyone trying to run an out-of-the-box Tomcat.

 (4)If nothing else is using the ports that I mentioned earlier when I
 use netstat -ano,  then why does it think there is a bind somewhere?

Something *is* using 8005, which will interfere with a Tomcat configured with 
the default shutdown port.

And again, be wary of running Tomcat under Eclipse, since Eclipse likes to use 
its own Tomcat configuration, not the one you thing you've set up.

 - Chuck

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: [OT] Tomcat dies suddenly

 From: André Warnier [mailto:a...@ice-sa.com]
 Subject: Re: [OT] Tomcat dies suddenly

 Maybe we should also investigate if the SegFaults are simultaneous with
 anyone specific entering the room where the servers are.

Ah yes, the old nylon underwear problem...

Or the pizza with plutonium toppings.

 - Chuck

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

RE: Socket Error in tomcat, white screen in browser

No - it shows that *something* is listening on 8005, but it's not likely to
be Tomcat. Use the Task Manager to find out what PID 520 is. As I
mentioned before, lots of products have Tomcat embedded in them, and at
least one (VMware) leaves the shutdown port set to the default, creating
difficulty for anyone trying to run an out-of-the-box Tomcat.

Something *is* using 8005, which will interfere with a Tomcat configured
with the default shutdown port.

And again, be wary of running Tomcat under Eclipse, since Eclipse likes to
use its own Tomcat configuration, not the one you thing you've set up.

The wierd thing about all of this is whenever I shut my tomcat down then the
127.0.0.1:8005 dissapears from the netstat list. This leads me to believe
that it is Tomcat which is using this. This also leads me to believe there
is something funky with eclipse's setup with Tomcat. Maybe the best
solution is to reinstall it? (I need to use it under eclipse for the
application I am creating JavaServlets/JSPs) If Eclipse uses its own
settings, then how do I make it use Tomcat's or vice versa or is there a
manual on this specific problem with eclipse and Tomcat getting confused
with one anothers configuration settings?

--
View this message in context:
http://old.nabble.com/Socket-Error-in-tomcat%2C-white-screen-in-browser-tp27567722p27579543.html
Sent from the Tomcat - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Socket Error in tomcat, white screen in browser

 From: millerKiller [mailto:smille8...@hotmail.com]
 Subject: RE: Socket Error in tomcat, white screen in browser

 The wierd thing about all of this is whenever I shut my tomcat down
 then the 127.0.0.1:8005 dissapears from the netstat list.

Again, use Task Manager to verify - you don't need to guess.  Does netstat show 
any other ports used by that PID?

 This also leads me to believe there is something funky with 
 eclipse's setup with Tomcat.

As we've been saying.  Personally, I never run Tomcat under an IDE because I 
don't want to introduce another layer of complication (and confusion).  There 
are certainly plenty of people who do control Tomcat with Eclipse, but doing so 
is a topic for an Eclipse mailing list.

 - Chuck

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Socket Error in tomcat, white screen in browser

2010-02-13 Thread Ken Bowen

Note that http://wiki.eclipse.org/WTP_Tomcat_FAQ has gobs of
(sometimes opaque) information about Eclipse and Tomcat. If you
configure Eclipse to use an external (separate) Tomcat, it uses the
external Tomcat , but at minimum, distorts the logging configuration
to just run catalina.out through its console. If you need to dig in
to a custom launch configuration for Tomcat under Eclipse, the FAQ
above has entries about that.

On Feb 13, 2010, at 6:19 PM, millerKiller wrote:

No - it shows that *something* is listening on 8005, but it's not
likely to

be Tomcat. Use the Task Manager to find out what PID 520 is. As I
mentioned before, lots of products have Tomcat embedded in them, and
at
least one (VMware) leaves the shutdown port set to the default,
creating

difficulty for anyone trying to run an out-of-the-box Tomcat.

Something *is* using 8005, which will interfere with a Tomcat
configured

with the default shutdown port.

And again, be wary of running Tomcat under Eclipse, since Eclipse
likes to

use its own Tomcat configuration, not the one you thing you've set up.

is something funky with eclipse's setup with Tomcat. Maybe the best
solution is to reinstall it? (I need to use it under eclipse for the
application I am creating JavaServlets/JSPs) If Eclipse uses its own
settings, then how do I make it use Tomcat's or vice versa or is
there a
manual on this specific problem with eclipse and Tomcat getting
confused

with one anothers configuration settings?

--
View this message in context:
http://old.nabble.com/Socket-Error-in-tomcat%2C-white-screen-in-browser-tp27567722p27579543.html
Sent from the Tomcat - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Socket Error in tomcat, white screen in browser


Maybe I should move this to the eclipse forums.  Before I go though, then
could we finish up with a few more things that I found and see if anyone
knows?  

I looked at my netstat and saw the following:


127.0.0.1:2402   127.0.0.1:2403 Established 4360
127.0.0.1:2403   127.0.0.1:2402 Established 3140
127.0.0.1:8005   0.0.0.0:0 Listening3140

This only appears when I start Tomcat in eclipse.  It looks to me like 2402
and 2403 are connected to each other through PID 4360.8005 then attempts
to connect, but PID 3140 is allready being used.  Is this look like the
problem?  If it is, then what can I do to fix it?

In the task manager then PID 3140 is javaw.exe and PID 4360 is eclipse.exe. 
When I kill either of these then they dont appear in netstat anymore.  any
ideas?
-- 
View this message in context: 
http://old.nabble.com/Socket-Error-in-tomcat%2C-white-screen-in-browser-tp27567722p27579882.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Alias not working for me in Tomcat 6.0.24

2010-02-13 Thread Peter McNeil


G'day,

I have the following Host setup in server.xml:-
   ...
Host name=cjugaustralia.org appBase=cjugapps
unpackWARs=true autoDeploy=true
xmlValidation=false xmlNamespaceAware=false
Aliaswww.cjugaustraila.org/Alias
Valve className=org.apache.catalina.valves.AccessLogValve 
directory=logs
   prefix=cjug_access_log. suffix=.txt pattern=common 
resolveHosts=false/

/Host
/Engine

I can happily access http://cjugaustralia.org but 
http://www.cjugaustralia.org shows the default localhost apache tomcat 
page, so it seems to be completely ignoring the Alias


Any thoughts on what is happening here? BTW I have a few virtual host 
set up in this server.xml all work, but none have Alias tags.


Cheers,
Peter.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Alias not working for me in Tomcat 6.0.24

2010/2/14 Peter McNeil pe...@mcneils.net:

Here is a patch for you:
-  Aliaswww.cjugaustraila.org/Alias
+ Aliaswww.cjugaustralia.org/Alias

Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Alias not working for me in Tomcat 6.0.24

2010-02-13 Thread Peter McNeil


On 14/02/10 13:58, Konstantin Kolinko wrote:

2010/2/14 Peter McNeilpe...@mcneils.net:

Here is a patch for you:
-Aliaswww.cjugaustraila.org/Alias
+Aliaswww.cjugaustralia.org/Alias

Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
   
lol, you're suggesting that the whitespace in front of the tag is a 
problem? happens to be a tab in this case, sure I prefer spaces but that 
should make no difference... and, of course, it doesn't... thanks for 
coming in ;-)


Cheers,
Peter.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Alias not working for me in Tomcat 6.0.24

2010/2/14 Peter McNeil pe...@mcneils.net:
 On 14/02/10 13:58, Konstantin Kolinko wrote:

 2010/2/14 Peter McNeilpe...@mcneils.net:

 Here is a patch for you:
 -Aliaswww.cjugaustraila.org/Alias
 +Aliaswww.cjugaustralia.org/Alias


 lol, you're suggesting that the whitespace in front of the tag is a problem?
 happens to be a tab in this case, sure I prefer spaces but that should make
 no difference... and, of course, it doesn't... thanks for coming in ;-)

No, I am suggesting that  *LIA.ORG != *ILA.ORG

Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Alias not working for me in Tomcat 6.0.24

2010-02-13 Thread Peter McNeil


On 14/02/10 14:38, Konstantin Kolinko wrote:

2010/2/14 Peter McNeilpe...@mcneils.net:
   

On 14/02/10 13:58, Konstantin Kolinko wrote:
 

2010/2/14 Peter McNeilpe...@mcneils.net:

Here is a patch for you:
-Aliaswww.cjugaustraila.org/Alias
+Aliaswww.cjugaustralia.org/Alias

   

lol, you're suggesting that the whitespace in front of the tag is a problem?
happens to be a tab in this case, sure I prefer spaces but that should make
no difference... and, of course, it doesn't... thanks for coming in ;-)
 

No, I am suggesting that  *LIA.ORG != *ILA.ORG

Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
   

ROFL - I completely missed that so many times - thanks!

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: [OT] Tomcat dies suddenly

2010-02-13 Thread Jorge Medina

There have been 144 messages on this thread...and you have spent already
months trying to solve the problem...I think it will be more cost effective
to replace the boxes, run a standard JVM from Sun..and close this
thread!

On Sat, Feb 13, 2010 at 6:11 PM, Caldarale, Charles R 
chuck.caldar...@unisys.com wrote:

  From: André Warnier [mailto:a...@ice-sa.com]
  Subject: Re: [OT] Tomcat dies suddenly

  Maybe we should also investigate if the SegFaults are simultaneous with
  anyone specific entering the room where the servers are.

 Ah yes, the old nylon underwear problem...

 Or the pizza with plutonium toppings.

  - Chuck

 THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
 MATERIAL and is thus for use only by the intended recipient. If you received
 this in error, please contact the sender and delete the e-mail and its
 attachments from all computers.

Re: [OT] Tomcat dies suddenly

2010-02-13 Thread anthonyvierra

CentOS, Sun JVM, IBM Hardware = 100% Uptime

On Sat, Feb 13, 2010 at 9:44 PM, Jorge Medina
cerebrotecnolog...@gmail.comwrote:

 There have been 144 messages on this thread...and you have spent already
 months trying to solve the problem...I think it will be more cost effective
 to replace the boxes, run a standard JVM from Sun..and close this
 thread!

 On Sat, Feb 13, 2010 at 6:11 PM, Caldarale, Charles R 
 chuck.caldar...@unisys.com wrote:

   From: André Warnier [mailto:a...@ice-sa.com]
   Subject: Re: [OT] Tomcat dies suddenly
  
   Maybe we should also investigate if the SegFaults are simultaneous with
   anyone specific entering the room where the servers are.
 
  Ah yes, the old nylon underwear problem...
 
  Or the pizza with plutonium toppings.
 
   - Chuck
 
 
  THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
  MATERIAL and is thus for use only by the intended recipient. If you
 received
  this in error, please contact the sender and delete the e-mail and its
  attachments from all computers.

Tomcat not seeing servlet

2010-02-13 Thread David Short

Hello,

 

I'm having a problem with Tomcat no seeing my servlet.  I have the servlet
defined and mapped in my web.xml file.  I've been Googling this for hours
and every example I find instructs to use the following setup.

 

Web.xml snippet:

 

servlet

servlet-nameAuthLoginServlet/servlet-name

servlet-classservlets.AuthLoginServlet/servlet-class

/servlet

 

servlet-mapping

servlet-nameAuthLoginServlet/servlet-name

url-pattern/AuthLogin/url-pattern

/servlet-mapping

 

 

 

Login.jsp snippet:

 

form name=login method=post action=/AuthLogin

 

 

 

Error message:

HTTP Status 404 - /AuthLogin

  _  

type Status report

message /AuthLogin

description The requested resource (/AuthLogin) is not available.

  _  

Apache Tomcat/6.0.20

 

Configuration

Tomcat 6.0.20 (port 80)

XP Pro

 

Any help would be greatly appreciated.

RE: Tomcat not seeing servlet