Anonymous | Login | Signup for a new account | 12-17-2024 08:49 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0001855 | [Resin] | minor | always | 07-06-07 08:55 | 07-18-07 10:21 | ||||
Reporter | sam | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | urgent | Resolution | fixed | ||||||
Status | closed | Product Version | 3.0.21 | ||||||
Summary | 0001855: Setting of socket timeouts fails on Solaris | ||||||||
Description |
(rep by T Corning) I was 'truss'ing the JVM and see this when it accepts connections on the HTTP Port: 20402/1069: setsockopt(112, tcp, TCP_NODELAY, 0xFFFFFFFE04BFEB10, 4, SOV_DEFAULT) = 0 20402/1069: setsockopt(112, SOL_SOCKET, SO_RCVTIMEO, 0xFFFFFFFE04BFEB18, 16, SOV_DEFAULT) Err#99 ENOPROTOOPT 20402/1069: setsockopt(112, SOL_SOCKET, SO_SNDTIMEO, 0xFFFFFFFE04BFEB18, 16, SOV_DEFAULT) Err#99 ENOPROTOOPT 20402/1069: getsockname(112, 0x1021890AC, 0xFFFFFFFE04BFEB34, SOV_DEFAULT) = 0 As you can see, both calls to set the timeout fail with ENOPROTOOPT, which is "Protocol not available". This means that the timeout isn't getting set. |
||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
There are no notes attached to this issue. |
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
27 total queries executed. 25 unique queries executed. |