Marcel Stör wrote:
On 08.03.2012 15:39, André Warnier wrote:
Additional notes in the text below.
Marcel Stör wrote:
First, thank you so much for the thorough response.
On 08.03.2012 14:47, André Warnier wrote:
Marcel Stör wrote:
Requirement:
a) /myapp authenticated against AD for all users
Hello,
This is in regard to the security vulnerability "Tomcat WAR Deployment
Directory Traversal Flaw May Cause Files to Be Deleted" as detailed
in http://securitytracker.com/id/1023504
Per the above, versions 5.5.0-5.5.28, 6.0.0-6.0.20 and possibly earlier
versions were affected.
Question
On 08.03.2012 15:39, André Warnier wrote:
Additional notes in the text below.
Marcel Stör wrote:
First, thank you so much for the thorough response.
On 08.03.2012 14:47, André Warnier wrote:
Marcel Stör wrote:
Requirement:
a) /myapp authenticated against AD for all users with Windows
authent
Hi
I am not going to venture down this path, I just added it in because I was
trying to compile the new version which is slightly different in the build
process. I had hoped to prove my build process was working..
My aim is to get the new version compiled.
But thanks for the help with this one
On 08/03/2012 20:10, David Wahler wrote:
> On Thu, Mar 8, 2012 at 1:59 PM, Mark Thomas wrote:
>> There is no way you compiled an application that uses
>> javax.annotation.Resource against the Servlet 2.4 / Java EE 1.4 API. If
>> you try that you'll get an error.
>
> As I said, javax.annotation.Re
On Thu, Mar 8, 2012 at 1:59 PM, Mark Thomas wrote:
> There is no way you compiled an application that uses
> javax.annotation.Resource against the Servlet 2.4 / Java EE 1.4 API. If
> you try that you'll get an error.
As I said, javax.annotation.Resource is included with J2SE 6 (as
specified in JS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
On 3/8/12 2:33 PM, David Wahler wrote:
> On Thu, Mar 8, 2012 at 12:58 PM, Caldarale, Charles R
> wrote:
>>> From: David Wahler [mailto:dwah...@indeed.com] Subject: Tomcat
>>> 5.5 JDK version compatibility
>>
>>> Does this mean that if a web
On 08/03/2012 19:33, David Wahler wrote:
> On Thu, Mar 8, 2012 at 12:58 PM, Caldarale, Charles R
> wrote:
>>> From: David Wahler [mailto:dwah...@indeed.com]
>>> Subject: Tomcat 5.5 JDK version compatibility
>>
>>> Does this mean that if a web application is deployed in Tomcat 5.5,
>>> it may not u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Debbie,
On 3/8/12 2:46 PM, Debbie Shapiro wrote:
> I recently upgraded my Tomcat to version 7.0.26. I'm using a third
> party application within Tomcat (InetSoft). All I do is place their
> web application folder within the Tomcat webapps directory.
2012/3/8 David Wahler :
> Hi all, I have a question about a comment on this bug report:
>
> https://issues.apache.org/bugzilla/show_bug.cgi?id=52545
>
> Mark Thomas noted that:
>
> "The application can not be compiled using a 1.4 JDK (the minimum Java version
> required by Servlet 2.4) since it use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Amit,
On 3/8/12 11:55 AM, Amit wrote:
> Enabling debug level would add some extra handling
>
> 1. We use slf4j & logback as our logging framework & tomcat uses
> jul logging. We would have to add jul-to-slf4j.jar to direct the
> jul messages to logba
I recently upgraded my Tomcat to version 7.0.26. I'm using a third party
application within Tomcat (InetSoft). All I do is place their web application
folder within the Tomcat webapps directory. Most recently, I had 7.0.23
installed and it would start up as expected. I have a process each night
Thanks guys. I will file a new bug with the details you provided about it
exposing too many get methods.
--
View this message in context:
http://tomcat.10.n6.nabble.com/What-is-the-best-way-to-view-Tomcat-JDBC-pool-properties-in-Tomcat-7-tp4557182p4559731.html
Sent from the Tomcat - User mailing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 3/8/12 11:34 AM, André Warnier wrote:
> Christopher Schultz wrote:
>> It looks like the MBean (or maybe the pool itself) is exposing
>> something that shouldn't be treated as a property: the
>> connection itself. Calling getConnection (or,
On Thu, Mar 8, 2012 at 12:58 PM, Caldarale, Charles R
wrote:
>> From: David Wahler [mailto:dwah...@indeed.com]
>> Subject: Tomcat 5.5 JDK version compatibility
>
>> Does this mean that if a web application is deployed in Tomcat 5.5,
>> it may not use any language features that were introduced in J
2012/3/8 David Sills :
> Hi!
>
>
>
> I'm having a most infuriating problem with an test client I am using to
> check whether or not my Tomcat app is working. I can call Tomcat
> perfectly well from my browser, but when I try to connect using the same
> URL exactly from the executable JAR file in my
On Thu, 2012-03-08 at 08:55 -0800, Amit wrote:
>
>
>
> On 08-Mar-2012, at 6:37 PM, Daniel Mikusa wrote:
>
> > On Thu, 2012-03-08 at 00:34 -0800, amit shah wrote:
> >> Comment below
> >>
> >> On Wed, Mar 7, 2012 at 8:53 PM, Christopher Schultz <
> >> ch...@christopherschultz.net> wrote:
> >>
> From: David Wahler [mailto:dwah...@indeed.com]
> Subject: Tomcat 5.5 JDK version compatibility
> Does this mean that if a web application is deployed in Tomcat 5.5,
> it may not use any language features that were introduced in J2SE
> 5.0 or later (e.g. annotations and generics), even if those
Hi all, I have a question about a comment on this bug report:
https://issues.apache.org/bugzilla/show_bug.cgi?id=52545
Mark Thomas noted that:
"The application can not be compiled using a 1.4 JDK (the minimum Java version
required by Servlet 2.4) since it uses annotations. While applications may
> From: David Sills [mailto:dsi...@datasourceinc.com]
> Subject: Problem connecting to Tomcat from executable JAR file
> I can call Tomcat perfectly well from my browser, but when I
> try to connect using the same URL exactly from the executable
> JAR file in my test client, the connection is ref
Hi!
I'm having a most infuriating problem with an test client I am using to
check whether or not my Tomcat app is working. I can call Tomcat
perfectly well from my browser, but when I try to connect using the same
URL exactly from the executable JAR file in my test client, the
connection is ref
Konstantin Kolinko schrieb:
2012/3/6 :
Hi folks,
I'd like to retrieve the context path from the a startup event in a context
lifecycle listener. My usecase is register that contextpath in the initial
context and access its value through Logback.
Unfortunately, LifecycleEvent does not seem to
On 08-Mar-2012, at 6:37 PM, Daniel Mikusa wrote:
> On Thu, 2012-03-08 at 00:34 -0800, amit shah wrote:
>> Comment below
>>
>> On Wed, Mar 7, 2012 at 8:53 PM, Christopher Schultz <
>> ch...@christopherschultz.net> wrote:
>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> Amit,
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonathan,
On 3/8/12 10:19 AM, hodgesz wrote:
Well the exact same Spring code doesn't throw an exception with
6.0.29 version of Tomcat.
See Rainer's note in the bug you filed: those properties didn't exist
in 6.0.x.
I h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonathan,
On 3/8/12 10:19 AM, hodgesz wrote:
> Well the exact same Spring code doesn't throw an exception with
> 6.0.29 version of Tomcat.
See Rainer's note in the bug you filed: those properties didn't exist
in 6.0.x.
> I have already entered a bug
Well the exact same Spring code doesn't throw an exception with 6.0.29
version of Tomcat.
I have already entered a bug
https://issues.apache.org/bugzilla/show_bug.cgi?id=52842 for similar
exceptions thrown with version 7 that didn't exist in 6.
I didn't use XA previously and I don't need it now s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas,
On 3/8/12 4:47 AM, Thomas Scheer wrote:
> Is there a way to block whole countries (e.g. Sudan) by ip-ranges
> and/or CIDR data? (in regex it would be a mess of data)
My spidey sense it tingling. I swear we discussed this.
Aah, here it is:
ht
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonathan,
So, ConnectionPool.getProxyConstructor definitely makes a decision
about what interfaces to expose when generating a proxy for a
PooledConnection (sorry for the word-wrapping):
public Constructor getProxyConstructor(boolean xa) throws
N
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonathan,
On 3/8/12 6:29 AM, hodgesz wrote:
> Yes you are correct we are creating the pool in Spring
> configuration as it is more natural for our application, but the
> only problem we see now is once we upgraded to 7.0.26 we see the
> following exce
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 3/8/12 4:17 AM, André Warnier wrote:
> Amol Puglia wrote:
>> Hi,
>>
>> Thanks for the response.
>>
>> I am having mod_proxy_balancer as a balancer and having apache
>> version 2.2.16.
>>
>> I can not used tomcat 6.0.35 because my applicat
Additional notes in the text below.
Marcel Stör wrote:
First, thank you so much for the thorough response.
On 08.03.2012 14:47, André Warnier wrote:
Marcel Stör wrote:
Requirement:
a) /myapp authenticated against AD for all users with Windows
authentication
b) /myapp/API authenticated against
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alex,
On 3/7/12 9:41 PM, Alex Samad - Yieldbroker wrote:
> Failed looking for jni headers... but I wanted to compile the
> latest version, because there have been patches applied to fix
> concurrent loading of the dll
So, did you try to fix the Makef
First, thank you so much for the thorough response.
On 08.03.2012 14:47, André Warnier wrote:
Marcel Stör wrote:
Requirement:
a) /myapp authenticated against AD for all users with Windows
authentication
b) /myapp/API authenticated against AD for /one/ user with basic-auth
The plan was to have
Thank you for the response Chris. I'm going to use of the workarounds to
update the code. It seems like I was just using incorrect coding. I'm
still iffy about the implementation, but your point on literals clears
up some of my confusion.
--Kerry--
http://www.kjaklive.com
Original Messa
Marcel Stör wrote:
Requirement:
a) /myapp authenticated against AD for all users with Windows
authentication
b) /myapp/API authenticated against AD for /one/ user with basic-auth
The plan was to have two sites in IIS with appropriate authentication
schemes. They both have a 'jakarata' virtual
Thomas Scheer wrote:
Hi,
Is there a way to block whole countries (e.g. Sudan) by ip-ranges and/or CIDR
data? (in regex it would be a mess of data)
In CIDR Format:
# Country: SUDAN
# ISO Code: SD
# Total Networks: 19
# Total Subnets: 283,904
41.67.0.0/18
41.78.108.0/22
41.79.24.0/22
41.79.120.0/
On Thu, 2012-03-08 at 00:34 -0800, amit shah wrote:
> Comment below
>
> On Wed, Mar 7, 2012 at 8:53 PM, Christopher Schultz <
> ch...@christopherschultz.net> wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Amit,
> >
> > On 3/7/12 12:12 AM, amit shah wrote:
> > > I am using
Requirement:
a) /myapp authenticated against AD for all users with Windows authentication
b) /myapp/API authenticated against AD for /one/ user with basic-auth
The plan was to have two sites in IIS with appropriate authentication
schemes. They both have a 'jakarata' virtual directory pointing to
Yes you are correct we are creating the pool in Spring configuration as it is
more natural for our application, but the only problem we see now is once we
upgraded to 7.0.26 we see the following exception in the logs when viewing
through JMXProxy. The data is retrieved correctly so the exception i
Hi,
Is there a way to block whole countries (e.g. Sudan) by ip-ranges and/or CIDR
data? (in regex it would be a mess of data)
In CIDR Format:
# Country: SUDAN
# ISO Code: SD
# Total Networks: 19
# Total Subnets: 283,904
41.67.0.0/18
41.78.108.0/22
41.79.24.0/22
41.79.120.0/22
41.95.0.0/16
41.202.
Amol Puglia wrote:
Hi,
Thanks for the response.
I am having mod_proxy_balancer as a balancer and having apache version 2.2.16.
I can not used tomcat 6.0.35 because my application eMatrix does not support
that version.
I do not know eMatrix, but on the face of it, that sounds very strange. A
Comment below
On Wed, Mar 7, 2012 at 8:53 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Amit,
>
> On 3/7/12 12:12 AM, amit shah wrote:
> > I am using tomcat-jdbc.jar and tomcat-juli.jar from version
> > 7.0.26.
> >
> >> I don'
On 03/06/2012 11:50 PM, Alex Samad - Yieldbroker wrote:
Hi
I patched Mmakefile.amd64 it was different to the x86 one then ran
nmake -f Makefile.amd64
again, built no errors or warnings
Thanks
Alex
Patch...
Index: Makefile.amd64
Hi,
Thanks for the response.
I am having mod_proxy_balancer as a balancer and having apache version 2.2.16.
I can not used tomcat 6.0.35 because my application eMatrix does not support
that version.
From: Christopher Schultz
To: Tomcat Users List
Cc: Amol
44 matches
Mail list logo
