Tomcat upgrades/security patching best practises
Hi, What are the best practices for upgrading the tomcat given the fact that they are no direct security patches available. Specially with the environments where there are large instances of Tomcat servers running it is challenging to upgrade these servers manually in all the systems. Are there any best practices defined for doing this given the frequency of security patches being applied on Tomcat (Leave alone JDK patches) Regards Satish J
Re: Tomcat 7 on FreeBSD
On 24.02.2014 00:09, Bobby Walker wrote: The FreeBSD way is install via ports. However, I will go this route and see what happens. I used to use FreeBSD when versions 5-6 were in use. I remember that Java port was not as stable as the Linux one. Compiled one had some problems, as well as the one ran with Linux compatibility enabled. Is it better nowadays? -- Mikolaj Rydzewski m...@ceti.pl - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat upgrades/security patching best practises
On 24/02/2014 09:20, satish jupalli wrote: Hi, What are the best practices for upgrading the tomcat given the fact that they are no direct security patches available. Specially with the environments where there are large instances of Tomcat servers running it is challenging to upgrade these servers manually in all the systems. Are there any best practices defined for doing this given the frequency of security patches being applied on Tomcat (Leave alone JDK patches) Use a separate $CATALINA_HOME and $CATALINA_BASE. Upgrading should then be as simple as: - modify the init.d script to point to the new $CATALINA_HOME (you can safely use the new Tomcat version to stop the old one). - stop the instance - start the instance You can use rsync to have multiple servers all pick up the new CATALINA_HOME (note you don't want to replace the old one with the new one, you need to have multiple CATALINA_HOMEs alongside each another). You could even use rsync to update the init.d script. You could probably go further still with the automation and have it handle the restart too but how best to do that for your environment (if indeed it even makes sense to go further) is going to vary from installation to installation. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat upgrades/security patching best practises
Thanks Mark. That helped a lot. On Mon, Feb 24, 2014 at 5:50 PM, Mark Thomas ma...@apache.org wrote: On 24/02/2014 09:20, satish jupalli wrote: Hi, What are the best practices for upgrading the tomcat given the fact that they are no direct security patches available. Specially with the environments where there are large instances of Tomcat servers running it is challenging to upgrade these servers manually in all the systems. Are there any best practices defined for doing this given the frequency of security patches being applied on Tomcat (Leave alone JDK patches) Use a separate $CATALINA_HOME and $CATALINA_BASE. Upgrading should then be as simple as: - modify the init.d script to point to the new $CATALINA_HOME (you can safely use the new Tomcat version to stop the old one). - stop the instance - start the instance You can use rsync to have multiple servers all pick up the new CATALINA_HOME (note you don't want to replace the old one with the new one, you need to have multiple CATALINA_HOMEs alongside each another). You could even use rsync to update the init.d script. You could probably go further still with the automation and have it handle the restart too but how best to do that for your environment (if indeed it even makes sense to go further) is going to vary from installation to installation. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
NullPointerException when processing doFilter call in async Filter
Hi all, I’m trying to write an asynchronous Servlet Filter using Tomcat 7.0.50 as the Servlet Container. My understanding of the Servlet 3.0 spec regarding the async-supported feature is that adding this element to the web.xml for the filter and calling ServletRequest#startAsync() should allow the filter to continue its processing asynchronously after the doFilter method has returned. To test this I created a simple filter which just creates a Future to make a call to FilterChain#doFilter. But what I see is a NullPointerException when making the call to FilterChain#doFilter. From debugging the Tomcat source code, it seems that once my Filters doFilter method has returned the StandardWrapperValve#invoke line 283 is calling ApplicationFilterChain#release method is being called, which nulls out some required variables. So when I make the FilterChain#doFilter call it tries to dereference these nulled variables. So my question is, if the Servlet API 3.0 spec allows asynchronous Filters then why am I seeing a NPE? It seems like a standard use-case. Have I misunderstood some part of the spec? Or is this a bug in Tomcat? (And from a quick look seems to be the case in 7.0.52 and 8.0.3) I have had a quick look at using Jetty 9 and it seems that the call to FilterChain#doFilter, in this case, does succeed as expected, i.e. processing gets passed to the next filter. (Although I’m seeing issues whilst that filter is performing its processing.) I’ve created a Gist of the code I used to reproduce the problem if its of any help, https://gist.github.com/phillcunnington/9185680. Any help with this would be much appreciated as its causing some major headaches! Thanks Phill Cunnington
Tomcat/Java Spring MVC 2.0/c3p0 - Consultant needed
Hi, Sorry if this is not the right forum for this kind of inquiry. I figure the best candidates would be in this forum from personal experience. Our company is having production issues which I believe are either due to application inefficiencies or a bug somewhere in our software stack. We are having production issues with our Tomcat connection pool using c3p0 and while my knowledge in this area has improved, I lack the Java developer background that might help in this area and we are at a point where we need this solved quickly. The problems could be related to leaked connections which I'm quite sure we have. I have turned on c3p0 debugging and identified this in the past and the ideal consultant could identify in our code where those are happening and fix them. We are looking to hire a consultant that would come to Fredericton, NB, Canada to work with us on this problem. Serious inquiries only. I will be looking for proof that you have extensive experience with Tomcat, Java Spring and c3p0. If you are interested, send me your resume (through your company or individually) and send me as much proof as possible of your experience with the specific technologies mentioned. Thanks, Charles
linux vs windows responses on the list
In general, is it assumed that all responses given to the list assume the OP is running a version of Linux, if they don't state the OS? For example, I read the post about Tomcat upgrades/security patching best practices and the advice given is to modify init.d script. I don't recall seeing the OP indicate they run Linux and the list usually gently bashes people for not being specific about their environment. Since I run Tomcat on Windows, I don't know what the init.d script is, but reading that response I get the feeling the that Tomcat on Linux is alot easier to manage than Tomcat on Windows, especially if you are running Tomcat as a Windows service. I would have thought that another option to that post would be to use the appBase attribute of a Host element and just move your webapps out of the traditional location located within the Tomcat installation directory. But I guess I didn't understand the OP. Is it time for us to go to Linux? Leo - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7 on FreeBSD
On Feb 24, 2014, at 3:28 AM, Mikolaj Rydzewski m...@ceti.pl wrote: On 24.02.2014 00:09, Bobby Walker wrote: The FreeBSD way is install via ports. However, I will go this route and see what happens. I used to use FreeBSD when versions 5-6 were in use. I remember that Java port was not as stable as the Linux one. Compiled one had some problems, as well as the one ran with Linux compatibility enabled. Is it better nowadays? -- Mikolaj Rydzewski m...@ceti.pl - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org I am definitely not a Linux fan at all. This is my first attempt to use Tomcat, so I really can't answer that question. What I can say about it is that it installed from ports very cleanly, using the openjdk6 port, and was up and running in short order with minimal fuss. The fuss is a result of the web application that I'm trying to run on the platform. As an earlier poster mentioned, the jasper-runtime has been out since before 6.x. So, I installed the last 5.x version and that indeed solved that issue, and created a new one too. I am next going to try to load the project and see if I can do anything to build it to more modern libraries. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: linux vs windows responses on the list
On 2/24/2014 10:59 AM, Leo Donahue wrote: In general, is it assumed that all responses given to the list assume the OP is running a version of Linux, if they don't state the OS? For example, I read the post about Tomcat upgrades/security patching best practices and the advice given is to modify init.d script. I don't recall seeing the OP indicate they run Linux and the list usually gently bashes people for not being specific about their environment. Since I run Tomcat on Windows, I don't know what the init.d script is, but reading that response I get the feeling the that Tomcat on Linux is alot easier to manage than Tomcat on Windows, especially if you are running Tomcat as a Windows service. I would have thought that another option to that post would be to use the appBase attribute of a Host element and just move your webapps out of the traditional location located within the Tomcat installation directory. But I guess I didn't understand the OP. Is it time for us to go to Linux? Not if you're already used to windows and not familiar with Linux; the difference isn't big enough to justify the learning curve. I use TC on windows at work, and my home server is Linux (Debian). The main advantage of windows is that you have GUIs available for setting most options, which is easier if you don't know exactly what you're looking for. The advantage of Linux IMO is that you have more fine-grained control of things, once you know what you're looking for. If you know either one of them well, switching isn't going to be enough of a gain from an administration POV to be worth the learning curve. Of course, there may be other considerations in your particular environment that may drive the decision one way or another. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: linux vs windows responses on the list
On 24/02/2014 16:15, David kerber wrote: On 2/24/2014 10:59 AM, Leo Donahue wrote: In general, is it assumed that all responses given to the list assume the OP is running a version of Linux, if they don't state the OS? For example, I read the post about Tomcat upgrades/security patching best practices and the advice given is to modify init.d script. I don't recall seeing the OP indicate they run Linux and the list usually gently bashes people for not being specific about their environment. That was more me picking an OS to respond to on the basis of my mode at the time rather than an expectation of Linux. Since I run Tomcat on Windows, I don't know what the init.d script is, but reading that response I get the feeling the that Tomcat on Linux is alot easier to manage than Tomcat on Windows, especially if you are running Tomcat as a Windows service. You can do pretty much the same thing for Windows. It would look something like: - push the new CATALINA_HOME via a shared drive - remote tweak the registry to point to the new CATALINA_HOME - remote restart the service All of the above can be scripted if you wish. Rather than pushing you could pull with some simple scripts and scheduled jobs. I would have thought that another option to that post would be to use the appBase attribute of a Host element and just move your webapps out of the traditional location located within the Tomcat installation directory. But I guess I didn't understand the OP. Is it time for us to go to Linux? Not if you're already used to windows and not familiar with Linux; the difference isn't big enough to justify the learning curve. I use TC on windows at work, and my home server is Linux (Debian). The main advantage of windows is that you have GUIs available for setting most options, which is easier if you don't know exactly what you're looking for. The advantage of Linux IMO is that you have more fine-grained control of things, once you know what you're looking for. If you know either one of them well, switching isn't going to be enough of a gain from an administration POV to be worth the learning curve. +1 Of course, there may be other considerations in your particular environment that may drive the decision one way or another. I've worked with Tomcat on Windows, Linux, Solaris, FreeBSD, HP-UX and some more unusual hardware like plug-computers. By far the biggest issue the first time I hit a new OS is figuring out how to do stuff in that OS. I'm comfortable with most OSes these days. Given a free choice for a server I'd start from some flavour of Linux but my desktop where I do all of my dev is Windows and is likely to stay that way (multi-head support for old-ish hardware is so much less hassle with Windows). Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: linux vs windows responses on the list
On 24/02/2014 16:33, Mark Thomas wrote: That was more me picking an OS to respond to on the basis of my mode at the time rather than an expectation of Linux. s/mode/mood/ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: linux vs windows responses on the list
On 2/24/14 8:33 AM, Mark Thomas wrote: . . . I've worked with Tomcat on Windows, Linux, Solaris, FreeBSD, HP-UX and some more unusual hardware like plug-computers. By far the biggest issue the first time I hit a new OS is figuring out how to do stuff in that OS. . . . And I have a fair amount of experience, FWIW, running it on OS/400. -- JHHL - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat 7.0.37 issue on our Sun Sparc
We newly installed Solaris 10 with all default settings on our Sun Sparc machine (sun4u sparc SUNW,UltraAX-i2 64-bit sparcv9 kernel modules). The OS Version: SunOS hostname 5.10 Generic_147147-26 sun4u sparc SUNW,UltraAX-i2. The Java in the environment: java version 1.6.0_37 Java(TM) SE Runtime Environment (build 1.6.0_37-b06) Java HotSpot(TM) Client VM (build 20.12-b01, mixed mode, sharing) We downloaded the apache-tomcat-7.0.37.tar.gz and just unpack it into /tmp. Then we started the Tomcat server using ./startup.sh. It was working ok after starting and we can see the Tomcat page on Web Browser at the port 8080. But The Tomcat stopped internally itself after several hours (looks randomly) without reason. We couldn't find this issue in the FAQ Known issues. Is anyone aware about this issue? Can you please provide any clues? Thanks, Jay PS. Here is the output from catalina.out: ## Feb 19, 2014 12:14:37 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/jdk/instances/jdk1.6.0/jre/lib/sparc/client:/usr/jdk/instances/jdk1.6.0 /jre/lib/sparc:/usr/jdk/instances/jdk1.6.0/jre/../lib/sparc:/usr/jdk/package s/lib/sparc:/lib:/usr/lib Feb 19, 2014 12:14:40 PM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [http-bio-8080] Feb 19, 2014 12:14:40 PM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [ajp-bio-8009] Feb 19, 2014 12:14:40 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 4968 ms Feb 19, 2014 12:14:40 PM org.apache.catalina.core.StandardService startInternal INFO: Starting service Catalina Feb 19, 2014 12:14:40 PM org.apache.catalina.core.StandardEngine startInternal INFO: Starting Servlet Engine: Apache Tomcat/7.0.37 Feb 19, 2014 12:14:40 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory /tmp/apache-tomcat-7.0.37/webapps/ROOT Feb 19, 2014 12:14:42 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory /tmp/apache-tomcat-7.0.37/webapps/docs Feb 19, 2014 12:14:43 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory /tmp/apache-tomcat-7.0.37/webapps/examples Feb 19, 2014 12:14:44 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory /tmp/apache-tomcat-7.0.37/webapps/host-manager Feb 19, 2014 12:14:44 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory /tmp/apache-tomcat-7.0.37/webapps/manager Feb 19, 2014 12:14:45 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler [http-bio-8080] Feb 19, 2014 12:14:45 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler [ajp-bio-8009] Feb 19, 2014 12:14:45 PM org.apache.catalina.startup.Catalina start INFO: Server startup in 4826 ms Feb 19, 2014 7:05:26 PM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler [http-bio-8080] Feb 19, 2014 7:05:26 PM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler [ajp-bio-8009] Feb 19, 2014 7:05:26 PM org.apache.catalina.core.StandardService stopInternal INFO: Stopping service Catalina Feb 19, 2014 7:05:26 PM org.apache.coyote.AbstractProtocol stop INFO: Stopping ProtocolHandler [http-bio-8080] Feb 19, 2014 7:05:26 PM org.apache.coyote.AbstractProtocol stop INFO: Stopping ProtocolHandler [ajp-bio-8009] Feb 19, 2014 7:05:26 PM org.apache.coyote.AbstractProtocol destroy INFO: Destroying ProtocolHandler [http-bio-8080] Feb 19, 2014 7:05:26 PM org.apache.coyote.AbstractProtocol destroy INFO: Destroying ProtocolHandler [ajp-bio-8009] ## - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7.0.37 issue on our Sun Sparc
On 24/02/2014 17:36, Jay wrote: We newly installed Solaris 10 with all default settings on our Sun Sparc machine (sun4u sparc SUNW,UltraAX-i2 64-bit sparcv9 kernel modules). The OS Version: SunOS hostname 5.10 Generic_147147-26 sun4u sparc SUNW,UltraAX-i2. The Java in the environment: java version 1.6.0_37 Java(TM) SE Runtime Environment (build 1.6.0_37-b06) Java HotSpot(TM) Client VM (build 20.12-b01, mixed mode, sharing) We downloaded the apache-tomcat-7.0.37.tar.gz and just unpack it into /tmp. Then we started the Tomcat server using ./startup.sh. It was working ok after starting and we can see the Tomcat page on Web Browser at the port 8080. But The Tomcat stopped internally itself after several hours (looks randomly) without reason. Nope. Not possible. Tomcat does not decide to shut itself down on a whim. That looks like a clean shut down so either: - something connected to the shut down port and sent the shut down command - something sent a SIGTERM to the Tomcat process. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RES: stop email excluir
Esta mensagem, incluindo seus anexos, é endereçada exclusivamente à(s) pessoa(s) e/ou instituições acima indicadas e pode conter informações confidenciais, particulares ou privilegiadas, as quais não podem, sob qualquer forma ou pretexto, ser utilizadas, divulgadas, alteradas, impressas ou copiadas, total ou parcialmente, por pessoas não autorizadas. No caso desta mensagem ser recebida por erro, por favor, providencie sua exclusão de qualquer sistema e/ou destrua quaisquer cópias reprográficas, notificando o remetente imediatamente. Eventual erro de transmissão desta mensagem em nenhuma hipótese constituirá renúncia à confidencialidade ou a qualquer direito ou prerrogativa decorrente da mesma. This message, and any attachments, is intended only for the named person's and/or entity's use and may contain confidential, proprietary or legally privileged information, which shall not be used, disclosed, changed, printed or copied, in whole or in part, by not intended recipients. If this message is received by error, please delete it from your system and/or destroy any hard copies of it and notify the sender, immediately. No confidentiality or privilege is waived by any mistransmission. -Mensagem original- De: Mark Thomas [mailto:ma...@apache.org] Enviada em: segunda-feira, 24 de fevereiro de 2014 14:41 Para: Tomcat Users List Assunto: Re: Tomcat 7.0.37 issue on our Sun Sparc On 24/02/2014 17:36, Jay wrote: We newly installed Solaris 10 with all default settings on our Sun Sparc machine (sun4u sparc SUNW,UltraAX-i2 64-bit sparcv9 kernel modules). The OS Version: SunOS hostname 5.10 Generic_147147-26 sun4u sparc SUNW,UltraAX-i2. The Java in the environment: java version 1.6.0_37 Java(TM) SE Runtime Environment (build 1.6.0_37-b06) Java HotSpot(TM) Client VM (build 20.12-b01, mixed mode, sharing) We downloaded the apache-tomcat-7.0.37.tar.gz and just unpack it into /tmp. Then we started the Tomcat server using ./startup.sh. It was working ok after starting and we can see the Tomcat page on Web Browser at the port 8080. But The Tomcat stopped internally itself after several hours (looks randomly) without reason. Nope. Not possible. Tomcat does not decide to shut itself down on a whim. That looks like a clean shut down so either: - something connected to the shut down port and sent the shut down command - something sent a SIGTERM to the Tomcat process. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 7.0.37 issue on our Sun Sparc
Hi Mark, Thank you for a quick response. It looks the Tomcat 7.0.37 is ok with Solaris 10 on other Sun Sparc machine ... could it be hardware related? Do you have any suggestion for us to capture that possible Shutdown command and/or possible SIGTERM? Thanks, Jay -Original Message- From: Mark Thomas [mailto:ma...@apache.org] Sent: Monday, February 24, 2014 12:41 PM To: Tomcat Users List Subject: Re: Tomcat 7.0.37 issue on our Sun Sparc On 24/02/2014 17:36, Jay wrote: We newly installed Solaris 10 with all default settings on our Sun Sparc machine (sun4u sparc SUNW,UltraAX-i2 64-bit sparcv9 kernel modules). The OS Version: SunOS hostname 5.10 Generic_147147-26 sun4u sparc SUNW,UltraAX-i2. The Java in the environment: java version 1.6.0_37 Java(TM) SE Runtime Environment (build 1.6.0_37-b06) Java HotSpot(TM) Client VM (build 20.12-b01, mixed mode, sharing) We downloaded the apache-tomcat-7.0.37.tar.gz and just unpack it into /tmp. Then we started the Tomcat server using ./startup.sh. It was working ok after starting and we can see the Tomcat page on Web Browser at the port 8080. But The Tomcat stopped internally itself after several hours (looks randomly) without reason. Nope. Not possible. Tomcat does not decide to shut itself down on a whim. That looks like a clean shut down so either: - something connected to the shut down port and sent the shut down command - something sent a SIGTERM to the Tomcat process. Mark - 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
tomcat 6 refuses mod_jk connections after server runs for a couple of days
Hello all, I'm running tomcat 6.0.32 on Cent OS 6 with 2 front end apache load balancers with a firewall in between the tomcat and load balancers using mod_jk v. 1.2.37 under apache 2.2.10 to connect the backend tomcat. I have had this running ok for a few years but our user traffic has increased significantly. A few months ago, the tomcat server seemed to refuse or not accept any new connections from either load balancer and required a restart on the tomcat end, even though I could easily connect to tomcat on port 8080(manager). I can intermittently telnet to port 8009, but am denied a bit as well both inside and outside the firewall. I proceeded to split the tomcats up into their own instances, hoping when this issue recurred that it would only affect a particular tomcat app. It also gave our developers the ability to patch a single tomcat app without downing all of our apps. Unfortunately, this issue has recurred several times and I have spent most of my days researching and digging for hope of someone with a similar experience that may have resolved it. Last Friday the problem was so bad, I had to completely restart the tomcat server(reboot it). So far I am at a loss...I have installed psi-probe on all tomcat instances to give me more in depth analysis to tomcat threads and related server metadata when the problem is occuring. I have made a few modifications to workers.properties, in particular to decrease the connection timeout as well as the tomcat ajp connector from 10 minutes to 5 minutes and added the ping timeout and socket timeout. I also increased my apache prefork MPM client connections to 500 on each load balancer. Below is my relevant configs...any suggestions to help remedy this would help... I have also increased threads from 200 to 500 on all tomcat instances. Workers.properties: worker.list=jkstatus,server1,server2,server3,server4,server5,server6,server7,server8 worker.jkstatus.type=status # Let's define some defaults worker.basic.port=8009 worker.basic.type=ajp13 worker.basic.socket_keepalive=True worker.basic.connection_pool_timeout=300 worker.basic.ping_timeout=1000 worker.basic.ping_mode=A worker.basic.socket_timeout=10 worker.lb1.distance=0 worker.lb1.reference=worker.basic worker.server1.host= server1hostname worker.server1.reference=worker.lb1 worker.server2.host=server2hostname worker.server2.reference=worker.lb1 worker.server3.host=server3hostname worker.server3.reference=worker.lb1 worker.server4.host= server4hostname worker.server4.reference=worker.lb1 worker.server5.host= server5hostname worker.server5.reference=worker.lb1 worker.server6.host= server6hostname worker.server6.reference=worker.lb1 worker.server7.host= server7hostname worker.server7.reference=worker.lb1 worker.server8.host= server7hostname worker.server8.reference=worker.lb1 httpd.conf: KeepAlive Off MaxKeepAliveRequests 100 KeepAliveTimeout 15 # prefork MPM # StartServers: number of server processes to start # MinSpareServers: minimum number of server processes which are kept spare # MaxSpareServers: maximum number of server processes which are kept spare # ServerLimit: maximum value for MaxClients for the lifetime of the server # MaxClients: maximum number of server processes allowed to start # MaxRequestsPerChild: maximum number of requests a server process serves IfModule prefork.c StartServers 8 MinSpareServers5 MaxSpareServers 20 ServerLimit 500 MaxClients 500 MaxRequestsPerChild 5000 /IfModule Tomcat server.xml: !-- Define an AJP 1.3 Connector on port 8009 -- Connector port=8009 address=x.x.x.x protocol=AJP/1.3 redirectPort=8443 connectionTimeout=30 maxThreads=500 /
Troubles to configure SSL
Hello, I have troubles configuring SSL, even if I follow https://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html. See my connectors as well as startup output below. After the startup I could navigate to http://localhost:8082/, but https://localhost:8445/ doesn't work. Any idea? Many thanks, Petr P.S. [Tomcat 7.0.50, Windows Server 2012 R2] *** server.xml connectors *** Connector port=8082 protocol=HTTP/1.1 connectionTimeout=2 redirectPort=8445 URIEncoding=UTF-8 / Connector port=8445 protocol=org.apache.coyote.http11.Http11NioProtocol SSLEnabled=true maxThreads=150 scheme=https secure=true clientAuth=false sslProtocol=TLS URIEncoding=UTF-8 keystoreFile=c:\@data\keystore\.keystore keystorePass=abcdef / Connector port=8011 protocol=AJP/1.3 redirectPort=8445 / *** startup output * II 24, 2014 8:51:04 ODP. org.apache.catalina.core.AprLifecycleListener init INFO: Loaded APR based Apache Tomcat Native library 1.1.29 using APR version 1.4.8. II 24, 2014 8:51:04 ODP. org.apache.catalina.core.AprLifecycleListener init INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true]. II 24, 2014 8:51:05 ODP. org.apache.catalina.core.AprLifecycleListener initializeSSL INFO: OpenSSL successfully initialized (OpenSSL 1.0.1e 11 Feb 2013) II 24, 2014 8:51:05 ODP. org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [http-apr-8082] II 24, 2014 8:51:05 ODP. org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [http-nio-8445] II 24, 2014 8:51:06 ODP. org.apache.tomcat.util.net.NioSelectorPool getSharedSelector INFO: Using a shared selector for servlet write/read II 24, 2014 8:51:06 ODP. org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [ajp-apr-8011] II 24, 2014 8:51:06 ODP. org.apache.catalina.startup.Catalina load INFO: Initialization processed in 2423 ms II 24, 2014 8:51:06 ODP. org.apache.catalina.core.StandardService startInternal INFO: Starting service Catalina II 24, 2014 8:51:06 ODP. org.apache.catalina.core.StandardEngine startInternal INFO: Starting Servlet Engine: Apache Tomcat/7.0.50 II 24, 2014 8:51:06 ODP. org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory C:\tomcat\apache-tomcat-7.0.50 test\webapps\ROOT II 24, 2014 8:51:07 ODP. org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory C:\tomcat\apache-tomcat-7.0.50 test\webapps\ROOTx II 24, 2014 8:51:07 ODP. org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler [http-apr-8082] II 24, 2014 8:51:07 ODP. org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler [http-nio-8445] II 24, 2014 8:51:07 ODP. org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler [ajp-apr-8011] II 24, 2014 8:51:07 ODP. org.apache.catalina.startup.Catalina start INFO: Server startup in 931 ms - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Installing the OWF webapp to an existing Tomcat Instance
I submitted the following request for help on the OWF mailing list but no one is replying. I'm hoping someone here may be able to help? OWF is a webapp I'm trying to install to an existing instance of Tomcat (the OWF webapp bundle ships with an older version of Tomcat). Appendix C of the attached guide provides short, simple steps to install OWF on an existing instance of Tomcat. I followed all the these straight-forward procedures but the webapp fails to start - I get a HTTP Status 404 (requested resource is not available). Also, if I access OWF through Tomcat's Application Manager, the URL address it follows goes to http://localhost:8080/owf/ when it should go to https://localhost:8443/owf/ (if I go to this site directly, the browser title bar just shows the message Waiting for localhost and never does anything. Other details of my setup: -Windows 7 -Tomcat 7.0.42 -MySQL 5.6 (Note that I followed the directions on p. 12-13 to integrate with MySQL). -JDK 1.7.0_51-b13 Sorry to ask this question on this list, but I don't know where else to go. Brian. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Installing the OWF webapp to an existing Tomcat Instance
Unsubscribe Sent from my iPhone On Feb 24, 2014, at 5:18 PM, J. Brian Hall jbrianhall...@me.com wrote: I submitted the following request for help on the OWF mailing list but no one is replying. I’m hoping someone here may be able to help? OWF is a webapp I’m trying to install to an existing instance of Tomcat (the OWF webapp bundle ships with an older version of Tomcat). Appendix C of the attached guide provides short, simple steps to install OWF on an existing instance of Tomcat. I followed all the these straight-forward procedures but the webapp fails to start – I get a HTTP Status 404 (requested resource is not available). Also, if I access OWF through Tomcat’s Application Manager, the URL address it follows goes to http://localhost:8080/owf/ when it should go to https://localhost:8443/owf/ (if I go to this site directly, the browser title bar just shows the message “Waiting for localhost” and never does anything. Other details of my setup: -Windows 7 -Tomcat 7.0.42 -MySQL 5.6 (Note that I followed the directions on p. 12-13 to integrate with MySQL). -JDK 1.7.0_51-b13 Sorry to ask this question on this list, but I don’t know where else to go. Brian. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Installing the OWF webapp to an existing Tomcat Instance
From: J. Brian Hall [mailto:jbrianhall...@me.com] Subject: Installing the OWF webapp to an existing Tomcat Instance if I access OWF through Tomcat's Application Manager, the URL address it follows goes to http://localhost:8080/owf/ when it should go to https://localhost:8443/owf/ That's expected - the manager doesn't know that the specified app is for https use only. However, there could be a problem with your server.xml file in Tomcat's conf directory, so you should post that here with comments removed and sensitive information masked out. Also, look in the various Tomcat log files to see if the application initialized properly. if I go to this site directly, the browser title bar just shows the message Waiting for localhost and never does anything. Could be a certificate problem. Other details of my setup: -Windows 7 -Tomcat 7.0.42 -MySQL 5.6 (Note that I followed the directions on p. 12-13 to integrate with MySQL). -JDK 1.7.0_51-b13 Thanks for that; many people forget. Sorry to ask this question on this list, but I don't know where else to go. This is an appropriate place for such questions. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Installing the OWF webapp to an existing Tomcat Instance
Hey Chuck, thanks (I was worried someone would yell at me for posting this question here). Responses are below ... -Original Message- From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: Monday, February 24, 2014 6:26 PM To: Tomcat Users List Subject: RE: Installing the OWF webapp to an existing Tomcat Instance From: J. Brian Hall [mailto:jbrianhall...@me.com] Subject: Installing the OWF webapp to an existing Tomcat Instance if I access OWF through Tomcat's Application Manager, the URL address it follows goes to http://localhost:8080/owf/ when it should go to https://localhost:8443/owf/ That's expected - the manager doesn't know that the specified app is for https use only. However, there could be a problem with your server.xml file in Tomcat's conf directory, so you should post that here with comments removed and sensitive information masked out. Also, look in the various Tomcat log files to see if the application initialized properly. Thanks. Two comments: 1. The only thing I added to server.xml per the instructions is: Connector port=8443 protocol=HTTP/1.1 SSLEnabled=true maxThreads=150 scheme=https secure=true keystoreFile=certs/keystore.jks keystorePass=changeit clientAuth=want sslProtocol=TLS / 2. Log files. Yes, the webapp fails to initialize. Here's the first few lines: ERROR org.springframework.web.context.ContextLoader - Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'messageSource': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionManager': Cannot resolve reference to bean 'sessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory': Cannot resolve reference to bean 'hibernateProperties' while setting bean property 'hibernateProperties'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hibernateProperties': Cannot resolve reference to bean 'dialectDetector' while setting bean property 'properties' with key [hibernate.dialect]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dialectDetector': Invocation of init method failed; nested exception is org.springframework.jdbc.support.MetaDataAccessException if I go to this site directly, the browser title bar just shows the message Waiting for localhost and never does anything. Could be a certificate problem. Other details of my setup: -Windows 7 -Tomcat 7.0.42 -MySQL 5.6 (Note that I followed the directions on p. 12-13 to integrate with MySQL). -JDK 1.7.0_51-b13 Thanks for that; many people forget. Sorry to ask this question on this list, but I don't know where else to go. This is an appropriate place for such questions. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat upgrades/security patching best practises
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 2/24/14, 4:50 AM, Mark Thomas wrote: On 24/02/2014 09:20, satish jupalli wrote: Hi, What are the best practices for upgrading the tomcat given the fact that they are no direct security patches available. Specially with the environments where there are large instances of Tomcat servers running it is challenging to upgrade these servers manually in all the systems. Are there any best practices defined for doing this given the frequency of security patches being applied on Tomcat (Leave alone JDK patches) Use a separate $CATALINA_HOME and $CATALINA_BASE. +1 I can't tell how much easier it is to manage Tomcat installations (even small ones) with these two separated: Tomcat base install goes one place, your configuration and everything you need goes another. Upgrades are as simply as changing the CATALINA_HOME path, and downgrades (if necessary) are just as simple. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTC+9KAAoJEBzwKT+lPKRYFTMP/igVwM4G36DJAGuFR264VfL6 T4I+N/XKYlKOBdg0yRO8LBhastCCxFoPd7gvzBuMjrgYqaA6Yfvj5CJ9fJJsSWDW qT9wh+//b/DY/VWrIFUrT+yBMLWfkVFV2kOiNqTDwhgH9L8YF4WW7PQJlIgl9nhr duClzSS9ZDNwPbLsyj+xbbUHrF7XjwD02Ofpf7xk/KZp6ihNQNEPavgvMTycKu2W 7BtsfYC+OLBofJi/KFhRAgJd4AtclhHDU42665Fhl7YMyuqcLqvmviY0v190o0m8 jKN/pS2+g2PKdM8Ictq3QVr1PsmjLB5G7MnuroON3210CSVsINTOAjzIW8s3kuWM CKSJML/rNk6Vz56BTC0qCPPFCceYyVWQbBQy7HL3xE5JZpDV1JpGZg0991omhdD6 Dbto3c/+EHGoo9bjceRYmtHMHO6CHBfa/UtrsTtuiooT16kHyQRbRt1MiB2Mbmqv 3wLx+5fk/mcR8rAqrcnlaB944ybJ0vVtgbxy9V9sUP0YXAejYuMxhV7P2K5Wk/N5 EUJiMK7Qf8ecBwPkHkHRIEjKhzujm9bi8AHcIJDESl07nyEfnYKmYbimCey1+etn MHQkzz8eDeJovdx4LMpd0b0Jx8Qv2TCy2mn3K3ZLhnY/bO0yw+JDWKK6xa+ckl4L 5Q7pdKUMthLp/osjtJXz =ds/z -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat/Java Spring MVC 2.0/c3p0 - Consultant needed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Charles, On 2/24/14, 10:15 AM, Charles Richard wrote: Sorry if this is not the right forum for this kind of inquiry. I figure the best candidates would be in this forum from personal experience. Our company is having production issues which I believe are either due to application inefficiencies or a bug somewhere in our software stack. We are having production issues with our Tomcat connection pool using c3p0 and while my knowledge in this area has improved, I lack the Java developer background that might help in this area and we are at a point where we need this solved quickly. I've never gotten the sense that c3p0 was production-ready. What made you deploy with c2p0 instead of either of the two connection pools that ship with Tomcat? (Note that c3p0 has nothing to do with Tomcat, other than that Tomcat can be configured to use c3p0 as its connection-pool). The problems could be related to leaked connections which I'm quite sure we have. I have turned on c3p0 debugging and identified this in the past and the ideal consultant could identify in our code where those are happening and fix them. Both pools Tomcat provides can help you track-down so-called abandoned connections by providing stack traces that point to the line of code that obtained the connection (or even Statement or ResultSet). I would highly recommend that you read this blog post I wrote several years ago that can help you look for obvious errors by providing examples for what JDBC code should look like -- if you are managing your own JDBC calls of course: http://blog.christopherschultz.net/index.php/2009/03/16/properly-handling-pooled-jdbc-connections/ We are looking to hire a consultant that would come to Fredericton, NB, Canada to work with us on this problem. Serious inquiries only. I will be looking for proof that you have extensive experience with Tomcat, Java Spring and c3p0. If you are interested, send me your resume (through your company or individually) and send me as much proof as possible of your experience with the specific technologies mentioned. While there is certainly no prohibition against doing so, this isn't really a help wanted message board. We are happy to help you -- for free! -- via email to solve your own problems. If you find this free forum helpful, please consider staying to be a part of the community. You may help others or learn things yourself. Before you hire anyone, you might want to try the following: 1. Swap c3p0 for something more reliable such as Tomcat's default pool (based upon commons-dbcp) or the newer, higher-performance tomcat-pool. You can find documentation for both of those online in the Users' Guide. If the pool is performing okay, this may not be necessary, but it's nearly free to try so it may be a good first-step. 2. Check your own code for resource-handling errors. Take some time to read my blog post, or have your engineers do it (better yet, have everyone read it). 3. Run a static-analysis tool such as FindBugs (which is free) against your code. It can detect resource leaks you may not have known you had. Running the tool takes almost no setup and/or skill, and you can read the report entirely for free. If you have a million errors, it might take you a lot of staff to identify and fix the problems, but it's likely to point-out some problem areas -- and point you to the exact line numbers where problems are likely to be. You might get a lot of mileage (kilometerage?) out of the above without having to hire anyone. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTDCmHAAoJEBzwKT+lPKRYUTAP/iNhYjUQqaYIXCEn7WrKEpVW PCn4+ZLmzlmm1r7GSVbSc0+632JKA+YSOz+c8LplGnMAmUa6eU7sz2KgrunsnCCm y5UiNySJ3nQEtKcHn0c7TpNmfGUGn61Y0GoK9A+JID8jubxBNMmt4nvH7FBfRrGA GjB93hwIsJ0pK0InmejXmcoBxRYIzaVavV7nW7I/63SURv+TnXmuriHtrC5KBB39 /o5V9VNaDZqsm7zsi3qqEYoxY2/yEMt+W9++bYajXFhhhUevWdRw2NFgihyewRuL xc4GWV+5OIvSlsr0JtKXlJha8ooz1BVPigRd6vRQDaw2DFNzXy0Jl30kGK5ECuwI SmldUzYjZZGEJBhN2RGNsJgDi0zpvOIBmAciUCWZFNy7xzhubx+DTK1AHUYjW15j H1ujwZAkXfSsfY9h+vP9ATntn2YBQ3R3L7pKtjd+d7T5C9ULDIglH4o3+2kK4TEg zV+bUhyLXM/sf9IXMOTUZa9TsF8EovbaT5sRx2gXWqbMKOgyy3lJuzMaOg3110Cd P5tOfypeevWE0NY5+nUXDtmgKz+GHAkaOkdhlvDBjQ0UwNL/yV9WU5ui1pev2KLi Ct7DHj92K//ROM6RerkMjHPCcLPX5c6bbBzXl5R/unfprkPoRZ0RwgxQK/2ARAst ZDSf1VD+AUL82qVQy1rf =VgOW -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: [OT] linux vs windows responses on the list
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Leo, On 2/24/14, 10:59 AM, Leo Donahue wrote: In general, is it assumed that all responses given to the list assume the OP is running a version of Linux, if they don't state the OS? In general, when I read a post where the OP does not state the OS, I just assume it's a Windows user[1] because in my experience they don't realize that there are other operating systems in the world[2]. For example, I read the post about Tomcat upgrades/security patching best practices and the advice given is to modify init.d script. I don't recall seeing the OP indicate they run Linux and the list usually gently bashes people for not being specific about their environment. I think the tide these days in the Linux world is moving away from init.d, anyway. systemd is the future, apparently. Just can't let a working system keep on working. Since I run Tomcat on Windows, I don't know what the init.d script is, but reading that response I get the feeling the that Tomcat on Linux is alot easier to manage than Tomcat on Windows, especially if you are running Tomcat as a Windows service. I find init.d scripts are a lot easier to understand: you can actually read the code that gets executed instead of reading property sheets and guessing what they do under the covers. I would have thought that another option to that post would be to use the appBase attribute of a Host element and just move your webapps out of the traditional location located within the Tomcat installation directory. But I guess I didn't understand the OP. It's possible your solution would have been better. Sometimes simpler answers are better. Is it time for us to go to Linux? As much as it pains me to say so, the answer is probably no, you should stick to Windows. Why? Well, if you've been administrating on Windows for a while, then you are used to all its quirks, etc. and switching would introduce risk into a situation that is currently less risky than that. Remember that risk is bad when it can be avoided. If you had never deployed anything on anything, I would generally recommend learning at least /some/ kind of *NIX and using that. Linux tends to be quite accessible to newcomers, so it's a pretty decent starting point. Every *NIX fan has their favorites but they all come from a similar lineage and philosophy and is decidedly different from Microsoft Windows. If you're looking for something new -- sure, try Linux. But do it in a lab where you can figure everything out without having the pressure of going into production and then having to figure out why none of your stuff works and its because of something stupid that you just had no clue about because in Windows there is no analog or it Just Works there. I think *NIX admins get paid more, so if you learn it, you can probably ask for a raise ;) - -chris [1] Unless they provide path names, which is usually a dead giveaway. [2] Otherwise, they would have used one of them. -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTDCuVAAoJEBzwKT+lPKRY/7IP/3hFZcthD53TWjCuCmkO1HYS NFwf9uiIR5L5zRyCqwWuZts7vFTOXu2hJPABcNt8L7gAy58en5Ycnw/ZxFGMv9GU 9giQkmvr/Gsqbedb9YqDQ5v6qZsVDGsuQIy1kEg+XKzOQMBmY0KSeCioYyGBxBkq /05KW0RZ3H5fvXSolrHXSv+sHma+VQiSB/tF6ZTskuQ/HJXn51g6rlHmftDZ9Ooo LIoGVZAIKg3ISk+uMAuj4X2zwjl85yxKbUCpZvqiUdGn7LIQMe687Qm7TU4HX0AY 3js+hfvj7YelhavdTN3JcXRka4M5Lx5yPCi06Tfvncvt227oAgn8zmpg3NTL9MtF wJFtvFmmlAdAGp8BccgXMRiAgdgytXcv5+o/wAfkfdouSd+GM+3L9u1SRFsGE2M2 KTVC7zgAOuPLC/+hFTE6JJ6wTQDFqzpURJdL2Sk22ithQUe3VCA9pmd6PIVd2ozh X6UDH2QRvuh2MWhVINiGp4UbpYksjJaL+FL0aBGFDVHflbvW+EncOUxa/D4KIG5a 69qufnJnRn4iPZTjlaeIcRDYGohRle/Xy7elTx0IG+MsklnFYHR7VuzkTjvsrcWm f4y6jnVeGdd6msIJ900G3TB+kzxfsDb5j7SlrkcLLfYaJsyOXEOmQfbQWz5HbmT3 Xo87PSJ1vxKB2RAiMBEp =FDgX -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: linux vs windows responses on the list
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 James, On 2/24/14, 11:43 AM, James H. H. Lampert wrote: On 2/24/14 8:33 AM, Mark Thomas wrote: . . . I've worked with Tomcat on Windows, Linux, Solaris, FreeBSD, HP-UX and some more unusual hardware like plug-computers. By far the biggest issue the first time I hit a new OS is figuring out how to do stuff in that OS. . . . And I have a fair amount of experience, FWIW, running it on OS/400. ... which I think we can all agree is worth avoiding ;) - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTDCwaAAoJEBzwKT+lPKRYWeAQAKIQXiknTmg1BOtubt0l+6nS zA6xsVxxKxijbEvHU3Z40dA4kphXIjnY4potdtRfnKtr2sEfJcRd3XxVW/YT6n83 qB5nXDhodqqOIAPVmfWJztffi2AHOIZ+D9qqYQ3Vfe3DlaAkGwGlex5DkoCLsHP7 rGdJBwpsPy1aIEN/DyKl0mIzx4uJCC98F3aOX71u/5p8Bpjtm9Pxsq7uDyhBwANB OtU6mrNsVH6G660n6jq39tFGNaZB0EYbgzI/fC32dcoVWhJ/x5ej+JZp0/wQ2scX UkfVcFDVdsUOpYDgGR8/lIAva25gDqTDCEta+HopM23JelUsFJq+xsNPRpD7fsRQ CfYpmPVTNC/V3GnARg5Yaz4ZLGwprm2EsYQ+3ZMOtXbq/aR09zgU5bcmChbh4FSh sRYkno7nzFwqvPNdVM4vuEcDEqwqRM+4GOTM0soab7GEm3I+ACQ2Rl36r1bHs90n 8f6KAuIAF50Ke7m3LoUsQETxUCxSnQ8J4WQEveOX4DQRR+SoAtdADRuwhpnuYTNR xELIa/otfbxolxgOVr32J1YaNA/mNXTvLCI7RDxBwBTzWsal8yNoPc84MRl/UcNJ 4m93oxWH++HVFjJZgCjMJyL5Gk6USAHQN06BwcsDuudesQynJnOVICreqfn5MOi8 yK5Wy2tmgLO12N37FC3u =nR9J -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7.0.37 issue on our Sun Sparc
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jay, On 2/24/14, 1:42 PM, Jay wrote: Hi Mark, Thank you for a quick response. It looks the Tomcat 7.0.37 is ok with Solaris 10 on other Sun Sparc machine ... could it be hardware related? Do you have any suggestion for us to capture that possible Shutdown command and/or possible SIGTERM? Was there any output in any other log files under CATALINA_BASE/logs? Hardware problems usually end with a disastrous JVM crash: you'll get a Java dump with both Java and native dumps, etc. On Solaris, I usually see BUS ERROR or something else similarly awful-sounding but more mundane in reality. If you have a choice, you might want to upgrade both Java and Tomcat: both versions you mentioned are quite old. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTDCzXAAoJEBzwKT+lPKRY89QP/0KLvuVZgbI6TTixqsr7jrMI FM5yS+cx5WoS1XBwxP8l5bxtFmAFnaB+DMW6XRUyap2Yl8s+5kFkRiDUcy+ET3jh B6TZ7L4oCz4vGdhnRtxJv010gi2CIQFiRfOZiAVy9V2XIL+jhtFxVJT72ZX7eHgl iFfXobcAoYeEQlI/BZRTazfzIR0g/l3w/ORbyxGcFc+OYYLxj1M9EDX0Dk1bmzRy IU2WSc7VqC9uOnt5wPFQvoAGdG43I18Cb2PlbG3nDzm82WqI2l0A5225wObhl5ub LhMbTWL0FgHv84lMQXgDGT9UbWQ5U56V6rl5A++mR0qZHCQC1AdyiJzVWoyo5Fqq ZrTJWdhCXA1tvJ/pNUUmNKyHnhIPNOecHoFEFuZ9obLHfalEbyoj/A8hg/i67evD yWz/kEu9CnpY4Ex+1Ky9M48ZG/Lk/C5pGY+8SH+sr8lyUyu+qjnlT9cR06KdL4f+ CHcGTQ+kSOEp6ld0kJoJJCIttcZR3C1MCT6Twhipdb5p9CgX41LIPlBqBi30ItJn d/S7Rr8lkv3LSY2JHYhbntdft2U66sARYHC2lyrUT0Up/cWlKDhr7gCS3EaLCpqt v1lWT1jiYuTR6QGJR0K2Dc3SwsijULI8dmNlnP8cF+/Yq8B8bvlPze/ZtYnZoJ8D aziO9WdHSunTob0UjFcB =Lebz -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Troubles to configure SSL
Hi. What happen's if you open in browser 8445? Does Tomcat really open port 8445? Try find it with: netstat -b -n | findstr 80 From your log - I don't see any problems. And here is Connector config from my server (under Linux - but there is must be difference): Connector port=8444 maxHttpHeaderSize=8192 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false disableUploadTimeout=true acceptCount=100 scheme=https secure=true clientAuth=false sslProtocol=TLS / As you see - there is no protocol= and SSLEnabled=true. Instead of last options - scheme=https secure=true used. But - we use 5.5 Tomcat. 24.02.2014 22:09, Petr Nemecek пишет: Hello, I have troubles configuring SSL, even if I follow https://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html. See my connectors as well as startup output below. After the startup I could navigate to http://localhost:8082/, but https://localhost:8445/ doesn't work. Any idea? Many thanks, Petr P.S. [Tomcat 7.0.50, Windows Server 2012 R2] *** server.xml connectors *** Connector port=8082 protocol=HTTP/1.1 connectionTimeout=2 redirectPort=8445 URIEncoding=UTF-8 / Connector port=8445 protocol=org.apache.coyote.http11.Http11NioProtocol SSLEnabled=true maxThreads=150 scheme=https secure=true clientAuth=false sslProtocol=TLS URIEncoding=UTF-8 keystoreFile=c:\@data\keystore\.keystore keystorePass=abcdef / Connector port=8011 protocol=AJP/1.3 redirectPort=8445 / *** startup output * II 24, 2014 8:51:04 ODP. org.apache.catalina.core.AprLifecycleListener init INFO: Loaded APR based Apache Tomcat Native library 1.1.29 using APR version 1.4.8. II 24, 2014 8:51:04 ODP. org.apache.catalina.core.AprLifecycleListener init INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true]. II 24, 2014 8:51:05 ODP. org.apache.catalina.core.AprLifecycleListener initializeSSL INFO: OpenSSL successfully initialized (OpenSSL 1.0.1e 11 Feb 2013) II 24, 2014 8:51:05 ODP. org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [http-apr-8082] II 24, 2014 8:51:05 ODP. org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [http-nio-8445] II 24, 2014 8:51:06 ODP. org.apache.tomcat.util.net.NioSelectorPool getSharedSelector INFO: Using a shared selector for servlet write/read II 24, 2014 8:51:06 ODP. org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [ajp-apr-8011] II 24, 2014 8:51:06 ODP. org.apache.catalina.startup.Catalina load INFO: Initialization processed in 2423 ms II 24, 2014 8:51:06 ODP. org.apache.catalina.core.StandardService startInternal INFO: Starting service Catalina II 24, 2014 8:51:06 ODP. org.apache.catalina.core.StandardEngine startInternal INFO: Starting Servlet Engine: Apache Tomcat/7.0.50 II 24, 2014 8:51:06 ODP. org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory C:\tomcat\apache-tomcat-7.0.50 test\webapps\ROOT II 24, 2014 8:51:07 ODP. org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory C:\tomcat\apache-tomcat-7.0.50 test\webapps\ROOTx II 24, 2014 8:51:07 ODP. org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler [http-apr-8082] II 24, 2014 8:51:07 ODP. org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler [http-nio-8445] II 24, 2014 8:51:07 ODP. org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler [ajp-apr-8011] II 24, 2014 8:51:07 ODP. org.apache.catalina.startup.Catalina start INFO: Server startup in 931 ms - 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: Troubles to configure SSL
From: Arseny [mailto:setev...@gmail.com] Subject: Re: Troubles to configure SSL But - we use 5.5 Tomcat. Then you really should not be giving people advice about how to configure supported Tomcat versions - a lot has changed. Moving up to a current version should be a priority for you. - 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: Troubles to configure SSL
25.02.2014 7:54, Caldarale, Charles R пишет: From: Arseny [mailto:setev...@gmail.com] Subject: Re: Troubles to configure SSL But - we use 5.5 Tomcat. Then you really should not be giving people advice about how to configure supported Tomcat versions - a lot has changed. Moving up to a current version should be a priority for you. - Chuck offtopic It is not my solution use old version and unfortunatelly - I can't change it. But yes - my config here can be wrong, thanks. /offtopic - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat 6 refuses mod_jk connections after server runs for a couple of days
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Isaac, On 2/24/14, 2:27 PM, Isaac Gonzalez wrote: Hello all, I'm running tomcat 6.0.32 on Cent OS 6 with 2 front end apache load balancers with a firewall in between the tomcat and load balancers using mod_jk v. 1.2.37 under apache 2.2.10 to connect the backend tomcat. I have had this running ok for a few years but our user traffic has increased significantly. A few months ago, the tomcat server seemed to refuse or not accept any new connections from either load balancer and required a restart on the tomcat end, even though I could easily connect to tomcat on port 8080(manager). I can intermittently telnet to port 8009, but am denied a bit as well both inside and outside the firewall. I proceeded to split the tomcats up into their own instances, hoping when this issue recurred that it would only affect a particular tomcat app. It also gave our developers the ability to patch a single tomcat app without downing all of our apps. Unfortunately, this issue has recurred several times and I have spent most of my days researching and digging for hope of someone with a similar experience that may have resolved it. Last Friday the problem was so bad, I had to completely restart the tomcat server(reboot it). So far I am at a loss...I have installed psi-probe on all tomcat instances to give me more in depth analysis to tomcat threads and related server metadata when the problem is occuring. I have made a few modifications to workers.properties, in particular to decrease the connection timeout as well as the tomcat ajp connector from 10 minutes to 5 minutes and added the ping timeout and socket timeout. I also increased my apache prefork MPM client connections to 500 on each load balancer. Below is my relevant configs...any suggestions to help remedy this would help... I have also increased threads from 200 to 500 on all tomcat instances. I'd be interested to see a thread dump on a stuck Tomcat to see what it's doing. If it happens again, please take a thread dump (or, better yet, 3 or so maybe 5-10 seconds apart) and post them back to the list. http://wiki.apache.org/tomcat/HowTo#How_do_I_obtain_a_thread_dump_of_my_running_webapp_.3F Does restarting the Tomcat instance fix everything, or do you have to also bounce httpd? What happens if you bounce only httpd? After the split, did both Tomcats appear to lock-up simultaneously, or did only one of them have a problem and the other one stayed up? Do the lock-ups appear to be related to anything you can observe, such as particularly high-load, etc.? Workers.properties: worker.list=jkstatus,server1,server2,server3,server4,server5,server6,server7,server8 worker.jkstatus.type=status # Let's define some defaults worker.basic.port=8009 worker.basic.type=ajp13 worker.basic.socket_keepalive=True worker.basic.connection_pool_timeout=300 worker.basic.ping_timeout=1000 worker.basic.ping_mode=A worker.basic.socket_timeout=10 worker.lb1.distance=0 worker.lb1.reference=worker.basic worker.server1.host= server1hostname worker.server1.reference=worker.lb1 worker.server2.host=server2hostname worker.server2.reference=worker.lb1 worker.server3.host=server3hostname worker.server3.reference=worker.lb1 worker.server4.host= server4hostname worker.server4.reference=worker.lb1 worker.server5.host= server5hostname worker.server5.reference=worker.lb1 worker.server6.host= server6hostname worker.server6.reference=worker.lb1 worker.server7.host= server7hostname worker.server7.reference=worker.lb1 worker.server8.host= server7hostname worker.server8.reference=worker.lb1 You didn't show any JkMounts in your httpd.conf file. What worker are you using? It sounded like you were load-balancing the servers, but your lb1 worker does not have any balance_workers setting so it doesn't look like it's going to work. httpd.conf: KeepAlive Off MaxKeepAliveRequests 100 KeepAliveTimeout 15 # prefork MPM # StartServers: number of server processes to start # MinSpareServers: minimum number of server processes which are kept spare # MaxSpareServers: maximum number of server processes which are kept spare # ServerLimit: maximum value for MaxClients for the lifetime of the server # MaxClients: maximum number of server processes allowed to start # MaxRequestsPerChild: maximum number of requests a server process serves IfModule prefork.c StartServers 8 MinSpareServers5 MaxSpareServers 20 ServerLimit 500 MaxClients 500 MaxRequestsPerChild 5000 /IfModule It would be good to see your Jk* setting as well. Tomcat server.xml: !-- Define an AJP 1.3 Connector on port 8009 -- Connector port=8009 address=x.x.x.x protocol=AJP/1.3 redirectPort=8443 connectionTimeout=30 maxThreads=500 / Why do you both having a connectionTimeout on an AJP connection? httpd should only send a request to you once the request line has been received by the client, so
Re: Installing the OWF webapp to an existing Tomcat Instance
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Brian, On 2/24/14, 6:46 PM, J. Brian Hall wrote: Hey Chuck, thanks (I was worried someone would yell at me for posting this question here). Responses are below ... -Original Message- From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] Sent: Monday, February 24, 2014 6:26 PM To: Tomcat Users List Subject: RE: Installing the OWF webapp to an existing Tomcat Instance From: J. Brian Hall [mailto:jbrianhall...@me.com] Subject: Installing the OWF webapp to an existing Tomcat Instance if I access OWF through Tomcat's Application Manager, the URL address it follows goes to http://localhost:8080/owf/ when it should go to https://localhost:8443/owf/ That's expected - the manager doesn't know that the specified app is for https use only. However, there could be a problem with your server.xml file in Tomcat's conf directory, so you should post that here with comments removed and sensitive information masked out. Also, look in the various Tomcat log files to see if the application initialized properly. Thanks. Two comments: 1. The only thing I added to server.xml per the instructions is: Connector port=8443 protocol=HTTP/1.1 SSLEnabled=true maxThreads=150 scheme=https secure=true keystoreFile=certs/keystore.jks keystorePass=changeit clientAuth=want sslProtocol=TLS / Sanity check: you do have a certs/keystore.jks file and the password is in fact changeIt, right? It would be best to fully-qualify the path of the keystore file. 2. Log files. Yes, the webapp fails to initialize. Here's the first few lines: ERROR org.springframework.web.context.ContextLoader - Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'messageSource': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionManager': Cannot resolve reference to bean 'sessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory': Cannot resolve reference to bean 'hibernateProperties' while setting bean property 'hibernateProperties'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hibernateProperties': Cannot resolve reference to bean 'dialectDetector' while setting bean property 'properties' with key [hibernate.dialect]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dialectDetector': Invocation of init method failed; nested exception is org.springframework.jdbc.support.MetaDataAccessException Failure to deploy ought to either cause Tomcat to immediately stop after trying to start or continue running and issue 404 responses for requests to /owf/ -- depending upon the severity of the error. Is there anything suspicious in logs/catalina.out (or any other log file in logs/ for that matter)? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTDDGAAAoJEBzwKT+lPKRYdVMP/i15PUUWaSFbZSvw9aT/sB0u ih0jGQAVseeg0M+DF9cGpLLFS2Eg5nBZH45ohefUdw1W2KmgWplJArzHn3bVnV/1 4b/qs2Tba+NKJSxG1Pd8k6RJ3zpi9hGkocIGxR31XYpVKlbK17z5nVp55jx0oxwh D5BqBwYT9SHzi24dCIMNdVA9GHp5jRxTh3raE4M3sYdLV8IfCtTInGq455CxDgMa bNnhpmQ12t2WJqZGIAu/6yZMqwovYyqKFBR7gUzJegfBwfbmLdElRmxfiGU2xZ/P u5lEwxcQxW2jCXjunc5jsQYX2i97/psA0khaiQaEG3r4HyfFSx5iqPXClKL8n5dB eui6HeCHq9zqBjfQxFexEm1Q2MTHqW4G+ta4Qh3hqbI7uXpD/XNAj4zfV1xOhksc aJukhdZkpmWfpfPsjmDZS6Icjz/L+IZGMmHhCQ7gP0bL+0PGMHQysZ6KV8ig4cs1 uplpanBhHVUCEcjw0Ja1xZNgn9epvKMIoJyJUwfsS8IOpfuBH9ZSGEZ9SuEOfAG3 c0+OJr6o9DQixKr17xXKWksgROqFvHyhND37B/2bo9xKlU8T3N4gDWwpBG+S3meg rRAgz6xixWAgDsX14KJCA5uk13sJQGVRbgCk640ZiAx3Wzeik8D5LNbXdILHwf85 rlc1cELEym7QBhAVy6c+ =AnAD -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Troubles to configure SSL
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Petr, On 2/24/14, 3:09 PM, Petr Nemecek wrote: Connector port=8445 protocol=org.apache.coyote.http11.Http11NioProtocol SSLEnabled=true maxThreads=150 scheme=https secure=true clientAuth=false sslProtocol=TLS URIEncoding=UTF-8 keystoreFile=c:\@data\keystore\.keystore Umm... something looks off there. Does @ mean something special to win32, or is that just a funny-lookin' path name? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTDDLHAAoJEBzwKT+lPKRYbGgP/0/PUZdE4Yxr84ok8pmTjiD5 WqTahTp7wjmaUcOwTq7nBo0AQUJNm7hxzX+EP8yUSRtUrbBFIe6Q3wbgR69zymfz aJslPBcIZ7glOS29UnfhbRMaBFDBKPbYjX6NF2jKsrc4LHL45X1A/HpeVLaGi4t0 Kec7mIEg5BalCzQ35sxT6JMwXhmWb9uoU5Zp1pzVev+t+OosNJJLrqhDIyDz259u rdSjETN4Pz0vddUnBwO44N7nEiHditZcPAoGYDqkRbBAWWMKNW+gUYzmjaOqo0SR VxszDk9oThdU3lgf89IEhr8NYT1Z8dIRtkWL2nvQkM/HxPd/sB0ArE4J733B5x7O 3rSpdn5jMwzjTnC4ZxdstgbzBRcCJdaSQ4AqaCKY0SDdpswb1vdpFztjPWKLK6bj q7W7eYR2N9lqgO7HFimRGeGBz3tTo89fd8na9yixhKT4Lj3jRI2BQHD+L1s/Z1Hb VI/j9VO4z3rJok4o+91pzN88FyKqe/4k0Wbg6+iwmrPZMBvmoa0VV7fbsGQqXuXk YciARFauRoMeyrRZTgjCiZgv2vk8JXUKgZ5o/IMJ0OpMkBt1gmc2Ny2+kazewj25 n/tYeix0zDD97//9eLOM4B2HQ026bVrk/VgSBY1saq8I9MHYETeTXWMQcpj6NPAv PaH56RYblc76k3QOF5a6 =qAtF -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Troubles to configure SSL
From: Petr Nemecek [mailto:p...@cmail.cz] Subject: Troubles to configure SSL After the startup I could navigate to http://localhost:8082/, but https://localhost:8445/ doesn't work. What does doesn't work mean? Did the building catch fire? Is the Windows firewall configured to allow traffic through port 8445? Have you examined all of the Tomcat logs for any issues? P.S. [Tomcat 7.0.50, Windows Server 2012 R2] Good to know; thanks. Connector port=8445 protocol=org.apache.coyote.http11.Http11NioProtocol SSLEnabled=true maxThreads=150 scheme=https secure=true clientAuth=false sslProtocol=TLS URIEncoding=UTF-8 keystoreFile=c:\@data\keystore\.keystore keystorePass=abcdef / The @ symbol in the keystoreFile path is a bit strange; are you sure that's correct? II 24, 2014 8:51:04 ODP. org.apache.catalina.core.AprLifecycleListener init INFO: Loaded APR based Apache Tomcat Native library 1.1.29 using APR version 1.4.8. II 24, 2014 8:51:04 ODP. org.apache.catalina.core.AprLifecycleListener init INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true]. Since you have APR installed, you could use that for SSL traffic - it's more efficient than pure Java encryption, but it does require a different certificate file format. There's not much point in running APR for your non-SSL Connector. Look here for the configuration differences: http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#SSL_Support - 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
Newbie Help - Up and Running with Tomcat on Windows
Hello all, I have had a difficult time getting Tomcat to start. I first tried installing it with xampp. I had a hunch that the problem was that there might be a port conflict, so I tried a different ports but still it would not start from the xampp control panel. BTW, this is trying to run on Windows 8.1. I also downloaded the full version of Netbeans which includes Tomcat and and Glassfish server bundled with the download. I am fairly certain that I told it to install Tomcat during the installation. I thought that maybe GlassFish server is interfering with Tomcat, but I only got that server when I installed Netbeans and I had trouble getting Tomcat to start even before installing Netbeans which integrated GlassFish server. It might be something as obvious as not having Java EE installed separately. Perhaps Tomee+ will provide all that is needed. Thanks in advance for any feedback, and help, Bruce - 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: Installing the OWF webapp to an existing Tomcat Instance
On 25.02.2014 00:46, J. Brian Hall wrote: ERROR org.springframework.web.context.ContextLoader - Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'messageSource': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionManager': Cannot resolve reference to bean 'sessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory': Cannot resolve reference to bean 'hibernateProperties' while setting bean property 'hibernateProperties'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hibernateProperties': Cannot resolve reference to bean 'dialectDetector' while setting bean property 'properties' with key [hibernate.dialect]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dialectDetector': Invocation of init method failed; nested exception is org.springframework.jdbc.support.MetaDataAccessException Is it the complete error message? Is there anything more in the logs? Those error messages are related to JDBC problems. Is your DB up and running with all tables created and with correct permissions? You said, that install guide is for older version of Tomcat. Several versions of Tomcat back, there were changes in way one configures datasource resources. Maybe your install guide refers to the old way? -- Mikolaj Rydzewski m...@ceti.pl - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
