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 option that's being ignored. You could turn up the logging level by setting JkLogLevel debug. You could also run truss against the jvm process to see what the socket option is. Sent from Techienuggets Netbeans IDE Forum: http://www.techienuggets.com/Detail?tx=11168 --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
