Re: Tomcat crash @ midnight - but why?
My logs are being being redirected to other directorys, where log levels are being applied. This are just the tomcat logs, since its tomcat which is crashing. The logs from stdout are just cases where things are still (or also) being written to Std out -which is the exception rather than the rule. Pid wrote: Martin Cavanagh wrote: Each time when Tomcat has crashed, it has been at midnight. At exactly midnight my program changes log directorys - from 20-09-2007 to 21-09-2007. This is a TimerTask. A thread which runs at exactly midnightat each of these crashes it has reported Can't create directory '\.cs-aterm\logs\SYSTEM\2007-09-25'. I can't help wondering if that might somehow be related. However if that happens, it should result in no logs being produced, not in Tomcat crashing. Is this the case for all 3 shutdown instances? If so, I'd suggest that understanding why that is happening will lead you to the cause of the shutdown... You're not really logging much from your app it would appear - is there any way to increase the logging level, or haven't you got much in the way of logging in the code? p - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Con-Sense-GmbH __ _Martin Cavanagh_ Tel.: +49541 800 83 0 Fax: +49541 800 83 99 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Con-Sense GmbH Neuer Graben 25 49074 Osnabrück www.con-sense-group.com http://www.con-sense-group.com Geschäftsführer Eckhard Schulz Amtsgericht Hildesheim HRB 3341 - 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 crash @ midnight - but why?
Hi Martin,
one problem could be insufficient RAM you assigned to Tomcat.
How much RAM have you set to your Tomcat? You can set a minimum of RAM while you
set a file called setenv.bat in C:\{CATALINA_HOME}\bin\ for example like this:
JAVA_OPTS=-server -Xms256M -Xmx512M -XX:MaxPermSize=128M
An other idea: Are you using Xerces for you applications? There is common bug in
the standard Xerces library from SUN, how causes memory leaks.
But I would first take a look to your VMware server. Have you any possibility to
take a copy of your Tomcat on a real machine?
-- Franck
Martin Cavanagh schrieb:
Thanks Alexey.
Notifications only :(
Keep the ideas coming guys!
just to to check - there is no hidden setting in Tomcat which says -
shut me down at midnight sometimes for an inexplainable reason?
Martin
Alexey Solofnenko wrote:
Maybe it is caused by automatic Windows Update. Did you check it?
- Alexey.
Martin Cavanagh wrote:
Hi guys, I'm still having this problem.
Its happened 3 times now. Always at exactly midnight. 21.09, 25.09
and 26.09.
We have VM Ware Server as the hardware - could this cause the problem?
I have a firewall on the machine with only the HTTPS port open.
In the config file there is the standard AJP port (8009) - what does
this actually do?
Hardware : VM Ware Server
OS: Win 2003
Tomcat Version: 5.5.23
Any ideas?
Thanks
Martin
David Smith wrote:
Huh?? The shutdown port explicitly binds to the localhost
interface. External clients cannot access it anyway. Easily
demonstrated with a netstat command.
--David
Martin Gainty wrote:
Hi Pid
you're going to need a firewall if someone can telnet to your
shutdown port
(check server.xml for the exact port number)
Martin--
- Original Message -
From: Pid [EMAIL PROTECTED]
To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, September 21, 2007 7:19 AM
Subject: Re: Tomcat crash @ midnight - but why?
What's immediately before the shutdown description in the logs?
p
Martin Cavanagh wrote:
Why would windows report it as crashing then?
I know I didn't shut it down, I was sleeping, as I assume
everyone else
was who had access to the system..
Thanks
Martin
David Delbecq wrote:
According to your log it did not crash. It did shutdown
following the
shutdown procedure (which can be executed by bin\shutdown.bat). I
suggest you investigate possibilities that a local service is
setup to
shutdown tomcat at midnight on the server.
The tomcat shutdown procedure is started when tomcat receive the
SHUTDOWN string at the admin connector (8005 here). This
connector is
by
default accessible only on local machine.
En l'instant précis du 21/09/07 09:21, Martin Cavanagh
s'exprimait en
ces termes:
Hi everyone.
Yesterday I started a 2nd Apache Server for my program. It was
installed several months ago. Version 5.5.0.23.
The server is running on Windows 2003 Server with Java JRE
1.5.0_11
It worked fine with my program for several hours. Then exactly at
midnight it crashed.
Dienst Apache Tomcat wurde unerwartet beendet. Dies ist
bereits 1
Mal passiert. - Which translates to,
Service Apache Tomcat stopped unexpectedly. This has
happened once
already.
The catalina logs show
21.09.2007 00:00:00 org.apache.coyote.http11.Http11AprProtocol
pause
INFO: Pausing Coyote HTTP/1.1 on http-443
21.09.2007 00:00:00 org.apache.coyote.ajp.AjpAprProtocol pause
INFO: Pausing Coyote AJP/1.3 on ajp-8009
21.09.2007 00:00:01 org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
21.09.2007 00:00:01 org.apache.coyote.http11.Http11AprProtocol
destroy
INFO: Stopping Coyote HTTP/1.1 on http-443
21.09.2007 00:00:01 org.apache.coyote.ajp.AjpAprProtocol destroy
INFO: Stopping Coyote AJP/1.3 on ajp-8009
Which unfortunately isn't really particularly useful. I can't
see any
other logs regarding this. How do I find out why my Tomcat
crashed?
Thanks
Martin
-
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]
--
Beste Grüße
Franck Borel
**
Dipl.-Hyd. Franck BorelTelefon: +49[0]761-203 3908
Universitätsbibliothek Fax: +49[0]761-203 3987
Werthmannsplatz 2 E-Mail : [EMAIL PROTECTED]
Re: Tomcat crash @ midnight - but why?
Caldarale, Charles R wrote: From: Darek Czarkowski [mailto:[EMAIL PROTECTED] Subject: Re: Tomcat crash @ midnight - but why? Now, this would be funny, can you search the source code of the deployed application for System.exit call? Heres trouble...the System does call System.exit(), when it can't create the directory... - so I understand why my application would stop- but why would tomcat shutdown? It's also using the client JVM not the server JVM (I installed JRE and there is no server JVM) Doesn't quite fit the symptoms. When a webapp calls System.exit(), the following entry does NOT appear in the logs: Sep 26, 2007 1:23:07 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8080 Whereas when the service is stopped or the shutdown string is sent to the shutdown port, the above message does appear in the logs. The OP did report that the Pausing ... message is present. - 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] -- Con-Sense-GmbH __ _Martin Cavanagh_ Tel.: +49541 800 83 0 Fax: +49541 800 83 99 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Con-Sense GmbH Neuer Graben 25 49074 Osnabrück www.con-sense-group.com http://www.con-sense-group.com Geschäftsführer Eckhard Schulz Amtsgericht Hildesheim HRB 3341 - 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 crash @ midnight - but why?
Martin Cavanagh wrote: Heres trouble...the System does call System.exit(), when it can't create the directory... - so I understand why my application would stop- but why would tomcat shutdown? And there is the problem. System.exit() will kill the JVM (unless you are running under a security manager and don't give the code permission to do this). Tomcat registers a shutdown hook on startup which performs a clean stop if the JVM is stopped. This is why you see what appears to be a 'normal' shutdown in the logs. 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]
Re: Tomcat crash @ midnight - but why?
Martin Cavanagh wrote: Caldarale, Charles R wrote: From: Darek Czarkowski [mailto:[EMAIL PROTECTED] Subject: Re: Tomcat crash @ midnight - but why? Now, this would be funny, can you search the source code of the deployed application for System.exit call? Heres trouble...the System does call System.exit(), when it can't create the directory... - so I understand why my application would stop- but why would tomcat shutdown? Because it shuts down the JVM, not your application. http://tomcat.apache.org/tomcat-5.5-doc/security-manager-howto.html p It's also using the client JVM not the server JVM (I installed JRE and there is no server JVM) Doesn't quite fit the symptoms. When a webapp calls System.exit(), the following entry does NOT appear in the logs: Sep 26, 2007 1:23:07 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8080 Whereas when the service is stopped or the shutdown string is sent to the shutdown port, the above message does appear in the logs. The OP did report that the Pausing ... message is present. - 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: Tomcat crash @ midnight - but why?
Are you using Log4j in your application? It has the option to do daily (midnight) rotates on log files... Oh - and you may want to have a serious talk with the cleaning lady, not that she unplugs the server for the vacuum cleaner.. ^^ Cheers Andrew On 26/09/2007, at 6:11 PM, Christopher Schultz wrote: Martin Cavanagh wrote: just to to check - there is no hidden setting in Tomcat which says - shut me down at midnight sometimes for an inexplainable reason? I think they removed that in 5.5.23, so you should be safe. It was fun while it lasted ;) - 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 crash @ midnight - but why?
Mark Thomas wrote: Martin Cavanagh wrote: Heres trouble...the System does call System.exit(), when it can't create the directory... - so I understand why my application would stop- but why would tomcat shutdown? And there is the problem. System.exit() will kill the JVM (unless you are running under a security manager and don't give the code permission to do this). Tomcat registers a shutdown hook on startup which performs a clean stop if the JVM is stopped. This is why you see what appears to be a 'normal' shutdown in the logs. Mark ahh good - and now I just need to work out why it can't create directorys on this one server - great! Now before I execute the System.exit I do a dump. Thanks alot. Additionaly I'll be installing the JDK so I can use the server JVM. Martin - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Con-Sense-GmbH __ _Martin Cavanagh_ Tel.: +49541 800 83 0 Fax: +49541 800 83 99 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Con-Sense GmbH Neuer Graben 25 49074 Osnabrück www.con-sense-group.com http://www.con-sense-group.com Geschäftsführer Eckhard Schulz Amtsgericht Hildesheim HRB 3341 - 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: Filter GET and POST
Hi Christopher, I'm not sure why you'd want to do this, since servlets do not really distinguish between GET and POST parameters -- the API abstracts that complexity away from your code. If I change the request from POST to GET the Servlet works. I have no possibility to change the Servlet behind. When you say does not work, what do you mean? What happens when you use POST? I don't know if you know Shibboleth. This is the servlet (IdP = Identity Provider) who lies behind. The servlet accepts only GET requests and brakes down if I send him a POST request. It would be (somewhat) trivial to accept a POST request on one URL and then forward (or redirect, I suppose) to another URL with the POST parameters converted into GET parameters. It's up to you to find out if a filter can do this properly, or even if that's what you want to do. I found a solution: I send the user back to the same address via sendRedirect. Now my filter works fine with the IdP behind. Thanks for your support! -- Franck - 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: Setting ClientAuth parameter to true
Thanks for getting back Tott. I did see that how-to link . it states that we have to use those fields only when we have a keystore format other than 'jks'. 1. I had my keystores files with a .keystore as extension. Hence I modified the connector configuration to :: keystoreType=keystore truststoreType=keystore. After this I restarted Tomcat but this didn't work. 2. Then I regenerated my keystores using a .jks extension and removed the 'type' fields in the connector configuration (since it said the fields should be used only when other-than-jks format is used). I restarted my Tomcat again and still it didn't work. Not sure what I should look at. Any help would be appreciated. -Subhash- -Original Message- From: Clinton J. Totten [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 26, 2007 6:28 PM To: Tomcat Users List Subject: RE: Setting ClientAuth parameter to true From inspection of your connector properties it looks like your missing the keystoreType attribute and the truststoreType attribute. If you check the documentation via this link (http://tomcat.apache.org/tomcat-5.5-doc/ssl-howto.html) it will tell you what you can have as a value in this field. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 26, 2007 8:31 AM To: users@tomcat.apache.org Subject: Setting ClientAuth parameter to true Hi, I am unable to set client authentication for SSL in tomcat 5.5.2. I have generated the certificate for the client and imported the same into the server's keystore so that the server can verify the client's certificate. The following is the modification I make on server.xml. Connector port=8443 maxHttpHeaderSize=8192 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false disableUploadTimeout=true acceptCount=100 scheme=https secure=true clientAuth=true sslProtocol=TLS keystoreFile=D:\Projects\Starwood\WSOverSSL\axis\server.keystore keystorePass=xx truststoreFile=D:\Projects\Starwood\WSOverSSL\axis\server.keystore truststorePass=xx / once this change is done and the server is restarted, I am not able to hit this url https://localhost:8443 https://localhost:8443/ . At the same time, if I change the value of clientAuth back to false I am able to access the url. Can some pls help where I went wrong? Thanks, -Subhash- This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. - 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 e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[OT] RE: Tomcat crash @ midnight - but why?
From: Andrew Miehs [mailto:[EMAIL PROTECTED] Oh - and you may want to have a serious talk with the cleaning lady, not that she unplugs the server for the vacuum cleaner.. ^^ Don't joke, it happened repeatedly to a box I used to manage in a hospital. Even after we taped over the plug, writing do not remove on it, she'd simply undo the tape, pull out the plug, vacuum away, and replace the plug and tape. The same cleaner would routinely plug the vacuum into the red power-conditioned emergency-equipment-only sockets around the hospital... - Peter - 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 crash @ midnight - but why?
From: Martin Cavanagh [mailto:[EMAIL PROTECTED] Now before I execute the System.exit I do a dump. Are you sure shutting down the entire Tomcat instance is the appropriate thing to do if you can't create the log directory? As opposed to, say, logging the problem and returning an appropriate status code to the client? If you're looking for environmental factors, here's one to think about: does the server have antivirus with real-time scanning enabled? This can be a performance pig on Windows, and especially on slower or virtual servers it can cause timeouts on pretty much any file operation. If it has, you might want to consider disabling real-time scanning altogether, or at least preventing scanning on the folders in which your log directories will be created. The problem's not purely theoretical - I've had clients lose SQL Server databases because of this issue, for example. - Peter - 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 Stops Responding
Yup that's what I thought was happening. When all threads are busy, tomcat can't accept any more requests. To an extent tomcat still accepts some request and waits for a thread to free up but eventually it'll reject the requests with a 50x error. Either the tomcat service is legitimately overloaded (over 250 concurrent requests) or a design issue is preventing threads from being freed for new requests. You'll have to do some profiling to determine which it is and the best way to fix it. Also see Chuck Caldarale's message regarding potential causes to look for. --David Etienne Lacombe wrote: David, I followed your advice and killed the JVM so as to get the stack trace when it stopped responding this afternoon. Here is what we had in the log before the stack trace: 3:27 org.apacheThreadPool logFull All threads (250) are currently busy, waiting. Increase maxThreads (250) or check the servlet status. 3:27 to 3:41 A few log statements from our webapps 3:41 - the stack trace dump... All threads are either TIMED_WAITING, RUNNABLE or WAITING. Etienne - 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]
Simultaneous Requests to servlet
Hi, I have a basic question about servlets in Tomcat 5.0.18. In theory, when there are simultaneous requests come for a servlet, it will either queue the requests and serve one by one or create multiple threads of the servlet and serve the request. My question is, what / how tomcat handles this situation? I need the answer for this, because, i have a synchronized access to an object from the servlet, and if tomcat handles the monitor for the object then i don't need to handle the monitoring condition else i may have to do it. I understand that Tomcat has a SingleThreadModel interface that allows only one thread access/One request at a time model. But help me solve the previous problem -- Pavan S. Kumar
RE: Simultaneous Requests to servlet
From: Pavan Singaraju [mailto:[EMAIL PROTECTED] In theory, when there are simultaneous requests come for a servlet, it will either queue the requests and serve one by one or create multiple threads of the servlet and serve the request. My question is, what / how tomcat handles this situation? It has already created and will use multiple threads - possibly hundreds in a large system. You need to handle synchronisation yourself, and for a high-throughput site you need to handle it very carefully so that you don't artificially limit how much can be run in parallel. - Peter - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FW: Redirection Problem
Hi All, I have had a side conversation with Bertrand.donnet and a big thanks goes out to him/her. He found a solution and wonderful instructions on how to set up the JK_mod with Tomcat 5, IIS6.0, and the native runtime library. The email sent to me is pasted below; with his/her contact removed. (Didn't know if he/she would want/care for me to post it). My original post is at the very end. Cheers Ok, thanks for your answer. I have investigated last night and found a great PDF solving the problem. It seems that you have to switch IIS 6 to IIS 5 isolation mode. Everything is well documented in this PDF. Read the intro and jump directly to page 14. The IIS part is up-to-date even if the rest is not. In my case (JDK 6u2 + JBOSS 4.2.1 + JK 1.2.25 + IIS 6.0 + W2K3) it works fine now. Perhaps a good idea to add the link on your post but i don't remember the site. hope it helps http://www.roktech.net/devblog/enclosures/iis6-Tomcat5-JK2.pdf ~Charlie The significant problems we have cannot be solved at the same level of thinking with which we created them. - Albert Einstein From: Charlie Wingate Sent: Tuesday, September 11, 2007 11:28 AM To: 'users@tomcat.apache.org' Subject: Redirection Problem Hi All, I am rather new to these help forums so please bear with me; I have always been able to find what I needed by searching the net and more specifically the Apache site, up until now that is. My problem is that the redirector catches the request, matches it, and forwards the escaped uri but the browser displays a 404 not found error. I have included what I think is the relevant information and things I have tried. Any insight that could be provided would be greatly appreciated. Server OS= Win2k3 sp2 Web Server= IIS6.0 Tomcat= 5.5.20 Native runtime library in Tomcat= 1.1.9.0 Isapi_redirect.dll=1.2.25.0 In IIS I have the following configured. Webservice Extension: Named=jakarta and pointing to c:\tomcat 5.5\bin\Jakarta Isapi Redirector\bin\isapi_redirect.dll Virtual Directory: Named=Jakarta, local path= c:\tomcat 5.5\bin\Jakarta Isapi Redirector\bin, directory security is set to enable anonymous access as the IUSR account on the local machine, Execute permissions are set to= scripts and executables, the app pool is set to the default app pool. Default App pool is set to use an identity of IWAM on the local machine. The folder permissions for c:\tomcat 5.5\bin\Jakarta Isapi Redirector\bin and the entire webapps folder in tomcat include the IUSR and IWAM accounts with full access and child propagation of the permissions. In Tomcat I have And ajp1.3 listener on port 8009. I have verified that is up via the stdout during tomcat load. I have also run a netstat and found that 8009 is actively being used by tomcat. The exact server.xml entry for it is as follows Connector protocol=AJP/1.3 Port=8009 enableLookups=false redirectPort=8443 / I have servlets-examples and a custom application called dgportal successfully deployed and accessible via an explicit 8080 port call on the url. I have omitted the registry settings I am using as they can be found in the iaspi log. Any ideas on what I should try next Logs Isapi_redirect.log [Tue Sep 11 10:45:15.642 2007] [3572:4604] [debug] jk_util.c (530): log time stamp format is '[%a %b %d %H:%M:%S.%Q %Y] ' [Tue Sep 11 10:45:15.642 2007] [3572:4604] [debug] jk_shm.c (169): Initialized shared memory size=28800 free=28672 addr=0x1b6 [Tue Sep 11 10:45:15.642 2007] [3572:4604] [debug] jk_isapi_plugin.c (1698): Using registry. [Tue Sep 11 10:45:15.658 2007] [3572:4604] [debug] jk_isapi_plugin.c (1701): Using log file C:\Tomcat 5.5\bin\Jakarta Isapi Redirector\log\isapi_redirect.log. [Tue Sep 11 10:45:15.658 2007] [3572:4604] [debug] jk_isapi_plugin.c (1702): Using log level 1. [Tue Sep 11 10:45:15.658 2007] [3572:4604] [debug] jk_isapi_plugin.c (1703): Using extension uri /jakarta/isapi_redirect.dll. [Tue Sep 11 10:45:15.658 2007] [3572:4604] [debug] jk_isapi_plugin.c (1704): Using worker file C:\Tomcat 5.5\bin\Jakarta Isapi Redirector\conf\workers.properties.minimal. [Tue Sep 11 10:45:15.658 2007] [3572:4604] [debug] jk_isapi_plugin.c (1705): Using worker mount file C:\Tomcat 5.5\bin\Jakarta Isapi Redirector\conf\uriworkermap.properties. [Tue Sep 11 10:45:15.658 2007] [3572:4604] [debug] jk_isapi_plugin.c (1707): Using rewrite rule file . [Tue Sep 11 10:45:15.658 2007] [3572:4604] [debug] jk_isapi_plugin.c (1709): Using uri select 3. [Tue Sep 11 10:45:15.658 2007] [3572:4604] [debug] jk_map.c (495): Adding property '/admin/*' with value 'wlb' to map. [Tue Sep 11 10:45:15.658 2007] [3572:4604] [debug] jk_map.c (495): Adding
Re: Simultaneous Requests to servlet
Pavan Singaraju wrote: Hi, I have a basic question about servlets in Tomcat 5.0.18. In theory, when there are simultaneous requests come for a servlet, it will either queue the requests and serve one by one or create multiple threads of the servlet and serve the request. My question is, what / how tomcat handles this situation? As I understand it one instance of the servlet per webapp is accessed from all threads in a reentrant manner. This is why you normally can't use any class instance variables in a servlet. The only queueing that occurs is in the connector's thread pool when all threads are busy handling requests. I need the answer for this, because, i have a synchronized access to an object from the servlet, and if tomcat handles the monitor for the object then i don't need to handle the monitoring condition else i may have to do it. I understand that Tomcat has a SingleThreadModel interface that allows only one thread access/One request at a time model. But help me solve the previous problem SingleThreadModel has it's uses, but is also hard to get right and usually discouraged because of that. I'd say you are going to have to implement monitoring to prevent concurrent access where necessary. Just try to keep the sync blocks small so a minimum amount of time is spent there and only as necessary. Your object is probably best served stored in the servlet context (ie application scope) with logic that handles synchronizing on update operations. --David - 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 crash @ midnight - but why?
Because tomcat is running as a service, permissions may be an issue for creating/writing to the directory in question, most likely this is why the task fails... unless the Timer task is a critical process don't use System.exit(0), just check the if the task runs or not and if not log the error/send an alert. Peter Martin Cavanagh wrote: Mark Thomas wrote: Martin Cavanagh wrote: Heres trouble...the System does call System.exit(), when it can't create the directory... - so I understand why my application would stop- but why would tomcat shutdown? And there is the problem. System.exit() will kill the JVM (unless you are running under a security manager and don't give the code permission to do this). Tomcat registers a shutdown hook on startup which performs a clean stop if the JVM is stopped. This is why you see what appears to be a 'normal' shutdown in the logs. Mark ahh good - and now I just need to work out why it can't create directorys on this one server - great! Now before I execute the System.exit I do a dump. Thanks alot. Additionaly I'll be installing the JDK so I can use the server JVM. Martin - 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: CacheRowSetImpl and Tomcat
Sorry, you can disregard this message. It was my design that was causing the problem, and all is good now. - 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: Simultaneous Requests to servlet
Pavan Singaraju a écrit : I understand that Tomcat has a SingleThreadModel interface that allows only one thread access/One request at a time model. But help me solve the previous problem -- Pavan S. Kumar Don't use SingleThreadModel anyway. From J2EE 1.4 docs: Deprecated. As of Java Servlet API 2.4, with no direct replacement. public interface SingleThreadModel Ensures that servlets handle only one request at a time. This interface has no methods. If a servlet implements this interface, you are guaranteed that no two threads will execute concurrently in the servlet's service method. The servlet container can make this guarantee by synchronizing access to a single instance of the servlet, or by maintaining a pool of servlet instances and dispatching each new request to a free servlet. Note that SingleThreadModel does not solve all thread safety issues. For example, session attributes and static variables can still be accessed by multiple requests on multiple threads at the same time, even when SingleThreadModel servlets are used. It is recommended that a developer take other means to resolve those issues instead of implementing this interface, such as avoiding the usage of an instance variable or synchronizing the block of the code accessing those resources. This interface is deprecated in Servlet API version 2.4. - 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 crash @ midnight - but why?
From: Franck Borel [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat crash @ midnight - but why?
one problem could be insufficient RAM you assigned to Tomcat.
How much RAM have you set to your Tomcat?
Don't confuse physical RAM with the virtual memory sizing of the Java
heap. Having insufficient RAM on the system will only result in
excessive paging, not process termination. Having insufficient swap
file space could result in termination.
You can set a minimum of RAM while you set a file
called setenv.bat in C:\{CATALINA_HOME}\bin\ for
example like this:
As has been stated numerous times in this thread, the OP is running
Tomcat as a Windows service, so no scripts are available. Heap settings
have to be done with the tomcat5w.exe program.
- 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: Simultaneous Requests to servlet
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pavan,
Pavan Singaraju wrote:
I have a basic question about servlets in Tomcat 5.0.18. In theory, when
there are simultaneous requests come for a servlet, it will either queue the
requests and serve one by one or create multiple threads of the servlet and
serve the request.
Nope: all requests will be handled in parallel unless other factors
exist (such as more requests than your server is configured to accept
simultaneously).
There used to be a SingleThreadModel interface you could implement that
would force the behavior you describe but it has been deprecated.
My question is, what / how tomcat handles this situation?
Tomcat does not take any special action when multiple requests come in
for a particular servlet.
I need the answer for this, because, i have a synchronized access to an
object from the servlet, and if tomcat handles the monitor for the object
then i don't need to handle the monitoring condition else i may have to do
it.
Tomcat will never handle monitors for your synchronized objects: the JVM
will do it. If you need serialized access to an object, then you need to
synchronize it yourself. Better yet, make multiple copies of it so you
don't have to serialize access to it (them). Even better, fix your
design so that it's thread safe and you don't need any synchronization
at all.
I understand that Tomcat has a SingleThreadModel interface that allows
only one thread access/One request at a time model.
SingleThreadModel has been deprecated as of Servlet API v2.4. Don't use it.
But help me solve the previous problem.
You can alway do this:
private Whatever _myProtectedResource;
public void service(HttpServletRequest req, HttpServletResponse rsp)
{
...
synchronized (_myProtectedResource) {
// do whatever you need to do in here that requires exclusive
// access to _myProtectedResource
}
...
}
Hope that helps,
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG+6ya9CaO5/Lv0PARAgTKAKC4UFTpSjZm65Kuv9390onquuZQWACgt2Sw
L6jIt3B3woKIxvM/jVSPs+4=
=4Ge9
-END PGP SIGNATURE-
-
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: Simultaneous Requests to servlet
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David, David Smith wrote: As I understand it one instance of the servlet per webapp is accessed from all threads in a reentrant manner. This is why you normally can't use any class instance variables in a servlet. While this is the most straightforward implementation of a servlet container, the servlet specification makes no guarantees whatsoever about the lifecycle of a specific servlet. The container is free to create a new instance of the servlet to handle every request, or to keep a single copy around for the life of the webapp. Or anything in between. The only guarantee made along these lines is for servlets that implement SingleThreadModel, which will either require serialized access or multiple instances to handle requests. Since this has been deprecated but not removed from the spec, I'll bet it will continue to be supported forever, but it's not a very good idea IMO. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG+64J9CaO5/Lv0PARAjpoAJ0WrN71Y3DsZMwsH3Id7yyVw7eSNgCgwenS 7F7lp0R5RGdDyYeopo6oQO4= =Ki+D -END PGP SIGNATURE- - 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 balancer (apache or hardware)
http://www.nabble.com/Load-Balancing-Tomcat-5.0.X%2C-hardware-or-software--tf4354748.html#a12408836 Check this post Johann -- View this message in context: http://www.nabble.com/Load-balancer-%28apache-or-hardware%29-tf4515421.html#a12921397 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: Tomcat crash @ midnight - but why?
Charles,
one problem could be insufficient RAM you assigned to Tomcat.
How much RAM have you set to your Tomcat?
Don't confuse physical RAM with the virtual memory sizing of the Java
heap. Having insufficient RAM on the system will only result in
excessive paging, not process termination.
What do you mean by paging?
You can set a minimum of RAM while you set a file
called setenv.bat in C:\{CATALINA_HOME}\bin\ for
example like this:
As has been stated numerous times in this thread, the OP is running
Tomcat as a Windows service, so no scripts are available. Heap settings
have to be done with the tomcat5w.exe program.
Ok...I slip this.
-- Franck
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Session Replication
Hello everyone!
For using Tomcat session clustering I need to put the following
component in all nodes?
Cluster
className=org.apache.catalina.cluster.tcp.SimpleTcpCluster
doClusterLog=true
clusterLogName=clusterlog
manager.className=org.apache.catalina.cluster.session.DeltaManager
manager.expireSessionsOnShutdown=false
manager.notifyListenersOnReplication=false
manager.notifySessionListenersOnReplication=false
manager.sendAllSessions=false
manager.sendAllSessionsSize=500
manager.sendAllSessionsWaitTime=20
Membership
className=org.apache.catalina.cluster.mcast.McastService
mcastAddr=228.0.0.4
mcastBindAddress=127.0.0.1
mcastClusterDomain=d10
mcastPort=45564
mcastFrequency=1000
mcastDropTime=3
recoveryCounter=10
recoveryEnabled=true
recoverySleepTime=5000/
Receiver
className=org.apache.catalina.cluster.tcp.ReplicationListener
tcpListenAddress=auto
tcpListenPort=9016
tcpSelectorTimeout=100
tcpThreadCount=6/
Sender
className=org.apache.catalina.cluster.tcp.ReplicationTransmitter
replicationMode=fastasyncqueue
recoverTimeout=5000
recoverCounter=6
doTransmitterProcessingStats=true
doProcessingStats=true
doWaitAckStats=true
queueTimeWait=true
queueDoStats=true
queueCheckLock=true
ackTimeout=15000
waitForAck=true
keepAliveTimeout=8
keepAliveMaxRequestCount=-1/
Valve
className=org.apache.catalina.cluster.tcp.ReplicationValve
filter=.*\.gif;.*\.js;.*\.css;.*\.png;.*\.jpeg;.*\.jpg;.*\.htm;.*\.html;.*\.txt;
primaryIndicator=true /
Valve
className=org.apache.catalina.cluster.session.JvmRouteBinderValve
enabled=true /
ClusterListener
className=org.apache.catalina.cluster.session.ClusterSessionListener
/
ClusterListener
className=org.apache.catalina.cluster.session.JvmRouteSessionIDBinderListener
/
Deployer
className=org.apache.catalina.cluster.deploy.FarmWarDeployer
tempDir=${catalina.base}/war-temp
deployDir=${catalina.base}/war-deploy/
watchDir=${catalina.base}/war-listen/
watchEnabled=true/
/Cluster
-
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: DeltaManager cannot receive message through TCP channel in Tomcat cluster
Hi In another thread I was advised to change my virtual host config, which has moved this problem on a little bit. I now have a manger context for each virtual host, rather than just on localhost, and these manager apps seem to report the session count; its only the localhost manager that doesn't seem to work properly. Does that shed any light on things? And no the old macs have been re-deployed somewhere else... Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan, Daniel M Garland wrote: Another strange thing is since this started happening I don't ever see the session count in the manager app increase above zero, even though if I sit in front of the webapp my session is persisted across the cluster... weird. Completely weird. Since we're grasping at straws, are you able to re-deploy the old Mac servers for testing purposes? I'd be interested to see if you do a new deployment on them if they will act properly. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG+mLr9CaO5/Lv0PARApsqAKCCBEMOIPHNAQNT1AIP8c61QVXTtwCfS5m4 vMNQ+fJPFlQEIgPOB67JaKc= =HdeT -END PGP SIGNATURE- - 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 email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Apache Portable Runtime 1.1.4 on Debian Etch?
Hi again, In my catalina.out I see the following INFO on a server startup: INFO: An older version 1.1.3 of the Apache Tomcat Native library is installed, while Tomcat recommends version greater than 1.1.4 I installed libapr1 and libapr1-dev using apt on Debain etch 64-bit version, and am up-to-date, any Debian users out there who know if there is a debain package for apr that is greater than 1.1.4? Dan __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - 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: Simultaneous Requests to servlet
Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David, David Smith wrote: As I understand it one instance of the servlet per webapp is accessed from all threads in a reentrant manner. This is why you normally can't use any class instance variables in a servlet. While this is the most straightforward implementation of a servlet container, the servlet specification makes no guarantees whatsoever about the lifecycle of a specific servlet. The container is free to create a new instance of the servlet to handle every request, or to keep a single copy around for the life of the webapp. Or anything in between. Yup and all the more reason to store this synchronized data object in the servlet context, implementing logic to make it thread-safe. The only guarantee made along these lines is for servlets that implement SingleThreadModel, which will either require serialized access or multiple instances to handle requests. Since this has been deprecated but not removed from the spec, I'll bet it will continue to be supported forever, but it's not a very good idea IMO. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG+64J9CaO5/Lv0PARAjpoAJ0WrN71Y3DsZMwsH3Id7yyVw7eSNgCgwenS 7F7lp0R5RGdDyYeopo6oQO4= =Ki+D -END PGP SIGNATURE- - 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: Session Replication
Andrew Hole wrote:
Hello everyone!
For using Tomcat session clustering I need to put the following
component in all nodes?
Yes, obviously. Any node without a cluster definition won't know that
it's supposed to be in a cluster without it...
I don't suppose you've read the docs on clustering, at all?
p
Cluster
className=org.apache.catalina.cluster.tcp.SimpleTcpCluster
doClusterLog=true
clusterLogName=clusterlog
manager.className=org.apache.catalina.cluster.session.DeltaManager
manager.expireSessionsOnShutdown=false
manager.notifyListenersOnReplication=false
manager.notifySessionListenersOnReplication=false
manager.sendAllSessions=false
manager.sendAllSessionsSize=500
manager.sendAllSessionsWaitTime=20
Membership
className=org.apache.catalina.cluster.mcast.McastService
mcastAddr=228.0.0.4
mcastBindAddress=127.0.0.1
mcastClusterDomain=d10
mcastPort=45564
mcastFrequency=1000
mcastDropTime=3
recoveryCounter=10
recoveryEnabled=true
recoverySleepTime=5000/
Receiver
className=org.apache.catalina.cluster.tcp.ReplicationListener
tcpListenAddress=auto
tcpListenPort=9016
tcpSelectorTimeout=100
tcpThreadCount=6/
Sender
className=org.apache.catalina.cluster.tcp.ReplicationTransmitter
replicationMode=fastasyncqueue
recoverTimeout=5000
recoverCounter=6
doTransmitterProcessingStats=true
doProcessingStats=true
doWaitAckStats=true
queueTimeWait=true
queueDoStats=true
queueCheckLock=true
ackTimeout=15000
waitForAck=true
keepAliveTimeout=8
keepAliveMaxRequestCount=-1/
Valve
className=org.apache.catalina.cluster.tcp.ReplicationValve
filter=.*\.gif;.*\.js;.*\.css;.*\.png;.*\.jpeg;.*\.jpg;.*\.htm;.*\.html;.*\.txt;
primaryIndicator=true /
Valve
className=org.apache.catalina.cluster.session.JvmRouteBinderValve
enabled=true /
ClusterListener
className=org.apache.catalina.cluster.session.ClusterSessionListener
/
ClusterListener
className=org.apache.catalina.cluster.session.JvmRouteSessionIDBinderListener
/
Deployer
className=org.apache.catalina.cluster.deploy.FarmWarDeployer
tempDir=${catalina.base}/war-temp
deployDir=${catalina.base}/war-deploy/
watchDir=${catalina.base}/war-listen/
watchEnabled=true/
/Cluster
-
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: Session Replication
yeah, but if you bind to 127.0.0.1 how do you expect clustering to work
between nodes? :)
Filip
Andrew Hole wrote:
Hello everyone!
For using Tomcat session clustering I need to put the following
component in all nodes?
Cluster
className=org.apache.catalina.cluster.tcp.SimpleTcpCluster
doClusterLog=true
clusterLogName=clusterlog
manager.className=org.apache.catalina.cluster.session.DeltaManager
manager.expireSessionsOnShutdown=false
manager.notifyListenersOnReplication=false
manager.notifySessionListenersOnReplication=false
manager.sendAllSessions=false
manager.sendAllSessionsSize=500
manager.sendAllSessionsWaitTime=20
Membership
className=org.apache.catalina.cluster.mcast.McastService
mcastAddr=228.0.0.4
mcastBindAddress=127.0.0.1
mcastClusterDomain=d10
mcastPort=45564
mcastFrequency=1000
mcastDropTime=3
recoveryCounter=10
recoveryEnabled=true
recoverySleepTime=5000/
Receiver
className=org.apache.catalina.cluster.tcp.ReplicationListener
tcpListenAddress=auto
tcpListenPort=9016
tcpSelectorTimeout=100
tcpThreadCount=6/
Sender
className=org.apache.catalina.cluster.tcp.ReplicationTransmitter
replicationMode=fastasyncqueue
recoverTimeout=5000
recoverCounter=6
doTransmitterProcessingStats=true
doProcessingStats=true
doWaitAckStats=true
queueTimeWait=true
queueDoStats=true
queueCheckLock=true
ackTimeout=15000
waitForAck=true
keepAliveTimeout=8
keepAliveMaxRequestCount=-1/
Valve
className=org.apache.catalina.cluster.tcp.ReplicationValve
filter=.*\.gif;.*\.js;.*\.css;.*\.png;.*\.jpeg;.*\.jpg;.*\.htm;.*\.html;.*\.txt;
primaryIndicator=true /
Valve
className=org.apache.catalina.cluster.session.JvmRouteBinderValve
enabled=true /
ClusterListener
className=org.apache.catalina.cluster.session.ClusterSessionListener
/
ClusterListener
className=org.apache.catalina.cluster.session.JvmRouteSessionIDBinderListener
/
Deployer
className=org.apache.catalina.cluster.deploy.FarmWarDeployer
tempDir=${catalina.base}/war-temp
deployDir=${catalina.base}/war-deploy/
watchDir=${catalina.base}/war-listen/
watchEnabled=true/
/Cluster
-
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]
Tomcat jsessionid cookie across subdomain valve
Hi all,
I have a web application that is installed on a virtual host that has a
number of subdomains defined with Alias elements in server.xml. We
would like cookie sessions persist to across these subdomains, and I
understand that this is not standard as defined in the servlet
specification. Therefore I am trying to write a custom Valve that
re-writes the domain on a Cookie to be .mydomain.com, rather than
www.mydomain.com. From searching the web to looking at what Daniel
Rall wrote for Tomcat 4 I have tried the invoke() method below in my
valve. Unfortunately, it doesn't seem to work; in my log I see the debug
output that tells me the domain is being set, but when I look at the
cookie in my Firefox web developer toolbar it says that the host of the
cookie is www.mydomain.com.
Has anyone got this to work in Tomcat 5.5.2? Why doesn't this code work
and can anybody tell me if there is anything else I need to change? From
what I can tell if this doesn't work my options are to edit Tomcat
sources or persuade the boss to get Resin (which supports this feature).
BTW I already have cookies=false in my Context for the time being, its
OK as an interim measure but I'd prefer to have cookies sorted.
public void invoke(Request request, Response response) throws
IOException, ServletException
{
if(request instanceof HttpServletRequest
response instanceof HttpServletResponse
request.getCookies() != null)
{
HttpServletRequest httprequest = (HttpServletRequest) request;
HttpServletResponse httpresponse = (HttpServletResponse)
response;
boolean domainwasset =
setDomainOnCookies(request.getCookies());
if(!domainwasset)
{
HttpSession session = httprequest.getSession();
if(session.isNew())
{
containerLog.info((session.isNew() ? new : old) +
session, requested ID=
+ httprequest.getRequestedSessionId() + , actual
ID = + session.getId());
Cookie cookie = new Cookie(Globals.SESSION_COOKIE_NAME,
session.getId());
cookie.setMaxAge(-1);
// Set the cookie path
String cookiepath = getCookiePath();
if(cookiepath == null || cookiepath.trim().length() == 0)
{
cookiepath = request.getContextPath();
if(cookiepath == null || cookiepath.trim().length() == 0)
{
cookiepath = /;
}
}
if(httprequest.isSecure())
{
cookie.setSecure(true);
}
cookie.setDomain(getCookieDomain());
containerLog.info(Adding cookie for + getCookieDomain());
httpresponse.addCookie(cookie);
}
}
}
// We're done, bring on the next valve
if(next != null)
{
next.invoke(request, response);
}
}
private boolean setDomainOnCookies(Cookie[] cookies)
{
boolean domainset = false;
if(cookies != null)
{
for(Cookie c : cookies)
{
if(c != null
c.getName().equals(Globals.SESSION_COOKIE_NAME))
{
containerLog.info(Setting cookie + c.getName() + to
+ getCookieDomain() + , was + c.getDomain());
c.setDomain(getCookieDomain());
domainset = true;
}
}
}
return domainset;
}
Thanks in advance
Dan Garland
[EMAIL PROTECTED]
__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
__
-
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.25 - 6.0.14 upgrade problem
hibernate is using the org.apache.commons.dbcp pool, so you need to configure that one, or tell hibernate to use tomcat's pool the clue here is, that tomcat's connection pool (while the same as commons.dbcp) has the package renamed to org.apache.tomcat.dbcp. this is a hibernate problem, your tomcat pool is configured correctly Filip aku1234 wrote: My code works on Tomcat 5.5.25, but when I move it to Tomcat 6.0.14 it stops working. When it starts up it succefully loads Acegi(Spring) which is using JNDI. Then when it tries to load Hibernate which uses the same JNDI resource, it doesn't work. Hibernate and JNDI work just fine on Tomcat 5.5.25. The exception says that it's trying to connect to URL 'null' which is pretty weird. The no suitable driver message is probably a byproduct of the null URL, since ojdbc.jar is in the lib directory. context.xml Context docBase=oms path=/oms reloadable=true Resource name=jdbc/OracleWellness type=javax.sql.DataSource auth=Container description=Database connection to Oracle wellness driverClassName=oracle.jdbc.driver.OracleDriver maxIdle=10 maxWait=1000 maxActive=20 username=foo password=bar url=jdbc:oracle:thin:@10.10.1.1:1521:topdb / web.xml resource-ref descriptionSQL Datasource for Oracle Wellness/description res-ref-namejdbc/OracleWellness/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref hibernate.cfg.xml session-factory property name=hibernate.connection.datasource java:comp/env/jdbc/OracleWellness /property /session-factory applicationContext-acegi-security.xml bean id=dataSource class=org.springframework.jndi.JndiObjectFactoryBean property name=jndiName valuejava:comp/env/jdbc/OracleWellness/value /property /bean INFO DatasourceConnectionProvider - Using datasource: java:comp/env/jdbc/OracleWellness WARN SettingsFactory - Could not obtain connection metadata org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null' at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:780) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540) at org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:69) at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:84) at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2009) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1292) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:915) at com.bhl.store.persistence.HibernateUtil.init(HibernateUtil.java:22) at com.bhl.store.persistence.HibernateUtil.getSessionFactory(HibernateUtil.java:44) at com.bhl.store.persistence.HibernateSessionRequestFilter.init(HibernateSessionRequestFilter.java:73) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:229) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:312) at org.apache.catalina.core.ApplicationFilterConfig.init(ApplicationFilterConfig.java:83) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3881) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4528) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1086) at org.apache.catalina.core.StandardHost.start(StandardHost.java:847) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1086) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:483) at org.apache.catalina.core.StandardService.start(StandardService.java:485) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2298) at org.apache.catalina.startup.Catalina.start(Catalina.java:537) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Caused by: java.sql.SQLException: No suitable driver at java.sql.DriverManager.getDriver(DriverManager.java:243) at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:773) ... 27 more INFO Dialect - Using dialect: org.hibernate.dialect.Oracle10gDialect
RE: Automatic Reload for Web Applications in User Directories
From: Niklas Frank [mailto:[EMAIL PROTECTED] Subject: Automatic Reload for Web Applications in User Directories My context.xml file looks like this: WatchedResourceWEB-INF/web.xml/WatchedResource Are you sure the timestamp on the WEB-INF/web.xml file of the updated webapp really changes? I tried adding a DefaultContext entry to the server.xml file The DefaultContext element was last supported in 5.0, so it certainly won't work in Tomcat 6. - 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: Session Replication
I only have one machine to test Session Replication. Every tomcat instances are in same machine. On 9/27/07, Caldarale, Charles R [EMAIL PROTECTED] wrote: From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Subject: Re: Session Replication yeah, but if you bind to 127.0.0.1 how do you expect clustering to work between nodes? :) Well, you could run all the Tomcat instances on the same box. What's that saying about eggs and baskets? - 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: Session Replication
then, the tcpListenPort must be unique for each instance, since you cannot share the port Filip Andrew Hole wrote: I only have one machine to test Session Replication. Every tomcat instances are in same machine. On 9/27/07, Caldarale, Charles R [EMAIL PROTECTED] wrote: From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Subject: Re: Session Replication yeah, but if you bind to 127.0.0.1 how do you expect clustering to work between nodes? :) Well, you could run all the Tomcat instances on the same box. What's that saying about eggs and baskets? - 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] - 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: Automatic Reload for Web Applications in User Directories
Hi Chuck, hi All, Are you sure the timestamp on the WEB-INF/web.xml file of the updated webapp really changes? Yes, positive. To check I made changes to the file. If I do the same for a web-app in $CATALINA_HOME/webapps the app gets automatically reloaded. in catalina.out this leads to: Sep 27, 2007 6:43:39 PM org.apache.catalina.startup.HostConfig checkResources INFO: Reloading context [/examples] but no reload or output is generated when I modify web.xml in the user dir. The DefaultContext element was last supported in 5.0, so it certainly won't work in Tomcat 6. ok, i thought it was deprecated, but just wanted to try anyway. thanks for confirming. do you have any ideas how i could go about this? kind regards dominik From: Niklas Frank [mailto:[EMAIL PROTECTED] Subject: Automatic Reload for Web Applications in User Directories My context.xml file looks like this: WatchedResourceWEB-INF/web.xml/WatchedResource Are you sure the timestamp on the WEB-INF/web.xml file of the updated webapp really changes? I tried adding a DefaultContext entry to the server.xml file The DefaultContext element was last supported in 5.0, so it certainly won't work in Tomcat 6. - 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: Session Replication
Thanks. Exists some layer to replicate database sessions? If my application is connected to an instance that crasches, every sessions dies. I would like to obtain response from the other database instance when this happens. Thanks On 9/27/07, Filip Hanik - Dev Lists [EMAIL PROTECTED] wrote: then, the tcpListenPort must be unique for each instance, since you cannot share the port Filip Andrew Hole wrote: I only have one machine to test Session Replication. Every tomcat instances are in same machine. On 9/27/07, Caldarale, Charles R [EMAIL PROTECTED] wrote: From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Subject: Re: Session Replication yeah, but if you bind to 127.0.0.1 how do you expect clustering to work between nodes? :) Well, you could run all the Tomcat instances on the same box. What's that saying about eggs and baskets? - 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] - 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: Session Replication
bit confused on what you are trying to achieve Filip Andrew Hole wrote: Thanks. Exists some layer to replicate database sessions? If my application is connected to an instance that crasches, every sessions dies. I would like to obtain response from the other database instance when this happens. Thanks On 9/27/07, Filip Hanik - Dev Lists [EMAIL PROTECTED] wrote: then, the tcpListenPort must be unique for each instance, since you cannot share the port Filip Andrew Hole wrote: I only have one machine to test Session Replication. Every tomcat instances are in same machine. On 9/27/07, Caldarale, Charles R [EMAIL PROTECTED] wrote: From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Subject: Re: Session Replication yeah, but if you bind to 127.0.0.1 how do you expect clustering to work between nodes? :) Well, you could run all the Tomcat instances on the same box. What's that saying about eggs and baskets? - 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] - 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 crash @ midnight - but why?
Martin Cavanagh wrote: Caldarale, Charles R wrote: From: Darek Czarkowski [mailto:[EMAIL PROTECTED] Subject: Re: Tomcat crash @ midnight - but why? Now, this would be funny, can you search the source code of the deployed application for System.exit call? Heres trouble...the System does call System.exit(), when it can't create the directory... - so I understand why my application would stop- but why would tomcat shutdown? It's also using the client JVM not the server JVM (I installed JRE and there is no server JVM) See that is funny after all, as other users explained system.exit will terminate JVM and not just your application. You should NEVER use this call in your application. Try to deal with the error in another way. -- Darek Czarkowski - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JRE 1.6 and Tomcat
Hi All, I have been using Tomcat (Embedded in JBoss) for several years now and back in june 2006 started a message thread where I switched from jre 1.5 to 1.6 and start to do some performance tuning and arch/design/implementation tuning. As of today I am in the 4 millisecond range for most of my transactions as measured at the client (RIA). My hope is to get down to the microsecond range as measured at the server some day soon. The link for the most of the discussing of tuning and some of the timing results is: http://www.jboss.org/index.html?module=bbop=viewtopict=84540 Most of my efforts focused on the embedded Tomcat inside JBoss. I am currently using JBoss 4.2.1 which has some version of 6 in it. I am trying to get to configuration where Tomcat 6 is used standalone rather than embedded. Also for the server I am using Apache 2.2.4 running on windows 2000 32-bit on a AMD64 X2 5200+ and my RIA is running on XP on a P4 3Ghz using a 1GBps Ethernet and 1Gb Router adn switch. I hope this answers some questions regarding the performance of jre 1.6. Regards, Tony Anecito Founder, MyUniPortal http://www.myuniportal.com Don't let your dream ride pass you by. Make it a reality with Yahoo! Autos. http://autos.yahoo.com/index.html - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat hangs, what to do to diagnose the problem?
Our Tomcat 4.1.30 instance seems to hang about once a week. i.e. the application is unresponsive and it can not be restarted from the management console. Tomcat must be restarted to restore functionality. There is nothing in the logs to indicate explicitly what is going on. The only logging that may be diagnostic is what gets logged when we attempt to restart the hung application. 2007-09-27 10:49:55 HTMLManager: restart: Reloading web application at '/OWEB' 2007-09-27 10:49:55 StandardContext[/OWEB]: Reloading this Context has started 2007-09-27 10:49:55 StandardWrapper[/OWEB:ControllerServlet]: Waiting for 66 instance(s) to be deallocated I'm not sure what this means but if there are 66 instances of the applications controller servlet that could be a clue as to what is going on. There should be only one. This instance of Tomcat is running only our application. We did not see this behavior with the previous release. We do not see the behavior on any of the three development/test machines. Along with a new release we moved from Java 1.4 to Java 5.0. The server in question is running Linux. Can anyone suggest diagnostics to tell what is going on? Are there any known scenarios that result in this 'hung' behavior? Thanks for any guidance, -=bill - 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.25 - 6.0.14 upgrade problem
I did some investigation and found a commons-dbcp and commons-pool
in my lib directory. I removed those, so now it's using
org.apache.tomcat.dbcp.dbcp.BasicDataSource, but I get a similar error.
I'm not sure what's wrong. I did notice that Tomcat 6 uses tomcat-dbcp
instead of commons-dbcp. I'm thinking that might be part of the problem,
but I don't know enough about tomcat-dbcp to figure it out.
Augustin
The new stacktrace:
INFO NamingHelper - JNDI InitialContext properties:{}
INFO DatasourceConnectionProvider - Using datasource:
java:comp/env/jdbc/OracleWellness
WARN SettingsFactory - Could not obtain connection metadata
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC driver of
class '' for connect URL 'null'
at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1150)
at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
at
org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:69)
at
org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:84)
at
org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2009)
at
org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1292)
at
org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:915)
at
com.bhl.store.persistence.HibernateUtil.init(HibernateUtil.java:22)
at
com.bhl.store.persistence.HibernateUtil.getSessionFactory(HibernateUtil.java:44)
at
com.bhl.store.persistence.HibernateSessionRequestFilter.init(HibernateSessionRequestFilter.java:73)
at
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
at
org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397)
at
org.apache.catalina.core.ApplicationFilterConfig.init(ApplicationFilterConfig.java:108)
at
org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3696)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4343)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825)
at
org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at
org.apache.catalina.core.StandardService.start(StandardService.java:516)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:566)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getDriver(DriverManager.java:243)
at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1143)
... 36 more
INFO Dialect - Using dialect: org.hibernate.dialect.Oracle10gDialect
Filip Hanik - Dev Lists wrote:
hibernate is using the org.apache.commons.dbcp pool, so you need to
configure that one, or tell hibernate to use tomcat's pool
the clue here is, that tomcat's connection pool (while the same as
commons.dbcp) has the package renamed to org.apache.tomcat.dbcp.
this is a hibernate problem, your tomcat pool is configured correctly
Filip
--
View this message in context:
http://www.nabble.com/Tomcat-5.5.25--%3E-6.0.14-upgrade-problem-tf4525323.html#a12928430
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail: users@tomcat.apache.org
To
RE: Tomcat hangs, what to do to diagnose the problem?
From: Wm.A.Stafford [mailto:[EMAIL PROTECTED] Subject: Tomcat hangs, what to do to diagnose the problem? Can anyone suggest diagnostics to tell what is going on? Try the usual: 1) enable JMX monitoring (-Dcom.sun.management.jmxremote) and look at the JVM with JConsole, especially at the heap and PermGen usage 2) get a thread dump (kill -3) and see where everybody is stuck - 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 hangs, what to do to diagnose the problem?
do kill -3 tomcat pid that generates stack trace for each thread (aka thread dump) into std.out, you might want to do it twice so that you can compare them dump Filip Wm.A.Stafford wrote: Our Tomcat 4.1.30 instance seems to hang about once a week. i.e. the application is unresponsive and it can not be restarted from the management console. Tomcat must be restarted to restore functionality. There is nothing in the logs to indicate explicitly what is going on. The only logging that may be diagnostic is what gets logged when we attempt to restart the hung application. 2007-09-27 10:49:55 HTMLManager: restart: Reloading web application at '/OWEB' 2007-09-27 10:49:55 StandardContext[/OWEB]: Reloading this Context has started 2007-09-27 10:49:55 StandardWrapper[/OWEB:ControllerServlet]: Waiting for 66 instance(s) to be deallocated I'm not sure what this means but if there are 66 instances of the applications controller servlet that could be a clue as to what is going on. There should be only one. This instance of Tomcat is running only our application. We did not see this behavior with the previous release. We do not see the behavior on any of the three development/test machines. Along with a new release we moved from Java 1.4 to Java 5.0. The server in question is running Linux. Can anyone suggest diagnostics to tell what is going on? Are there any known scenarios that result in this 'hung' behavior? Thanks for any guidance, -=bill - 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 5.5.25 - 6.0.14 upgrade problem
ok, that's a good start. take a look at this
Caused by: java.sql.SQLException: No suitable driver
did you put the .jar file for the JDBC driver in TC_HOME/lib?
Filip
aku1234 wrote:
I did some investigation and found a commons-dbcp and commons-pool
in my lib directory. I removed those, so now it's using
org.apache.tomcat.dbcp.dbcp.BasicDataSource, but I get a similar error.
I'm not sure what's wrong. I did notice that Tomcat 6 uses tomcat-dbcp
instead of commons-dbcp. I'm thinking that might be part of the problem,
but I don't know enough about tomcat-dbcp to figure it out.
Augustin
The new stacktrace:
INFO NamingHelper - JNDI InitialContext properties:{}
INFO DatasourceConnectionProvider - Using datasource:
java:comp/env/jdbc/OracleWellness
WARN SettingsFactory - Could not obtain connection metadata
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC driver of
class '' for connect URL 'null'
at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1150)
at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
at
org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:69)
at
org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:84)
at
org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2009)
at
org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1292)
at
org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:915)
at
com.bhl.store.persistence.HibernateUtil.init(HibernateUtil.java:22)
at
com.bhl.store.persistence.HibernateUtil.getSessionFactory(HibernateUtil.java:44)
at
com.bhl.store.persistence.HibernateSessionRequestFilter.init(HibernateSessionRequestFilter.java:73)
at
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
at
org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397)
at
org.apache.catalina.core.ApplicationFilterConfig.init(ApplicationFilterConfig.java:108)
at
org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3696)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4343)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825)
at
org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at
org.apache.catalina.core.StandardService.start(StandardService.java:516)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:566)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getDriver(DriverManager.java:243)
at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1143)
... 36 more
INFO Dialect - Using dialect: org.hibernate.dialect.Oracle10gDialect
Filip Hanik - Dev Lists wrote:
hibernate is using the org.apache.commons.dbcp pool, so you need to
configure that one, or tell hibernate to use tomcat's pool
the clue here is, that tomcat's connection pool (while the same as
commons.dbcp) has the package renamed to org.apache.tomcat.dbcp.
this is a hibernate problem, your tomcat pool is configured correctly
Filip
-
To start a new topic, e-mail: users@tomcat.apache.org
To
Re: Tomcat 5.5.25 - 6.0.14 upgrade problem
Yes. Anything else I should look at?
Filip Hanik - Dev Lists wrote:
ok, that's a good start. take a look at this
Caused by: java.sql.SQLException: No suitable driver
did you put the .jar file for the JDBC driver in TC_HOME/lib?
Filip
aku1234 wrote:
I did some investigation and found a commons-dbcp and commons-pool
in my lib directory. I removed those, so now it's using
org.apache.tomcat.dbcp.dbcp.BasicDataSource, but I get a similar error.
I'm not sure what's wrong. I did notice that Tomcat 6 uses tomcat-dbcp
instead of commons-dbcp. I'm thinking that might be part of the problem,
but I don't know enough about tomcat-dbcp to figure it out.
Augustin
The new stacktrace:
INFO NamingHelper - JNDI InitialContext properties:{}
INFO DatasourceConnectionProvider - Using datasource:
java:comp/env/jdbc/OracleWellness
WARN SettingsFactory - Could not obtain connection metadata
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC driver
of
class '' for connect URL 'null'
at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1150)
at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
at
org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:69)
at
org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:84)
at
org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2009)
at
org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1292)
at
org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:915)
at
com.bhl.store.persistence.HibernateUtil.init(HibernateUtil.java:22)
at
com.bhl.store.persistence.HibernateUtil.getSessionFactory(HibernateUtil.java:44)
at
com.bhl.store.persistence.HibernateSessionRequestFilter.init(HibernateSessionRequestFilter.java:73)
at
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
at
org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397)
at
org.apache.catalina.core.ApplicationFilterConfig.init(ApplicationFilterConfig.java:108)
at
org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3696)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4343)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825)
at
org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at
org.apache.catalina.core.StandardService.start(StandardService.java:516)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:566)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getDriver(DriverManager.java:243)
at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1143)
... 36 more
INFO Dialect - Using dialect: org.hibernate.dialect.Oracle10gDialect
Filip Hanik - Dev Lists wrote:
hibernate is using the org.apache.commons.dbcp pool, so you need to
configure that one, or tell hibernate to use tomcat's pool
the clue here is, that tomcat's connection pool (while the same as
commons.dbcp) has the package renamed to org.apache.tomcat.dbcp.
this is a hibernate problem, your tomcat
Re: Tomcat 5.5.25 - 6.0.14 upgrade problem
aku1234 wrote:
Yes. Anything else I should look at?
As Filip pointed out, without a driver you'll go nowhere. This would
appear to be the immediate issue to deal with.
What driver jar did you put in the lib dir?
Is there another copy in your WEB-INF/lib? You must remove that one if
there is.
p
Filip Hanik - Dev Lists wrote:
ok, that's a good start. take a look at this
Caused by: java.sql.SQLException: No suitable driver
did you put the .jar file for the JDBC driver in TC_HOME/lib?
Filip
aku1234 wrote:
I did some investigation and found a commons-dbcp and commons-pool
in my lib directory. I removed those, so now it's using
org.apache.tomcat.dbcp.dbcp.BasicDataSource, but I get a similar error.
I'm not sure what's wrong. I did notice that Tomcat 6 uses tomcat-dbcp
instead of commons-dbcp. I'm thinking that might be part of the problem,
but I don't know enough about tomcat-dbcp to figure it out.
Augustin
The new stacktrace:
INFO NamingHelper - JNDI InitialContext properties:{}
INFO DatasourceConnectionProvider - Using datasource:
java:comp/env/jdbc/OracleWellness
WARN SettingsFactory - Could not obtain connection metadata
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC driver
of
class '' for connect URL 'null'
at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1150)
at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
at
org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:69)
at
org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:84)
at
org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2009)
at
org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1292)
at
org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:915)
at
com.bhl.store.persistence.HibernateUtil.init(HibernateUtil.java:22)
at
com.bhl.store.persistence.HibernateUtil.getSessionFactory(HibernateUtil.java:44)
at
com.bhl.store.persistence.HibernateSessionRequestFilter.init(HibernateSessionRequestFilter.java:73)
at
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
at
org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397)
at
org.apache.catalina.core.ApplicationFilterConfig.init(ApplicationFilterConfig.java:108)
at
org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3696)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4343)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825)
at
org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at
org.apache.catalina.core.StandardService.start(StandardService.java:516)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:566)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getDriver(DriverManager.java:243)
at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1143)
... 36 more
INFO Dialect - Using dialect: org.hibernate.dialect.Oracle10gDialect
Filip Hanik - Dev Lists wrote:
hibernate is using the org.apache.commons.dbcp pool,
Re: Tomcat hangs, what to do to diagnose the problem?
On 9/27/07, Wm.A.Stafford [EMAIL PROTECTED] wrote: Our Tomcat 4.1.30 instance seems to hang about once a week. i.e. the application is unresponsive and it can not be restarted from the management console. Tomcat must be restarted to restore functionality. There is nothing in the logs to indicate explicitly what is going on. The only logging that may be diagnostic is what gets logged when we attempt to restart the hung application. 2007-09-27 10:49:55 HTMLManager: restart: Reloading web application at '/OWEB' 2007-09-27 10:49:55 StandardContext[/OWEB]: Reloading this Context has started 2007-09-27 10:49:55 StandardWrapper[/OWEB:ControllerServlet]: Waiting for 66 instance(s) to be deallocated I'm not sure what this means but if there are 66 instances of the applications controller servlet that could be a clue as to what is going on. There should be only one. This instance of Tomcat is running only our application. We did not see this behavior with the previous release. We do not see the behavior on any of the three development/test machines. Along with a new release we moved from Java 1.4 to Java 5.0. The server in question is running Linux. Can anyone suggest diagnostics to tell what is going on? Are there any known scenarios that result in this 'hung' behavior? Thanks for any guidance, -=bill - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Does that version of Tomcat leak OS resources (e.g. file handles) when reloading webapps (v. a server stop/start)? - 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.25 - 6.0.14 upgrade problem
I double checked everything. There is an ojdbc.jar file in TC_HOME/lib and nowhere else. I'm not sure that it even knows what driver it's trying to load. The top part of the stacktrace was: Cannot create JDBC driver of class '' for connect URL 'null' Augustin aku1234 wrote: Yes. Anything else I should look at? As Filip pointed out, without a driver you'll go nowhere. This would appear to be the immediate issue to deal with. What driver jar did you put in the lib dir? Is there another copy in your WEB-INF/lib? You must remove that one if there is. p -- View this message in context: http://www.nabble.com/Tomcat-5.5.25--%3E-6.0.14-upgrade-problem-tf4525323.html#a12929828 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: Tomcat 5.5.25 - 6.0.14 upgrade problem
yeah, but you are not using ojdbc, you are using oracle's driver oracle.jdbc.driver.OracleDriver for this, you need to have classes12.jar Filip aku1234 wrote: I double checked everything. There is an ojdbc.jar file in TC_HOME/lib and nowhere else. I'm not sure that it even knows what driver it's trying to load. The top part of the stacktrace was: Cannot create JDBC driver of class '' for connect URL 'null' Augustin aku1234 wrote: Yes. Anything else I should look at? As Filip pointed out, without a driver you'll go nowhere. This would appear to be the immediate issue to deal with. What driver jar did you put in the lib dir? Is there another copy in your WEB-INF/lib? You must remove that one if there is. p - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Identify a Startup Error Message
Hello All Tomcat Gurus!! :-) Windows XP SP2 Tomcat 5.5.25 Java JDK - 1.5.0_06 JRE - 1.5.0_06 We have a Web-application, Actually it is our ERP system that has a web based interface that uses Tomcat and Java. Every time I startup Tomcat using c:\tomcat\bin\startup.sh file I get the following messages: Does anybody what are these messages? I can get Tomcat up and running, but not an expert though. Can anybody give some highlights? INFO: XML validation disabled - Unable to find required classes )javax.activation.DataHandler and javax.mail.internet.MimeMultipart). Attachment support is disabled. - Duplicated component startup order. (component= com.qad.chart.mgrs.IDataSourceManager;order=3) ParameterManager: Loading using Env mgr with config-files.xml ParameterManager: Loading log4j:WARN No appenders could be found for logger ( org.apache.struts.util.PropertyMessageResources). But after these messages, Tomcat startup ok and I can get into the application. INFO: Server startup in 20309 ms Thanks in advance, Best Regards, Bruno
New to Apache
Hi, I'm new to these technologies and hope one of you pros can point me in the correct location. We are using a product written in Java that integrates into our website. This product obviously needs to run under a J2EE compliant application server so we choose Apache Tomcat 5.5 with Java 1.5. However we are having a lot of issues with performance and are trying to diagnose these issues. We are running on a Windows 2003 Server and running Apache Tomcat as a Windows service. The two things I'd like to find out are (1) how do you measure the performance of Apache and (2) where can I find good documentation on the different options/parameters/etc on running an Apache server as a Windows service? Also, I ran across some statements before about server configurations/options? Where can I find information on that topic? Thanks, Tony - 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.25 - 6.0.14 upgrade problem
I'm sorry, I must have confused you. After we dowloaded ojdbc14.jar from Oracle we just renamed it to ojdbc.jar. I believe this is for use with JDK 1.4 and above. I think the classes12.jar is for JDK 1.2 and 1.3. For the record we're using the latest version of Java 5. I opened up ojdbc14.jar to verified that oracle.jdbc.driver.OracleDriver was there. It was. I also tried using the latest Oracle JDBC driver, but I got the same error message. Augustin Filip Hanik - Dev Lists wrote: yeah, but you are not using ojdbc, you are using oracle's driver oracle.jdbc.driver.OracleDriver for this, you need to have classes12.jar Filip aku1234 wrote: I double checked everything. There is an ojdbc.jar file in TC_HOME/lib and nowhere else. I'm not sure that it even knows what driver it's trying to load. The top part of the stacktrace was: Cannot create JDBC driver of class '' for connect URL 'null' Augustin aku1234 wrote: Yes. Anything else I should look at? As Filip pointed out, without a driver you'll go nowhere. This would appear to be the immediate issue to deal with. What driver jar did you put in the lib dir? Is there another copy in your WEB-INF/lib? You must remove that one if there is. p - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Tomcat-5.5.25--%3E-6.0.14-upgrade-problem-tf4525323.html#a12930859 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: Tomcat 5.5.25 - 6.0.14 upgrade problem
got it, you could turn on debugging for DBCP and JNDI, by adding org.apache.naming.level=FINE org.apache.tomcat.dbcp.level=FINE to the bottom of your TC_HOME/conf/logging.properties that might give you a clue, somehow your entered JNDI names don't match with what Tomcat think it has bound the datasource too. Filip aku1234 wrote: I'm sorry, I must have confused you. After we dowloaded ojdbc14.jar from Oracle we just renamed it to ojdbc.jar. I believe this is for use with JDK 1.4 and above. I think the classes12.jar is for JDK 1.2 and 1.3. For the record we're using the latest version of Java 5. I opened up ojdbc14.jar to verified that oracle.jdbc.driver.OracleDriver was there. It was. I also tried using the latest Oracle JDBC driver, but I got the same error message. Augustin Filip Hanik - Dev Lists wrote: yeah, but you are not using ojdbc, you are using oracle's driver oracle.jdbc.driver.OracleDriver for this, you need to have classes12.jar Filip aku1234 wrote: I double checked everything. There is an ojdbc.jar file in TC_HOME/lib and nowhere else. I'm not sure that it even knows what driver it's trying to load. The top part of the stacktrace was: Cannot create JDBC driver of class '' for connect URL 'null' Augustin aku1234 wrote: Yes. Anything else I should look at? As Filip pointed out, without a driver you'll go nowhere. This would appear to be the immediate issue to deal with. What driver jar did you put in the lib dir? Is there another copy in your WEB-INF/lib? You must remove that one if there is. p - 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 can java do this
import java.io.Serializable;
public class Accomplice {
/**
* @param args
*/
public static void main(String[] args) {
// TODO Auto-generated method stub
Data d=new Data();
System.out.println(d.getS(4));
System.out.println(Data.count);
System.out.println(d.getS(3));
System.out.println(Data.count);
}
}
final class Data implements Serializable
{
public static int count=0;
public Data()
{
Data.counter();
}
private static void counter()
{
count=count+1;
if(count=2)
{
s=null;
}
}
private static String s=abc;
public String getS(int key)
{
if(key==3)
{
Data.counter();
return s;
}
else
{
Data.counter();
return try again;
}
}
}
Hi all see if you can hack to the Data i call it the tapeworm concept.
Thanks
Regards
Shivakanth
-
Luggage? GPS? Comic books?
Check out fitting gifts for grads at Yahoo! Search.
RE: Tomcat hangs when shutting down
Chuck, Thankyou very much. This pointed me in the correct direction. I didn't notice the 8009 connector. I am running tomcat standalone, and I have no need for an 8009 connector. When I commented it out, my issue is resolved. Regards, Andrew -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Thursday, 27 September 2007 3:20 PM To: Tomcat Users List Subject: RE: Tomcat hangs when shutting down From: Andrew Friebel [mailto:[EMAIL PROTECTED] Subject: RE: Tomcat hangs when shutting down I have no AprLifecycleListener to comment out in server.xml The APR connector did not exist in Tomcat 5.0. Sep 26, 2007 9:00:57 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 This probably isn't relevant, but mod_jk2 has been deprecated for something over two years. You might want to switch to mod_jk (it's the one undergoing active development), and see if it has any effect. - 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: New to Apache
Please don't hi-jack threads. 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]
Re: Identify a Startup Error Message
Bruno Vilardo wrote: INFO: XML validation disabled Tomcat message. Tells you context.xml files and tld files will not be validated. - Unable to find required classes )javax.activation.DataHandler and javax.mail.internet.MimeMultipart). Attachment support is disabled. Struts message. Tells you a couple of optional JARs are not present so you can't use attachments with SOAP messages. - Duplicated component startup order. (component= com.qad.chart.mgrs.IDataSourceManager;order=3) No idea. This is from a 3rd party JAR I have never used. ParameterManager: Loading using Env mgr with config-files.xml ParameterManager: Loading No idea. log4j:WARN No appenders could be found for logger ( org.apache.struts.util.PropertyMessageResources). Log4j message. Log4j isn't configured properly. See the log4j docs for info on this. HTH, 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]
Re: How can java do this
Please don't hi-jack threads. 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]
Re: Automatic Reload for Web Applications in User Directories
Niklas Frank wrote: Hi Chuck, hi All, Are you sure the timestamp on the WEB-INF/web.xml file of the updated webapp really changes? Yes, positive. To check I made changes to the file. If I do the same for a web-app in $CATALINA_HOME/webapps the app gets automatically reloaded. This won't work. o.a.c.startup.UserConfig doesn't use o.a.c.startup.HostConfig to deploy the user contexts so they never get checked for re-loading. Some thought needs to be applied to refactoring UserConfig. Ideally, HostConfig should be completely de-coupled from UserConfig. Please create a bugzilla entry for this. 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]
Re: Tomcat hangs, what to do to diagnose the problem?
Hi, Sorry if i'd hijacked this thread, just wonder is the JMX package bundled together with Tomcat 4.1 as well? or it's only available to Tomcat 5.0 onwards? Thanx FooShyn Caldarale, Charles R wrote: From: Wm.A.Stafford [mailto:[EMAIL PROTECTED] Subject: Tomcat hangs, what to do to diagnose the problem? Can anyone suggest diagnostics to tell what is going on? Try the usual: 1) enable JMX monitoring (-Dcom.sun.management.jmxremote) and look at the JVM with JConsole, especially at the heap and PermGen usage 2) get a thread dump (kill -3) and see where everybody is stuck - 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: Tomcat hangs, what to do to diagnose the problem?
Please do not hi-jack threads. 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]
RE: Tomcat hangs, what to do to diagnose the problem?
From: foo shyn [mailto:[EMAIL PROTECTED] Subject: Re: Tomcat hangs, what to do to diagnose the problem? just wonder is the JMX package bundled together with Tomcat 4.1 as well? or it's only available to Tomcat 5.0 onwards? JMX (and therefore JConsole) is dependent on the JRE level, not Tomcat. You need a 1.5 or later Sun JDK in order to use JConsole. (Newer versions of Tomcat use JMX MBeans, but we're interested in the ones internal to the JVM in order to examine heap consumption.) - 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]
