On 22/01/2014 00:38, Melanie Langlois wrote:
> Hi,
>
> Do you have an ETA for a stable release of Tomcat version 8?
No. It depends on the feedback we get from the 8.0.x releases.
We have had a number of RCs and the next release will be 8.0.0. I'd
expect that to be beta. How many further releases
We are trying to use FarmWarDeployer at the moment, however it fails
ocassionally on the "slave" nodes with the following log message:
Jan 22, 2014 11:00:23 AM org.apache.catalina.ha.deploy.FarmWarDeployer
messageReceived
SEVERE: Application [/xxx] is being serviced. Touch war file [xxx.war] aga
this is because tomcat expects that the 2 jars servlet-api.jar and
jsp-api.jar are in the same classloader
because org.apache.tomcat.util.descriptor.DigesterFactory has this method:
private static String idFor(String url) {
URL id = ServletContext.class.getResource("resources/" + url);
On 22/01/2014 11:56, Johan Compagner wrote:
> this is because tomcat expects that the 2 jars servlet-api.jar and
> jsp-api.jar are in the same classloader
https://issues.apache.org/bugzilla/show_bug.cgi?id=56016
http://svn.us.apache.org/repos/asf/tomcat/tc7.0.x/trunk/webapps/docs/changelog.xml
Ma
On 22/01/2014 10:24, Michael Gloegl wrote:
> Can somebody shed any light here on what the "serviced" status means and how
> we can avoid this FarmWarDeployer Failure?
It usually means that the manager application or the auto deployment
code is doing something (starting, stopping, deploying, unde
I opened a Bug at https://issues.apache.org/bugzilla/show_bug.cgi?id=56051
I will give disabling automatic deployment a try and comment on the bug if that
changes things.
We are experimenting as well with just skipping the whole
Cluster/FarmWarDeployer thing completely and just deploying throug
Hi Jeffrey,
> -Original Message-
> From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com]
> Sent: Tuesday, January 21, 2014 10:19 PM
> Eureka, I finally figured it out!
> It was a real eureka moment, some remembrance burned its way up from
> my subconscious and I had the answer.
> Read
I've recently upgraded some of our tomcats from 7.0.47 to 7.0.50.
After upgrading I got lots of the below errors recorded in catalina.out
The errors are not logged if I disable tldValidation (either by settings
tldValidation=false in context.xml or removing the CATALINA_OPTS property:
org.apache.
thx :)
On 22 January 2014 13:02, Mark Thomas wrote:
> On 22/01/2014 11:56, Johan Compagner wrote:
> > this is because tomcat expects that the 2 jars servlet-api.jar and
> > jsp-api.jar are in the same classloader
>
> https://issues.apache.org/bugzilla/show_bug.cgi?id=56016
>
> http://svn.us.apa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jeffrey,
On 1/21/14, 4:18 PM, Jeffrey Janner wrote:
>
>
> Eureka, I finally figured it out! It was a real eureka moment, some
> remembrance burned its way up from my subconscious and I had the
> answer. Ready guys? Really surprised no one mention
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Konstantin,
On 1/22/14, 9:03 AM, Konstantin Preißer wrote:
> Hi Jeffrey,
>
>> -Original Message- From: Jeffrey Janner
>> [mailto:jeffrey.jan...@polydyne.com] Sent: Tuesday, January 21,
>> 2014 10:19 PM
>
>> Eureka, I finally figured it out
On 22/01/2014 14:12, Paul Beckett wrote:
> Does anyone know:
- Why this occurs only since 7.0.50
Changes to XML validation introduced in 7.0.48->7.0.50
- Where the root issue is likely to be / how to fix it
Psi probe ships with an implementation of the standard tag library that
includes the follow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Paul,
On 1/22/14, 9:12 AM, Paul Beckett wrote:
> I've recently upgraded some of our tomcats from 7.0.47 to 7.0.50.
> After upgrading I got lots of the below errors recorded in
> catalina.out The errors are not logged if I disable tldValidation
> (e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Paul,
On 1/22/14, 10:20 AM, Christopher Schultz wrote:
> Paul,
>
> On 1/22/14, 9:12 AM, Paul Beckett wrote:
>> I've recently upgraded some of our tomcats from 7.0.47 to 7.0.50.
>> After upgrading I got lots of the below errors recorded in
>> cata
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 1/22/14, 10:15 AM, Mark Thomas wrote:
> On 22/01/2014 14:12, Paul Beckett wrote:
>> Does anyone know:
> - Why this occurs only since 7.0.50 Changes to XML validation
> introduced in 7.0.48->7.0.50
>
> - Where the root issue is likely to be
> -Original Message-
> From: Konstantin Preißer [mailto:kpreis...@apache.org]
> Sent: Wednesday, January 22, 2014 8:03 AM
> To: 'Tomcat Users List'
> Subject: [OT] RE: Cannot connect from outside using Tomcat 7/APR/SSL on
> AWS Windows system
>
> Hi Jeffrey,
>
> > -Original Message---
> -Original Message-
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Wednesday, January 22, 2014 9:15 AM
> To: Tomcat Users List
> Subject: Re: [OT] RE: Cannot connect from outside using Tomcat
> 7/APR/SSL on AWS Windows system
>
> -BEGIN PGP SIGNED MESSAGE---
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Konstantin,
On 1/22/14, 9:03 AM, Konstantin Preißer wrote:
Hi Jeffrey,
-Original Message- From: Jeffrey Janner
[mailto:jeffrey.jan...@polydyne.com] Sent: Tuesday, January 21,
2014 10:19 PM
Eureka, I finally fi
Hi,
I'd like to create a XA datasource within Tomcat 6 but i don't find any
example to do so. Tomcat6 provides its own dbcp package but when i compare
it to the standard dbcp package i notice that class related to XA Driver
are missing. The following classes :
org/apache/commons/dbcp/managed/Data
On 22/01/2014 17:04, Sylvain Goulmy wrote:
> Hi,
>
> I'd like to create a XA datasource within Tomcat 6 but i don't find any
> example to do so. Tomcat6 provides its own dbcp package but when i compare
> it to the standard dbcp package i notice that class related to XA Driver
> are missing. The fo
Thanks for the example Valery. Even with your approach, I'm finding that
unless I create a directory "webapps" in the directory from which I run the
program, I get this exception:
java.io.IOException: Application base [{1}] for host [/tmp/./webapps] does
not exist or is not a directory.
It seems
I've set up at least half a dozen AS/400 installations of Tomcat, with
SSL on 443, and once I got the hang of it, they went smoothly, and ran
flawlessly.
So now, I'm asked to do it on a WinDoze Server 2008 box, and it's not
working. Netsat -na shows 443 listening when Tomcat is active, and not
> From: James H. H. Lampert [mailto:jam...@touchtonecorp.com]
> Subject: Weird issue setting up SSL on a WinDoze box
> Caused by: java.lang.Exception: Connector attribute SSLCertificateFile
> must be defined when using SSL with APR
> The relevant connector tag in server.xml is, on this installa
On 1/22/14 5:26 PM, Caldarale, Charles R wrote:
You have installed and enabled the APR connector, but are trying to use the
Java keystore.
Actually, *I* didn't do the installation (the fellow at the next desk
over did), and so I have no idea what options were selected.
AS/400 installations
delete the file tcnative-1.dll and tomcat reverts to java based ssl and
keystores.
On Wednesday, January 22, 2014, James H. H. Lampert <
jam...@touchtonecorp.com> wrote:
> On 1/22/14 5:26 PM, Caldarale, Charles R wrote:
>
>> You have installed and enabled the APR connector, but are trying to use
25 matches
Mail list logo
