Re: Bundle Tomcat and Test in Eclipse
On 17/10/2012 21:12, Jason Aleski wrote: I am working on a project with specifications to bundle Tomcat7 with a Web Application. I am having trouble with the initial package setup, as this is my first time bundling Tomcat7. I've developed WAR files that have been deployed before. I'm trying to start basic and get the bundle instance of Tomcat7 working in Eclipse. That way, when I compile, it will launch using my version of Tomcat. I've searched online, but have not found exactly what I need to accomplish this. I'm sure my keywords are wrong. I see a lot of items on embedding Tomcat, but this is not what I need. Additional Information Assumptions 1)Users will install the appropriate Java version (due to distribution legal) Needs 1)Deliver custom instance of tomcat with various JDBC and tools included in the libraries. Expectations 1)Users will download a ZIP file or pull it via Git/SVN. No install required other than unpacking the files. 2)There will be some minor configuration changes to various Tomcat configs based on the users environment (LDAP, sFTP, databases, etc.) 3)The same file can be downloaded via Linux, Windows or Mac and Tomcat will execute and launch the web application/web services. So take a tomcat zip install, unpack it, add stuff and zip it back up again. 4)All development is to be done in Eclipse. Upon testing, Eclipse will launch the bundled version of Tomcat. Development of what, the bundle? So write a build script to unpack, modify zip it up. This sounds like an Eclipse question rather than a Tomcat one. p Can anyone offer any guidance on what I should be looking for? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- [key:62590808] signature.asc Description: OpenPGP digital signature
RE: asking advice for tomcat 7 config
Hi there! Some news for you about my problem. I did all the modifications you suggested, it increased the response time a little bit (2-3 seconds better on a 15 seconds scale). It was already good to take, and helped me to create a healthy configuration. After that, I looked deeper into the database configuration, as I saw in the tests that non db relative actions were responding very fast (50ms for a 1000 users basis). I finally found an OracleDataSource in the Oracle Driver, which reacts far way better than the BasicDataSource I was using before (12s for 150 users for the basic data source, 1.5s for the oracle one, same test). So I think my problems are solved, thanks to you guys! Many thanks for the advices, Romain. -Original Message- From: André Warnier [mailto:a...@ice-sa.com] Sent: mercredi 17 octobre 2012 11:49 To: Tomcat Users List Subject: Re: asking advice for tomcat 7 config Pid wrote: ... Executor name=tomcatThreadPool namePrefix=catalina-exec-80- maxThreads=650 minSpareThreads=100 / Connector executor=tomcatThreadPool address=10.10.10.10 port=80 maxHttpHeaderSize=8192 protocol=org.apache.coyote.http11.Http11NioProtocol connectionTimeout=2 redirectPort=443 server=lighthttpd/2.0.0 enableLookups=false acceptorThreadCount=4 socket.directBuffer=false compression=off compressableMimeType=text/html,text/xml,text/plain,text/javascript,text/css,image/jpeg,image/png,image/gif acceptCount=50 bufferSize=4096 / Executor name=stomcatThreadPool namePrefix=catalina-exec-443- maxThreads=650 minSpareThreads=100 / Connector executor=stomcatThreadPool protocol=org.apache.coyote.http11.Http11NioProtocol port=443 SSLEnabled=true scheme=https secure=true clientAuth=false sslProtocol=TLS keystoreFile=D:\keystore\appks server=lighthttpd/2.0.0 enableLookups=false keystorePass=changeit address=10.10.10.10 acceptorThreadCount=4 socket.directBuffer=false compression=off compressableMimeType=text/html,text/xml,text/plain,text/javascript,text/css,image/jpeg,image/png,image/gif acceptCount=50 bufferSize=4096 /Connector You've configured a separate pool for connectors on ports 80 and 443. Why? You've reduced the acceptCount to 50. Why? You are compressing compressed images. Why? There is : compression=off in both connectors though. So I guess that compressableMimeType should be ignored. (It /is/ still questionable to have changed the default of compressableMimeType, to include types which are inherently compressed already.) You are setting acceptorThreadCount=4. Why? Does your app have a database connection pool? What are the sizing parameters for this pool? Also, - for the HTTP connector, connectionTimeout is set to 2 (milliseconds), and keepAliveTimeout is not set. - for the HTTPS connector, neither one is set. That will cause : - for the HTTP connector : - connectionTimeout = 2 ms (20 s.) - keepAliveTimeout = 2 ms - for the HTTPS connector : - connectionTimeout = 6 ms (60 s.) - keepAliveTimeout = 6 ms 1) So it means that if a client connects to the server, but does not send any request line for a while on that connection, the server will allocate a thread to serve the request; this thread will wait up to 20 s (on HTTP) or 60 s. (on HTTPS), before timing out and returning to the pool of available threads. Of course only a malicious client would do that.. 2) it also means that a perfectly non-malicious client can connect to the server, and send a first request on the connection; the server will allocate a thread to handle this request; and then, if the same client has no more requests to send for a while, this thread will nevertheless remain waiting on this connection for 20 s. (HTTP) or 60 s. (HTTPS), just in case the client /would/ send another request on it. During this time, the thread is unavailable to process other client requests. Discarding item (1) for now as being a DOS attack, might (2) not go a long way to explain the symtoms that the OP is mentioning ? I would try setting : - for the HTTP connector : - connectionTimeout = 5000 ms (5 s.) - keepAliveTimeout = 5000 ms - for the HTTPS connector : - connectionTimeout = 5000 ms (5 s.) - keepAliveTimeout = 5000 ms on the premises that : - a genuine well-intentioned client is very unlikely to establish a connection with a webserver, and then not send any request on that connection for all of 5 seconds - if a client, after making a first request and having obtained the response to it, is then not making any further request to the server on the same connection for more than 5 seconds, it probably means that he has for now nothing more to request. And it is not the overhead of establishing a new TCP connection later that is nowadays going to penalise the client or the server. And
Re: asking advice for tomcat 7 config
Hey I'm facing similar problems too and I guess with a good configuration of my server.xml would be a good start point. So could kindly share a good Connector configuration in this mail thread? What would that be the best choice in terms of max min threads keep alived timeout configurations ? Thanks in advance! Sent from my iPhone On 18/10/2012, at 07:05, Romain Van der Keilen romain.vanderkei...@uniway.be wrote: Hi there! Some news for you about my problem. I did all the modifications you suggested, it increased the response time a little bit (2-3 seconds better on a 15 seconds scale). It was already good to take, and helped me to create a healthy configuration. After that, I looked deeper into the database configuration, as I saw in the tests that non db relative actions were responding very fast (50ms for a 1000 users basis). I finally found an OracleDataSource in the Oracle Driver, which reacts far way better than the BasicDataSource I was using before (12s for 150 users for the basic data source, 1.5s for the oracle one, same test). So I think my problems are solved, thanks to you guys! Many thanks for the advices, Romain. -Original Message- From: André Warnier [mailto:a...@ice-sa.com] Sent: mercredi 17 octobre 2012 11:49 To: Tomcat Users List Subject: Re: asking advice for tomcat 7 config Pid wrote: ... Executor name=tomcatThreadPool namePrefix=catalina-exec-80- maxThreads=650 minSpareThreads=100 / Connector executor=tomcatThreadPool address=10.10.10.10 port=80 maxHttpHeaderSize=8192 protocol=org.apache.coyote.http11.Http11NioProtocol connectionTimeout=2 redirectPort=443 server=lighthttpd/2.0.0 enableLookups=false acceptorThreadCount=4 socket.directBuffer=false compression=off compressableMimeType=text/html,text/xml,text/plain,text/javascript,text/css,image/jpeg,image/png,image/gif acceptCount=50 bufferSize=4096 / Executor name=stomcatThreadPool namePrefix=catalina-exec-443- maxThreads=650 minSpareThreads=100 / Connector executor=stomcatThreadPool protocol=org.apache.coyote.http11.Http11NioProtocol port=443 SSLEnabled=true scheme=https secure=true clientAuth=false sslProtocol=TLS keystoreFile=D:\keystore\appks server=lighthttpd/2.0.0 enableLookups=false keystorePass=changeit address=10.10.10.10 acceptorThreadCount=4 socket.directBuffer=false compression=off compressableMimeType=text/html,text/xml,text/plain,text/javascript,text/css,image/jpeg,image/png,image/gif acceptCount=50 bufferSize=4096 /Connector You've configured a separate pool for connectors on ports 80 and 443. Why? You've reduced the acceptCount to 50. Why? You are compressing compressed images. Why? There is : compression=off in both connectors though. So I guess that compressableMimeType should be ignored. (It /is/ still questionable to have changed the default of compressableMimeType, to include types which are inherently compressed already.) You are setting acceptorThreadCount=4. Why? Does your app have a database connection pool? What are the sizing parameters for this pool? Also, - for the HTTP connector, connectionTimeout is set to 2 (milliseconds), and keepAliveTimeout is not set. - for the HTTPS connector, neither one is set. That will cause : - for the HTTP connector : - connectionTimeout = 2 ms (20 s.) - keepAliveTimeout = 2 ms - for the HTTPS connector : - connectionTimeout = 6 ms (60 s.) - keepAliveTimeout = 6 ms 1) So it means that if a client connects to the server, but does not send any request line for a while on that connection, the server will allocate a thread to serve the request; this thread will wait up to 20 s (on HTTP) or 60 s. (on HTTPS), before timing out and returning to the pool of available threads. Of course only a malicious client would do that.. 2) it also means that a perfectly non-malicious client can connect to the server, and send a first request on the connection; the server will allocate a thread to handle this request; and then, if the same client has no more requests to send for a while, this thread will nevertheless remain waiting on this connection for 20 s. (HTTP) or 60 s. (HTTPS), just in case the client /would/ send another request on it. During this time, the thread is unavailable to process other client requests. Discarding item (1) for now as being a DOS attack, might (2) not go a long way to explain the symtoms that the OP is mentioning ? I would try setting : - for the HTTP connector : - connectionTimeout = 5000 ms (5 s.) - keepAliveTimeout = 5000 ms - for the HTTPS connector : - connectionTimeout = 5000 ms (5 s.) - keepAliveTimeout = 5000 ms on the premises that : - a genuine well-intentioned client is very unlikely to establish a connection with a webserver, and then
Re: asking advice for tomcat 7 config
On 18/10/2012 12:22, Daniel Barcellos wrote: Hey I'm facing similar problems too and I guess with a good configuration of my server.xml would be a good start point. So could kindly share a good Connector configuration in this mail thread? What would that be the best choice in terms of max min threads keep alived timeout configurations ? It's probably not your connector config that's the problem, if there is one. Most of the time it's your app. Use a profiler, monitor JMX (use VisualVM with the MBeans plugin) and understand what's happening rather than assuming someone else's connector config is good or better. Start a new thread when you've tried this have questions. p Thanks in advance! Sent from my iPhone On 18/10/2012, at 07:05, Romain Van der Keilen romain.vanderkei...@uniway.be wrote: Hi there! Some news for you about my problem. I did all the modifications you suggested, it increased the response time a little bit (2-3 seconds better on a 15 seconds scale). It was already good to take, and helped me to create a healthy configuration. After that, I looked deeper into the database configuration, as I saw in the tests that non db relative actions were responding very fast (50ms for a 1000 users basis). I finally found an OracleDataSource in the Oracle Driver, which reacts far way better than the BasicDataSource I was using before (12s for 150 users for the basic data source, 1.5s for the oracle one, same test). So I think my problems are solved, thanks to you guys! Many thanks for the advices, Romain. -Original Message- From: André Warnier [mailto:a...@ice-sa.com] Sent: mercredi 17 octobre 2012 11:49 To: Tomcat Users List Subject: Re: asking advice for tomcat 7 config Pid wrote: ... Executor name=tomcatThreadPool namePrefix=catalina-exec-80- maxThreads=650 minSpareThreads=100 / Connector executor=tomcatThreadPool address=10.10.10.10 port=80 maxHttpHeaderSize=8192 protocol=org.apache.coyote.http11.Http11NioProtocol connectionTimeout=2 redirectPort=443 server=lighthttpd/2.0.0 enableLookups=false acceptorThreadCount=4 socket.directBuffer=false compression=off compressableMimeType=text/html,text/xml,text/plain,text/javascript,text/css,image/jpeg,image/png,image/gif acceptCount=50 bufferSize=4096 / Executor name=stomcatThreadPool namePrefix=catalina-exec-443- maxThreads=650 minSpareThreads=100 / Connector executor=stomcatThreadPool protocol=org.apache.coyote.http11.Http11NioProtocol port=443 SSLEnabled=true scheme=https secure=true clientAuth=false sslProtocol=TLS keystoreFile=D:\keystore\appks server=lighthttpd/2.0.0 enableLookups=false keystorePass=changeit address=10.10.10.10 acceptorThreadCount=4 socket.directBuffer=false compression=off compressableMimeType=text/html,text/xml,text/plain,text/javascript,text/css,image/jpeg,image/png,image/gif acceptCount=50 bufferSize=4096 /Connector You've configured a separate pool for connectors on ports 80 and 443. Why? You've reduced the acceptCount to 50. Why? You are compressing compressed images. Why? There is : compression=off in both connectors though. So I guess that compressableMimeType should be ignored. (It /is/ still questionable to have changed the default of compressableMimeType, to include types which are inherently compressed already.) You are setting acceptorThreadCount=4. Why? Does your app have a database connection pool? What are the sizing parameters for this pool? Also, - for the HTTP connector, connectionTimeout is set to 2 (milliseconds), and keepAliveTimeout is not set. - for the HTTPS connector, neither one is set. That will cause : - for the HTTP connector : - connectionTimeout = 2 ms (20 s.) - keepAliveTimeout = 2 ms - for the HTTPS connector : - connectionTimeout = 6 ms (60 s.) - keepAliveTimeout = 6 ms 1) So it means that if a client connects to the server, but does not send any request line for a while on that connection, the server will allocate a thread to serve the request; this thread will wait up to 20 s (on HTTP) or 60 s. (on HTTPS), before timing out and returning to the pool of available threads. Of course only a malicious client would do that.. 2) it also means that a perfectly non-malicious client can connect to the server, and send a first request on the connection; the server will allocate a thread to handle this request; and then, if the same client has no more requests to send for a while, this thread will nevertheless remain waiting on this connection for 20 s. (HTTP) or 60 s. (HTTPS), just in case the client /would/ send another request on it. During this time, the thread is unavailable to process other client requests. Discarding item (1) for now as being a DOS attack, might (2) not go a long way to explain the symtoms that the OP
Re: asking advice for tomcat 7 config
Hi. Romain Van der Keilen wrote: Hi there! Some news for you about my problem. I did all the modifications you suggested, it increased the response time a little bit (2-3 seconds better on a 15 seconds scale). It was already good to take, and helped me to create a healthy configuration. As previously mentioned by Mark (who is one of the Tomcat developers), I was wrong and the changes to timeouts and keepAlive that I recommended should not have made a difference, considering that you are using the NIO connector in your configuration. (My comments were only valid in the case of a BIO connector). Yet you seem to indicate 2-3 s. improvement over 15 s., which is about 20%. That is puzzling. Are you sure, and can you reproduce this consistently ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Get active session list
I need to get the active session list. Searching about I saw a lot of people with the same question, but no answer. I don't want to write a list inside a HttpSessionListener and keep the session list there, because I use session serialization and the list inside the listener would be destroyed in case the server is restarted. I'd like know which class does the Manager Application uses to get the session list, so I can use it in my application too. Thanks a lot, Phillip
Re: Thread related MBean questions
Hi Pid, Thanks for your comments! I would like a representative metric of how many active threads are in Tomcat at a given time. currentBusyThreads may or may not be a good counter because at the time of poll, there is one current operation or none - giving me a value or 1 or 0 consistently. And again, that may just be the case. In the middle of the night, though, I sometimes get a currentBusyThreads=50 value, perhaps due to a spidering of the site or another batch operation on the server. What is DaemonThreadCount=85 please? Is that the current size of the ThreadPool? I looked at our server.xml, and an Executor ThreadPool is not in use for the 8080 and 8443 HTTP connectors. Could that mean that idle threads are not expired properly? So at one point, the thread pool size could have gone up to 85. --server.xml snippet:--- Connector port=8443 clientAuth=false connectionTimeout=6 disableUploadTimeout=true emptySessionPath=true enableLookups=false maxHttpHeaderSize=8192 maxSpareThreads=75 maxThreads=256 minSpareThreads=25 protocol=HTTP/1.1 scheme=https secure=true SSLEnabled=true sslProtocol=TLS URIEncoding=UTF-8 acceptCount=100 SSLCertificateFile=cert.cer SSLCertificateKeyFile=cert_key.key / --end of snippet-- A quick browse on Google showed up the following discussion: http://tomcat.10.n6.nabble.com/Managing-Tomcat-6-threads-How-to-make-tomcat-destroy-threads-when-idle-td2114714.html I might need to change the server.xml to use the executor Thread Pool, I think. Thanks. -Shanti On Wed, Oct 17, 2012 at 9:07 AM, Pid p...@pidster.com wrote: On 16/10/2012 17:52, Shanti Suresh wrote: Greetings. I have some questions on finding the number of active threads in Tomcat. (1) On our QA system, I notice that the currenthreadsBusy MBean is either zero or one for the 8443 and 8080 connectors. ThreadCount != currentThreadsBusy One is the count of threads, one is the threads that are doing work. Why then is ThreadCount = 93 when there is not much going on on QA? Because you've previously done enough work for Tomcat to maintain 93 threads. (2) When I want to graph the thread activity in Tomcat (the thread Pool usage), which is a better counter to look at - currentThreadsBusy or ThreadCount? Depends what you want know. It seems like ThreadCount is what JConsole displays as Live Threads. (3) Why is TotalStartedThreadCount: 264? Is that a cumulative total since Tomcat was restarted? Yes. p --Thread-related MBean snippet:- Name: Catalina:type=ThreadPool,name=http-apr-8443 currentThreadsBusy: 1 ... Name: Catalina:type=ThreadPool,name=http-apr-8080 currentThreadsBusy: 0 ... Name: java.lang:type=Threading DaemonThreadCount: 85 PeakThreadCount: 99 AllThreadIds: Array[long] of length 93 135 119 118 117 ... CurrentThreadCpuTime: 46 CurrentThreadUserTime: 402000 ThreadCount: 93 TotalStartedThreadCount: 264 ThreadCpuTimeSupported: true ... ---end of snippet Thanks! -Shanti -- [key:62590808]
Re: Get active session list
2012/10/18 Felipe Jaekel fkjae...@gmail.com: I need to get the active session list. Searching abou I saw a lot of people with the same question, but no answer. https://code.google.com/p/psi-probe/ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Get active session list
On 18/10/2012 14:34, Felipe Jaekel wrote: I need to get the active session list. Searching about I saw a lot of people with the same question, but no answer. I don't want to write a list inside a HttpSessionListener and keep the session list there, because I use session serialization and the list inside the listener would be destroyed in case the server is restarted. I'd like know which class does the Manager Application uses to get the session list, so I can use it in my application too. Have you looked at the Tomcat source code? The short answer is from an implementation of the Manager interface but that won't really help you as you need to get a reference to the correct Manager instance. How to do that should be apparent from the ManagerServlet source code but feel free to ask here if you need some pointers. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Context fails to load during start of Tomcat, and stalls tomcat startup
Hi! Running apache-tomcat 7.0.26 on FreeBSD 8.1@vmware, I've spotted a really curious issue. We are hosting ~8 different contexts on 4 servers all matching the above setup, and in normal operation we have no beef at all, except when the server guys needs to reboot the servers for whatever reason. When this happens, the a specific context prevents tomcat from starting up it simply stops doing anything after these lines: server17# bin/catalina.sh run Using CATALINA_BASE: /usr/local/apache-tomcat-7.0 Using CATALINA_HOME: /usr/local/apache-tomcat-7.0 Using CATALINA_TMPDIR: /usr/local/apache-tomcat-7.0/temp Using JRE_HOME:/usr/local Using CLASSPATH: /usr/local/apache-tomcat-7.0/bin/bootstrap.jar:/usr/local/apache-tomcat-7.0/ bin/tomcat-juli.jar Oct 18, 2012 1:06:03 PM org.apache.catalina.core.AprLifecycleListener init INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/local/diablo-jdk1.6.0/jre/lib/i386/server:/usr/local/diablo-jdk1.6.0/jr e/lib/i386:/usr/local/diablo-jdk1.6.0/jre/../lib/i386:/usr/java/packages/lib /i386:/lib:/usr/lib:/usr/local/lib Oct 18, 2012 1:06:03 PM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [http-bio-8180] Oct 18, 2012 1:06:03 PM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [http-bio-8443] Oct 18, 2012 1:06:04 PM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [ajp-bio-8009] Oct 18, 2012 1:06:04 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1488 ms Oct 18, 2012 1:06:04 PM org.apache.catalina.core.StandardService startInternal INFO: Starting service Catalina Oct 18, 2012 1:06:04 PM org.apache.catalina.core.StandardEngine startInternalINFO: Starting Servlet Engine: Apache Tomcat/7.0.26 Oct 18, 2012 1:06:04 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive /usr/local/apache-tomcat-7.0/webapps/XXX##10.4b2.war Oct 18, 2012 1:06:04 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive /usr/local/apache-tomcat-7.0/webapps/.war Oct 18, 2012 1:06:12 PM com.sun.xml.ws.server.MonitorBase createRoot INFO: Metro monitoring rootname successfully set to: com.sun.metro:pp=/,type=WSEndpoint,name=/-RequestHandler-RequestHand lerPort Oct 18, 2012 1:06:12 PM com.sun.xml.ws.transport.http.servlet.WSServletDelegate init INFO: WSSERVLET14: JAX-WS servlet initializing Oct 18, 2012 1:06:12 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized INFO: WSSERVLET12: JAX-WS context listener initializing Oct 18, 2012 1:06:12 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized INFO: WSSERVLET12: JAX-WS context listener initializing Oct 18, 2012 1:06:12 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive /usr/local/apache-tomcat-7.0/webapps/##10.4b1.war Oct 18, 2012 1:06:15 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized INFO: WSSERVLET12: JAX-WS context listener initializing And nothing happens now, even if I leave it for 1+ hours Now the ZZ(culprit) context is a perhaps not ultra-simple, as it is both a SOAP service (using metro) and also a SOAP client, but beyond that I wouldn't call it that complex. I can then remove the .war file and folder from webapps, and it will come up just nicely, and I can deploy the context via the html interface with now complaints. At this point, when the ZZZ context is deployed and running and I'll be good until the next reboot/restart of tomcat. The issue occurs regardless if I only have the context folder in webapps, or I also have the .war file present. I've used most of the day searching the web for solutions, but it is kinda hard when there is no indication of what is stalling things.. Could this be a tomcat issue? It is kinda hard to setup other (specific) versions of tomcat to test this, and I've tried 7.0.28, but its a completely separate environment with other versions of java etc, but there I run into other issues related to JAX/Metro, so thats not much help as it is. Any help is greatly appreciated! /Steffen I guess it could be the same underlying cause but why
Re: asking advice for tomcat 7 config
ok... thanks for nothing... 2012/10/18 Pid p...@pidster.com On 18/10/2012 12:22, Daniel Barcellos wrote: Hey I'm facing similar problems too and I guess with a good configuration of my server.xml would be a good start point. So could kindly share a good Connector configuration in this mail thread? What would that be the best choice in terms of max min threads keep alived timeout configurations ? It's probably not your connector config that's the problem, if there is one. Most of the time it's your app. Use a profiler, monitor JMX (use VisualVM with the MBeans plugin) and understand what's happening rather than assuming someone else's connector config is good or better. Start a new thread when you've tried this have questions. p Thanks in advance! Sent from my iPhone On 18/10/2012, at 07:05, Romain Van der Keilen romain.vanderkei...@uniway.be wrote: Hi there! Some news for you about my problem. I did all the modifications you suggested, it increased the response time a little bit (2-3 seconds better on a 15 seconds scale). It was already good to take, and helped me to create a healthy configuration. After that, I looked deeper into the database configuration, as I saw in the tests that non db relative actions were responding very fast (50ms for a 1000 users basis). I finally found an OracleDataSource in the Oracle Driver, which reacts far way better than the BasicDataSource I was using before (12s for 150 users for the basic data source, 1.5s for the oracle one, same test). So I think my problems are solved, thanks to you guys! Many thanks for the advices, Romain. -Original Message- From: André Warnier [mailto:a...@ice-sa.com] Sent: mercredi 17 octobre 2012 11:49 To: Tomcat Users List Subject: Re: asking advice for tomcat 7 config Pid wrote: ... Executor name=tomcatThreadPool namePrefix=catalina-exec-80- maxThreads=650 minSpareThreads=100 / Connector executor=tomcatThreadPool address=10.10.10.10 port=80 maxHttpHeaderSize=8192 protocol=org.apache.coyote.http11.Http11NioProtocol connectionTimeout=2 redirectPort=443 server=lighthttpd/2.0.0 enableLookups=false acceptorThreadCount=4 socket.directBuffer=false compression=off compressableMimeType=text/html,text/xml,text/plain,text/javascript,text/css,image/jpeg,image/png,image/gif acceptCount=50 bufferSize=4096 / Executor name=stomcatThreadPool namePrefix=catalina-exec-443- maxThreads=650 minSpareThreads=100 / Connector executor=stomcatThreadPool protocol=org.apache.coyote.http11.Http11NioProtocol port=443 SSLEnabled=true scheme=https secure=true clientAuth=false sslProtocol=TLS keystoreFile=D:\keystore\appks server=lighthttpd/2.0.0 enableLookups=false keystorePass=changeit address=10.10.10.10 acceptorThreadCount=4 socket.directBuffer=false compression=off compressableMimeType=text/html,text/xml,text/plain,text/javascript,text/css,image/jpeg,image/png,image/gif acceptCount=50 bufferSize=4096 /Connector You've configured a separate pool for connectors on ports 80 and 443. Why? You've reduced the acceptCount to 50. Why? You are compressing compressed images. Why? There is : compression=off in both connectors though. So I guess that compressableMimeType should be ignored. (It /is/ still questionable to have changed the default of compressableMimeType, to include types which are inherently compressed already.) You are setting acceptorThreadCount=4. Why? Does your app have a database connection pool? What are the sizing parameters for this pool? Also, - for the HTTP connector, connectionTimeout is set to 2 (milliseconds), and keepAliveTimeout is not set. - for the HTTPS connector, neither one is set. That will cause : - for the HTTP connector : - connectionTimeout = 2 ms (20 s.) - keepAliveTimeout = 2 ms - for the HTTPS connector : - connectionTimeout = 6 ms (60 s.) - keepAliveTimeout = 6 ms 1) So it means that if a client connects to the server, but does not send any request line for a while on that connection, the server will allocate a thread to serve the request; this thread will wait up to 20 s (on HTTP) or 60 s. (on HTTPS), before timing out and returning to the pool of available threads. Of course only a malicious client would do that.. 2) it also means that a perfectly non-malicious client can connect to the server, and send a first request on the connection; the server will allocate a thread to handle this request; and then, if the same client has no more requests to send for a while, this thread will nevertheless remain waiting on this connection for 20 s. (HTTP) or 60 s. (HTTPS), just in case the client /would/ send another request on it. During this time, the thread is unavailable to process other client requests.
Re: Get active session list
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Felipe, On 10/18/12 9:34 AM, Felipe Jaekel wrote: I need to get the active session list. Searching about I saw a lot of people with the same question, but no answer. I don't want to write a list inside a HttpSessionListener and keep the session list there, because I use session serialization and the list inside the listener would be destroyed in case the server is restarted. You *can* get notification of sessions being de-serialized from the disk to maintain your list. Look at the other session-related listeners in the servlet API. You could also use JMX to get a list of sessions. Use JConsole to poke-around in Tomcat's JMX beans and find the one(s) that expose sessions. You may have to make your webapp privileged in order to make JMX calls. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCAEgwACgkQ9CaO5/Lv0PARBACfZ+EG7KJWXt+49sbB1kVsLunF A4MAoKv1hM4KBlaAS4a1UaP0ePqfRr3W =n3WU -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: asking advice for tomcat 7 config
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Romain, On 10/18/12 6:05 AM, Romain Van der Keilen wrote: After that, I looked deeper into the database configuration, as I saw in the tests that non db relative actions were responding very fast (50ms for a 1000 users basis). I finally found an OracleDataSource in the Oracle Driver, which reacts far way better than the BasicDataSource I was using before (12s for 150 users for the basic data source, 1.5s for the oracle one, same test). I'd be interested to see the difference in configuration. I've never had problems with Tomcat's (really commons-dbcp's) BasicDataSource. Perhaps when you switched, you changed some essential configuration option? The obvious one being the size of the connection pool: if you are try to test 70 simultaneous db-related operations but your connection pool only contains 50 connections, then many of the requests are going to sit idly-waiting for db connections. Basically, you cannot scale beyond 50 simultaneous HTTP connections if all your requests are db-related. The equation looks something like this (where 'R' is the number of HTTP requests, 'P' is the size of your connection pool and 'L' is the proportion of all request you expect to require a db connection): max(R) = P / L So, if you have 50 connections in your pool and you expect 50% of your requests to require a database connection, then you can only expect to be able to serve 50 / 0.5 = 100 simultaneous HTTP connections. Conversely, if you want to be able to handle 500 connections at 50% rate, then you need to have 250 connections available in your database pool. Of course, if you have multiple servers, then you have to be aware that each app instance will open 250 connections to your database. If you can't handle N*250 on the database side, then you have to do the equation from the resource-limited side instead of from the demand-I-want-to-serve side. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCAFWIACgkQ9CaO5/Lv0PDKZACgmocnQvpoGVKSS4x2GcwWE9e6 kLEAn2YgbZrpQ0HqrgIiC1s5s2GanNbQ =Kasu -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: asking advice for tomcat 7 config
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel, On 10/18/12 10:12 AM, Daniel Barcellos wrote: ok... thanks for nothing... No thanks for the snarkiness. :( Pid's advice is actually good, even if you don't want to hear it: 2012/10/18 Pid p...@pidster.com It's probably not your connector config that's the problem, if there is one. Most of the time it's your app. Use a profiler, monitor JMX (use VisualVM with the MBeans plugin) and understand what's happening rather than assuming someone else's connector config is good or better. Taking someone else's configuration doesn't really help you. Instead, it makes you feel good that it improved someone else's situation and therefore is likely to benefit you. Maybe Romain has a 64-way blade server with 32GiB of heap space: he can afford a lot of threads, etc. Maybe you have a 1GiB dual-core CPU and his configuration will make your environment royally suck. If you want advice, ask for it. But don't just say oh, hey, your configuration worked great for you so give it to me and it will certainly work great. Start a new thread when you've tried this have questions. +1 Technically, Daniel, you're hijacking Romain's thread. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCAFnUACgkQ9CaO5/Lv0PDpkwCgvMnJKQbrRJtKe9380RtDCOBR E5sAn3P171y2P6CHcTm92ruFQgNaMtH+ =JT0G -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Context fails to load during start of Tomcat, and stalls tomcat startup
Is it possible that the context in question depends on another context in your setup for something during startup? Do you have something in a context listener (or a servlet that gets deployed on startup) that makes a web service call to another context in your system during initialization? If so, what happens if that context is not available? Does it wait and try again or does it just hang? On Thu, 2012-10-18 at 16:08 +0200, Steffen Schumacher wrote: Hi! Running apache-tomcat 7.0.26 on FreeBSD 8.1@vmware, I've spotted a really curious issue. We are hosting ~8 different contexts on 4 servers all matching the above setup, and in normal operation we have no beef at all, except when the server guys needs to reboot the servers for whatever reason. When this happens, the a specific context prevents tomcat from starting up it simply stops doing anything after these lines: server17# bin/catalina.sh run Using CATALINA_BASE: /usr/local/apache-tomcat-7.0 Using CATALINA_HOME: /usr/local/apache-tomcat-7.0 Using CATALINA_TMPDIR: /usr/local/apache-tomcat-7.0/temp Using JRE_HOME:/usr/local Using CLASSPATH: /usr/local/apache-tomcat-7.0/bin/bootstrap.jar:/usr/local/apache-tomcat-7.0/ bin/tomcat-juli.jar Oct 18, 2012 1:06:03 PM org.apache.catalina.core.AprLifecycleListener init INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/local/diablo-jdk1.6.0/jre/lib/i386/server:/usr/local/diablo-jdk1.6.0/jr e/lib/i386:/usr/local/diablo-jdk1.6.0/jre/../lib/i386:/usr/java/packages/lib /i386:/lib:/usr/lib:/usr/local/lib Oct 18, 2012 1:06:03 PM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [http-bio-8180] Oct 18, 2012 1:06:03 PM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [http-bio-8443] Oct 18, 2012 1:06:04 PM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [ajp-bio-8009] Oct 18, 2012 1:06:04 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1488 ms Oct 18, 2012 1:06:04 PM org.apache.catalina.core.StandardService startInternal INFO: Starting service Catalina Oct 18, 2012 1:06:04 PM org.apache.catalina.core.StandardEngine startInternalINFO: Starting Servlet Engine: Apache Tomcat/7.0.26 Oct 18, 2012 1:06:04 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive /usr/local/apache-tomcat-7.0/webapps/XXX##10.4b2.war Oct 18, 2012 1:06:04 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive /usr/local/apache-tomcat-7.0/webapps/.war Oct 18, 2012 1:06:12 PM com.sun.xml.ws.server.MonitorBase createRoot INFO: Metro monitoring rootname successfully set to: com.sun.metro:pp=/,type=WSEndpoint,name=/-RequestHandler-RequestHand lerPort Oct 18, 2012 1:06:12 PM com.sun.xml.ws.transport.http.servlet.WSServletDelegate init INFO: WSSERVLET14: JAX-WS servlet initializing Oct 18, 2012 1:06:12 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized INFO: WSSERVLET12: JAX-WS context listener initializing Oct 18, 2012 1:06:12 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized INFO: WSSERVLET12: JAX-WS context listener initializing Oct 18, 2012 1:06:12 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive /usr/local/apache-tomcat-7.0/webapps/##10.4b1.war Oct 18, 2012 1:06:15 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized INFO: WSSERVLET12: JAX-WS context listener initializing And nothing happens now, even if I leave it for 1+ hours Now the ZZ(culprit) context is a perhaps not ultra-simple, as it is both a SOAP service (using metro) and also a SOAP client, but beyond that I wouldn't call it that complex. I can then remove the .war file and folder from webapps, and it will come up just nicely, and I can deploy the context via the html interface with now complaints. At this point, when the ZZZ context is deployed and running and I'll be good until the next reboot/restart of tomcat. The issue occurs regardless if I only have the context folder in webapps, or I also have the .war file present. I've used most of the day searching the web for solutions, but it is kinda hard when there is no indication of what is stalling things.. Could this be a tomcat issue? It is kinda hard to setup other (specific) versions of tomcat to test this, and I've tried 7.0.28, but its a completely separate environment with other versions of java etc, but there I run into other issues related to JAX/Metro, so thats not much help as it is. Any help is greatly appreciated! /Steffen I guess it could be the same underlying cause but why -
Re: asking advice for tomcat 7 config
Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel, On 10/18/12 10:12 AM, Daniel Barcellos wrote: ok... thanks for nothing... No thanks for the snarkiness. :( Pid's advice is actually good, even if you don't want to hear it: 2012/10/18 Pid p...@pidster.com It's probably not your connector config that's the problem, if there is one. Most of the time it's your app. Use a profiler, monitor JMX (use VisualVM with the MBeans plugin) and understand what's happening rather than assuming someone else's connector config is good or better. Taking someone else's configuration doesn't really help you. Instead, it makes you feel good that it improved someone else's situation and therefore is likely to benefit you. Maybe Romain has a 64-way blade server with 32GiB of heap space: he can afford a lot of threads, etc. Maybe you have a 1GiB dual-core CPU and his configuration will make your environment royally suck. If you want advice, ask for it. But don't just say oh, hey, your configuration worked great for you so give it to me and it will certainly work great. Start a new thread when you've tried this have questions. +1 Technically, Daniel, you're hijacking Romain's thread. +, Daniel : Think of it this way : if there was a combination of settings that worked in all cases, then what would be the point of these adjustable parameters ? The Tomcat guys would just set them all to the optimal value, and there would be no need for a lot of the code and the documentation. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: asking advice for tomcat 7 config
Ok guys, apologies for my inconvenience. I was just wondering if there was a way to solve a few problems that I'm facing here like threads that get stuck and no way to release them. I already chat with my client's architechs in order to ask them if they are closing any output source when downloading things from my app. Well I will wait when those thread problems come bach and see if I can catch some thread dumps and stuffs... Thanks! 2012/10/18 André Warnier a...@ice-sa.com Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel, On 10/18/12 10:12 AM, Daniel Barcellos wrote: ok... thanks for nothing... No thanks for the snarkiness. :( Pid's advice is actually good, even if you don't want to hear it: 2012/10/18 Pid p...@pidster.com It's probably not your connector config that's the problem, if there is one. Most of the time it's your app. Use a profiler, monitor JMX (use VisualVM with the MBeans plugin) and understand what's happening rather than assuming someone else's connector config is good or better. Taking someone else's configuration doesn't really help you. Instead, it makes you feel good that it improved someone else's situation and therefore is likely to benefit you. Maybe Romain has a 64-way blade server with 32GiB of heap space: he can afford a lot of threads, etc. Maybe you have a 1GiB dual-core CPU and his configuration will make your environment royally suck. If you want advice, ask for it. But don't just say oh, hey, your configuration worked great for you so give it to me and it will certainly work great. Start a new thread when you've tried this have questions. +1 Technically, Daniel, you're hijacking Romain's thread. +, Daniel : Think of it this way : if there was a combination of settings that worked in all cases, then what would be the point of these adjustable parameters ? The Tomcat guys would just set them all to the optimal value, and there would be no need for a lot of the code and the documentation. --**--**- To unsubscribe, e-mail: users-unsubscribe@tomcat.**apache.orgusers-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
question about krb5.conf file
Hi,
I am trying to get my AIX box configured to use Windows Authentication from the
tomcat server (web browser). I have been relying on the example that is at
http://tomcat.apache.org/tomcat-7.0-doc/windows-auth-howto.html#Tomcat_instance.
Here is my question. The example is using all windows and not unix, so I am
not 100% sure on my syntax AND I have two domains I am working with. One for
the tomcat server and one for the windows domain controller. The example shows
them all on the same domain and I have tried a few different configurations and
they haven't worked. So I am hoping to get an answer here.
This is my info:
AIX 6100-04-11-1140
apache-tomcat-7.0.27
tomcat server domain: CON-WAY.COM
windows AD domain: CONWAY.PROD.CON-WAY.COM
Here is what I currently have in the krb5.conf file (it has changed many times
LOL):
[libdefaults]
default_realm = CONWAY.PROD.CON-WAY.COM
default_keytab_name = FILE:/opt/apache-tomcat-7.0.27/conf/tomcat.keytab
default_tkt_enctypes = des-cbc-md5 des-cbc-crc
default_tgs_enctypes = des-cbc-md5 des-cbc-crc
forwardable=true
[realms]
CONWAY.PROD.CON-WAY.COM = {
kdc = ciits003.conway.prod.con-way.com:88
}
[domain_realm]
con-way.com = CONWAY.PROD.CON-WAY.COM
.con-way.com = CONWAY.PROD.CON-WAY.COM
[logging]
kdc = FILE:/var/krb5/log/krb5kdc.log
admin_server = FILE:/var/krb5/log/kadmin.log
default = FILE:/var/krb5/log/krb5lib.log
Anyone see any blaring errors? I am not sure I need to put the word FILE in
front of all file locations, but it was in the Windows example
Jen
Re: Get active session list
Found the following: context = (Context) wrapper.getParent(); host = (Host) context.getParent(); Context ctx = (Context) host.findChild(name); Manager manager = ctx.getManager(); Session [] sessions = manager.findSessions(); Had the same doubt I had when I looked at the PSI Probe code some days ago: how to handle the wrapper property? As a alternative I tried to implement *HttpSessionActivationListener*, but the methods aren't called when I restart the server. Thanks again for the help, Phillip 2012/10/18 Christopher Schultz ch...@christopherschultz.net -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Felipe, On 10/18/12 9:34 AM, Felipe Jaekel wrote: I need to get the active session list. Searching about I saw a lot of people with the same question, but no answer. I don't want to write a list inside a HttpSessionListener and keep the session list there, because I use session serialization and the list inside the listener would be destroyed in case the server is restarted. You *can* get notification of sessions being de-serialized from the disk to maintain your list. Look at the other session-related listeners in the servlet API. You could also use JMX to get a list of sessions. Use JConsole to poke-around in Tomcat's JMX beans and find the one(s) that expose sessions. You may have to make your webapp privileged in order to make JMX calls. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCAEgwACgkQ9CaO5/Lv0PARBACfZ+EG7KJWXt+49sbB1kVsLunF A4MAoKv1hM4KBlaAS4a1UaP0ePqfRr3W =n3WU -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Help on Windows 2008(64 bit)\Tomcat
I am new to the Tomcat and IIs 7 world and I am having issues getting mine app to work beyond the default port 8080. I am building a new server with those specs. I tried to keep this short but still include details of what I have done. If anyone has any ideas of items I can research or try, it would be greatly appreciated. I installed apache-tomcat-6.0.35.exe and tomcat-connectors-1.2.37-windows-x86_64-iis.zip from Tomcat site. I followed the following site, as much as I could. I had to find other guides for help with the IIS7 parts. http://tomcat.apache.org/connectors-doc/webserver_howto/iis.html I do not have my Application Pools enabling 32 bit applications. I then ran a axis2.war I had from our old server to install a new webapp and it works also, when on port 8080. At this time, when I do not use port 8080, it asks if I want to download a file, but no matter what name I put it asks me that same thing. It is not even a real file. Nothing is jumping out at me within the log files. Main 2 errors I see are below, but research shows the second one should not matter. [ERROR] Missing wsse:Security header in request org.apache.axis2.AxisFault: Missing wsse:Security header in request SEVERE: Error, processing connection java.lang.IndexOutOfBoundsException at java.io.BufferedInputStream.read(Unknown Source) Thank you, Jace -Message Disclaimer- This e-mail message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply email to conn...@principal.com and delete or destroy all copies of the original message and attachments thereto. Email sent to or from the Principal Financial Group or any of its member companies may be retained as required by law or regulation. Nothing in this message is intended to constitute an Electronic signature for purposes of the Uniform Electronic Transactions Act (UETA) or the Electronic Signatures in Global and National Commerce Act (E-Sign) unless a specific statement to the contrary is included in this message. While this communication may be used to promote or market a transaction or an idea that is discussed in the publication, it is intended to provide general information about the subject matter covered and is provided with the understanding that The Principal is not rendering legal, accounting, or tax advice. It is not a marketed opinion and may not be used to avoid penalties under the Internal Revenue Code. You should consult with appropriate counsel or other advisors on all matters pertaining to legal, tax, or accounting obligations and requirements - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: question about krb5.conf file
Hi. Mead, Jen L wrote: Hi, I am trying to get my AIX box configured to use Windows Authentication from the tomcat server (web browser). I have been relying on the example that is at http://tomcat.apache.org/tomcat-7.0-doc/windows-auth-howto.html#Tomcat_instance. Here is my question. The example is using all windows and not unix, so I am not 100% sure on my syntax AND I have two domains I am working with. One for the tomcat server and one for the windows domain controller. The example shows them all on the same domain and I have tried a few different configurations and they haven't worked. So I am hoping to get an answer here. I am not sure, but I believe, that the SPNEGO authentication which is included in Tomcat right now presupposes that the Tomcat host itself is a Windows machine, and member of the Windows domain in which you want the authentication to take place (or probably at least a trusted domain). If that were the case, then you may be better off having a look at the other alternatives indicated in that documentation page, or at Jespa (www.ioplex.com) which is a commercial (but affordable) solution which works with whatever OS Tomcat is running under. I can't figure out from the Waffle website if Waffle works on other than on Windows Tomcat hosts either. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Help on Windows 2008(64 bit)\Tomcat
McDaniel, Jace wrote: I am new to the Tomcat and IIs 7 world and I am having issues getting mine app to work beyond the default port 8080. So what you are saying is that your application does work, when you access Tomcat directly through port 8080 ? And it doesn't work when you try to access it through IIS (presumably port 80) and the Isapi_redirector module ? I am building a new server with those specs. I tried to keep this short but still include details of what I have done. If anyone has any ideas of items I can research or try, it would be greatly appreciated. I installed apache-tomcat-6.0.35.exe and tomcat-connectors-1.2.37-windows-x86_64-iis.zip from Tomcat site. I followed the following site, as much as I could. I had to find other guides for help with the IIS7 parts. http://tomcat.apache.org/connectors-doc/webserver_howto/iis.html I do not have my Application Pools enabling 32 bit applications. I then ran a axis2.war I had from our old server (?) to install a new webapp (?) and it works also (?), when on port 8080. At this time, when I do not use port 8080, it asks if I want to download a file, ... And when you use port 8080, what does it (?) do ? but no matter what name I put it asks me that same thing. It is not even a real file. You know, this is a bit obscure as an explanation. Nothing is jumping out at me within the log files. Main 2 errors I see are below, but research shows the second one should not matter. [ERROR] Missing wsse:Security header in request org.apache.axis2.AxisFault: Missing wsse:Security header in request This looks like an Axis problem, not a Tomcat one. Did you ask on the Axis list what it means ? SEVERE: Error, processing connection java.lang.IndexOutOfBoundsException at java.io.BufferedInputStream.read(Unknown Source) and the rest ? (the log lines after that one) In general, about the above message : - you indicated which versions of Tomcat and the Isapi_redirector you have downloaded and installed. That's good. - you are telling us which version of IIS you are using, and which instructions you followed. That's good too. - but the rest of your explanations are not very clear, and make it difficult to figure out what kind of problem you may have, and how to help you. That's not good. Can you : - give us an example of a URL that you are using with the port 8080 and which works, and tell us precisely what happens in the browser when you use that URL - and then another example of (preferably) the same URL that you are using with not-port-8080 and which does not work, and tell us precisely what happens in the browser when you use that URL - and then tell us what you mean by I then ran a axis2.war ? What did you do with that axis2.war file ? In which directory did you copy it ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
