; Subject: java.net.SocketTimeoutException: Read timed out
>>
>> > The stack trace below is the exception that occurred today. Does this
>> look
>> > like a tomcat or google calendar issue?
>>
>> It has nothing to do with Tomcat; it's your webapp that
On Fri, Apr 12, 2013 at 7:25 PM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: Howard W. Smith, Jr. [mailto:smithh032...@gmail.com]
> > Subject: java.net.SocketTimeoutException: Read timed out
>
> > The stack trace below is the exception that occur
On Fri, Apr 12, 2013 at 7:45 PM, antoine philippe chaker <
philippe.cha...@gmail.com> wrote:
> I think that Chuck is right : it has nothing to do with Tomcat, it's more a
> problem of communication between your webapp and the Google API.
>
>
Agreed. :)
I think that Chuck is right : it has nothing to do with Tomcat, it's more a
problem of communication between your webapp and the Google API.
2013/4/12 Caldarale, Charles R
> > From: Howard W. Smith, Jr. [mailto:smithh032...@gmail.com]
> > Subject: java.net.SocketTimeoutExce
> From: Howard W. Smith, Jr. [mailto:smithh032...@gmail.com]
> Subject: java.net.SocketTimeoutException: Read timed out
> The stack trace below is the exception that occurred today. Does this look
> like a tomcat or google calendar issue?
It has nothing to do with Tomcat; it's
t please advise.
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at java.net.SocketInputStream.read(Unknown Source)
at sun.security.ssl.InputRecord.readFully(Unknown Source)
at sun.security.ssl.I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bert,
On 1/18/12 4:22 PM, Bert Verhees wrote:
> I have done my testing, and at this moment, it seems that I found
> the problem, I forgot to close a databaseconnection in a function
> which is called a zillion times. Just one line of code, and the
> p
I have done my testing, and at this moment, it seems that I found the
problem, I forgot to close a databaseconnection in a function which is
called a zillion times.
Just one line of code, and the problem was solved.
At least I am so honest I admit it freely, and it will follow my career
until
Sorry, readers of this list for not replying, I am very busy
investigating the problem, I try replying later.
Bert
On 16-01-12 23:55, André Warnier wrote:
Hi.
I'll follow-up with an "out of band" message just for now.
It was not very clear from your initial explanations whether you were
sen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bert,
On 1/16/12 4:39 PM, Bert Verhees wrote:
> On 16-01-12 22:26, Pid wrote:
>> The JConsole and VisualVM applications provided with the JDK
>> will tell you how much memory is being consumed by the
>> application in various areas of the Java program
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bert,
On 1/16/12 11:15 AM, Bert Verhees wrote:
> I am not sure if it is an Axis2 problem or a Tomcat-problem.
>
> I have an client-application for test-purposes which runs inside
> the Eclipse-IDE. The problem only occurs when running Axis2 inside
>
Hi.
I'll follow-up with an "out of band" message just for now.
It was not very clear from your initial explanations whether you were sending all of the
1000, 2000, .. 8000 "person's data records" at once, in one HTTP POST, or sending the data
in a person-by-person way.
So my wild guess was base
On 16-01-12 22:26, Pid wrote:
The JConsole and VisualVM applications provided with the JDK will tell
you how much memory is being consumed by the application in various
areas of the Java program's process heap.
You may use them to observe behaviour during the operation you are
experimenting with
STs to the server ?
>
> This is one post.
>>
>>> This is slow, I must investigate the library directly without
>>> webservice if that is a problem of my coding. So we forget that for
>>> the moment.
>>>
>>> The problem which bothers me
it takes 8
seconds. When it reaches 1300, it already takes 17 seconds.
When at Person 1330, it is already 29 seconds, and at 1340 it is 39
seconds, and than a few persons more and a time-out exception occurs.
I receive a java.net.SocketTimeoutException: Read timed out from the
client side-code. T
330, it is already 29 seconds, and at 1340 it is 39
seconds, and than a few persons more and a time-out exception occurs.
I receive a java.net.SocketTimeoutException: Read timed out from the
client side-code. The default time-out time for Axis2-code is 40 seconds.
The printstacktrace is below,
.
When at Person 1330, it is already 29 seconds, and at 1340 it is 39
seconds, and than a few persons more and a time-out exception occurs.
I receive a java.net.SocketTimeoutException: Read timed out from the
client side-code. The default time-out time for Axis2-code is 40 seconds.
The
Hi Mark & all,
After using the Jpcap (java sniffer tool) to watch the http packets, We
Finally
found out the root cause of this problem is indeed the keep-live BUG of
Internet
Explorer, below is our finding for your reference :
Finding 1 : When using AJAX to make http requests, Internet Explorer
: Monday, October 13, 2008 11:35 AM
> Subject: Re: question : encounter java.net.SocketTimeoutException: Read
> timed out occasionally
>
>
>> Hi Johnny,
>>
>> Yes, We are using ajax to make the post requests, and the header do
>> include
>> content-len
.
> From: [EMAIL PROTECTED]
> To: users@tomcat.apache.org
> Subject: Re: question : encounter java.net.SocketTimeoutException: Read timed
> out occasionally
> Date: Mon, 13 Oct 2008 13:10:55 +0200
>
>
> - Original Message -
> From: "James Wang" &l
- Original Message -
From: "James Wang" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Monday, October 13, 2008 11:35 AM
Subject: Re: question : encounter java.net.SocketTimeoutException: Read
timed out occasionally
Hi Johnny,
Yes, We are using ajax
wrote:
>
> - Original Message - From: "James Wang" <[EMAIL PROTECTED]>
> To: "Tomcat Users List"
> Sent: Monday, October 13, 2008 7:11 AM
> Subject: Re: question : encounter java.net.SocketTimeoutException: Read
> timed out occasionally
>
&g
- Original Message -
From: "Johnny Kewl" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Monday, October 13, 2008 10:34 AM
Subject: Re: question : encounter java.net.SocketTimeoutException: Read
timed out occasionally
- Original Message -
- Original Message -
From: "James Wang" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Monday, October 13, 2008 7:11 AM
Subject: Re: question : encounter java.net.SocketTimeoutException: Read
timed out occasionally
Hi Mark,
In order to
Hi Mark,
In order to find out if the problem of Request.getParameter("parm") return
null (missing post
body part) is related to http keep-alive, We've tried to reduce
the KeepaliveTimeout setting in
Apache httpd server from 15 seconds to 5 seconds, the strange thing
happened, We found
the null p
James Wang wrote:
> Hi Mark,
>
> Would like to know if Request.getParameter("parm") return null is related to
> the
> SocketTimeoutException error, below was my finding that I posted last time
> for
> your reference .
Unlikely.
Mark
Hi Mark,
Would like to know if Request.getParameter("parm") return null is related to
the
SocketTimeoutException error, below was my finding that I posted last time
for
your reference .
Thanks.
James.
On Fri, Oct 3, 2008 at 9:50 AM, James Wang <[EMAIL PROTECTED]> wrote:
> Hi Mark,
> We also fou
en :60 <> actualLen :0
SEVERE: formData Len error len :74 <> actualLen :0
SEVERE: formData Len error len :145 <> actualLen :0
SEVERE: formData Len error len :60 <> actualLen :0
Thanks & Best Regards.
James Wang
On Fri, Sep 5, 2008 at 10:26 PM, Mark Thomas <[EMAIL PROTEC
the error message.
Mark
>
> Thanks a lot & Best Regards.
> James Wang.
>
> On Fri, Sep 5, 2008 at 10:26 PM, Mark Thomas <[EMAIL PROTECTED]> wrote:
>
>> James Wang wrote:
>>> Hi all,
>>>
>>> we are encountering java.net.SocketTime
ll it cause too many connections
opened in our apache httpd servers.
Thanks a lot & Best Regards.
James Wang.
On Fri, Sep 5, 2008 at 10:26 PM, Mark Thomas <[EMAIL PROTECTED]> wrote:
> James Wang wrote:
> > Hi all,
> >
> > we are encountering java.net.SocketTimeoutExcept
James Wang wrote:
> Hi all,
>
> we are encountering java.net.SocketTimeoutException: Read timed out
> occasionally,
> wondering if it's something related to network problem,
> Would highly appreciate if someone can help, following are the program stack
If the client is I
Hi all,
we are encountering java.net.SocketTimeoutException: Read timed out
occasionally,
wondering if it's something related to network problem,
Would highly appreciate if someone can help, following are the program stack
found in tomcat log for your reference :
WARNING: Exception t
32 matches
Mail list logo
