Re: Tomcat hangs when cmd window fills up
2009/10/13 Ron McNulty rmcnu...@xtra.co.nz: Hi all This is possibly a little OT, but maybe someone has come across this. We are running Tomcat 5 (Actually Jetspeed-2.1.3) on a Windows 2K box. We start it from a cmd window, using startup.bat. All runs fine until a large amount of text gets output to the log (redirected to the Tomcat window). Tomcat then locks up. Pressing ctrl C produces another burst of data, and makes things run again for a while. I suspect this is not a Tomcat problem, but I can't find anything on google that helps. If it is not garbage collection, then maybe some synchronization. Writing out a large amount of text to a console may take some time, if console draws slowly. If the writing thread owns some synchronized resource, other threads can wait to obtain it. The output stream itself can be such resource (for example, PrintWriter.write() has a synchronized block), but you won't notice congestion with writing unless some other threads are also trying to write. It might be as well some other valuable resource somewhere up the call chain. Your thread dumps might help you to spot it. http://wiki.apache.org/tomcat/HowTo#How_do_I_obtain_a_thread_dump_of_my_running_webapp_.3F Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Question ad alternative of BSF taglib in Tomcat ? [Fwd: In the move of some taglibs to Tomcat, the BSF taglib got retired]
Henri Yandell wrote: Not sure where Christopher's email was, but: If there is any interest in a retired taglib, I'm all for it being merged into the Extended Taglib. Currently I plan to consider replacing the functionality from String Taglib (mostly as EL functions), Log Taglib and JNDI Taglib (perhaps). It sounds like BSF taglib, given it has only the two tags, might be very interesting if a dependency on BSF itself can be avoided (ie: base it on javax.script). +1 If you include just the taglib (the JSR-223 to be created), then its usage would be restricted to Java 6 and up, such that current Java 1.4 and 1.5 installations in the field could not take advantage of it. To cover Java 1.4 and 1.5 BSF 3.0 got created, which implements the javax.script specifications. If BSF 3.0 is included then the scripting support will be available from Java 1.4 on. Starting with Java 6 the Java 6 javax.script would prevail due to using its own package by placement of the classes. ---rony - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Multiple Domains on one Tomcat Server now MySQL not working
Hi Chuck, thanks for this detailed answer. I'm running tomcat 6 on an ubuntu server. I read the official documentation and modified the configuration of my tomcat. The complete current server.xml (without comments and after my latest modification) looks like this: server.xml: Server port=8005 shutdown=SHUTDOWN Listener className=org.apache.catalina.core.AprLifecycleListener SSLEngine=on / Listener className=org.apache.catalina.core.JasperListener / Listener className=org.apache.catalina.mbeans.ServerLifecycleListener / Listener className=org.apache.catalina.mbeans.GlobalResourcesLifecycleListener / GlobalNamingResources Resource name=UserDatabase auth=Container type=org.apache.catalina.UserDatabase description=User database that can be updated and saved factory=org.apache.catalina.users.MemoryUserDatabaseFactory pathname=conf/tomcat-users.xml / /GlobalNamingResources Service name=Catalina Connector port=8080 protocol=HTTP/1.1 connectionTimeout=2 redirectPort=8443 / Connector port=8009 protocol=AJP/1.3 redirectPort=8443 / Engine name=Catalina defaultHost=localhost Realm className=org.apache.catalina.realm.UserDatabaseRealm resourceName=UserDatabase/ Host name=localhost appBase=webapps unpackWARs=true autoDeploy=true xmlValidation=false xmlNamespaceAware=false /Host Host name=localhost.localdomain debug=0 appBase=webapps2 unpackWARs=true autoDeploy=true xmlValidation=false xmlNamespaceAware=false Aliaswww.clubpirat.de/Alias /Host /Engine /Service /Server I checked that in /etc/hosts the two domains localhost and localhost.localdomain are assigned to 127.0.0.1. Now, i have the following directory structure: CATALINA_HOME/webapps CATALINA_HOME/webapps2 CATALINA_HOME/conf/Catalina/localhost CATALINA_HOME/conf/Catalina/localhost.localdomain CATALINA_HOME/webapps2/ROOT/META-INF In CATALINA_HOME/conf/Catalina/localhost.localdomain i got the following files: ROOT.xml log4j_errors.log manager.xml And the latter ROOT.xml looks like this: ?xml version='1.0' encoding='utf-8'? Context displayName=localhost.localdomain workDir=work/Catalina/clubpirat.de/_ /Context I also copied my war file into the CATALINA_HOME/webapps2 directory and tomcat has deploied the file. Okay, i when enter the url www.clubpirat.de but i get an 404 error. The other url works fine, no problems. Caldarale, Charles R schrieb: From: Paul van Hoven [mailto:paul.van.ho...@googlemail.com] Subject: Multiple Domains on one Tomcat Server now MySQL not working I'm not shure if this problem really relates to Tomcat but it happened after altering the tomcat configuration. Care to give us a hint about version of Tomcat you're using? Configuration is different from level to level. Therefore i search on the internet how to manage multiple domains on Tomcat. Might be better to read the real documentation first: http://tomcat.apache.org/tomcat-6.0-doc/virtual-hosting-howto.html http://tomcat.apache.org/tomcat-5.5-doc/virtual-hosting-howto.html I found this resource: http://www.westsoftware.net/java/domains-on-tomcat.jsp. It's unfortunate you found that, since it's chock full of errors. Host name=localhost appBase=webapps unpackWARs=true autoDeploy=true xmlValidation=false xmlNamespaceAware=false /Host Host name=mydomain.de debug=0 appBase=webapps/myapp2 The above is not good; the different appBase directories must be distinct, not one under another. unpackWARs=true autoDeploy=true xmlValidation=false xmlNamespaceAware=false Logger className=org.apache.catalina.logger.FileLogger directory=logs prefix=mydomain.de-log. suffix=.txt timestamp=true/ Logger elements have not been used in Tomcat for some years. Aliaswww.mydomain.de/Alias /Host /Engine /Service /Server and i added the follwing ROOT.xml file in the folder $CATALINA_HOME/conf/Catalina/mydomain.de ROOT.xml: ?xml version='1.0' encoding='utf-8'? Context displayName=mydomain.de docBase= path= workDir=work/Catalina/mydomain.de/_ /Context Both the docBase and path attributes have invalid values; luckily, neither one is allowed here, and they are hopefully being ignored. Actually it works fine, i can now differentiate between the two webapps by the domain. What two webapps? You have only shown us one Context element. But while the first webapp has no problems accessing the mysql database i do have problems with the second webapp for which i added the new configuration. What's the first webapp? What Resource
Re: SSL/HTTPS forwarding under Apache + mod_jk + tomcat
[This should really be a new thread, but...] 2009/10/13 Tezza auspa...@hotmail.com: I got 1 apache and 2 tomcat servers (all on different machines). I already got SSL set up on individual Tomcat machines to work on port 8443. There is no SSL installed on Apache. I got mod_jk installed on apache to forward all HTTP requests to tomcat servers for load balancing. It works fine. I like to also forward all HTTPS requests to tomcat servers. Question: Do I must install certificate (SSL) on apache server? Yes. and remove from tomcat servers??? No need - they're not doing any harm, they just won't be used in your environment. If possible: I prefer to leave SSL on tomcat servers, and just tell apache to forward all HTTPS to tomcats just like HTTP. My tomcat servers will handle the workload fine with https. Can it be done? No. If your clients use SSL to httpd, httpd must be able to handle the SSL connection - mod_jk has no way of forwarding raw encrypted data to Tomcat. Therefore httpd must have SSL set up locally - including the certificate. - Peter - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Datasource configuration issue
Hi, I am using Tomcat 5.0. I have one application test. In test i created META-INF folder and put context.xml file.Here is the content context resource name=jdbc/PDBDataSource scope=Shareable type=javax.sql.DataSource resourceparams name=jdbc/PDBDataSource parameter namefactory/name valueorg.apache.commons.dbcp.BasicDataSourceFactory/value /parameter parameter nameurl/name valuejdbc:sqlserver://localhost;DatabaseName=test;SelectMethod=cursor;/value /parameter parameter namedriverClassName/name valuecom.microsoft.jdbc.sqlserver.SQLServerDriver/value /parameter parameter nameusername/name valuesa/value /parameter parameter namepassword/name valuesa/value /parameter parameter /resourceparams /resource /context in WEB-INF\web.xml file i have the entires web-app resource-ref res-ref-namejdbc/PDBDataSource /res-ref-name res-type javax.sql.DataSource /res-type res-auth Container /res-auth /resource-ref /web-app in my jsp code i have the code Context initCtx = new InitialContext(); Context envCtx = (Context) initCtx.lookup(java:comp/env); DataSource ds = (DataSource) envCtx.lookup(jdbc/PDBDataSource); Connection conn = ds.getConnection(); conn.close(); I am getting the follwoing error when accessing my page javax.servlet.ServletException: Cannot create JDBC driver of class '' for connect URL 'null' org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:846) org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:779) org.apache.jsp.index_jsp._jspService(index_jsp.java:69) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) Help me to resolve this :confused: -- View this message in context: http://www.nabble.com/Datasource-configuration-issue-tp25868686p25868686.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: SSL/HTTPS forwarding under Apache + mod_jk + tomcat
Peter thank you; this part is clear to me now. Few more clarification:
and remove [certs] from tomcat servers???
No need - they're not doing any harm, they just won't be used in your
environment.
So in server.xml, I can leave the Connector SSLEnabled=true
port=8443...other other SSL related attributes.../ ???
Also, my current AJP connection is like this:
Connector port=8009 address=${jboss.bind.address}
protocol=AJP/1.3
emptySessionPath=true enableLookups=false redirectPort=8443
/
Do I need another connector in server.xml for mod_jk worker to forward HTTPS
traffic???
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
--
View this message in context:
http://www.nabble.com/SSL-HTTPS-forwarding-under-Apache-%2B-mod_jk-%2B-tomcat-tp17817647p25868827.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: trouble with connector configured to receive from SSL accelerator
2009/10/13 Sam Gendler sgend...@vid.me: That method uses request.getScheme(), to retrieve https (correct) and request.getServerName() to get the correct host name. It then calls request.getServerPort(), which incorrectly returns the value of 80. [...] What do I need to do to get the request to correctly return 443 as the port when a request arrives on the connector without any port in the url or Host header? The keyword to look for is Proxying - your SSL front-end is proxying the SSL connector for you. http://tomcat.apache.org/tomcat-6.0-doc/config/http.html shows connector attributes of proxyHost and proxyPort, which I think will do exactly what you want. Hope this helps! - Peter - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: PATCH: Session ID from URL; would like some input!
Johan Ström wrote: Hello list! First of all, this maybe better suited for the dev list, but a quick peek only showed svn log mails etc soo.. Sending here instead, let me know if its wrong! It is 50/50. The patch is of more interest to the dev list but if the patch is rejected then the users list is the best place to get ideas about other ways of doing things. The mailing lists block most patches so an enhancement request in Bugzilla is the best place for your patch. Without seeing the patch it is hard to comment but SRV.7.1 makes it clear that cookies override URL parameters. It doesn't make a comment on what if the cookie session is invalid and the URL one not. There might be some scope for flexibility here. We're having a problem related to Tomcat, in a pretty unusual scenario. Basicly the problem is with old expired sessions, and reading session ID from URL instead of cookie. An example, in our case browser A is a main browser, and browser B is a slave browser (actually only a webkit rendering engine) which we only call with an URL to show a specific page, and we do not have control over cookies in browser B. Any way to close browser B? That should delete the session cookie. So, browser B sends both the old session ID in the cookie (which is an expired session), and the new sessionid on the URL. This confuses tomcat. In catalina/connector/Request.java and CoyoteAdaptor, we first check for a sessino ID on the URL, store it in Request, and then we check for a cookie, and if we got one, we just overwrite the session ID from the URL. My solution? The attached patch! Now, what I'd like to know, can anyone of you developers see any nasty side effects that I might have missed about this? In principle, it sounds OK but I'd want to see the patch first. If it were implemented, then it would go into Tomcat 7 and may not be back-ported to earlier versions. It may also be made optional. Keep in mind that session handling is more configurable in the Servlet 3.0 spec (not that I think it helps with this issue) and that changing the session ID on authentication to protect against session fixation is an open enhancement request that should also get included in Tomcat 7. One thing that was concerned about was that it would introduce session hijacking risks, but the only difference is that the evildoer have to erase his (already expired) cookie.. Normal tomcat accepts jsessionid on URL anyway, as long as there is no cookie, so that should not be a security concern. Agreed. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Datasource configuration issue
VijayKS wrote: Hi, I am using Tomcat 5.0. I have one application test. In test i created META-INF folder and put context.xml file.Here is the content context That should be Context resource name=jdbc/PDBDataSource scope=Shareable That should be Resource ... Case matters. Check your config against the docs. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: SSL/HTTPS forwarding under Apache + mod_jk + tomcat
Peter Crowther wrote:
2009/10/13 Tezza auspa...@hotmail.com:
So in server.xml, I can leave the Connector SSLEnabled=true
port=8443...other other SSL related attributes.../ ???
If you want to, you can leave it. It's an extra way into your server,
and might be considered an extra attack vector for a cracker, so you
might also want to remove it :-).
Also, my current AJP connection is like this:
Connector port=8009 address=${jboss.bind.address}
protocol=AJP/1.3
emptySessionPath=true enableLookups=false redirectPort=8443
/
Do I need another connector in server.xml for mod_jk worker to forward HTTPS
traffic???
I'll leave that to one of the experts - I know the theory, but have
never had to maintain an AJP system in reality.
No, you don't need a separate connector to proxy SSL over AJP. The AJP
protocol is smart enough to pass along the SSL info Tomcat needs.
Mark
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
PATCH: Session ID from URL; would like some input!
Hello list! First of all, this maybe better suited for the dev list, but a quick peek only showed svn log mails etc soo.. Sending here instead, let me know if its wrong! We're having a problem related to Tomcat, in a pretty unusual scenario. Basicly the problem is with old expired sessions, and reading session ID from URL instead of cookie. An example, in our case browser A is a main browser, and browser B is a slave browser (actually only a webkit rendering engine) which we only call with an URL to show a specific page, and we do not have control over cookies in browser B. 1. Browser A goes to our site, gets a new session, authenticates etc. 2. Browser A spawns browser B with url http://example.com/someresource;jsessionid= the session ID from browser A's cookie 3. Browser B loads the page, no session cookie provided since its freshly started, and gets the correct session. Now, lets say both browsers are idle for awhile, enough for the session to timeout 1. Browser A does some activity again, noticing that he got a new JSESSIONID cookie and re-authenticates in the new session. 2. Browser A spawns browser B with an url containing the new jsessionid 3 (this is where the problem is). Browser B loads the page, this time with its old jsessionid cookie, and also the new jsessionid on the URL. So, browser B sends both the old session ID in the cookie (which is an expired session), and the new sessionid on the URL. This confuses tomcat. In catalina/connector/Request.java and CoyoteAdaptor, we first check for a sessino ID on the URL, store it in Request, and then we check for a cookie, and if we got one, we just overwrite the session ID from the URL. My solution? The attached patch! Now, what I'd like to know, can anyone of you developers see any nasty side effects that I might have missed about this? One thing that was concerned about was that it would introduce session hijacking risks, but the only difference is that the evildoer have to erase his (already expired) cookie.. Normal tomcat accepts jsessionid on URL anyway, as long as there is no cookie, so that should not be a security concern.. Well, thanks for any ideas and input, and for Tomcat ofcourse! Best regards Johan Ström Headweb AB - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: SSL/HTTPS forwarding under Apache + mod_jk + tomcat
2009/10/13 Tezza auspa...@hotmail.com:
So in server.xml, I can leave the Connector SSLEnabled=true
port=8443...other other SSL related attributes.../ ???
If you want to, you can leave it. It's an extra way into your server,
and might be considered an extra attack vector for a cracker, so you
might also want to remove it :-).
Also, my current AJP connection is like this:
Connector port=8009 address=${jboss.bind.address}
protocol=AJP/1.3
emptySessionPath=true enableLookups=false redirectPort=8443
/
Do I need another connector in server.xml for mod_jk worker to forward HTTPS
traffic???
I'll leave that to one of the experts - I know the theory, but have
never had to maintain an AJP system in reality.
- Peter
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat hangs for minutes between ContextConfig and StandardContext (Starting the app)
By any chance, is there a case mismatch - is your webapp properly
deployed in [appBase]/Spc.xml or perhaps incorrectly in
[appBase]/spc.xml?
I'm not sure I understand this question. The Spc.war file is copied to
${CATALINA_HOME}/webapps and Tomcat deploys it to
${CATALINA_HOME}/webapps/Spc. There is no other Spc.xml file except the
one in ${CATALINA_HOME}/conf/Catalina/localhost. Is there supposed to
be another Spc.xml file in the deployment?
Can you post your entire server.xml?
My server.xml (it should be the distribution copy with SSL and access
log enabled):
By the way, I appreciate your help and time, but I would surely
understand if you let this go - no one else where I work has this
problem and it doesn't seem to be endemic in the wider population of
Tomcat users. Any way, thanks again.
8--
---
?xml version='1.0' encoding='utf-8'?
!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version
2.0
(the License); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an AS IS BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied.
See the License for the specific language governing permissions and
limitations under the License.
--
!-- Note: A Server is not itself a Container, so you may not
define subcomponents such as Valves at this level.
Documentation at /docs/config/server.html
--
Server port=8005 shutdown=SHUTDOWN
!--APR library loader. Documentation at /docs/apr.html --
Listener className=org.apache.catalina.core.AprLifecycleListener
SSLEngine=on /
!--Initialize Jasper prior to webapps are loaded. Documentation at
/docs/jasper-howto.html --
Listener className=org.apache.catalina.core.JasperListener /
!-- JMX Support for the Tomcat server. Documentation at
/docs/non-existent.html --
Listener
className=org.apache.catalina.mbeans.ServerLifecycleListener /
Listener
className=org.apache.catalina.mbeans.GlobalResourcesLifecycleListener
/
!-- Global JNDI resources
Documentation at /docs/jndi-resources-howto.html
--
GlobalNamingResources
!-- Editable user database that can also be used by
UserDatabaseRealm to authenticate users
--
Resource name=UserDatabase auth=Container
type=org.apache.catalina.UserDatabase
description=User database that can be updated and saved
factory=org.apache.catalina.users.MemoryUserDatabaseFactory
pathname=conf/tomcat-users.xml /
/GlobalNamingResources
!-- A Service is a collection of one or more Connectors that
share
a single Container Note: A Service is not itself a
Container,
so you may not define subcomponents such as Valves at this
level.
Documentation at /docs/config/service.html
--
Service name=Catalina
!--The connectors can use a shared executor, you can define one or
more named thread pools--
!--
Executor name=tomcatThreadPool namePrefix=catalina-exec-
maxThreads=150 minSpareThreads=4/
--
!-- A Connector represents an endpoint by which requests are
received
and responses are returned. Documentation at :
Java HTTP Connector: /docs/config/http.html (blocking
non-blocking)
Java AJP Connector: /docs/config/ajp.html
APR (HTTP/AJP) Connector: /docs/apr.html
Define a non-SSL HTTP/1.1 Connector on port 8080
--
Connector port=8080 protocol=HTTP/1.1
connectionTimeout=2
redirectPort=8443 /
!-- A Connector using the shared thread pool--
!--
Connector executor=tomcatThreadPool
port=8080 protocol=HTTP/1.1
connectionTimeout=2
redirectPort=8443 /
--
!-- Define a SSL HTTP/1.1 Connector on port 8443
This connector uses the JSSE configuration, when using APR, the
connector should be using the OpenSSL style configuration
described in the APR documentation --
Connector port=8443 protocol=HTTP/1.1 SSLEnabled=true
maxThreads=150 scheme=https secure=true
clientAuth=false sslProtocol=TLS /
!-- Define an AJP 1.3 Connector on port 8009 --
Connector port=8009 protocol=AJP/1.3 redirectPort=8443 /
!-- An Engine represents the entry point (within Catalina) that
processes
every request. The Engine implementation for Tomcat stand
alone
analyzes the HTTP headers included with the request, and
Re: trouble with connector configured to receive from SSL accelerator
Is it possible that sessions aren't persistent when switching between connectors. The proxyPort attribute on the connector did fix my problem, but I've discovered that logging in over an https connection only works if I click the remember-me checkbox, which sets a cookie on the client and stores some state in a db which can associate the cookie with the identity of the user. If I don't use remember me, the authentication occurs when connected via the secure connector and the user's identity is stored in the session, but when the system switches back to the other connector, it fails to find the authorization info in the session, so it redirects right back to the login page via https. I suspect the session cookie is being set as https-only, so it doesn't get passed back when accessing via http. Is there any way to correct this behaviour? I'll confirm momentarily. On Tue, Oct 13, 2009 at 1:00 AM, Sam Gendler sgend...@vid.me wrote: That looks like it will work, but it doesn't explain why the connector would think port 80 was appropriate. I could see port 8090 showing up, but given that the scheme is https and there was no port number in the request, surely it should have resolved that to port 443 instead of port 80? It just seems like a bug to me. It does look like proxyPort can be used to force it to 443, though, so that will work. On Tue, Oct 13, 2009 at 12:19 AM, Peter Crowther peter.crowt...@melandra.com wrote: 2009/10/13 Sam Gendler sgend...@vid.me: That method uses request.getScheme(), to retrieve https (correct) and request.getServerName() to get the correct host name. It then calls request.getServerPort(), which incorrectly returns the value of 80. [...] What do I need to do to get the request to correctly return 443 as the port when a request arrives on the connector without any port in the url or Host header? The keyword to look for is Proxying - your SSL front-end is proxying the SSL connector for you. http://tomcat.apache.org/tomcat-6.0-doc/config/http.html shows connector attributes of proxyHost and proxyPort, which I think will do exactly what you want. Hope this helps! - Peter - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: trouble with connector configured to receive from SSL accelerator
That looks like it will work, but it doesn't explain why the connector would think port 80 was appropriate. I could see port 8090 showing up, but given that the scheme is https and there was no port number in the request, surely it should have resolved that to port 443 instead of port 80? It just seems like a bug to me. It does look like proxyPort can be used to force it to 443, though, so that will work. On Tue, Oct 13, 2009 at 12:19 AM, Peter Crowther peter.crowt...@melandra.com wrote: 2009/10/13 Sam Gendler sgend...@vid.me: That method uses request.getScheme(), to retrieve https (correct) and request.getServerName() to get the correct host name. It then calls request.getServerPort(), which incorrectly returns the value of 80. [...] What do I need to do to get the request to correctly return 443 as the port when a request arrives on the connector without any port in the url or Host header? The keyword to look for is Proxying - your SSL front-end is proxying the SSL connector for you. http://tomcat.apache.org/tomcat-6.0-doc/config/http.html shows connector attributes of proxyHost and proxyPort, which I think will do exactly what you want. Hope this helps! - Peter - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: trouble with connector configured to receive from SSL accelerator
Sam Gendler wrote: Is it possible that sessions aren't persistent when switching between connectors. The proxyPort attribute on the connector did fix my problem, but I've discovered that logging in over an https connection only works if I click the remember-me checkbox, which sets a cookie on the client and stores some state in a db which can associate the cookie with the identity of the user. If I don't use remember me, the authentication occurs when connected via the secure connector and the user's identity is stored in the session, but when the system switches back to the other connector, it fails to find the authorization info in the session, so it redirects right back to the login page via https. I suspect the session cookie is being set as https-only, so it doesn't get passed back when accessing via http. Is there any way to correct this behaviour? No. That is by design. The session ID is almost as valuable as the password. If you need SSL to protect the password, you should use SSL to protect the session ID. You can work your way around this with code if you really want to. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: trouble with connector configured to receive from SSL accelerator
No. That is by design. The session ID is almost as valuable as the password. If you need SSL to protect the password, you should use SSL to protect the session ID. Well, that's fairly application specific, but the argument has also been done to death elsewhere. Workaround is already in place.
RE: Datasource configuration issue
Hi Also suggested to have the JDBC Driver to be in TOMCAT/lib folder rather then in the /webapps/application/web-inf/lib with regards Karthik -Original Message- From: VijayKS [mailto:ksvijay...@gmail.com] Sent: Tuesday, October 13, 2009 1:31 PM To: users@tomcat.apache.org Subject: Datasource configuration issue Hi, I am using Tomcat 5.0. I have one application test. In test i created META-INF folder and put context.xml file.Here is the content context resource name=jdbc/PDBDataSource scope=Shareable type=javax.sql.DataSource resourceparams name=jdbc/PDBDataSource parameter namefactory/name valueorg.apache.commons.dbcp.BasicDataSourceFactory/value /parameter parameter nameurl/name valuejdbc:sqlserver://localhost;DatabaseName=test;SelectMethod=cursor;/value /parameter parameter namedriverClassName/name valuecom.microsoft.jdbc.sqlserver.SQLServerDriver/value /parameter parameter nameusername/name valuesa/value /parameter parameter namepassword/name valuesa/value /parameter parameter /resourceparams /resource /context in WEB-INF\web.xml file i have the entires web-app resource-ref res-ref-namejdbc/PDBDataSource /res-ref-name res-type javax.sql.DataSource /res-type res-auth Container /res-auth /resource-ref /web-app in my jsp code i have the code Context initCtx = new InitialContext(); Context envCtx = (Context) initCtx.lookup(java:comp/env); DataSource ds = (DataSource) envCtx.lookup(jdbc/PDBDataSource); Connection conn = ds.getConnection(); conn.close(); I am getting the follwoing error when accessing my page javax.servlet.ServletException: Cannot create JDBC driver of class '' for connect URL 'null' org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:846) org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:779) org.apache.jsp.index_jsp._jspService(index_jsp.java:69) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) Help me to resolve this :confused: -- View this message in context: http://www.nabble.com/Datasource-configuration-issue-tp25868686p25868686.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Persistent Storage for Webapps
Am Mon, 12 Oct 2009 18:57:43 +0200 schrieb Jesse Long j...@unknown.za.net: Thanks for your answers Tobias. Unfortunately we have a very real use case for multiple instances on one host, with different data paths. So, /etc/app.properties is not usable, but /etc/app-context path derived data.properties might be but virtual hosting would break. No way datato identify unique host consistently. It depends on how you implement virtual hosting. I have no experience with Tomcats virtual hosting but a Tomcat-application can always can request the hostname from the URI and use it to build a path name. We are using this hostname to give users via VPN other privileges than users via public internet. Not really secure but within our business it's enough. We're using Apache2-vhosts and run one Tomcat (in its own JVM) per vhost. This wastes RAM but avoids that a crash|deadlock|overload|whatever in one vhost affects the other vhosts seriously. In our scenario we have one home-directory per vhost (e.g. /srv/vhost1) where we install Tomcat (mostly by symbolic links to unpacked Tomcats-archives) incl. startup/shutdown-scripts, cronjobs, logs, Apache2-document-root, Tomcat-ROOT and persistent data for import/export. Tomcat's webapps-concept is only used to deploy some standard applications like Lambda probe, Webservice or j4p. This vhost-home also contains some *.properties-files with parameters, e.g. for database-access (we don't use JNDI due to historic reasons), paths for import/export, etc. If your using only one Tomcat with several name-based vhosts it probably will be enough if you read hostname from URI and use this information to construct the path to a tree with /srv/vhost1, /srv/vhost2, etc. as data directories. Gruß, Tobias. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: SSL/HTTPS forwarding under Apache + mod_jk + tomcat
Thanks heaps. I will attempt it and report back in a couple of days. I had a hard time, for over a week now, trying to get these answers from our open source support ppl. -- View this message in context: http://www.nabble.com/SSL-HTTPS-forwarding-under-Apache-%2B-mod_jk-%2B-tomcat-tp17817647p25870792.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: PATCH: Session ID from URL; would like some input!
Hi Mark, thanks for your response! On Oct 13, 2009, at 10:29 , Mark Thomas wrote: Johan Ström wrote: Hello list! First of all, this maybe better suited for the dev list, but a quick peek only showed svn log mails etc soo.. Sending here instead, let me know if its wrong! It is 50/50. The patch is of more interest to the dev list but if the patch is rejected then the users list is the best place to get ideas about other ways of doing things. The mailing lists block most patches so an enhancement request in Bugzilla is the best place for your patch. I see, it's available here if you'd like to take a quick look: https://dev.headweb.com/johan/pub/Request.java.patch Without seeing the patch it is hard to comment but SRV.7.1 makes it clear that cookies override URL parameters. It doesn't make a comment on what if the cookie session is invalid and the URL one not. There might be some scope for flexibility here. Correct, cookies override URL parameter, but as you said, not when the session in cookie is invalid. I guess one could make it configurable but I have no idea how that would be done, haven't dug that deep into the tomcat source :) We're having a problem related to Tomcat, in a pretty unusual scenario. Basicly the problem is with old expired sessions, and reading session ID from URL instead of cookie. An example, in our case browser A is a main browser, and browser B is a slave browser (actually only a webkit rendering engine) which we only call with an URL to show a specific page, and we do not have control over cookies in browser B. Any way to close browser B? That should delete the session cookie. Unfortunately not, so not a solution. So, browser B sends both the old session ID in the cookie (which is an expired session), and the new sessionid on the URL. This confuses tomcat. In catalina/connector/Request.java and CoyoteAdaptor, we first check for a sessino ID on the URL, store it in Request, and then we check for a cookie, and if we got one, we just overwrite the session ID from the URL. My solution? The attached patch! Now, what I'd like to know, can anyone of you developers see any nasty side effects that I might have missed about this? In principle, it sounds OK but I'd want to see the patch first. If it were implemented, then it would go into Tomcat 7 and may not be back-ported to earlier versions. It may also be made optional. See URL above. Keep in mind that session handling is more configurable in the Servlet 3.0 spec (not that I think it helps with this issue) and that changing the session ID on authentication to protect against session fixation is an open enhancement request that should also get included in Tomcat 7. Me changing the session ID is not what I'm doing, its rather that the old session ID has timed out, and browser A is assigned a new session which i need to tell browser B to use too. One thing that was concerned about was that it would introduce session hijacking risks, but the only difference is that the evildoer have to erase his (already expired) cookie.. Normal tomcat accepts jsessionid on URL anyway, as long as there is no cookie, so that should not be a security concern. Agreed. Great :) Johan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat hangs for minutes between ContextConfig and StandardContext (Starting the app)
From: Law, Christopher [mailto:chris@snapon.com] Subject: RE: Tomcat hangs for minutes between ContextConfig and StandardContext (Starting the app) By any chance, is there a case mismatch - is your webapp properly deployed in [appBase]/Spc.xml or perhaps incorrectly in [appBase]/spc.xml? Sorry - shouldn't have been responding when it was so late after a really, really long day. The above should have been referring to Spc.war and spc.war, not any .xml files. Just looking for possible casing issues, since Java and Tomcat are case-sensitive, whereas Windows is not. My server.xml (it should be the distribution copy with SSL and access log enabled): That all looks fine. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Getting out of memory using tomcat 6.0.20 but works fine in tomcat 5.5.28
From: Curtis Garman [mailto:curt.gar...@gmail.com] Subject: Re: Getting out of memory using tomcat 6.0.20 but works fine in tomcat 5.5.28 I believe the default amount of PermGenSpace in tomcat was reduced between 5 and 6... You believe incorrectly. Tomcat itself cannot affect the JVM heap settings, since they're already established by the time any Tomcat logic gets control. It is possible for the startup scripts to set heap size values, but the ones distributed with Tomcat do not. It is theoretically possible that Tomcat 6.0 requires a larger PermGen than 5.5 did, but I have seen no evidence to support that (there is some evidence that the opposite is true). Without more information about what portion of the heap is exhausted, this is all speculation. Since an OOME is also thrown for a variety of non-heap issues, this may not even be heap related. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Multiple Domains on one Tomcat Server now MySQL not working
On Mon, Oct 12, 2009 at 11:40 PM, Paul van Hoven paul.van.ho...@googlemail.com wrote: Host name=localhost.localdomain ... Aliaswww.clubpirat.de/Alias I checked that in /etc/hosts the two domains localhost and localhost.localdomain are assigned to 127.0.0.1. Okay, i when enter the url www.clubpirat.de but i get an 404 error. And does www.clubpirat.de resolve to your local computer? Either through an entry in /etc/hosts or DNS? -- Hassan Schroeder hassan.schroe...@gmail.com twitter: @hassan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Multiple Domains on one Tomcat Server now MySQL not working
Hi Hassan, yeah, acutually that was the problem, I just discovered it an instant before you answered me :). I made the appropriate changes and now it is working fine. Thanks for your answer anyway. Tom Hassan Schroeder schrieb: On Mon, Oct 12, 2009 at 11:40 PM, Paul van Hoven paul.van.ho...@googlemail.com wrote: Host name=localhost.localdomain ... Aliaswww.clubpirat.de/Alias I checked that in /etc/hosts the two domains localhost and localhost.localdomain are assigned to 127.0.0.1. Okay, i when enter the url www.clubpirat.de but i get an 404 error. And does www.clubpirat.de resolve to your local computer? Either through an entry in /etc/hosts or DNS? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
how to replace apache's mod_alias
environment: Tomcat 6.0.18 under apache2 on Mac OS X Server 10.6 (Snow Leopard). I have a web app that works under Tomcat with Apache as the front end. I have had issues with the Apache-Tomcat connectors and am trying to set up the app to be served directly by Tomcat, listening on port 80. This is working to a point, but I have some functionality that depends on accessing directories within the document base, and that was handled previously my Mod_Alias in apache. Is there any documentation on how to replace the alias elements in httpd.conf with corresponding elements in Tomcat's configuration? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Does Tomcat http work on port 80?
If I got it correctly, you are trying to setup your JBoss on port 80 when you already have an apache running on port 80... Is that correct? If so, you need to understand that only one process may listen to a given port number. This is your issue. If not, please clarify... Regards 2009/10/9 Tony Anecito adanec...@yahoo.com First off my question was answered (in the subject line) that what I am doing should work for Windows OS. When I did a view source in Firefox there was nothing. When I looked at the error dialog box in FireFox there was nothing. When I looked at the server logs for Jboss (both boot and log written to after booting) there was no mention of an error. By default there is no access log for Tomcat I have to enable it according to an email sent by Chuck. I have not looked for any additional browser plugins yet since for me FireFox has been great at showing errors. But I will look at the other option you mentioned. I have installed both JBoss 5.1.0GA and Tomcat 6.0.20 on another OS Windows XP and changing to port 80 worked fine. The initial responses on this forum were Linux related but later ones after reading that I was stating Windows 2000 Prof made adjusments to their answer to my question. From the responses sounds as if no one has seen this type of problem which is probably related to some other install or OS specific or combination of all the above. Regards, -Tony Regards, -Tony --- On Fri, 10/9/09, André Warnier a...@ice-sa.com wrote: From: André Warnier a...@ice-sa.com Subject: Re: Does Tomcat http work on port 80? To: Tomcat Users List users@tomcat.apache.org Date: Friday, October 9, 2009, 11:00 AM Tony Anecito wrote: ... When I changed the server.xml recommended by Jboss and others to port 80 I got the white page (no source) Tony, you may get a page that looks empty in your browser. But that is not all that you are getting. If you look at the page source, you will probably see more. If you look at the server logs, you will see much more. If you get some add-on to your browser (like HttpFox or Fiddler2), you will see even more, in the form of HTTP headers and a status code that the server returns. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- -- pieroxy
Autodeploy on cluster
I have a Tomcat6 cluster. Im looking for a solution to put a webapp folder in a node and automatically deploy the application, or the changes, to other cluster's nodes. I used FarmWarDeployer, but it isn't my ideal solution. Have some idea? Thanks
Re: Does Tomcat http work on port 80?
Nope. I turned off Apache before I launched JBoss after it was configured to run port 80. That way only one process was running with port 80. Tomcat external to JBoss worked for my environment. Anyway, I went with a architecture where Tomcat was outside of Jboss which is where I was headed a couple of years ago. Back then I could not get jndi to work between JBoss and Tomcat but I did two nights ago. Now I can update Tomcat and stay ahead of JBoss releases since it was usually behind Tomcat upgrades which is expected due dependencies. I got very close to my goal with what hardware/configuration I could last night. Thanks for replying, -Tony --- On Tue, 10/13/09, pieroxy pier...@gmail.com wrote: From: pieroxy pier...@gmail.com Subject: Re: Does Tomcat http work on port 80? To: Tomcat Users List users@tomcat.apache.org Date: Tuesday, October 13, 2009, 9:54 AM If I got it correctly, you are trying to setup your JBoss on port 80 when you already have an apache running on port 80... Is that correct? If so, you need to understand that only one process may listen to a given port number. This is your issue. If not, please clarify... Regards 2009/10/9 Tony Anecito adanec...@yahoo.com First off my question was answered (in the subject line) that what I am doing should work for Windows OS. When I did a view source in Firefox there was nothing. When I looked at the error dialog box in FireFox there was nothing. When I looked at the server logs for Jboss (both boot and log written to after booting) there was no mention of an error. By default there is no access log for Tomcat I have to enable it according to an email sent by Chuck. I have not looked for any additional browser plugins yet since for me FireFox has been great at showing errors. But I will look at the other option you mentioned. I have installed both JBoss 5.1.0GA and Tomcat 6.0.20 on another OS Windows XP and changing to port 80 worked fine. The initial responses on this forum were Linux related but later ones after reading that I was stating Windows 2000 Prof made adjusments to their answer to my question. From the responses sounds as if no one has seen this type of problem which is probably related to some other install or OS specific or combination of all the above. Regards, -Tony Regards, -Tony --- On Fri, 10/9/09, André Warnier a...@ice-sa.com wrote: From: André Warnier a...@ice-sa.com Subject: Re: Does Tomcat http work on port 80? To: Tomcat Users List users@tomcat.apache.org Date: Friday, October 9, 2009, 11:00 AM Tony Anecito wrote: ... When I changed the server.xml recommended by Jboss and others to port 80 I got the white page (no source) Tony, you may get a page that looks empty in your browser. But that is not all that you are getting. If you look at the page source, you will probably see more. If you look at the server logs, you will see much more. If you get some add-on to your browser (like HttpFox or Fiddler2), you will see even more, in the form of HTTP headers and a status code that the server returns. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- -- pieroxy - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat with Netscape Portable Runtime (NSPR)
Is it possible to configure Tomcat to use NSPR similar to the way you can configure Tomcat to use the Apache Portable Runtime (APR)? I have been successful in configuring Tomcat to use the APR and modifying the server.xml. THe same config does not seem to work with the NSPR and I have been unable to find any documentation.
Re: Tomcat with Netscape Portable Runtime (NSPR)
2009/10/13 G S skis...@gmail.com: Is it possible to configure Tomcat to use NSPR similar to the way you can configure Tomcat to use the Apache Portable Runtime (APR)? No. In the same way, it's not possible to configure Mozilla to use the Apache Portable Runtime. - Peter - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat with Netscape Portable Runtime (NSPR)
Peter, Thank you for the response. My ultimate goal is to use the Netscape encryption modules through JSS on a Tomcat Server. I have JSS installed as a Security Provider on my system now but I have been unable to get Tomcat to use it for SSL connections. Do you have any suggestions on how I might accomplish that? On Tue, Oct 13, 2009 at 2:38 PM, Peter Crowther peter.crowt...@melandra.com wrote: 2009/10/13 G S skis...@gmail.com: Is it possible to configure Tomcat to use NSPR similar to the way you can configure Tomcat to use the Apache Portable Runtime (APR)? No. In the same way, it's not possible to configure Mozilla to use the Apache Portable Runtime. - Peter - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
tomcat 5.5.25 and loosing spaces between printing jstl variables
Has anyone else experienced loosing spaces between printing jstl
variables. I've got something that is printing
${firstName} ${lastName} -- Curtis Garman
but instead the space in between the two names is getting lost so it prints as
CurtisGarman
The wierd thing is that it displays just fine on a mirrored server but
messes up on our production server? My thought is that it has to be a
combination of tomcat/jstl. I've had this problem before but it has
never mattered. Any ideas or fixes? I do have set in the default
web.xml...anyone know if this is a problem?
init-param
param-nametrimSpace/param-name
param-valuetrue/param-value
/init-param
...I set it because apache recommends this
http://tomcat.apache.org/tomcat-6.0-doc/jasper-howto.html#Production%20Configuration
--
Curtis Garman
Web Programmer
Heartland Community College
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: PATCH: Session ID from URL; would like some input!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Johan, On 10/13/2009 3:41 AM, Johan Ström wrote: In catalina/connector/Request.java and CoyoteAdaptor, we first check for a sessino ID on the URL, store it in Request, and then we check for a cookie, and if we got one, we just overwrite the session ID from the URL. Is it acceptable to simply disable the use of cookies for your site entirely? Setting Context cookies=false will disable the use of cookies altogether for your site. This would allow you to configure your way out of this problem rather than coding your way out of it (at least, until a more permanent cookie-friendly solution could be reached). Hope that helps, - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrU7dYACgkQ9CaO5/Lv0PA9XQCeKV74piFh5XVWvZq9ia4HRBYX EJYAn0IWgYM5iyTUOd2zQozRdu6vlt8S =5fZp -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Getting out of memory using tomcat 6.0.20 but works fine in tomcat 5.5.28
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kalpana, On 10/12/2009 10:22 PM, kalpanab wrote: My application working fine in tomcat 5.5.28 and java version 1.5.0_19 while doing load balancing tests. But when I upgrade tomcat to version 6.0.20 getting out of memory soon. I looked at the heap dump using Eclipse memory analyzer below listed taking more memory. java.util.concurrent.ConcurrentHashMap$Segment 44.73 % (3,353 objects) What does that 44.73% mean? Since you have a profiler handy, can you see what objects are hanging onto the ConcurrentHashMap objects that own those Segment objects? I have seen several reports from Tomcat users here on the list that Tomcat 6.0 appears to take more memory than Tomcat 5.5, so it's possible that you will need to increase your heap size in order to feed the later version. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrU++8ACgkQ9CaO5/Lv0PDDJACdHEwUx5etsFEbB0E9aS/sHaki 0lsAn11sOUOM36TOgX9BSClPpfvsIPm6 =P5CE -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Datasource configuration issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Karthik, On 10/13/2009 6:18 AM, Karthik Nanjangude wrote: Also suggested to have the JDBC Driver to be in TOMCAT/lib folder rather then in the /webapps/application/web-inf/lib I believe this is a /requirement/, not just good practice. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrU/CsACgkQ9CaO5/Lv0PDVnACfVFx4Wh4Ep03X94xBMuDNvQp3 z/0AoIwEiZP7kakdbb2Q6EzG4c4CPIKP =+Zq+ -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: PATCH: Session ID from URL; would like some input!
On Oct 13, 2009, at 23:15 , Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Johan, On 10/13/2009 3:41 AM, Johan Ström wrote: In catalina/connector/Request.java and CoyoteAdaptor, we first check for a sessino ID on the URL, store it in Request, and then we check for a cookie, and if we got one, we just overwrite the session ID from the URL. Is it acceptable to simply disable the use of cookies for your site entirely? Setting Context cookies=false will disable the use of cookies altogether for your site. This would allow you to configure your way out of this problem rather than coding your way out of it (at least, until a more permanent cookie-friendly solution could be reached). I'm afraid not, since the URL loaded is in the same app as the main app, just with a custom view. So as long as its per application, thats not a solution. Anyway, I have tested my patch and I do have my own (now) custom built Tomcat, so using this solution is not a problem. Just wanted to get input from someone more experienced with the tomcat internals before I started more testing/deploying of this! So, thanks for any input :) Johan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Getting out of memory using tomcat 6.0.20 but works fine in tomcat 5.5.28
Thank you for all your suggestions. I did not wait till getting out of memory. I analyzed heap dumps continuous and find keeps on increasing the objects and also taking more memory so I stopped after half an hour. I want to know why StandardSessions are increasing. It is not happening in tomcat 5.5.28. See the attached image for the finding out what taking more memory. http://www.nabble.com/file/p25883072/Tomcat6.0.20-heap-analysis.png Thanks, Kalpana Caldarale, Charles R wrote: From: Curtis Garman [mailto:curt.gar...@gmail.com] Subject: Re: Getting out of memory using tomcat 6.0.20 but works fine in tomcat 5.5.28 I believe the default amount of PermGenSpace in tomcat was reduced between 5 and 6... You believe incorrectly. Tomcat itself cannot affect the JVM heap settings, since they're already established by the time any Tomcat logic gets control. It is possible for the startup scripts to set heap size values, but the ones distributed with Tomcat do not. It is theoretically possible that Tomcat 6.0 requires a larger PermGen than 5.5 did, but I have seen no evidence to support that (there is some evidence that the opposite is true). Without more information about what portion of the heap is exhausted, this is all speculation. Since an OOME is also thrown for a variety of non-heap issues, this may not even be heap related. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- View this message in context: http://www.nabble.com/Getting-out-of-memory-using-tomcat-6.0.20-but-works-fine-in-tomcat-5.5.28-tp25866219p25883072.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
