There is already a hibernate issue on this bug
(https://hibernate.atlassian.net/browse/HHH-8818).
Regards,
Christian
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail:
On Wed, Apr 16, 2014 at 7:03 AM, Philippe Couas pco...@orange.fr wrote:
Hi, I want migrate from tomcat 7.0.52 to 7.0.53. My tomcat is launched in
standalone mode from command line (linux level3)Currently i have a servlet
that create image to disk and only with last version i have following
Tomcat version 6.0.x on Linux OS
Hello all,
Sorry to post my question again but I have no answer till now.
Could anyone tell me if it would be better to post it to the tomcat-dev
mailing list?
I don't think so, but maybe I'm wrong.
For more details, please see the original question here:
Hi Shanti,
On 04/15/2014 09:56 PM, Shanti Suresh wrote:
[...]
I find Chris' example on writing filters to map to URL patterns for
response-time metrics relevant. I would also like stall counts,
concurrent invocations etc.
What is a stall-count? How would you record concurrent invocations,
On 16/04/2014 09:31, lo lo wrote:
Tomcat version 6.0.x on Linux OS
Hello all,
Sorry to post my question again but I have no answer till now.
http://wiki.apache.org/tomcat/FAQ/Tomcat_User#Q2
Could anyone tell me if it would be better to post it to the tomcat-dev
mailing list?
No, this
I was able to get one of our developers and it was simple for them to add the
logging for our app to the logback we are using a file and add logging
rotation. My issue is resolved. Thanks for the help though.
-Original Message-
From: Scott Bailey [mailto:sbai...@donlen.com]
Sent:
On Sun, Apr 13, 2014 at 4:02 PM, Konstantin Kolinko
knst.koli...@gmail.comwrote:
By the way, there exists an Apache project implementing the JPA
specification,
http://openjpa.apache.org/
It does not really work with Tomcat though does it? See this issue:
I am running Tomcat 7.0.47 and it occasionally returns HTTP status codes
of 400, such as the following from my access log.
A 400 suggests a malformed request, but many of these are simple GET
requests on an image, so it seems odd they are malformed. We're not
positive, but it seems that as
How do I prevent Tomcat 6 from responding to a request to an IP address,
that is I only want my Tomcat server to respond to requests to
www.mydomain.com vs. 10.1.1.1.
Is this possible?
The problem is that our web security scanner is reporting Web Server Uses
Basic Authentication Without HTTPS,
I have a Tomcat 7.0.30 server I'm trying to patch to resolve the heartbleed
exploit.
I shut down the server and overwrite tcnative-1.dll with the recently released
version.
When I restart tomcat, I get errors about the Java Key Store.
Apr 16, 2014 9:36:07 AM
2014-04-16 21:44 GMT+04:00 Cormier, Greg greg.corm...@dfo-mpo.gc.ca:
I have a Tomcat 7.0.30 server I'm trying to patch to resolve the heartbleed
exploit.
I shut down the server and overwrite tcnative-1.dll with the recently
released version.
When I restart tomcat, I get errors about the
-Original Message-
From: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
Sent: April-16-14 2:12 PM
To: Tomcat Users List
Subject: Re: Patching Tomcat for Heartbleed
2014-04-16 21:44 GMT+04:00 Cormier, Greg greg.corm...@dfo-mpo.gc.ca:
I have a Tomcat 7.0.30 server I'm trying to
On Apr 16, 2014, at 1:42 PM, Mark Murphy jmarkmur...@gmail.com wrote:
How do I prevent Tomcat 6 from responding to a request to an IP address,
that is I only want my Tomcat server to respond to requests to
www.mydomain.com vs. 10.1.1.1.
Just an idea, but you could probably do this with a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Greg,
On 4/16/14, 2:28 PM, Cormier, Greg wrote:
-Original Message- From: Konstantin Kolinko
[mailto:knst.koli...@gmail.com] Sent: April-16-14 2:12 PM To:
Tomcat Users List Subject: Re: Patching Tomcat for Heartbleed
2014-04-16 21:44
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 4/16/14, 12:42 PM, David Wall wrote:
I am running Tomcat 7.0.47 and it occasionally returns HTTP status
codes of 400, such as the following from my access log.
A 400 suggests a malformed request, but many of these are simple
GET
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 4/16/14, 10:44 AM, David Landis wrote:
On Sun, Apr 13, 2014 at 4:02 PM, Konstantin Kolinko
knst.koli...@gmail.comwrote:
By the way, there exists an Apache project implementing the JPA
specification, http://openjpa.apache.org/
On 4/16/2014 3:17 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The access log of course does not give the whole story. It's possible
that the client sent for example a badly-formed HTTP header value. In
those cases, the request-line (shown in the access log)
I've never done a request dumper before, but is there a way to trigger
it only if Tomcat is going to issue a 400?
Sorry for replying to my own posting, but for JSP urls, we do seem to
know that request.getScheme() for example returns null when things are
bad, though I'm not sure how a bad
18 matches
Mail list logo
