executing accept
java.net.SocketException: Invalid argument
at java.net.PlainSocketImpl.socketSetOption(Native Method)
at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:240)
at java.net.Socket.setSoLinger(Socket.java:826
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aaron,
Aaron wrote:
Sun v245 running Solaris 10
I think this might have been covered before, but I'm not entirely sure.
You'd have to check the circumstances. Search the archives for
SocketException, socketSetOption, and IPv6. I think that you
try adding
|-Djava.net.preferIPv4Stack=true
to your startup script
Filip
|
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aaron,
Aaron wrote:
Sun v245 running Solaris 10
I think this might have been covered before, but I'm not entirely sure.
You'd have to
What's your server OS?
In Response To:
I am running Tomcat 5.0.28 and Apache 2.2 using mod_jk. I am constantly seeing
the following error show up in the catalina.log:
WARNING: Exception executing accept
java.net.SocketException: Invalid argument
]
Sent: Thursday, August 23, 2007 9:51 PM
To: users@tomcat.apache.org
Subject: Re: java.net.SocketException: Invalid argument
Importance: High
What's your server OS?
In Response To:
I am running Tomcat 5.0.28 and Apache 2.2 using mod_jk. I am constantly
seeing the following error show up
-7528 | f (817) 804-4696
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 23, 2007 9:51 PM
To: [EMAIL PROTECTED]
Subject: Re: java.net.SocketException: Invalid argument
Importance: High
What's your server OS?
In Response To:
I am running
Looks like the SO_LINGER option isn't being set. I would look into that.
In Response To:
By looking at the stack trace it looks like setsockopt() is trying to set an
option on the underlying socket that's not supported by your TCP/IP
implementation. It probably is some performance related
