Process explorer, select columns, Process I/O, delta total bytes might show the
story.
http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
Christopher Schultz wrote:
- -1 CPU
+1 I/O
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rainer,
On 7/23/14, 4:10 PM, Rainer Jung wrote:
> Am 23.07.2014 um 21:03 schrieb Christopher Schultz:
>
>> On 7/23/14, 1:49 PM, Rainer Jung wrote:
>
>>> The other case, a request with an invalid session ID accessing
>>> a tomcat instance with acti
Am 23.07.2014 um 21:03 schrieb Christopher Schultz:
On 7/23/14, 1:49 PM, Rainer Jung wrote:
The other case, a request with an invalid session ID accessing a
tomcat instance with activation disabled can IMHO be handled by a
filter that
- checks whether the request has a valid session using
ge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rainer,
On 7/23/14, 1:49 PM, Rainer Jung wrote:
> Am 23.07.2014 um 17:59 schrieb Christopher Schultz:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> Rainer,
>>
>> On 7/23/14, 11:23 AM, Rainer Jung wrote:
>>> On 23.07.2014 16:37, Christop
Am 23.07.2014 um 17:59 schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rainer,
On 7/23/14, 11:23 AM, Rainer Jung wrote:
On 23.07.2014 16:37, Christopher Schultz wrote:
On 7/18/14, 12:13 PM, Rainer Jung wrote:
On 17.06.2014 16:43, Christopher Schultz wrote:
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rainer,
On 7/23/14, 11:23 AM, Rainer Jung wrote:
> On 23.07.2014 16:37, Christopher Schultz wrote:
>
>> On 7/18/14, 12:13 PM, Rainer Jung wrote:
>
>>> On 17.06.2014 16:43, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SH
On 7/22/2014 11:04 AM, George Sexton wrote:
I'm using Tomcat 7.0.54 with the security manager. I'm getting an
exception I don't understand:
2014-07-22 09:27:03,934 [http-bio-80-exec-64] ERROR
org.apache.catalina.core.ContainerBase.[Catalina].[somehostname.mhsoftware.com].[/].[jsp]-
Servlet.se
On 23.07.2014 16:37, Christopher Schultz wrote:
On 7/18/14, 12:13 PM, Rainer Jung wrote:
On 17.06.2014 16:43, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
All,
I've been using sticky sessions with mod_jk and I can see that
there is a bit of a problem when atte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rainer,
On 7/23/14, 10:40 AM, Christopher Schultz wrote:
> Rainer,
>
> On 7/23/14, 10:37 AM, Christopher Schultz wrote:
>>> On 17.06.2014 16:43, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
All,
>
Hi, Chris. Thanks for replay.
Biggest problem is that I'm not our application developer >.<
2014-07-23 17:26 GMT+03:00 Christopher Schultz :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Арсений,
>
> On 7/23/14, 10:14 AM, Арсений Зинченко wrote:
> > We have Tomcat with:
> >
> > > au
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rainer,
On 7/23/14, 10:37 AM, Christopher Schultz wrote:
>> On 17.06.2014 16:43, Christopher Schultz wrote:
>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>>
>>> All,
>>>
>>> I've been using sticky sessions with mod_jk and I can see that
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rainer,
On 7/18/14, 12:13 PM, Rainer Jung wrote:
> late answer but at least an answer. See below.
I appreciate the late answer, because it was very helpful. I have some
concerns, though. Please see below.
> On 17.06.2014 16:43, Christopher Schultz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Арсений,
On 7/23/14, 10:14 AM, Арсений Зинченко wrote:
> We have Tomcat with:
>
> autoDeploy="false" deployOnStartup="true" >
>
> While startup I got ERROR in log:
>
> 14-07-22 15:13:01,551+0100 > 289 INFO
> [com.***.listener.PropertiesConfig
Hi.
We have Tomcat with:
While startup I got ERROR in log:
14-07-22 15:13:01,551+0100 > 289 INFO
[com.***.listener.PropertiesConfigListener] (main:) Adapter is a log4j
adapter ?org.slf4j.impl.Log4jLoggerAdapter
14-07-22 15:13:01,552+0100 > 290 ERROR
[com.***.listener.PropertiesCon
maxAge is not a timeout setting. It simply means the connection gets
retired(closed) instead of returned to the pool after a certain amount of
time
timeBetweenEvictionRunsMillis is not a timeout either. It is the interval
that the thread checks for timeouts, but not query, connection checkout
time
So, it means that if the timeout is detected not using setQueryTimeout
method, but by the tomcat pool settings (setMaxAge or
setTimeBetweenEvictionRunsMillis), it means that no exception can be thrown
at all?
Vasily
2014-07-23 12:14 GMT+04:00 Filip Hanik :
> Vasily, the exception depends on wh
Vasily, the exception depends on where the timeout occurs.
If the timeout is triggered by the driver, because you hit the
setQueryTimeout limit
http://docs.oracle.com/javase/7/docs/api/java/sql/Statement.html#setQueryTimeout(int)
then yes, as per javadoc, it is up to the JDBC driver to throw an ex
Thank you, I have changed timeBetweenEvictionRunsMillis value and it is
working properly now. Another problem has appeared: although the timeout is
handled correctly, no exception is thrown. I thought an SQLException would
be thrown if query takes too long. Maybe pool does not throw exceptions at
a
18 matches
Mail list logo