|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
|
|
java.net.SocketException while using DWRI am developing a web-based chat application. Though, my application runs pretty well and allows users to chat. i get the following error message in the Tomcat console. i want to mention that this error keeps coming time to time, my application does not seems get affected by this. But, after all an error is an error. So, please tell me what can be the reason behind this and the possible solution
i am using HTTPS on port 8443. i start my Tomcat as https://localhost:8443 Apr 15, 2008 4:57:43 PM org.apache.tomcat.util.net.PoolTcpEndpoint processSocket SEVERE: Socket error caused by remote host /127.0.0.1 java.net.SocketException: Software caused connection abort: recv failed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at com.sun.net.ssl.internal.ssl.InputRecord.readFully(Unknown Source) at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.waitForClose(Unknown Source) at com.sun.net.ssl.internal.ssl.HandshakeOutStream.flush(Unknown Source) at com.sun.net.ssl.internal.ssl.Handshaker.sendChangeCipherSpec(Unknown Source) at com.sun.net.ssl.internal.ssl.ServerHandshaker.sendChangeCipherAndFinish(Unknown Source) at com.sun.net.ssl.internal.ssl.ServerHandshaker.clientFinished(Unknown Source) at com.sun.net.ssl.internal.ssl.ServerHandshaker.processMessage(Unknown Source) at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Unknown Source) at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source) at org.apache.tomcat.util.net.jsse.JSSESocketFactory.handshake(JSSESocketFactory.java:119) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:520) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Unknown Source) Apr 15, 2008 4:57:43 PM org.apache.tomcat.util.net.PoolTcpEndpoint processSocket SEVERE: Socket error caused by remote host /127.0.0.1 |
|
|
Re: java.net.SocketException while using DWRI'm not sure what could be causing this, but I'm not sure that it has anything to do with DWR - the stack trace doesn't mention DWR at all. A couple of things to consider: - Are you using DWR timeouts? - Can you track this on a firebug console and see what is breaking? Joe. On Tue, Apr 15, 2008 at 12:36 PM, Nitin Thakur <myegotrip@...> wrote:
|
|
|
Re: java.net.SocketException while using DWRRecently, I have noticed something. The problem i mentioned in my last thread comes only when i am on IE. Firefox never have problem with it. I do not see anything problematic on Firebug, it shows me nothing but the long lived connections(which remains for around 60123ms and then restarted) and the requests and responses that are sent over it. There is no certain task that when performed makes this exception occurs. It just occurs somewhere during the execution. sometimes, i see this when displaying the chat pop-up which contains some images; sometimes while sending the messages etc. I still doubt, it has anything to do with HTTPS; or when the number of requests increase. I am using the following parameters in my web.xml
dwr-invoker : org.directwebremoting.servlet.DwrServlet debug : true activeReverseAjaxEnabled : true initApplicationScopeCreatorsAtStartup : true maxWaitAfterWrite : 1 preStreamWaitTime : 1 postStreamWaitTime : 1 maxCallCount : 20 scriptSessionTimeout : 1800000 maxWaitingThreads : 100 ignoreLastModified : true I have already played around with these values, but it does not affect the problem at all. |
| Free Forum Powered by Nabble | Forum Help |