-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Michael,
On 5/7/13 4:33 PM, Michael-O wrote:
> Am 2013-05-07 17:20, schrieb Christopher Schultz:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> Michael,
>>
>> On 5/7/13 6:43 AM, Michael-O wrote:
Von: "Mark Thomas" On 07/05/2013 10:
Hello Christopher,
Am 2013-05-07 17:20, schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Michael,
On 5/7/13 6:43 AM, Michael-O wrote:
Von: "Mark Thomas" On 07/05/2013 10:25,
Michael-O wrote:
Von: "Mark Thomas" On 07/05/2013 09:16,
Michael-O wrote:
Hi folks,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 5/7/13 8:48 AM, Mark Thomas wrote:
> On 07/05/2013 13:43, André Warnier wrote:
>> Hendré Louw wrote:
>>> André
>>>
>>> Thank you for the link. The page states "Minimum Java Version".
>>> Can I therefor run Tomcat 7.0.35 on Java 1.7.0_21? I
On May 7, 2013, at 9:40 AM, "Mark H. Wood" wrote:
> Well, the developer can simply pack into the app. whatever internal
> configuration is needed, since he has ready access to the interior of
> the app and can deposit on the classpath *.properties, *.xml, or
> anything else he wants. He can have
> -Original Message-
> From: Mark H. Wood [mailto:mw...@iupui.edu]
> Sent: Tuesday, May 07, 2013 8:41 AM
> To: users@tomcat.apache.org
> Subject: Re: Why is context.xml no longer copied to
> Catalina/localhost/myapp.xml?
>
> On Mon, May 06, 2013 at 04:35:19PM -0400, Jesse Barnum wrote:
> [
> -Original Message-
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: Monday, May 06, 2013 4:01 PM
> To: Tomcat Users List
> Subject: Re: Why is context.xml no longer copied to
> Catalina/localhost/myapp.xml?
>
> On 06/05/2013 21:35, Jesse Barnum wrote:
> > On May 6, 2013, at 1:55 PM,
> From: Leo Donahue - RDSA IT [mailto:leodona...@mail.maricopa.gov]
> Subject: server jvm
> now that there is a separate download for a server jre at 7u21, should we
> be using that instead?
It looks like the "Server JRE" is somewhere in between a JDK and traditional
JRE. It is 64-bit only, b
Installing Tomcat 7.0.39 using the service.bat will pick up the server jvm.dll
located in the jdk directory, but now that there is a separate download for a
server jre at 7u21, should we be using that instead?
C:\Program Files\Java\jdk1.7.0_21\jre\bin\server\jvm.dll
Or use the new "Server JRE"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hendré,
On 5/7/13 7:41 AM, Hendré Louw wrote:
> What are the certified JDKs that Tomcat 7.0.35 can run on in a
> production environment?
I run Tomcat 7.0.3x+ on Oracle Java 1.6.0_26-b03. I haven't quite
moved-up to Java 1.7 anywhere, yet, but Mark
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Michael,
On 5/7/13 6:43 AM, Michael-O wrote:
>> Von: "Mark Thomas" On 07/05/2013 10:25,
>> Michael-O wrote:
>>>
Von: "Mark Thomas" On 07/05/2013 09:16,
Michael-O wrote:
> Hi folks,
>
> I recently enabled a QueryTimeoutInte
On Mon, May 06, 2013 at 04:35:19PM -0400, Jesse Barnum wrote:
[snip]
> I am sure that this would be out of scope, but if we pictured an ideal
> scenario, it seems like there would be one configuration file that is tightly
> managed by the developer, which is replaced when the app is redeployed, a
On 07/05/2013 13:43, André Warnier wrote:
> Hendré Louw wrote:
>> André
>>
>> Thank you for the link. The page states "Minimum Java Version". Can I
>> therefor run Tomcat 7.0.35 on Java 1.7.0_21? Is the exact Java version
>> the Tomcat development team used for a specific Tomcat release not
>> more
Hendré Louw wrote:
André
Thank you for the link. The page states "Minimum Java Version". Can I
therefor run Tomcat 7.0.35 on Java 1.7.0_21? Is the exact Java version
the Tomcat development team used for a specific Tomcat release not
more correct for production environments?
It should not be,
André
Thank you for the link. The page states "Minimum Java Version". Can I
therefor run Tomcat 7.0.35 on Java 1.7.0_21? Is the exact Java version
the Tomcat development team used for a specific Tomcat release not
more correct for production environments?
Hendré
On 7 May 2013 13:47, André Warnie
On 07/05/2013 12:47, André Warnier wrote:
> Hendré Louw wrote:
>> Hello
>>
>> What are the certified JDKs that Tomcat 7.0.35 can run on in a
>> production environment?
>>
>
> I believe that should be mentioned on the "which version ?" page at
> http://tomcat.apache.org
+1. Those are the minimum v
Hendré Louw wrote:
Hello
What are the certified JDKs that Tomcat 7.0.35 can run on in a
production environment?
I believe that should be mentioned on the "which version ?" page at
http://tomcat.apache.org
-
To unsubscribe,
Hello
What are the certified JDKs that Tomcat 7.0.35 can run on in a
production environment?
Hendré
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
> Von: "Mark Thomas"
> On 07/05/2013 10:25, Michael-O wrote:
> >
> >> Von: "Mark Thomas" On 07/05/2013 09:16,
> >> Michael-O wrote:
> >>> Hi folks,
> >>>
> >>> I recently enabled a QueryTimeoutInterceptor with queryTimeout of
> >>> 60 seconds in a JDBC Pool data source (7.0.37). When the app wa
> Von: "Mark Thomas"
> On 07/05/2013 10:25, Michael-O wrote:
> >
> >> Von: "Mark Thomas" On 07/05/2013 09:16,
> >> Michael-O wrote:
> >>> Hi folks,
> >>>
> >>> I recently enabled a QueryTimeoutInterceptor with queryTimeout of
> >>> 60 seconds in a JDBC Pool data source (7.0.37). When the app wa
Hi All,
Thanks for your views.
It seems to be like very difficult to come for a conclusion :-)
Regards
Eashwar
On Thu, May 2, 2013 at 11:08 PM, David N. Smith wrote:
> >
> > Didn't you know that 'rm' was vulnerable on Linux?!?!
> >
> > An attacker with escalated privileges can -- thro
On 07/05/2013 10:25, Michael-O wrote:
>
>> Von: "Mark Thomas" On 07/05/2013 09:16,
>> Michael-O wrote:
>>> Hi folks,
>>>
>>> I recently enabled a QueryTimeoutInterceptor with queryTimeout of
>>> 60 seconds in a JDBC Pool data source (7.0.37). When the app was
>>> shut down, Tomcat said: "The web
> Von: "Mark Thomas"
> On 07/05/2013 09:16, Michael-O wrote:
> > Hi folks,
> >
> > I recently enabled a QueryTimeoutInterceptor with queryTimeout of 60
> > seconds in a JDBC Pool data source (7.0.37). When the app was shut down,
> > Tomcat said: "The web application [/...] appears to have star
On 07/05/2013 09:16, Michael-O wrote:
> Hi folks,
>
> I recently enabled a QueryTimeoutInterceptor with queryTimeout of 60 seconds
> in a JDBC Pool data source (7.0.37). When the app was shut down, Tomcat said:
> "The web application [/...] appears to have started a thread named
> [OracleTimeou
Hi folks,
I recently enabled a QueryTimeoutInterceptor with queryTimeout of 60 seconds in
a JDBC Pool data source (7.0.37). When the app was shut down, Tomcat said: "The
web application [/...] appears to have started a thread named
[OracleTimeoutPollingThread] but has failed to stop it..."
We
24 matches
Mail list logo
