Re: FW: question regarding 'mod_jk: error flushing'
Hi Durk, are you really talking about mod_jk? Yep, the package apache2-jakarta-tomcat-connectors contains (from the included README file): 1. mod_jk + Ajp13Connector 2. mod_jk2 + CoyoteConnector + JkCoyoteHandler 3. mod_webapp + WarpConnector 2 is experimental, 3 is deprected, we're using option 1; mod_jk. If yes: which version of nod_jk are you using? It would be nice, if you could check version 1.2.19. It was kinda hard to figure out the version... I've grepped in /usr/lib/apache2/mod_jk.so for '1.2', and it came up with 1.2.6-dev. Source for the apache2-jakarta-tomcat-connectors package was a tarball called jakarta-tomcat-connectors-4.1.30-src.tar.gz. 4.1.30 seems to be the version of connector bundle. I found the jk-version in jakarta-tomcat-connectors-4.1.30-src/jk/native/common/jk_version.h, which shows: 1.2.6, just as expected. Replacing this version with 1.2.9 isn't quite easy considering maintenance. The version that came with the SUSE-distribution ensures stability/compatibility (at least I may hope so considering it's an enterprise grade distro) and is easier maintainable (security updates just come with the update tool). Well, I COULD do some tests with other versions of mod_jk on the testing system, but as long as the issue doesn't harm the functionality of the web applications, I'm hesitating a little in investing my time and downtime of the system. But then again, IF a new version of mod_jk would eliminate the error messages, we still don't know why or what it actually was. Durk Regards, Rainer Durk Strooisma wrote: Hi all! I'm wondering the same. I've got four servers (two production machines and their testing counter parts) running SUSE Linux Enterprise Server 9 with Apache 2, Tomcat 5, and ModJK. Below the relevant packages are shown: apache2 2.0.49-27.59 apache2-prefork 2.0.49-27.59 apache2-jakarta-tomcat-connectors 5.0.19-29.1 jakarta-tomcat5.0.19-29.1 Since June 2006 I'm getting lots of mod_jk: Error flushing \n on one production system (and its testing system as well), but everything seems to work fine... The other production system isn't affected. It's kind of annoying that there's no timestamp shown in the error message. Debugging is really tough this way. I'm wondering what it means and whether it's harmless or not. Like Kevin states, nowhere on the internet this question seems to answered. Thanks in advance! Durk Hello there, Does anyone know what is this 'mod_jk: error flushing' about? I am using Tomcat 5.0, Apache and Mod_JK in production environment and keep getting this error in error log. I do google search and find lots of persons asking this question but no answer. Can anybody having experience with this shed a light on what it might be and how to resolve it? Thanks a lot, Kevin Song - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- kippdata informationstechnologie GmbH Bornheimer Str. 33a 53111 Bonn Tel. 0228/98549-0 Fax 0228/98549-50 www.kippdata.de === kippdata informationstechnologie GmbH Bornheimer Str. 33a D-53111 Bonn Germany Tel. +49/228/98549-0 Fax +49/228/98549-50 www.kippdata.de - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Re: JNDIRealm exception
After some further investigation I saw the follwing...
If my user is in the first directory i'm binding to then the result.
getName() (JNDIRealm.java 1079) statement returns
CN=dasquery,OU=Herisau-AR-NET and everything works as expected.
If the user is found in a referral domain than the same statement
returns
ldap://teufen.ar-net.ch:389/CN=Test-Query,OU=Benutzer,DC=teufen,
DC=ar-net,DC=ch.
this result is not parsable as the exception says. But for me it is
a correct answer from Ad with referral=follow. Is this a bug in
JNDIRealm??
Ursprüngliche Nachricht
Von: [EMAIL PROTECTED]
Datum: 31.10.2006 15:14
An: Tomcat Users Listusers@tomcat.apache.org, [EMAIL PROTECTED]
ch
Betreff: Re: JNDIRealm exception
Hello
can we please see the statements leading up to NameParser.parse()
method call
are you able to ldapsearch using DC and OU parameters without CN?
M-
This e-mail communication and any attachments may contain
confidential and privileged information for the use of the
designated recipients named above. If you are not the intended
recipient, you are hereby notified that you have received
this communication in error and that any review, disclosure,
dissemination, distribution or copying of it or its
contents
- Original Message -
From: [EMAIL PROTECTED]
To: users@tomcat.apache.org
Sent: Tuesday, October 31, 2006 7:00 AM
Subject: JNDIRealm exception
Problem with JNDIRealm
I successfully authenticate my users against active Directory
(single domain). But now I have a setup with trusted domains and
the
authentication fails with the following exception.
Everything is working fine if my user is in the domain ar-net.
ch.
Now I want to authenticate a user in the Domain teufen.ar-net.
ch.
As I see with Ethereal, referrals are followed and the user is
found.
But the user is not authenticated and the log shows the
following
exception.
Tomcat server is 5.5.15 and java is 1.5.0_06
Thank you for any clue
Exception performing authentication
javax.naming.InvalidNameException: Invalid name: ldap:
at javax.naming.ldap.Rfc2253Parser.doParse(Unknown
Source)
at javax.naming.ldap.Rfc2253Parser.parseDn(Unknown
Source)
at javax.naming.ldap.LdapName.parse(Unknown Source)
at javax.naming.ldap.LdapName.init(Unknown Source)
at com.sun.jndi.ldap.LdapNameParser.parse(Unknown
Source)
at org.apache.catalina.realm.JNDIRealm.
getUserBySearch
(JNDIRealm.java:1079)
at org.apache.catalina.realm.JNDIRealm.getUser
(JNDIRealm.java:958)
at org.apache.catalina.realm.JNDIRealm.authenticate
(JNDIRealm.java:907)
at org.apache.catalina.realm.JNDIRealm.authenticate
(JNDIRealm.java:808)
at org.apache.catalina.authenticator.
FormAuthenticator.
authenticate(FormAuthenticator.java:257)
at org.apache.catalina.authenticator.
AuthenticatorBase.
invoke(AuthenticatorBase.java:416)
at org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke
(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.
invoke
(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.
service
(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process
(Http11Processor.java:869)
at org.apache.coyote.http11.
Http11BaseProtocol$Http11ConnectionHandler.processConnection
(Http11BaseProtocol.java:667)
at org.apache.tomcat.util.net.PoolTcpEndpoint.
processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.
LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:
80)
at org.apache.tomcat.util.threads.
ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Unknown Source)
31.10.2006 08:57:59 org.apache.catalina.realm.JNDIRealm close
Here is the config?
Realm name=myrealm
className=org.apache.catalina.realm.JNDIRealm debug=99
connectionName=CN=dasquery,OU=Herisau-AR-NET,DC=ar-net,DC=ch
connectionPassword=not public
connectionURL=ldap://s1.ar-net.ch:389;
userBase=DC=ar-net,DC=ch
userSubtree=true
userSearch=userPrincipalName=
{0}
roleName=cn
roleSearch=(member={0})
roleBase=OU=DASGROUPS,OU=Herisau-AR-NET,DC=ar-net,DC=ch
referrals=follow
/
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL
Tomcat at port 443
Hi all, I have to modify the default tomcat port 8080 to another port because there is a another application running at port 8080. If I want to connect on https I get an error message that the connection is refused. What must I else modify to connect at https when tomcat is running at a non default port. Best regards -- Dr. Andrea König (Entwicklung) G.punkt - medical services Halberstädter Str. 115A Eiskellerpassage 39112 Magdeburg Tel: +49 391 280380 Fax: +49 391 2803822 Inet: www.gmatic.de mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat at port 443
Have you uncommented the https connector in the server.xml? By default it is commented out as shown below !-- Define a SSL HTTP/1.1 Connector on port 8443 -- !-- Connector port=8443 maxHttpHeaderSize=8192 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false disableUploadTimeout=true acceptCount=100 scheme=https secure=true clientAuth=false sslProtocol=TLS / -- Ben On 11/1/06, Andrea König [EMAIL PROTECTED] wrote: Hi all, I have to modify the default tomcat port 8080 to another port because there is a another application running at port 8080. If I want to connect on https I get an error message that the connection is refused. What must I else modify to connect at https when tomcat is running at a non default port. Best regards -- Dr. Andrea König (Entwicklung) G.punkt - medical services Halberstädter Str. 115A Eiskellerpassage 39112 Magdeburg Tel: +49 391 280380 Fax: +49 391 2803822 Inet: www.gmatic.de mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Handling expired client certificate
Hi, I've configured Tomcat 5.5.17 to use CLIENT-CERT as authentication mechanism via web.xml in my web application. This works as expected and the user gets prompted for a certificate. I'm facing a problem, because when the user supplies a certificate that has expired Tomcat throws an exception in the log like this: INFO: SSL Error getting client Certs javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateExpiredException: NotAfter: Thu Jan 19 08:40:14 CET 2 006 at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1518) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:174) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:168) at com.sun.net.ssl.internal.ssl.ServerHandshaker.clientCertificate(ServerHandshaker.java:1098) at com.sun.net.ssl.internal.ssl.ServerHandshaker.processMessage(ServerHandshaker.java:187) at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:495) at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:433) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:818) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:680) at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75) at java.io.InputStream.read(InputStream.java:89) at org.apache.tomcat.util.net.jsse.JSSE14Support.synchronousHandshake(JSSE14Support.java:87) at org.apache.tomcat.util.net.jsse.JSSE14Support.handShake(JSSE14Support.java:66) at org.apache.tomcat.util.net.jsse.JSSESupport.getPeerCertificateChain(JSSESupport.java:120) at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:1126) at org.apache.coyote.Request.action(Request.java:348) at org.apache.catalina.authenticator.SSLAuthenticator.authenticate(SSLAuthenticator.java:134) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java :664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Caused by: java.security.cert.CertificateExpiredException: NotAfter: Thu Jan 19 08:40:14 CET 2006 at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:256) at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:570) at sun.security.validator.SimpleValidator.engineValidate(SimpleValidator.java:123) at sun.security.validator.Validator.validate(Validator.java:203) at sun.security.validator.Validator.validate(Validator.java:172) at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkClientTrusted(X509TrustManagerImpl.java:142) at com.sun.net.ssl.internal.ssl.JsseX509TrustManager.checkClientTrusted(SSLContextImpl.java:303) at com.sun.net.ssl.internal.ssl.ServerHandshaker.clientCertificate(ServerHandshaker.java:1091) ... 24 more 2006-11-01 11:27:58 org.apache.coyote.http11.Http11Processor action WARNING: Exception getting SSL attributes javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateExpiredException: NotAfter: Thu Jan 19 08:40:14 CET 2 006 at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1518) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:174) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:168) at com.sun.net.ssl.internal.ssl.ServerHandshaker.clientCertificate(ServerHandshaker.java:1098) at com.sun.net.ssl.internal.ssl.ServerHandshaker.processMessage(ServerHandshaker.java:187) at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:495) at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:433) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:818) at
Re: load balancing with controlled failover
Hi Gary, from my understanding of the code mod_proxy(_balancer) at the moment is not able to do that. There are status settings disable and stopped one can set, but at the moment disbled and stopped behave the same. I didn't really try, but I derive that from looking at the code. This holds true for version 2.2.3, the head of branch 2.2 and trunk as well. I remember some mail on httpd-dev, that this is known and will be corrected. The module mod_jk also has the concept of disable and stop. For mod_jk disable means, that requests with sessions on a disabled target still get routed there, but requests without a session do not get routed to a disabled target. So if your sessions are relatively short, you can considerably decrease the number of remaining sessions on a target by disabling it some time before your maintenance. I'm sure, this behaviour will come to mod_proxy too, but it looks like it's not there yet. Anybody: please correct me if I'm wrong. If you are going to use mod_jk, please get the latest release 1.2.19. It's important to know, that mod_jk can only handle ajp backends. Regards Gary Feltham schrieb: Hi, I have a load balancing setup using Apache 2.2.2 (Win32) and 2 instances of Tomcat 5.5.15 and 5.5.17. So far I have been able to establish a successful load balancing using sticky sessions with the following config: ProxyPass /test balancer://testcluster stickysession=JSESSIONID nofailover=On Proxy balancer://testcluster BalancerMember ajp://127.0.0.1:18009/test smax=5 route=node01 BalancerMember ajp://127.0.0.1:28009/test smax=5 route=node02 /Proxy I am not wanting to setup a tomcat cluster for this deployment but have 2 independant instances of tomcat running independant sessions. Currently this is also setup to not failover if an instance goes down. For instance node01 is shutdown, the status is: LoadBalancer Status for balancer://testcluster StickySession Timeout FailoverAttemptsMethod JSESSIONID 0 1 byrequests Worker URL Route RouteRedir Factor Status ajp://127.0.0.1:18009/test node01 1 Err ajp://127.0.0.1:28009/test node02 1 Ok All expected and a request to node 1 results in a 503 response. My question therefore is: Within the context of a scheduled down time such as redeployment of the application or reboot of the server I would like to be able to control closure of the load balancer. For example, node 1 is targeted to be shutdown for maintenance, currently I have 10 user sessions on that instance and say 9 on node 2. If new users join then the load balancer will evenly distribute to each node per request. What I want to control is that each NEW user should only go to node 2, then each session on node 1 will expire eventually leaving 0 sessions on node 1. Node 1 can then be removed cleanly for maintenance and its status set as disabled. Is there a current method of performing this in either mod_proxy or mod_jk - I don't mind which but would like to gain that control? Many thanks, Gary Feltham - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat at port 443
Andrea König wrote: I have to modify the default tomcat port 8080 to another port because there is a another application running at port 8080. If I want to connect on https I get an error message that the connection is refused. What must I else modify to connect at https when tomcat is running at a non default port. 1. To change the ports Tomcat binds to, modify conf/server.xml appropriately: http://tomcat.apache.org/tomcat-5.5-doc/config/http.html (if you're using Tomcat 5.5). 2. Accessing an HTTP Connector via HTTPS will not work - regardless whether or not Tomcat listens to the default port. If you want Tomcat to be accessible via HTTPS, you have to set up a HTTPS Connector. The stock web.xml contains one which is commented by default. Regards mks - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JNDI Realm and Active Directory root search
I'm trying to get a JNDI Realm working as one might expect with Active Directory. Tomcat 5.5.20 Java 1.5.06 Windows 2000 Server The basic issue is that searching from a domain root dc=company,dc=com and using userSubtree=true results in: Oct 31, 2006 3:18:20 PM org.apache.catalina.realm.JNDIRealm authenticate SEVERE: Exception performing authentication javax.naming.PartialResultException: Unprocessed Continuation Reference(s); remaining name 'dc=company,dc=com' If I use a more specific search base of ou=Employees,dc=company,dc=com and then the userSubtree is irrelevant, it works fine. Problem is our AD structure demands that users be in two different OU's and thus the search must be done from the root. I understand that AD does not handle referrals as expected and that could be contributing. http://www.mail-archive.com/cas@tp.its.yale.edu/msg00797.html In this case I suggest adjusting the local hosts file to fool DNS (c:\windows\system32\drivers\etc\hosts). Find out the wrong DNS name in the referral and point that name to your real AD. -- Velpi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat at port 443
Markus Schönhaber wrote: Connector. The stock web.xml contains one which is commented by default. make that server.xml ^^^ Regards mks - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FW: question regarding 'mod_jk: error flushing'
Hi Durk, the flushing has been changed in May 2005 around the time of version 1.2.13 or 1.2.14. Previously there were a lot of calls to ap_rflush() during the writing of responses. Because that produced many problems (not only log messages) concerning performance and memory requirements, these calls have been made optional. So updating to 1.2.19 really changes the flushing behaviour (and the log statement is not there any longer). The old behaviour (lots of flushing, but without the annoying log messages) can be configured with newer mod_jk with JkOptions +FlushPackets. That should only be necessary, if your application has complex timing requirements. Per default the switch is off. Regards, Rainer Durk Strooisma schrieb: Hi Durk, are you really talking about mod_jk? Yep, the package apache2-jakarta-tomcat-connectors contains (from the included README file): 1. mod_jk + Ajp13Connector 2. mod_jk2 + CoyoteConnector + JkCoyoteHandler 3. mod_webapp + WarpConnector 2 is experimental, 3 is deprected, we're using option 1; mod_jk. If yes: which version of nod_jk are you using? It would be nice, if you could check version 1.2.19. It was kinda hard to figure out the version... I've grepped in /usr/lib/apache2/mod_jk.so for '1.2', and it came up with 1.2.6-dev. Source for the apache2-jakarta-tomcat-connectors package was a tarball called jakarta-tomcat-connectors-4.1.30-src.tar.gz. 4.1.30 seems to be the version of connector bundle. I found the jk-version in jakarta-tomcat-connectors-4.1.30-src/jk/native/common/jk_version.h, which shows: 1.2.6, just as expected. Replacing this version with 1.2.9 isn't quite easy considering maintenance. The version that came with the SUSE-distribution ensures stability/compatibility (at least I may hope so considering it's an enterprise grade distro) and is easier maintainable (security updates just come with the update tool). Well, I COULD do some tests with other versions of mod_jk on the testing system, but as long as the issue doesn't harm the functionality of the web applications, I'm hesitating a little in investing my time and downtime of the system. But then again, IF a new version of mod_jk would eliminate the error messages, we still don't know why or what it actually was. Durk Regards, Rainer Durk Strooisma wrote: Hi all! I'm wondering the same. I've got four servers (two production machines and their testing counter parts) running SUSE Linux Enterprise Server 9 with Apache 2, Tomcat 5, and ModJK. Below the relevant packages are shown: apache2 2.0.49-27.59 apache2-prefork 2.0.49-27.59 apache2-jakarta-tomcat-connectors 5.0.19-29.1 jakarta-tomcat5.0.19-29.1 Since June 2006 I'm getting lots of mod_jk: Error flushing \n on one production system (and its testing system as well), but everything seems to work fine... The other production system isn't affected. It's kind of annoying that there's no timestamp shown in the error message. Debugging is really tough this way. I'm wondering what it means and whether it's harmless or not. Like Kevin states, nowhere on the internet this question seems to answered. Thanks in advance! Durk Hello there, Does anyone know what is this 'mod_jk: error flushing' about? I am using Tomcat 5.0, Apache and Mod_JK in production environment and keep getting this error in error log. I do google search and find lots of persons asking this question but no answer. Can anybody having experience with this shed a light on what it might be and how to resolve it? Thanks a lot, Kevin Song - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- kippdata informationstechnologie GmbH Bornheimer Str. 33a 53111 Bonn Tel. 0228/98549-0 Fax 0228/98549-50 www.kippdata.de === kippdata informationstechnologie GmbH Bornheimer Str. 33a D-53111 Bonn Germany Tel. +49/228/98549-0 Fax +49/228/98549-50 www.kippdata.de - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat at port 443
Hi all, many thanks for your help. Modifying the appropriate connectors I could start tomcat at a non default port and could connect on https. Best regards -- Dr. Andrea König (Entwicklung) G.punkt - medical services Halberstädter Str. 115A Eiskellerpassage 39112 Magdeburg Tel: +49 391 280380 Fax: +49 391 2803822 Inet: www.gmatic.de mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
HTTP Status 408
Hi I am trying to setup my webapp. I am using: MS windows server 2003 Tomcat 5.5.20 MS SQL server 2000 I am trying to setup realm I get a login error when the username or password is wrong but when it is correct I get the following error HTTP Status 408 - The time allowed for the login process has been exceeded. If you wish to continue you must either click back twice and re-click the link you requested or close and re-open your browser type Status report message The time allowed for the login process has been exceeded. If you wish to continue you must either click back twice and re-click the link you requested or close and re-open your browser description The client did not produce a request within the time that the server was prepared to wait (The time allowed for the login process has been exceeded. If you wish to continue you must either click back twice and re-click the link you requested or close and re-open your browser). I really need help. Any info is greatly appriciated - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Please Help!Tomcat Not Running on Linux Fedora
From: Teh Noranis Mohd Aris [mailto:[EMAIL PROTECTED] Subject: Please Help!Tomcat Not Running on Linux Fedora Unfortunately, when I tried to execute Tomcat in the bin directory by typing ./startup.sh the following message appeared: The JAVA_HOME environment variable is not defined This environment variable is needed to run this program Read the RUNNING.txt file in the Tomcat base directory for the answer to this and other setup questions. - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HTTP Status 408
Søren, I get a login error when the username or password is wrong but when it is correct I get the following error HTTP Status 408 - The time allowed for the login process has been exceeded. If you wish to continue you must either click back twice and re-click the link you requested or close and re-open your browser This might happen if your session isn't found when you try to login. This might be caused by cookies being disabled, but the session if not being encoded in your login URL (i.e. /j_security_check;jsessionid=ABCD...). Otherwise, there are two possibilities: 1. You really are exceeding the session timeout before logging in (unlikely). 2. The session is not being found for some other reason. Maybe you have a proxy or load balancer something like that dropping the cookie? -chris signature.asc Description: OpenPGP digital signature
getting the full URL
I'm trying to do what should be a fairly easy thing, but I'm really tearing my hair out over this... All I want is to be able to get the full URL (including scheme, queryString, etc.). Right now, I'm trying something like: % out.write(request.getScheme() + :/ + request.getRequestURI().replace(jsp,do) + (request.getQueryString().length() 0 ? ? + request.getQueryString() : )); % It feels like this should be a simple, single call. Any takers? Thanks! Daniel
FAIL - Application at context path /jetspeed could not be started
Hi! While trying to start jetspeed I get an error message: FAIL - Application at context path /jetspeed could not be started catalina.2006-11-01.log fail shows several security role errors: Nov 1, 2006 3:58:13 PM org.apache.coyote.http11.Http11AprProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 Nov 1, 2006 3:58:13 PM org.apache.coyote.ajp.AjpAprProtocol init INFO: Initializing Coyote AJP/1.3 on ajp-8009 Nov 1, 2006 3:58:13 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1656 ms Nov 1, 2006 3:58:13 PM org.apache.catalina.core.StandardService start INFO: Starting service Catalina Nov 1, 2006 3:58:13 PM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.20 Nov 1, 2006 3:58:13 PM org.apache.catalina.core.StandardHost start INFO: XML validation disabled Nov 1, 2006 3:58:15 PM org.apache.catalina.startup.ContextConfig validateSecurityRoles INFO: WARNING: Security role name admin used in an auth-constraint without being defined in a security-role Nov 1, 2006 3:58:15 PM org.apache.catalina.core.StandardContext start SEVERE: Error listenerStart Nov 1, 2006 3:58:15 PM org.apache.catalina.core.StandardContext start SEVERE: Context [/jetspeed] startup failed due to previous errors Nov 1, 2006 3:58:17 PM org.apache.coyote.http11.Http11AprProtocol start INFO: Starting Coyote HTTP/1.1 on http-8080 Nov 1, 2006 3:58:17 PM org.apache.coyote.ajp.AjpAprProtocol start INFO: Starting Coyote AJP/1.3 on ajp-8009 Nov 1, 2006 3:58:17 PM org.apache.catalina.storeconfig.StoreLoader load INFO: Find registry server-registry.xml at classpath resource Nov 1, 2006 3:58:17 PM org.apache.catalina.startup.Catalina start INFO: Server startup in 4563 ms Nov 1, 2006 4:03:57 PM org.apache.catalina.startup.ContextConfig validateSecurityRoles INFO: WARNING: Security role name admin used in an auth-constraint without being defined in a security-role Nov 1, 2006 4:03:57 PM org.apache.catalina.core.StandardContext start SEVERE: Error listenerStart Nov 1, 2006 4:03:57 PM org.apache.catalina.core.StandardContext start SEVERE: Context [/jetspeed] startup failed due to previous errors As my C:\Tomcat\Tomcat 5.5\conf\tomcat-users.xml gives to user admin all possible roles, I do not understand what should I do to get the application running. ?xml version=1.0 encoding=utf-8 ? - tomcat-users role rolename=tomcat / role rolename=role1 / role rolename=manager / role rolename=admin / user username=tomcat password=tomcat roles=tomcat / user username=both password=tomcat roles=tomcat,role1 / user username=role1 password=tomcat roles=role1 / user username=admin password=remxxx fullName= roles=admin,manager,role1,tomcat / /tomcat-users Looking forward to advise, Evi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: getting the full URL
request.getRequestURL().toString(); getRequestURL is a StringBuffer of the full URL. Daniel Blumenthal wrote: I'm trying to do what should be a fairly easy thing, but I'm really tearing my hair out over this... All I want is to be able to get the full URL (including scheme, queryString, etc.). Right now, I'm trying something like: % out.write(request.getScheme() + :/ + request.getRequestURI().replace(jsp,do) + (request.getQueryString().length() 0 ? ? + request.getQueryString() : )); % It feels like this should be a simple, single call. Any takers? Thanks! Daniel - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Change Display Icon
From: Madhuraka Godahewa [mailto:[EMAIL PROTECTED] Subject: Change Display Icon But, still I have not been able to change the icon, which displayed on the browser (Firefox) when my site is loaded. The tomcat icon is shown. Firefox likes to hang onto the favicon, regardless of whether or not it changes on the web site. Try clearing the browser cache (Tools - Clear Private Data, select the cache check box). - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: FAIL - Application at context path /jetspeed could not be started
From: evimail [mailto:[EMAIL PROTECTED] Subject: FAIL - Application at context path /jetspeed could not be started While trying to start jetspeed I get an error message: FAIL - Application at context path /jetspeed could not be started Nov 1, 2006 3:58:15 PM org.apache.catalina.startup.ContextConfig validateSecurityRoles INFO: WARNING: Security role name admin used in an auth-constraint without being defined in a security-role As my C:\Tomcat\Tomcat 5.5\conf\tomcat-users.xml gives to user admin all possible roles, I do not understand what should I do to get the application running. This has nothing to do with what's in tomcat-users.xml - you're missing required security-role entries in the web.xml of the jetspeed app. See section 12 of the Servlet spec and look at Tomcat's manager app for examples. - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat-5.5.20 tld listeners from jars only from .../tomcat/common/lib?
Hi Zsolt- Straight from the doc http://tomcat.apache.org/tomcat-5.5-doc/class-loader-howto.html If you're using webappX classloader the search order is a.. Bootstrap classes of your JVM b.. System class loader classses (described above) a.. $CATALINA_HOME/bin/bootstrap.jar - Contains the main() method that is used to initialize the Tomcat 5 server, and the class loader implementation classes it depends on. b.. $JAVA_HOME/lib/tools.jar - Contains the javac compiler used to convert JSP pages into servlet classes. c.. $CATALINA_HOME/bin/commons-logging-api.jar - Jakarta commons logging API. d.. $CATALINA_HOME/bin/commons-daemon.jar - Jakarta commons daemon API. e.. jmx.jar - The JMX 1.2 implementation. c.. /WEB-INF/classes of your web application d.. /WEB-INF/lib/*.jar of your web application e.. $CATALINA_HOME/common/classes f.. $CATALINA_HOME/common/endorsed/*.jar g.. $CATALINA_HOME/common/i18n/*.jar h.. $CATALINA_HOME/common/lib/*.jar i.. $CATALINA_BASE/shared/classes j.. $CATALINA_BASE/shared/lib/*.jar Martin-- This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents - Original Message - From: Zsolt [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Tuesday, October 24, 2006 10:13 AM Subject: tomcat-5.5.20 tld listeners from jars only from .../tomcat/common/lib? Hi, After some debuging I have the impressions that tomcat-5.5.20 searches for tld listeners only in jars files under /tomcat/common/lib. Am I right? Is that a bug or a (new) feature? Zsolt - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: getting the full URL
Dan-
iterate thru all of the header variables and print the header variable..
%
Enumeration headerNames = request.getHeaderNames();
while(headerNames.hasMoreElements())
{
String headerName = (String)headerNames.nextElement();
out.print(TRTD + headerName);
out.println(request.getHeader(headerName)+/TD/TR);
}
%
Anyone else?
M-
This e-mail communication and any attachments may contain confidential and
privileged information for the use of the
designated recipients named above. If you are not the intended recipient, you
are hereby notified that you have received
this communication in error and that any review, disclosure, dissemination,
distribution or copying of it or its
contents
- Original Message -
From: Daniel Blumenthal [EMAIL PROTECTED]
To: 'Tomcat Users List' users@tomcat.apache.org
Sent: Wednesday, November 01, 2006 8:37 AM
Subject: getting the full URL
I'm trying to do what should be a fairly easy thing, but I'm really tearing
my hair out over this...
All I want is to be able to get the full URL (including scheme, queryString,
etc.). Right now, I'm trying something like:
%
out.write(request.getScheme() + :/ +
request.getRequestURI().replace(jsp,do) +
(request.getQueryString().length() 0 ? ? + request.getQueryString() :
));
%
It feels like this should be a simple, single call. Any takers?
Thanks!
Daniel
Re: Handling expired client certificate
On 11/1/06, Subscriber [EMAIL PROTECTED] wrote: Hi, I've configured Tomcat 5.5.17 to use CLIENT-CERT as authentication mechanism via web.xml in my web application. This works as expected and the user gets prompted for a certificate. I'm facing a problem, because when the user supplies a certificate that has expired Tomcat throws an exception in the log like this: INFO: SSL Error getting client Certs javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateExpiredException: NotAfter: Thu Jan 19 08:40:14 CET 2 006 My problem is, that I would like to handle the case myself and avoid exceptions in the log and present the user with a good error message. In this case, the user has no clue what-so-ever of what happened because the error remains within Tomcat. What can I do to catch the error myself? Have you tried something like this in your web.xml? error-page exception-typejava.security.cert.CertificateExpiredException/exception-type location/WEB-INF/errors/expired.jsp/location /error-page -- Hassan Schroeder [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat-5.5.20 tld listeners from jars only from .../tomcat/common/lib?
While this relevant to a more generic question of classloaders, it doesn't address the OP's issue. Zsolt -- can we get a bit more context for this? My experience with taglibs is they work just find under tc 5.5.x. --David Martin Gainty wrote: Hi Zsolt- Straight from the doc http://tomcat.apache.org/tomcat-5.5-doc/class-loader-howto.html If you're using webappX classloader the search order is a.. Bootstrap classes of your JVM b.. System class loader classses (described above) a.. $CATALINA_HOME/bin/bootstrap.jar - Contains the main() method that is used to initialize the Tomcat 5 server, and the class loader implementation classes it depends on. b.. $JAVA_HOME/lib/tools.jar - Contains the javac compiler used to convert JSP pages into servlet classes. c.. $CATALINA_HOME/bin/commons-logging-api.jar - Jakarta commons logging API. d.. $CATALINA_HOME/bin/commons-daemon.jar - Jakarta commons daemon API. e.. jmx.jar - The JMX 1.2 implementation. c.. /WEB-INF/classes of your web application d.. /WEB-INF/lib/*.jar of your web application e.. $CATALINA_HOME/common/classes f.. $CATALINA_HOME/common/endorsed/*.jar g.. $CATALINA_HOME/common/i18n/*.jar h.. $CATALINA_HOME/common/lib/*.jar i.. $CATALINA_BASE/shared/classes j.. $CATALINA_BASE/shared/lib/*.jar Martin-- This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents - Original Message - From: Zsolt [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Tuesday, October 24, 2006 10:13 AM Subject: tomcat-5.5.20 tld listeners from jars only from .../tomcat/common/lib? Hi, After some debuging I have the impressions that tomcat-5.5.20 searches for tld listeners only in jars files under /tomcat/common/lib. Am I right? Is that a bug or a (new) feature? Zsolt - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: getting the full URL
Martin,
Martin Gainty wrote:
Dan-
iterate thru all of the header variables and print the header variable..
%
Enumeration headerNames = request.getHeaderNames();
while(headerNames.hasMoreElements())
{
String headerName = (String)headerNames.nextElement();
out.print(TRTD + headerName);
out.println(request.getHeader(headerName)+/TD/TR);
}
%
Dude, WTF are you talking about? Headers don't go in the URL. This
question was already answered correctly by someone who apparently
actually read the OP.
:(
-chris
signature.asc
Description: OpenPGP digital signature
Re: load balancing with controlled failover
This is expected to be added to the proxy module, but in a way which is more inline with expectations for a specific proxy server (whether serving ajp or http or anything else). On Nov 1, 2006, at 5:39 AM, Rainer Jung wrote: Hi Gary, from my understanding of the code mod_proxy(_balancer) at the moment is not able to do that. There are status settings disable and stopped one can set, but at the moment disbled and stopped behave the same. I didn't really try, but I derive that from looking at the code. This holds true for version 2.2.3, the head of branch 2.2 and trunk as well. I remember some mail on httpd-dev, that this is known and will be corrected. The module mod_jk also has the concept of disable and stop. For mod_jk disable means, that requests with sessions on a disabled target still get routed there, but requests without a session do not get routed to a disabled target. So if your sessions are relatively short, you can considerably decrease the number of remaining sessions on a target by disabling it some time before your maintenance. I'm sure, this behaviour will come to mod_proxy too, but it looks like it's not there yet. Anybody: please correct me if I'm wrong. If you are going to use mod_jk, please get the latest release 1.2.19. It's important to know, that mod_jk can only handle ajp backends. Regards Gary Feltham schrieb: Hi, I have a load balancing setup using Apache 2.2.2 (Win32) and 2 instances of Tomcat 5.5.15 and 5.5.17. So far I have been able to establish a successful load balancing using sticky sessions with the following config: ProxyPass /test balancer://testcluster stickysession=JSESSIONID nofailover=On Proxy balancer://testcluster BalancerMember ajp://127.0.0.1:18009/test smax=5 route=node01 BalancerMember ajp://127.0.0.1:28009/test smax=5 route=node02 /Proxy I am not wanting to setup a tomcat cluster for this deployment but have 2 independant instances of tomcat running independant sessions. Currently this is also setup to not failover if an instance goes down. For instance node01 is shutdown, the status is: LoadBalancer Status for balancer://testcluster StickySession Timeout FailoverAttemptsMethod JSESSIONID 0 1 byrequests Worker URL Route RouteRedir Factor Status ajp://127.0.0.1:18009/test node01 1 Err ajp://127.0.0.1:28009/test node02 1 Ok All expected and a request to node 1 results in a 503 response. My question therefore is: Within the context of a scheduled down time such as redeployment of the application or reboot of the server I would like to be able to control closure of the load balancer. For example, node 1 is targeted to be shutdown for maintenance, currently I have 10 user sessions on that instance and say 9 on node 2. If new users join then the load balancer will evenly distribute to each node per request. What I want to control is that each NEW user should only go to node 2, then each session on node 1 will expire eventually leaving 0 sessions on node 1. Node 1 can then be removed cleanly for maintenance and its status set as disabled. Is there a current method of performing this in either mod_proxy or mod_jk - I don't mind which but would like to gain that control? Many thanks, Gary Feltham - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Unable to read TLD META-INF/c.tld from JAR file
Hello! Strange problem appears with Tomcat. It can't read the tlds from JAR file (standard.jar). org.apache.jasper.JasperException: Unable to read TLD META-INF/c.tld from JAR file It happens only once when Tomcat/work folder is empty. After page refresh everything goes well. Details: 1. Tomcat 5.0.28 2. J2SDK 1.4.2_02 3. standard.jar is not corrupted and includes all tlds in META-INF 4. WEB-INF/lib doesn't contain jsp-api.jar Any ideas? Thanks in advance Best regards, Vasiliy - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JNDI Realm and Active Directory root search
With that lead, I figured out what was going on. Two issues: - referrals=follow is required if you search from the top of an ldap tree instead of a specific OU. That property is not documented in Tomcat docs as it might be: http://tomcat.apache.org/tomcat-5.5-doc/realm-howto.html#JNDIRealm Without it, you'll get a javax.naming.PartialResultException: Unprocessed Continuation Reference(s); remaining name 'dc=company,dc=com' - The referral URL returned by AD is not why one might expect. If your Tomcat server is NOT using DNS provided by the AD server you will likely run into a problem. When searching LDAP from the root, you will get a referral reply from AD that has a server DNS name of JUST the domain name (ie company.com). NOT the initial server name you used in your connectionURL. If your DNS or your local hosts files does not resolve that root domain name to an AD server, it will throw a javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: company.com:389 [Root exception is java.net.UnknownHostException: company.com]] I've tried to update this integration guide. Hopefully The Google will help others in the future: http://www.jspwiki.org/wiki/ActiveDirectoryIntegration http://www.mail-archive.com/cas@tp.its.yale.edu/msg00797.html In this case I suggest adjusting the local hosts file to fool DNS (c:\windows\system32\drivers\etc\hosts). Find out the wrong DNS name in the referral and point that name to your real AD. -- Velpi I'm trying to get a JNDI Realm working as one might expect with Active Directory. Tomcat 5.5.20 Java 1.5.06 Windows 2000 Server The basic issue is that searching from a domain root dc=company,dc=com and using userSubtree=true results in: Oct 31, 2006 3:18:20 PM org.apache.catalina.realm.JNDIRealm authenticate SEVERE: Exception performing authentication javax.naming.PartialResultException: Unprocessed Continuation Reference(s); remaining name 'dc=company,dc=com' If I use a more specific search base of ou=Employees,dc=company,dc=com and then the userSubtree is irrelevant, it works fine. Problem is our AD structure demands that users be in two different OU's and thus the search must be done from the root. I understand that AD does not handle referrals as expected and that could be contributing. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Handling expired client certificate
Hi Hassan, Thanks for your answer. Yes, I've already tried your suggestion. Both with the java.security.cert.CertificateExpiredException and the javax.net.ssl.SSLHandshakeException, but the problem remains. As I can see, the exception is thrown somewhere inside Tomcat, before handling control to the webapplication. Hence, the exception is not catchable inside my webapplication, but is to be handled in some other way inside the Tomcat engine. ...Suggestions are still very welcome :-) regards, kews Hassan Schroeder wrote: On 11/1/06, Subscriber [EMAIL PROTECTED] wrote: Hi, I've configured Tomcat 5.5.17 to use CLIENT-CERT as authentication mechanism via web.xml in my web application. This works as expected and the user gets prompted for a certificate. I'm facing a problem, because when the user supplies a certificate that has expired Tomcat throws an exception in the log like this: INFO: SSL Error getting client Certs javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateExpiredException: NotAfter: Thu Jan 19 08:40:14 CET 2 006 My problem is, that I would like to handle the case myself and avoid exceptions in the log and present the user with a good error message. In this case, the user has no clue what-so-ever of what happened because the error remains within Tomcat. What can I do to catch the error myself? Have you tried something like this in your web.xml? error-page exception-typejava.security.cert.CertificateExpiredException/exception-type location/WEB-INF/errors/expired.jsp/location /error-page - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unable to read TLD META-INF/c.tld from JAR file
Are you deleting the content of work folder while tomcat is running? Don't! Work Folder: Automatically generated by Tomcat, this is where Tomcat places intermediate files (such as compiled JSP files) during it's work. If you delete this directory while Tomcat is running you will not be able to execute JSP pages. -- Darek Czarkowski www.infinitesource.ca darekc at infinitesource dot ca On Wed, 2006-11-01 at 19:03 +0200, Vasiliy Keretsman wrote: Hello! Strange problem appears with Tomcat. It can't read the tlds from JAR file (standard.jar). org.apache.jasper.JasperException: Unable to read TLD META-INF/c.tld from JAR file It happens only once when Tomcat/work folder is empty. After page refresh everything goes well. Details: 1. Tomcat 5.0.28 2. J2SDK 1.4.2_02 3. standard.jar is not corrupted and includes all tlds in META-INF 4. WEB-INF/lib doesn't contain jsp-api.jar Any ideas? Thanks in advance Best regards, Vasiliy - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Change Display Icon
On Wed, 2006-11-01 at 12:16 -0800, Madhuraka Godahewa wrote: Hi, I am using tomcat 5.0.30. I have developed a web application and is ready to launch. But, still I have not been able to change the icon, which displayed on the browser (Firefox) when my site is loaded. The tomcat icon is shown. I renamed the 'favicon.ico' in the 'ROOT' folder as 'favicon1.ico' and put my own icon with the name 'favicon.ico'. But, still it displays the tomcat icon. Does anyone know how to change this? Thanks in advance, --- Madhuraka Godahewa Telecommunications Engineer Research and Development Unit Electroteks Global Networks (Pte.) Ltd. 68, Attidiya Road, Ratmalana, SRI LANKA. Mobile : + 94-777-647055 Tel(Home): + 94-38-4283181 Tel (Office) : + 94-11-4213771 Fax(Office) : + 94-11-4213980 - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Why don't you search mailing list archives for favicon? Add to the page head: link rel=icon href=/mywebapp/myfavicon.ico type=image/x-icon / You can also add: LINK REL=SHORTCUT ICON HREF=/mywebapp/favicon.ico type=image/x-icon -- Darek Czarkowski www.infinitesource.ca darekc at infinitesource dot ca - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DBCP Pool not context-specific?
I have a DBCP quandry that I'm puzzled by. I use per-context JNDI handles to the same Postgres database for multiple apps running inside tomcat. Each context.xml sets up connection limits, max idle, etc, slightly differently. One of my apps was not closing DBhandle correctly (I might take issue with the instructions posted at http://tomcat.apache.org/tomcat-5.5-doc/jndi-datasource-examples-howto.html , but that's for another email) and was exhausting the pool. The part that puzzles me is that the other applications were ALSO affected by the pool exhaustion. Does tomcat not set up per-context pools, but rather share one pool among all contexts, even though I specified pools per context? If it only uses one pool, which set of configuration params does it choose (since I set different params in each context.xml). Thanks! John Gorkos - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Handling expired client certificate
Kews,
Subscriber wrote:
Hi Hassan,
Thanks for your answer. Yes, I've already tried your suggestion. Both
with the java.security.cert.CertificateExpiredException and the
javax.net.ssl.SSLHandshakeException, but the problem remains. As I can
see, the exception is thrown somewhere inside Tomcat, before handling
control to the webapplication. Hence, the exception is not catchable
inside my webapplication, but is to be handled in some other way
inside the Tomcat engine.
What you need to do is override Java's certificate validator. This is
not a Tomcat issue -- you'd have it with any Java-based code that uses
the JRE's SSL libraries.
I'm not sure if Tomcat has a setting for doing this, but you might be
able to do it programmatically.
I have had to deal with this in the past, and I wrote myself a little
readme about it, since it's not worth keeping in my brain. I seem to
have lost it, but I do have some code that will turn off cert validation
for /outgoing/ HttpsURLConnections. You may have to adapt this code to
change the way ServetSockets are handled:
public static void disableSSLCertificateChecking()
throws NoSuchAlgorithmException, KeyManagementException
{
TrustManager[] trustAllCerts = new TrustManager[] {
new X509TrustManager() {
public X509Certificate[] getAcceptedIssuers() {
return null;
}
public void checkClientTrusted(X509Certificate[] certs,
String authType) {
}
public void checkServerTrusted(X509Certificate[] certs,
String authType) {
}
}
};
SSLContext sc = SSLContext.getInstance(SSL);
sc.init(null, trustAllCerts, new java.security.SecureRandom());
HttpsURLConnection.setDefaultSSLSocketFactory(sc.getSocketFactory());
}
If you'd like, you can implement your own version of checking instead of
disabling validation entirely. This is actually overriding the validator
with one that doesn't do any validation... it's not really disabling it.
You are free to provide your own implementation.
I can't seem to find any relevant methods in SSLServerSocketFactory,
which would be the most likely place to call some kind of
setDefaultSSLSocketFactory method, much like the HttpsURLConnection
method of the same name used above.
Sorry if this leads you down the wrong path!
-chris
signature.asc
Description: OpenPGP digital signature
Re: DBCP Pool not context-specific?
John, John Gorkos wrote: I use per-context JNDI handles to the same Postgres database for multiple apps running inside tomcat. Each context.xml sets up connection limits, max idle, etc, slightly differently. You said per-context JNDI handles, not per-context JNDI DataSources. Where are you defining your datasource? In context.xml, or in server.xml with additional, per-context configuration in context.xml? Can you show us the configuration for your JNDI DataSource, including the location in whatever file you use? For instance, if you use server.xml, /where/ you do put the Resource element? -chris signature.asc Description: OpenPGP digital signature
Webapps that run on 5.0.28 but not 5.5.x?
Hello, Question: How common is it for a webapp to be able to run on Tomcat 5.0.28 but *not* 5.5.20? For the installation of a commerical web application that calls for installation of Tomcat 5.0.28, I'm inclined to just go ahead and use the 5.5 series of servlet containers. Customer support is concerned that Tomcat 5.5 will not work (or at least has not been tested on the new version). My thinking is that: 1.) Both containers implement the same specifications, so their development team would *really* have to be coding obscurely, bending over backwards to try to trip up the 5.5 servlet container, to be able to manage to build a webapp that will run on 5.0.28 but not 5.5.20. 2.) Further, it would require an extremely talented development team to be able to create a webapp that will run on 5.0.28 but not 5.5.20, but paradoxically, if they had that level of talent they would *not* build an application anyway that will work on 5.0.28 but not 5.5.20. Is my logic here correct or faulty? To what degree is This webapp will work on 5.0.28 but not 5.5.20 an old wives' tale? Thanks, Glen - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unable to read TLD META-INF/c.tld from JAR file
Not while Tomcat is running. I am aware of the work folder. It happens when Tomcat starts with empty work folder. Just upgraded to J2SDK1.4.2_12 - the same result On 01/11/06, Darek Czarkowski [EMAIL PROTECTED] wrote: Are you deleting the content of work folder while tomcat is running? Don't! Work Folder: Automatically generated by Tomcat, this is where Tomcat places intermediate files (such as compiled JSP files) during it's work. If you delete this directory while Tomcat is running you will not be able to execute JSP pages. -- Darek Czarkowski www.infinitesource.ca darekc at infinitesource dot ca On Wed, 2006-11-01 at 19:03 +0200, Vasiliy Keretsman wrote: Hello! Strange problem appears with Tomcat. It can't read the tlds from JAR file (standard.jar). org.apache.jasper.JasperException: Unable to read TLD META-INF/c.tld from JAR file It happens only once when Tomcat/work folder is empty. After page refresh everything goes well. Details: 1. Tomcat 5.0.28 2. J2SDK 1.4.2_02 3. standard.jar is not corrupted and includes all tlds in META-INF 4. WEB-INF/lib doesn't contain jsp-api.jar Any ideas? Thanks in advance Best regards, Vasiliy - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DBCP Pool not context-specific?
On Wednesday 01 November 2006 11:58, Christopher Schultz wrote: John, John Gorkos wrote: I use per-context JNDI handles to the same Postgres database for multiple apps running inside tomcat. Each context.xml sets up connection limits, max idle, etc, slightly differently. You said per-context JNDI handles, not per-context JNDI DataSources. Where are you defining your datasource? In context.xml, or in server.xml with additional, per-context configuration in context.xml? Can you show us the configuration for your JNDI DataSource, including the location in whatever file you use? For instance, if you use server.xml, /where/ you do put the Resource element? -chris Chris - thanks for the quick response. We've just moved to tomcat 5.5. I'm using a per-app context XML that looks like this: ?xml version='1.0' encoding='utf-8'? Context crossContext=true debug=10 docBase=AMDSTools path=/AMDSTools reloadable=true antiJARLocking=true antiResourceLocking=true Logger className=org.apache.catalina.logger.FileLogger prefix=localhost_log. suffix=.txt timestamp=true/ Resource name=jdbc/psql auth=Container type=javax.sql.DataSource username=amds password=XxXxXx factory=org.apache.commons.dbcp.BasicDataSourceFactory driverClassName=org.postgresql.Driver url=jdbc:postgresql://127.0.0.1:5432/amds removeAbandoned=true removeAbandonedTimeout=2 logAbandoned=true maxActive=60 maxIdle=30 maxWait=5000 poolPreparedStatements=true/ /Context My server.xml is untouched from the default distribution of tomcat 5.5. And yes, I think the term I was searching for was per-context datasources. John Gorkos - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: haaving trouble html in tomcat 5.5.20
Thank u for responding. Where exactly should I put this in my coding? response.setHeader(Content-Type,video/x-ms-wmv); My file is .html How should I implement it. I am just a basic user of tomcat. thank u - Original Message From: Martin Gainty [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org; Zeina Aoun [EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 9:36:13 PM Subject: Re: haaving trouble html in tomcat 5.5.20 have you tried to apprise the response to setHeader so it may understand the specific wmv content-type e.g. response.setHeader(Content-Type,video/x-ms-wmv); M- This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents - Original Message - From: Zeina Aoun [EMAIL PROTECTED] To: users@tomcat.apache.org Sent: Tuesday, October 31, 2006 7:16 PM Subject: haaving trouble html in tomcat 5.5.20 I am having trouble with html in tomcat. I am using the Apache Tomcat 5.5.20 Server The problem is hard to describe. I am trying to enable some video clip files to be downloaded by users, but unfortunatley instead of downloading it opens up the garbage text on the webpage, just like if u try to open a media file in notepad or wordpad. It does not allow to download the media files. But when I try running the html page outside tomcat or in another server, it opens up perfectly. I am using .rmvb and .wmv format clips. I am using this type of basic coding. !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1 - transitional.dtd html xmlns=http://www.w3.org/1999/xhtml;; html head title download video/title /head brbrbr a href=video1.rmvb Clip1 /a brbr a href=video2.wmv Clip2 /a div /html Thank u
Re: Webapps that run on 5.0.28 but not 5.5.x?
Glen, Question: How common is it for a webapp to be able to run on Tomcat 5.0.28 but *not* 5.5.20? For the installation of a commerical web application that calls for installation of Tomcat 5.0.28 [...] [snip] To what degree is This webapp will work on 5.0.28 but not 5.5.20 an old wives' tale? I'm guessing that this is good-old CYA talking, here. The authors don't want you to install it on an untested version of the server platform and then come crying to them if something goes wrong. I can't speak to the success ratio of a blind upgrade from 5.0.x to 5.5.x, but you could always give it a try. Just make sure that you test it yourself before you let any of your real users get their hands on it. A good dose of paranoia is always a good thing in this case. -chris signature.asc Description: OpenPGP digital signature
Re: DBCP Pool not context-specific?
John, John Gorkos wrote: On Wednesday 01 November 2006 11:58, Christopher Schultz wrote: John Gorkos wrote: I use per-context JNDI handles to the same Postgres database for multiple apps running inside tomcat. Each context.xml sets up connection limits, max idle, etc, slightly differently. You said per-context JNDI handles, not per-context JNDI DataSources. Where are you defining your datasource? In context.xml, or in server.xml with additional, per-context configuration in context.xml? Can you show us the configuration for your JNDI DataSource, including the location in whatever file you use? For instance, if you use server.xml, /where/ you do put the Resource element? -chris Chris - thanks for the quick response. We've just moved to tomcat 5.5. I'm using a per-app context XML that looks like this: Context crossContext=true debug=10 docBase=AMDSTools It looks like you have your resource defined (correctly) in context.xml, which is what I would expect do to for context isolation of such a DataSource. I wonder if crossContext=true muddles this at all? My understanding is that crossContext=true basically changes the cookie path from /myapp to /, and allows a globally-managed session instead of per-context sessions. I'm grasping at straws, here, since your config at least looks plausible. Resource name=jdbc/psql auth=Container Any chance that your JNDI names are colliding with other apps? I dunno if Tomcat provides JNDI isolation for contexts (although it wouldn't make any sense not to provide that). If none of these turns out to be the problem, you may have to re-post your question. Often, folks on the list assume that a continued conversation means that the problem is getting solved by someone else, and might not read it. If you don't get a reply for a day or so, re-post with some of the extra information you've provided to me. I'm not an expert when it comes to the subtleties of Tomcat and context isolation. Who knows... maybe you even found a bug. -chris signature.asc Description: OpenPGP digital signature
RE: Webapps that run on 5.0.28 but not 5.5.x?
From: Glen Mazza [mailto:[EMAIL PROTECTED] Subject: Webapps that run on 5.0.28 but not 5.5.x? Question: How common is it for a webapp to be able to run on Tomcat 5.0.28 but *not* 5.5.20? The probability of it not running is near zero, with two caveats: 1) If the webapp utilizes internal Tomcat/Catalina classes, these may have changed. Highly unlikely in anything other than manager/admin/monitoring applications. 2) Resource configuration has changed between 5.0 and 5.5, so container-specific files like context.xml and server.xml need some translation between levels. The web.xml of the app should not need any updates. - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DBCP Pool not context-specific?
On Wednesday 01 November 2006 12:19, Christopher Schultz wrote: snip using a per-app context XML that looks like this: Context crossContext=true debug=10 docBase=AMDSTools It looks like you have your resource defined (correctly) in context.xml, which is what I would expect do to for context isolation of such a DataSource. I wonder if crossContext=true muddles this at all? My understanding is that crossContext=true basically changes the cookie path from /myapp to /, and allows a globally-managed session instead of per-context sessions. I'm grasping at straws, here, since your config at least looks plausible. Resource name=jdbc/psql auth=Container Any chance that your JNDI names are colliding with other apps? I dunno if Tomcat provides JNDI isolation for contexts (although it wouldn't make any sense not to provide that). Indeed, they ALL use this same resource name... If none of these turns out to be the problem, you may have to re-post your question. Often, folks on the list assume that a continued conversation means that the problem is getting solved by someone else, and might not read it. If you don't get a reply for a day or so, re-post with some of the extra information you've provided to me. I'm not an expert when it comes to the subtleties of Tomcat and context isolation. Who knows... maybe you even found a bug. -chris thanks for your help. I think I'll try changing resource names. A name that includes the appName would help prevent collisions, especially on a shared server, where I don't own all the apps. John Gorkos - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: haaving trouble html in tomcat 5.5.20
Zeina Aoun ha scritto: I am having trouble with html in tomcat. I am using the Apache Tomcat 5.5.20 Server The problem is hard to describe. I am trying to enable some video clip files to be downloaded by users, but unfortunatley instead of downloading it opens up the garbage text on the webpage, just like if u try to open a media file in notepad or wordpad. It does not allow to download the media files. But when I try running the html page outside tomcat or in another server, it opens up perfectly. It seems that tomcat doesn't set up the proper mime type of your media files, the error is not in the html page. I think that you can take a look at $TOMCAT/conf/web.xml and set up the proper mime type, in my web.xml there is no mapping for rmvb or wmv. loocking in mime.types of my linux machine: for wmv the mime type is video/x-ms-wmv Edoardo I am using .rmvb and .wmv format clips. I am using this type of basic coding. !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1 - transitional.dtd html xmlns=http://www.w3.org/1999/xhtml; html head title download video/title /head brbrbr a href=video1.rmvb Clip1 /a brbr a href=video2.wmv Clip2 /a div /html Thank u -- [EMAIL PROTECTED] AIM: edoardopn Jabber: [EMAIL PROTECTED] tel:075 9142766 - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Webapps that run on 5.0.28 but not 5.5.x?
I am currently testing just such an upgrade. We have a current webapp that runs in 5.0.28. The war file has a context.xml in the META-INF that has a JNDI datasource entry. If I place the myapp.war file into TC 5.5, it expands and places our context file in the conf/Catalina/localhost dir. I use JNDI datasource in the context.xml, and made sure that databse excises and is running. This setup is just as we do with 5.0, but when I access our app, I get this error. I have not done any research on this error yet, but since this topic just came up, and there was mention of customer support which I am very concerned about, in regards to helping our clients use Tomcat I though it was worth mentioning. In as much as a blind upgrade, from a client's perspective. type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception org.apache.jasper.JasperException: setAttribute: Non-serializable attribute org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWra pper.java:512) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:3 95) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) octane.Home.doGet(Home.java:211) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) root cause java.lang.IllegalArgumentException: setAttribute: Non-serializable attribute org.apache.catalina.session.StandardSession.setAttribute(StandardSession.jav a:1255) org.apache.catalina.session.StandardSession.setAttribute(StandardSession.jav a:1233) org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessi onFacade.java:129) org.apache.jasper.runtime.PageContextImpl.doSetAttribute(PageContextImpl.jav a:329) org.apache.jasper.runtime.PageContextImpl.setAttribute(PageContextImpl.java: 308) org.apache.jsp.Login_jsp._jspService(Login_jsp.java:47) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:3 34) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) octane.Home.doGet(Home.java:211) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 01, 2006 12:21 PM To: Tomcat Users List Subject: RE: Webapps that run on 5.0.28 but not 5.5.x? From: Glen Mazza [mailto:[EMAIL PROTECTED] Subject: Webapps that run on 5.0.28 but not 5.5.x? Question: How common is it for a webapp to be able to run on Tomcat 5.0.28 but *not* 5.5.20? The probability of it not running is near zero, with two caveats: 1) If the webapp utilizes internal Tomcat/Catalina classes, these may have changed. Highly unlikely in anything other than manager/admin/monitoring applications. 2) Resource configuration has changed between 5.0 and 5.5, so container-specific files like context.xml and server.xml need some translation between levels. The web.xml of the app should not need any updates. - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
including a jsp outside of tomcat directory
Hi, I have something like a content management webapp where I want to keep a directory on the filesystem containing markup fragments (JSP and HTML). Ideally I'd like this directory to be outside of my webapp, so that users could simply drop in a new WAR without blowing away the content directory. Unfortunately I see that if I use the RequestDispatcher.include mechanism to include a file not in the webapp, it doesn't work-- are there any workarounds available? Thanks, Jason - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Webapps that run on 5.0.28 but not 5.5.x?
Apart from the changes in suggested deployment strategies and ressourec definitions there's something to be careful: Upgrading to TC 5.5 and upgrading from Java 1.4 to Java 5 are two different things. As long as you do only the first, chances are good, that you get the webapp to run without code changes. An upgrade to Java 5 should be tried only after you get the webapp to run under TC 5.5 with Java 1.4. Regards, Rainer Glen Mazza schrieb: Hello, Question: How common is it for a webapp to be able to run on Tomcat 5.0.28 but *not* 5.5.20? For the installation of a commerical web application that calls for installation of Tomcat 5.0.28, I'm inclined to just go ahead and use the 5.5 series of servlet containers. Customer support is concerned that Tomcat 5.5 will not work (or at least has not been tested on the new version). My thinking is that: 1.) Both containers implement the same specifications, so their development team would *really* have to be coding obscurely, bending over backwards to try to trip up the 5.5 servlet container, to be able to manage to build a webapp that will run on 5.0.28 but not 5.5.20. 2.) Further, it would require an extremely talented development team to be able to create a webapp that will run on 5.0.28 but not 5.5.20, but paradoxically, if they had that level of talent they would *not* build an application anyway that will work on 5.0.28 but not 5.5.20. Is my logic here correct or faulty? To what degree is This webapp will work on 5.0.28 but not 5.5.20 an old wives' tale? Thanks, Glen - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How stable is tomcat
Wednesday, November 1, 2006, 8:19:07 PM, you wrote: CS John, CS John Gorkos wrote: On Wednesday 01 November 2006 11:58, Christopher Schultz wrote: John Gorkos wrote: I use per-context JNDI handles to the same Postgres database for multiple apps running inside tomcat. Each context.xml sets up connection limits, max idle, etc, slightly differently. You said per-context JNDI handles, not per-context JNDI DataSources. Where are you defining your datasource? In context.xml, or in server.xml with additional, per-context configuration in context.xml? Can you show us the configuration for your JNDI DataSource, including How stable is tomcat with Sun's HotSpot JVM 1.5? Right now we have apache servers that are up for 3 and 4 months. So I guess apache 1.3 may works for months. How stable is tomcat against apache or other webservers? Would tomcat be able to work 1 year without restart? I ask that because tomcat with eclipse became unstable twice today. (May be it was happening because of debugging mode of JVM) -- Best regards, Dimamailto:[EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Webapps that run on 5.0.28 but not 5.5.x?
Yes, thanks for the reminder. That's also something I need to keep in mind, as my installation guide says to load JRE 1.4.2, and I'm using 5.0. But again, I'd like to say that 1.4.2-compiled class files *should* be able to run on a 5.0 JRE. (I know if you recompile the source files--which I don't have access to anyway--and have 1.4.2-specific coding such as variables called enum, that would create problems.) But I suspect this would be less of a given than having a 5.0.28-able application be able to run on 5.5.20. Thanks, Glen Rainer Jung wrote: Apart from the changes in suggested deployment strategies and ressourec definitions there's something to be careful: Upgrading to TC 5.5 and upgrading from Java 1.4 to Java 5 are two different things. As long as you do only the first, chances are good, that you get the webapp to run without code changes. An upgrade to Java 5 should be tried only after you get the webapp to run under TC 5.5 with Java 1.4. Regards, Rainer Glen Mazza schrieb: Hello, Question: How common is it for a webapp to be able to run on Tomcat 5.0.28 but *not* 5.5.20? For the installation of a commerical web application that calls for installation of Tomcat 5.0.28, I'm inclined to just go ahead and use the 5.5 series of servlet containers. Customer support is concerned that Tomcat 5.5 will not work (or at least has not been tested on the new version). My thinking is that: 1.) Both containers implement the same specifications, so their development team would *really* have to be coding obscurely, bending over backwards to try to trip up the 5.5 servlet container, to be able to manage to build a webapp that will run on 5.0.28 but not 5.5.20. 2.) Further, it would require an extremely talented development team to be able to create a webapp that will run on 5.0.28 but not 5.5.20, but paradoxically, if they had that level of talent they would *not* build an application anyway that will work on 5.0.28 but not 5.5.20. Is my logic here correct or faulty? To what degree is This webapp will work on 5.0.28 but not 5.5.20 an old wives' tale? Thanks, Glen - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How stable is tomcat
Dima Retov wrote: How stable is tomcat with Sun's HotSpot JVM 1.5? Right now we have apache servers that are up for 3 and 4 months. So I guess apache 1.3 may works for months. How stable is tomcat against apache or other webservers? Would tomcat be able to work 1 year without restart? I've had three instances of 5.5.12 running on the same machine for 6 months without a restart, and that restart 6 months ago was due to a power failure. One of those instances gets around 2 million transactions per day. I ask that because tomcat with eclipse became unstable twice today. (May be it was happening because of debugging mode of JVM) It's probably not due to tomcat; you have a lot more going on than just a tomcat server in that situation. Dave - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Webapps that run on 5.0.28 but not 5.5.x?
Yes, binary compatibility should be OK. But most webapps have JSPs and you are soon in the area of source code compatibility: http://java.sun.com/javase/technologies/compatibility.jsp I only wanted to indicate, that it might be better to migrate in two steps, to keep the two possible reasons for trouble separate, especially when arguing with your webapp supplier. Regards, Rainer Glen Mazza schrieb: Yes, thanks for the reminder. That's also something I need to keep in mind, as my installation guide says to load JRE 1.4.2, and I'm using 5.0. But again, I'd like to say that 1.4.2-compiled class files *should* be able to run on a 5.0 JRE. (I know if you recompile the source files--which I don't have access to anyway--and have 1.4.2-specific coding such as variables called enum, that would create problems.) But I suspect this would be less of a given than having a 5.0.28-able application be able to run on 5.5.20. Thanks, Glen Rainer Jung wrote: Apart from the changes in suggested deployment strategies and ressourec definitions there's something to be careful: Upgrading to TC 5.5 and upgrading from Java 1.4 to Java 5 are two different things. As long as you do only the first, chances are good, that you get the webapp to run without code changes. An upgrade to Java 5 should be tried only after you get the webapp to run under TC 5.5 with Java 1.4. Regards, Rainer Glen Mazza schrieb: Hello, Question: How common is it for a webapp to be able to run on Tomcat 5.0.28 but *not* 5.5.20? For the installation of a commerical web application that calls for installation of Tomcat 5.0.28, I'm inclined to just go ahead and use the 5.5 series of servlet containers. Customer support is concerned that Tomcat 5.5 will not work (or at least has not been tested on the new version). My thinking is that: 1.) Both containers implement the same specifications, so their development team would *really* have to be coding obscurely, bending over backwards to try to trip up the 5.5 servlet container, to be able to manage to build a webapp that will run on 5.0.28 but not 5.5.20. 2.) Further, it would require an extremely talented development team to be able to create a webapp that will run on 5.0.28 but not 5.5.20, but paradoxically, if they had that level of talent they would *not* build an application anyway that will work on 5.0.28 but not 5.5.20. Is my logic here correct or faulty? To what degree is This webapp will work on 5.0.28 but not 5.5.20 an old wives' tale? Thanks, Glen - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How stable is tomcat
I also know a couple of instances which ran under high load for a couple of months. Usually though the frequency for changes in the apps are higher than that. Be careful: I would avoid hot deployment in critical production. Also: It's not totally unusual for apps to have memory leaks. So minotor your memory usage in the first weeks to check, if it gets stable. Regards, Rainer David Kerber schrieb: Dima Retov wrote: How stable is tomcat with Sun's HotSpot JVM 1.5? Right now we have apache servers that are up for 3 and 4 months. So I guess apache 1.3 may works for months. How stable is tomcat against apache or other webservers? Would tomcat be able to work 1 year without restart? I've had three instances of 5.5.12 running on the same machine for 6 months without a restart, and that restart 6 months ago was due to a power failure. One of those instances gets around 2 million transactions per day. I ask that because tomcat with eclipse became unstable twice today. (May be it was happening because of debugging mode of JVM) It's probably not due to tomcat; you have a lot more going on than just a tomcat server in that situation. Dave - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re[2]: How stable is tomcat
Thanks Dave. What version of JVM have you used? Wednesday, November 1, 2006, 8:57:19 PM, you wrote: DK Dima Retov wrote: How stable is tomcat with Sun's HotSpot JVM 1.5? Right now we have apache servers that are up for 3 and 4 months. So I guess apache 1.3 may works for months. How stable is tomcat against apache or other webservers? Would tomcat be able to work 1 year without restart? DK I've had three instances of 5.5.12 running on the same machine for 6 DK months without a restart, and that restart 6 months ago was due to a DK power failure. One of those instances gets around 2 million DK transactions per day. I ask that because tomcat with eclipse became unstable twice today. (May be it was happening because of debugging mode of JVM) DK It's probably not due to tomcat; you have a lot more going on than just DK a tomcat server in that situation. DK Dave DK - DK To start a new topic, e-mail: users@tomcat.apache.org DK To unsubscribe, e-mail: [EMAIL PROTECTED] DK For additional commands, e-mail: [EMAIL PROTECTED] -- Best regards, Dimamailto:[EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How stable is tomcat
Concerning my experience: no stability issues with either 1.4.2 or 1.5, as long as you stick to a reasonably new patch level (not the one, which might be only a week old, but the newest one older than a month should be perfect). Dima Retov schrieb: Thanks Dave. What version of JVM have you used? Wednesday, November 1, 2006, 8:57:19 PM, you wrote: DK Dima Retov wrote: How stable is tomcat with Sun's HotSpot JVM 1.5? Right now we have apache servers that are up for 3 and 4 months. So I guess apache 1.3 may works for months. How stable is tomcat against apache or other webservers? Would tomcat be able to work 1 year without restart? DK I've had three instances of 5.5.12 running on the same machine for 6 DK months without a restart, and that restart 6 months ago was due to a DK power failure. One of those instances gets around 2 million DK transactions per day. I ask that because tomcat with eclipse became unstable twice today. (May be it was happening because of debugging mode of JVM) DK It's probably not due to tomcat; you have a lot more going on than just DK a tomcat server in that situation. DK Dave DK - DK To start a new topic, e-mail: users@tomcat.apache.org DK To unsubscribe, e-mail: [EMAIL PROTECTED] DK For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How stable is tomcat
We had thousands of problems with Sun JDK that is why we switched to IBM JDK who manage GC in a great manner. You see the progress of the memory going down but it recover every single bit. Sun jdk always recover but there is some remaining memory that he do not release. -Original Message- From: Rainer Jung [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 01, 2006 2:06 PM To: Tomcat Users List Subject: Re: How stable is tomcat I also know a couple of instances which ran under high load for a couple of months. Usually though the frequency for changes in the apps are higher than that. Be careful: I would avoid hot deployment in critical production. Also: It's not totally unusual for apps to have memory leaks. So minotor your memory usage in the first weeks to check, if it gets stable. Regards, Rainer David Kerber schrieb: Dima Retov wrote: How stable is tomcat with Sun's HotSpot JVM 1.5? Right now we have apache servers that are up for 3 and 4 months. So I guess apache 1.3 may works for months. How stable is tomcat against apache or other webservers? Would tomcat be able to work 1 year without restart? I've had three instances of 5.5.12 running on the same machine for 6 months without a restart, and that restart 6 months ago was due to a power failure. One of those instances gets around 2 million transactions per day. I ask that because tomcat with eclipse became unstable twice today. (May be it was happening because of debugging mode of JVM) It's probably not due to tomcat; you have a lot more going on than just a tomcat server in that situation. Dave - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee. Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How stable is tomcat
Dima Retov wrote: Thanks Dave. What version of JVM have you used? I believe (not sure) it's 1.5.0_06 on the server; I'm running _07 on my dev machine. As Rainer mentioned, don't try to use hot deployment for busy apps; I always stop tomcat for updates, so my updates tend to be saved up and posted every few months. As Rainer also mentioned, check your memory usage for the first few weeks to be sure you don't have any leaks. I had a couple when that busy app first went into beta testing a couple of years ago, and it wouldn't go more than a week or so without running into out of memory errors.. Dave - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Webapps that run on 5.0.28 but not 5.5.x?
From: Michael Hencin [mailto:[EMAIL PROTECTED] Subject: RE: Webapps that run on 5.0.28 but not 5.5.x? This setup is just as we do with 5.0, but when I access our app, I get this error. org.apache.jasper.JasperException: setAttribute: Non-serializable attribute One of the things 5.5 does better than 5.0 is catch errors earlier. In this case, it looks like the app is trying to store a non-serializable attribute into a Session, which expects everything to be serializable. By default, Tomcat persists sessions across restarts, so serialization is required. You can disable this persistence (look in conf/context.xml); that may not have an effect on this particular situation, since the problem is being detected during compilation of a JSP. - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DBCP Pool not context-specific?
if, (for whatever reason), one webapp isn't releasing connections, but is able to keep creating them, then eventually you'll run out of available connections at the DB end, no? i'd expend effort determining why the app isn't releasing the connections, as that's the real problem. John Gorkos wrote: On Wednesday 01 November 2006 12:19, Christopher Schultz wrote: snip using a per-app context XML that looks like this: Context crossContext=true debug=10 docBase=AMDSTools It looks like you have your resource defined (correctly) in context.xml, which is what I would expect do to for context isolation of such a DataSource. I wonder if crossContext=true muddles this at all? My understanding is that crossContext=true basically changes the cookie path from /myapp to /, and allows a globally-managed session instead of per-context sessions. I'm grasping at straws, here, since your config at least looks plausible. Resource name=jdbc/psql auth=Container Any chance that your JNDI names are colliding with other apps? I dunno if Tomcat provides JNDI isolation for contexts (although it wouldn't make any sense not to provide that). Indeed, they ALL use this same resource name... If none of these turns out to be the problem, you may have to re-post your question. Often, folks on the list assume that a continued conversation means that the problem is getting solved by someone else, and might not read it. If you don't get a reply for a day or so, re-post with some of the extra information you've provided to me. I'm not an expert when it comes to the subtleties of Tomcat and context isolation. Who knows... maybe you even found a bug. -chris thanks for your help. I think I'll try changing resource names. A name that includes the appName would help prevent collisions, especially on a shared server, where I don't own all the apps. John Gorkos - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JNDI Realm and Active Directory root search
When searching LDAP from the root, you will get a referral reply from AD that has a server DNS name of JUST the domain name (ie company.com). NOT the initial server name you used in your connectionURL. one small remark: company.com in your post is what you chose as root object for your AD when you installed it. I guess this is one of the reasons why MS tells you to give the machine an FQDN *before* upgrading it to a domain controller. I've already seen a few variations from people that do not use their AD for DNS (eg company.local etc). Good job ;). Have you tried setting referrals=ignore? I would think this would mean don't bother about referrals, but in my last attempt that didn't solve things. What's the result in your case? -- Velpi - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Webapps that run on 5.0.28 but not 5.5.x?
have you actually looked to see what the code says at line 211 in Home.java? octane.Home.doGet(Home.java:211) is that part of your app? the exception posted earlier in the thread indicates that an attribute isn't serializable and the cause is at line 211, I think... ? i've got a feeling that TC 5.5 is more strict about serialization - but i could be mixing that up with something else, so don't take it as gospel. you might wish to investigate all the same, if the contents of line 211 don't identify the cause. Rainer Jung wrote: Yes, binary compatibility should be OK. But most webapps have JSPs and you are soon in the area of source code compatibility: http://java.sun.com/javase/technologies/compatibility.jsp I only wanted to indicate, that it might be better to migrate in two steps, to keep the two possible reasons for trouble separate, especially when arguing with your webapp supplier. Regards, Rainer Glen Mazza schrieb: Yes, thanks for the reminder. That's also something I need to keep in mind, as my installation guide says to load JRE 1.4.2, and I'm using 5.0. But again, I'd like to say that 1.4.2-compiled class files *should* be able to run on a 5.0 JRE. (I know if you recompile the source files--which I don't have access to anyway--and have 1.4.2-specific coding such as variables called enum, that would create problems.) But I suspect this would be less of a given than having a 5.0.28-able application be able to run on 5.5.20. Thanks, Glen Rainer Jung wrote: Apart from the changes in suggested deployment strategies and ressourec definitions there's something to be careful: Upgrading to TC 5.5 and upgrading from Java 1.4 to Java 5 are two different things. As long as you do only the first, chances are good, that you get the webapp to run without code changes. An upgrade to Java 5 should be tried only after you get the webapp to run under TC 5.5 with Java 1.4. Regards, Rainer Glen Mazza schrieb: Hello, Question: How common is it for a webapp to be able to run on Tomcat 5.0.28 but *not* 5.5.20? For the installation of a commerical web application that calls for installation of Tomcat 5.0.28, I'm inclined to just go ahead and use the 5.5 series of servlet containers. Customer support is concerned that Tomcat 5.5 will not work (or at least has not been tested on the new version). My thinking is that: 1.) Both containers implement the same specifications, so their development team would *really* have to be coding obscurely, bending over backwards to try to trip up the 5.5 servlet container, to be able to manage to build a webapp that will run on 5.0.28 but not 5.5.20. 2.) Further, it would require an extremely talented development team to be able to create a webapp that will run on 5.0.28 but not 5.5.20, but paradoxically, if they had that level of talent they would *not* build an application anyway that will work on 5.0.28 but not 5.5.20. Is my logic here correct or faulty? To what degree is This webapp will work on 5.0.28 but not 5.5.20 an old wives' tale? Thanks, Glen - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Cannot shutdown tomcat-5.5.4
Greetings,
Would you guys be able to give me pointers what needs to be checked if the
shutdown.sh scripts for tomcat 5 doesnt work?
I can try re-installing but would like to determine if there is anything
else I can check?
Thanks,
Rizalino
---
server: {1011} % netstat -an | grep 64.26.161.161
64.26.161.161.8009 *.* 0 0 0 0 LISTEN
server: {1012} % lsof -i -n | grep 64.26.161.161
java 25260 userid 9u inet 0x30008e9b438 0t0 TCP 64.26.161.161:8009 (LISTEN)
server: {1013} % ps -ef | grep 25260
root 6543 6140 0 13:19:18 pts/0 0:00 grep 25260
userid 25260 1 0 Oct 30 ? 26:39
/domain/web/software/java/jsdk/jdk1.5.0/bin/java
-Djava.endorsed.dirs=/domain/web
server: {1014} %
server: {1005} % ./bin/shutdown.sh
Using CATALINA_BASE: /domain/users/userid/tomcat5
Using CATALINA_HOME: /domain/web/software/java/tomcat/jakarta-tomcat-5.5.4
Using CATALINA_TMPDIR: /domain/users/u51/userid/tomcat5/temp
Using JAVA_HOME: /domain/web/software/java/jsdk/jdk1.5.0
13:21:25,320 ERROR Catalina:403 - Catalina.stop:
java.net.NoRouteToHostException: Cannot assign requested address
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:364)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
at java.net.Socket.init(Socket.java:365)
at java.net.Socket.init(Socket.java:178)
at org.apache.catalina.startup.Catalina.stopServer(Catalina.java:394)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3
9)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
pl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.stopServer(Bootstrap.java:320)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:411)
server: {1006} % ps -ef | grep userid
userid 7018 6140 0 13:21:02 pts/0 0:00 -tcsh
userid 7178 7018 0 13:21:34 pts/0 0:00 grep userid
userid 25260 1 0 Oct 30 ? 26:40
/domain/web/software/java/jsdk/jdk1.5.0/bin/java
-Djava.endorsed.dirs=/domain/web
server: {1007} %
server: {1013} % /sbin/ifconfig -a | grep 64.26.161.161
inet 64.26.161.161 netmask ff00 broadcast 64.26.159.255
server: {1014} %
server: {1015} % nslookup www.userid.com
Server: mag1.domaincom.com
Address: 206.191.0.210
Name: www.userid.com
Address: 64.26.161.161
server: {1016} %
--
View this message in context:
http://www.nabble.com/Cannot-shutdown-tomcat-5.5.4-tf2555490.html#a7121107
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: DBCP Pool not context-specific?
On Wednesday 01 November 2006 13:39, Pid wrote: if, (for whatever reason), one webapp isn't releasing connections, but is able to keep creating them, then eventually you'll run out of available connections at the DB end, no? Yes, but the database was set up to allow 500 connections, and the pool was running dry after 50. The disturbing part is that the pool was running dry in one context and causing other contexts in the same VM to throw PoolExhausted exceptions. I was hoping for a higher degree of seperation between contexts than what I got. i'd expend effort determining why the app isn't releasing the connections, as that's the real problem. Done. We followed the JNDI datasource reccomendations on the Tomcat web page and got bit. It was my fault for cutting and pasting so verbatim. The app works and releases correctly now. John Gorkos - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Cannot shutdown tomcat-5.5.4
From: Rizalino [mailto:[EMAIL PROTECTED] Subject: Cannot shutdown tomcat-5.5.4 Would you guys be able to give me pointers what needs to be checked if the shutdown.sh scripts for tomcat 5 doesnt work? First: I'd suggest moving up to a newer level - lots of things have been fixed since 5.5.4. Second: Before running the shutdown script, verify that Tomcat is actually listening on the designated port - usually 8005, defined in conf/server.xml. Third: Tomcat not terminating is often caused by some webapp kicking off a thread, and then not having a prescribed way of terminating that thread. Try taking a thread dump and see what's left lying around after running the shutdown script. - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unable to read TLD META-INF/c.tld from JAR file
On Wed, 2006-11-01 at 20:05 +0200, Vasiliy Keretsman wrote: Not while Tomcat is running. I am aware of the work folder. It happens when Tomcat starts with empty work folder. Just upgraded to J2SDK1.4.2_12 - the same result On 01/11/06, Darek Czarkowski [EMAIL PROTECTED] wrote: Are you deleting the content of work folder while tomcat is running? Don't! Work Folder: Automatically generated by Tomcat, this is where Tomcat places intermediate files (such as compiled JSP files) during it's work. If you delete this directory while Tomcat is running you will not be able to execute JSP pages. -- Darek Czarkowski www.infinitesource.ca darekc at infinitesource dot ca On Wed, 2006-11-01 at 19:03 +0200, Vasiliy Keretsman wrote: Hello! Strange problem appears with Tomcat. It can't read the tlds from JAR file (standard.jar). org.apache.jasper.JasperException: Unable to read TLD META-INF/c.tld from JAR file It happens only once when Tomcat/work folder is empty. After page refresh everything goes well. Details: 1. Tomcat 5.0.28 2. J2SDK 1.4.2_02 3. standard.jar is not corrupted and includes all tlds in META-INF 4. WEB-INF/lib doesn't contain jsp-api.jar Any ideas? Thanks in advance Best regards, Vasiliy - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Should have tried google first, if you did, you should provide more details. Here is what searching for your problem comes up with. http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi? ubb=get_topicf=50t=007815 Is this similar to your problem? Or perhaps you are deploying jsp- api.jar with your application? there is number of reasons this could be happening. -- Darek Czarkowski www.infinitesource.ca darekc at infinitesource dot ca - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How stable is tomcat
Dima, Please don't steal threads. Start a new one next time. How stable is tomcat with Sun's HotSpot JVM 1.5? How stable is tomcat against apache or other webservers? They are not directly comparable (Apache httpd and Tomcat) as Tomcat does things Apache httpd cannot do, and vice versa. Would tomcat be able to work 1 year without restart? My current longest running Tomcat instance was started on May 13th of this year (running Tomcat 4.1.30 and Java 1.4.2_04 on Linux). The only reason it hasn't run longer than that is because we perform semi-regular releases of new features. With a well-written application, Tomcat can run forever. -chris signature.asc Description: OpenPGP digital signature
Re: Unable to read TLD META-INF/c.tld from JAR file
On Wed, 2006-11-01 at 12:02 -0800, Darek Czarkowski wrote: On Wed, 2006-11-01 at 20:05 +0200, Vasiliy Keretsman wrote: Not while Tomcat is running. I am aware of the work folder. It happens when Tomcat starts with empty work folder. Just upgraded to J2SDK1.4.2_12 - the same result On 01/11/06, Darek Czarkowski [EMAIL PROTECTED] wrote: Are you deleting the content of work folder while tomcat is running? Don't! Work Folder: Automatically generated by Tomcat, this is where Tomcat places intermediate files (such as compiled JSP files) during it's work. If you delete this directory while Tomcat is running you will not be able to execute JSP pages. -- Darek Czarkowski www.infinitesource.ca darekc at infinitesource dot ca On Wed, 2006-11-01 at 19:03 +0200, Vasiliy Keretsman wrote: Hello! Strange problem appears with Tomcat. It can't read the tlds from JAR file (standard.jar). org.apache.jasper.JasperException: Unable to read TLD META-INF/c.tld from JAR file It happens only once when Tomcat/work folder is empty. After page refresh everything goes well. Details: 1. Tomcat 5.0.28 2. J2SDK 1.4.2_02 3. standard.jar is not corrupted and includes all tlds in META-INF 4. WEB-INF/lib doesn't contain jsp-api.jar Any ideas? Thanks in advance Best regards, Vasiliy - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Should have tried google first, if you did, you should provide more details. Here is what searching for your problem comes up with. http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi? ubb=get_topicf=50t=007815 Is this similar to your problem? Or perhaps you are deploying jsp- api.jar with your application? there is number of reasons this could be happening. I am sorry I didn't see the details. perhaps there is a problem with running tomcat with compatibility package and having tld's in WEB- INF/lib/standard.jar file. -- Darek Czarkowski Ph: 604 294 6557 (Ext. 113) Fx: 604 294 6507 www.infinitesource.ca darekc at infinitesource dot ca - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Webapps that run on 5.0.28 but not 5.5.x?
Thanks I will pass this along to our programmers. I am in a special position as we are the webapp supplier and specify as our requirements that the end clients use Tomcat. I therefore look at tomcat in a different light, as a tool. I am always concerned with what it the most elegant and simplest method to have our web app work with TC. As our target clients typically do not have TC running at all, there expertise is novice. I am learning TC more and more and appreciate the very clear and astute feedback I find here. Thanks. I am not a programmer and am tasked with writing out installation guide and handling TC related deployment issues. So this thread in particular is of concern to me and how I specify our installation guide and requirements. When I tested TC 5.5, I also used the recommended 1.4 JRE. And did the two steps at once. Probably now that would be not the method I should choose for an upgrade. As I know that our clients already have the 1.4 JDK installed. I will proceed with just an TC 5.5 upgrade using the previous JAVA install I used with 5.0.28. Mike -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 01, 2006 1:37 PM To: Tomcat Users List Subject: RE: Webapps that run on 5.0.28 but not 5.5.x? From: Michael Hencin [mailto:[EMAIL PROTECTED] Subject: RE: Webapps that run on 5.0.28 but not 5.5.x? This setup is just as we do with 5.0, but when I access our app, I get this error. org.apache.jasper.JasperException: setAttribute: Non-serializable attribute One of the things 5.5 does better than 5.0 is catch errors earlier. In this case, it looks like the app is trying to store a non-serializable attribute into a Session, which expects everything to be serializable. By default, Tomcat persists sessions across restarts, so serialization is required. You can disable this persistence (look in conf/context.xml); that may not have an effect on this particular situation, since the problem is being detected during compilation of a JSP. - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Webapps that run on 5.0.28 but not 5.5.x?
From: Michael Hencin [mailto:[EMAIL PROTECTED] Subject: RE: Webapps that run on 5.0.28 but not 5.5.x? When I tested TC 5.5, I also used the recommended 1.4 JRE. I presume you meant the 1.5 JRE in the above statement. I will proceed with just an TC 5.5 upgrade using the previous JAVA install I used with 5.0.28. Using the 1.4 JRE requires installing the Compatibility Package, which is no big deal. However, when you do upgrade to the 1.5 JRE, make sure to remove the package, which is a step many forget. - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
accessing settings in server.xml from the servlet
Hi, how can a servlet access maxThreads settings defined in server.xml? I tried getServletContext(), getServletConfig(), getInitParameter(..), getAttribute(..), etc, but I still can't find a way to access server.xml configuration. I guess I need to get ahold of the catalina engine and the get the setting from the http connector. But what is the right way to do this? Thanks. Alec
RE: accessing settings in server.xml from the servlet
From: Alec Swan [mailto:[EMAIL PROTECTED] Subject: accessing settings in server.xml from the servlet how can a servlet access maxThreads settings defined in server.xml? Usually via JMX. This is your rather terse starting point: http://tomcat.apache.org/tomcat-5.5-doc/mbeans-descriptor-howto.html Look at code in Tomcat's manager and admin apps for examples. - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: accessing settings in server.xml from the servlet
Charles , I agree with you that this starting point is rather terse. Is there a way to access settings in server.xml without MBeans? I would like to write a simple servlet that doesn't require special configuraion, such as mbeans-descriptor.xml file. Is it possible to get ahold of catalina engine from the servlet code and then somehow inspect http connectors? Thanks. On 11/1/06, Caldarale, Charles R [EMAIL PROTECTED] wrote: From: Alec Swan [mailto:[EMAIL PROTECTED] Subject: accessing settings in server.xml from the servlet how can a servlet access maxThreads settings defined in server.xml? Usually via JMX. This is your rather terse starting point: http://tomcat.apache.org/tomcat-5.5-doc/mbeans-descriptor-howto.html Look at code in Tomcat's manager and admin apps for examples. - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: accessing settings in server.xml from the servlet
From: Alec Swan [mailto:[EMAIL PROTECTED] Subject: Re: accessing settings in server.xml from the servlet Is there a way to access settings in server.xml without MBeans? Other than rolling your own infrastructure, probably not, at least not easily. That's what MBeans are for and why Tomcat utilizes them. - 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 start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: load balancing with controlled failover
Hi Rainer/Jim, Many thanks, just ran a test with mod_jk 1.2.19 and works great by setting the node to disabled through the JK status manager. From further reading it appears to be commonly known as session draining. Regards, Gary From: Jim Jagielski [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Date: Wed, 1 Nov 2006 11:14:14 -0500 Subject: This is expected to be added to the proxy module, but in a way which is more inline with expectations for a specific proxy server (whether serving ajp or http or anything else). On Nov 1, 2006, at 5:39 AM, Rainer Jung wrote: Hi Gary, from my understanding of the code mod_proxy(_balancer) at the moment is not able to do that. There are status settings disable and stopped one can set, but at the moment disbled and stopped behave the same. I didn't really try, but I derive that from looking at the code. This holds true for version 2.2.3, the head of branch 2.2 and trunk as well. I remember some mail on httpd-dev, that this is known and will be corrected. The module mod_jk also has the concept of disable and stop. For mod_jk disable means, that requests with sessions on a disabled target still get routed there, but requests without a session do not get routed to a disabled target. So if your sessions are relatively short, you can considerably decrease the number of remaining sessions on a target by disabling it some time before your maintenance. I'm sure, this behaviour will come to mod_proxy too, but it looks like it's not there yet. Anybody: please correct me if I'm wrong. If you are going to use mod_jk, please get the latest release 1.2.19. It's important to know, that mod_jk can only handle ajp backends. Regards Gary Feltham schrieb: Hi, I have a load balancing setup using Apache 2.2.2 (Win32) and 2 instances of Tomcat 5.5.15 and 5.5.17. So far I have been able to establish a successful load balancing using sticky sessions with the following config: ProxyPass /test balancer://testcluster stickysession=JSESSIONID nofailover=On Proxy balancer://testcluster BalancerMember ajp://127.0.0.1:18009/test smax=5 route=node01 BalancerMember ajp://127.0.0.1:28009/test smax=5 route=node02 /Proxy I am not wanting to setup a tomcat cluster for this deployment but have 2 independant instances of tomcat running independant sessions. Currently this is also setup to not failover if an instance goes down. For instance node01 is shutdown, the status is: LoadBalancer Status for balancer://testcluster StickySession Timeout FailoverAttemptsMethod JSESSIONID 0 1 byrequests Worker URL Route RouteRedir Factor Status ajp://127.0.0.1:18009/test node01 1 Err ajp://127.0.0.1:28009/test node02 1 Ok All expected and a request to node 1 results in a 503 response. My question therefore is: Within the context of a scheduled down time such as redeployment of the application or reboot of the server I would like to be able to control closure of the load balancer. For example, node 1 is targeted to be shutdown for maintenance, currently I have 10 user sessions on that instance and say 9 on node 2. If new users join then the load balancer will evenly distribute to each node per request. What I want to control is that each NEW user should only go to node 2, then each session on node 1 will expire eventually leaving 0 sessions on node 1. Node 1 can then be removed cleanly for maintenance and its status set as disabled. Is there a current method of performing this in either mod_proxy or mod_jk - I don't mind which but would like to gain that control? Many thanks, Gary Feltham - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: accessing settings in server.xml from the servlet
Alec Swan wrote: Is it possible to get ahold of catalina engine from the servlet code and then somehow inspect http connectors? Take a look at http://wiki.apache.org/tomcat/HowTo#head-42e95596753a1fa4a4aa396d53010680e3d509b5 Mark - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
