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
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
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
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
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
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
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
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
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
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
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:
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
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
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:
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,
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-
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
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,
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
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
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
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
-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
-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
-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
-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
-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
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
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.
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
-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
-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
-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
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
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
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
36 matches
Mail list logo
