On 24 February 2015 17:29:13 GMT, Rajesh Biswas wrote:
>Dear Experts,
>
>I am using container managed datasource to manage the database
>connections.
>
>But while shutting down the server I am getting lot of messages like
>below:
>
>appears to have started a thread named [pool-1-thread-1] but has
2015-02-25 2:29 GMT+09:00 Rajesh Biswas :
> Dear Experts,
>
> I am using container managed datasource to manage the database connections.
>
> But while shutting down the server I am getting lot of messages like below:
>
> appears to have started a thread named [pool-1-thread-1] but has failed to
>
How about using an "extras" package If you want to use Log4j for Tomcat
logging?
http://tomcat.apache.org/tomcat-8.0-doc/logging.html#Using_Log4j
2015-02-26 5:23 GMT+09:00 Owens, Stephen (ITD) :
> Hello,
>
> For tomcat 8 using log4j and apache commons logging, what would be the
> correct values t
Hi;
Tuckey plugin did the trick. Thanks for the help.
Br.
2015-02-24 20:30 GMT+01:00 André Warnier :
> Baran Topal wrote:
>
>> Hi;
>>
>> Thanks for the swift replies. I am not allowed to tuckey's rewrite (at
>> least until i cannot find a normative Tomcat solution).
>>
>> I looked for the docum
Hello Jan,
that would be better yes. For example some time ago, there were a virus
that would place a modified jsp in a webapp and try to access further data
from it. If the user, the tomcat runs under, would have limited permission,
such a malware would have less chances to actually do something
Dear All,
there are plenty resources mentioning it is a must to run tomcat as a
dedicated user with limited permissions.
Is it still true when tomcat doesn't run standalone, but via Apache web
server connected via AJP? That webserver already runs in the restrictive
mode.
Thanks, Jan
Hello,
For tomcat 8 using log4j and apache commons logging, what would be the correct
values to specify in setenv.sh for:
LOGGING_MANAGER
LOGGING_CONFIG
For a tomcat-7.0.26 installation, the values in setenv.sh were:
export LOGGING_CONFIG="-Dlog4j.configuration=log4j.properties"
export
LOGGING_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rémy,
On 2/25/15 11:44 AM, Rémy Maucherat wrote:
> 2015-02-25 17:17 GMT+01:00 Christopher Schultz
> > :
>
>> This configuration seems to solve the issue:
>>
>> > protocol="org.apache.coyote.ajp.AjpNioProtocol"
>> URIEncoding="UTF-8" packetSize="6
2015-02-25 17:17 GMT+01:00 Christopher Schultz :
> This configuration seems to solve the issue:
>
> redirectPort="443"
>protocol="org.apache.coyote.ajp.AjpNioProtocol"
> URIEncoding="UTF-8"
> packetSize="65536"
> socket.appReadBufSize="65536"
> socket.appWr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rémy,
On 2/25/15 10:39 AM, Rémy Maucherat wrote:
> 2015-02-25 15:10 GMT+01:00 Christopher Schultz
> > :
>
>> SEVERE: Exception while dispatching incoming RPC call
>> java.lang.IllegalArgumentException at
>> java.nio.Buffer.limit(Buffer.java:275) a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rémy,
On 2/25/15 10:39 AM, Rémy Maucherat wrote:
> 2015-02-25 15:10 GMT+01:00 Christopher Schultz
> > :
>
>> SEVERE: Exception while dispatching incoming RPC call
>> java.lang.IllegalArgumentException at
>> java.nio.Buffer.limit(Buffer.java:275) a
2015-02-25 15:10 GMT+01:00 Christopher Schultz :
> SEVERE: Exception while dispatching incoming RPC call
> java.lang.IllegalArgumentException
> at java.nio.Buffer.limit(Buffer.java:275)
> at
> org.apache.coyote.ajp.AjpNioProcessor.readSocket(AjpNioProcessor.java:179)
>
I see no ch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
On 2/25/15 10:18 AM, Christopher Schultz wrote:
> All,
>
> On 2/25/15 9:44 AM, Christopher Schultz wrote:
>> All,
>
>> On 2/25/15 9:10 AM, Christopher Schultz wrote:
>>> We are testing on Tomcat 8.0.17 and we have been getting
>>> failures t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
On 2/25/15 9:44 AM, Christopher Schultz wrote:
> All,
>
> On 2/25/15 9:10 AM, Christopher Schultz wrote:
>> We are testing on Tomcat 8.0.17 and we have been getting
>> failures that look like this:
>
>> SEVERE: Exception while dispatching inc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
On 2/25/15 9:10 AM, Christopher Schultz wrote:
> We are testing on Tomcat 8.0.17 and we have been getting failures
> that look like this:
>
> SEVERE: Exception while dispatching incoming RPC call
> java.lang.IllegalArgumentException at
> java
> -Original Message-
> From: Rainer Jung [mailto:rainer.j...@kippdata.de]
> Sent: Wednesday, February 25, 2015 3:41 AM
> To: Tomcat Users List
> Subject: Re: mod_jk causing stuck Apache processes
>
> So here is a patch for version 1.2.40:
>
> http://people.apache.org/~rjung/patches/jk_shm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
We are testing on Tomcat 8.0.17 and we have been getting failures that
look like this:
SEVERE: Exception while dispatching incoming RPC call
java.lang.IllegalArgumentException
at java.nio.Buffer.limit(Buffer.java:275)
at
org.ap
> Date: Tue, 24 Feb 2015 20:45:09 +0100
> From: a...@ice-sa.com
> To: users@tomcat.apache.org
> Subject: Re: Active Directory User Authentication Apache Tomcat 5.5 Struts
> Servlets JSP
>
> Seema Patel wrote:
> > Hi,
> >
> > We are using Apache Tomcat 5.5, JDK 1.5 and have a internal portal on
On Wed, Feb 25, 2015 at 2:19 AM, nandy r
wrote:
> Hello,
> I wanted to setup tomcat+hibernate+JOTM+sqlite but could not find any
> information on sqlite setup.
> I did read a document on setting up datasources and also one tomcat
> document relating to mysql, postgresql.
> It appears I need to su
Hi Jesse,
Am 24.02.2015 um 19:27 schrieb Jesse Defer:
-Original Message-
From: Rainer Jung [mailto:rainer.j...@kippdata.de]
Sent: Monday, February 23, 2015 5:00 PM
To: Tomcat Users List
Subject: Re: mod_jk causing stuck Apache processes
Am 24.02.2015 um 00:29 schrieb Jesse Defer:
I s
20 matches
Mail list logo
