Closed
Bug 434034
Opened 17 years ago
Closed 3 years ago
Insufficient system resources error.
Categories
(JSS Graveyard :: Tests, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: slavomir.katuscak+mozilla, Unassigned)
Details
Build:
securitytip/20080515.1/charm~HP-UXB.11.11_64_DBG
Log:
============= SSLClientAuth bypass on
/share/builds/components/jdk/1.5.0_06/HP-UX/jre/bin/java -d64 -cp /share/builds/mccrel3/security/securitytip/builds/20080515.1/hploan1_HPUX11i/mozilla/dist/release/no-policy/classes_DBG/org/../xpclass_dbg.jar org.mozilla.jss.tests.SSLClientAuth /share/builds/mccrel3/security/securitytip/builds/20080515.1/wozzeck_Solaris8/mozilla/tests_results/jss/charm.3 passwords 2906 bypass 140
main: jss library loaded
***FilePasswordCallback returns m1oZilla
Server about to create socket
Server created socket
Server specified cert directly
Server about to accept
client about to connect
Client specified cert directly
client connected
Server accepted
Server about to read
server got a completed handshake (security is ON)
client got a completed handshake (security is ON)
client forced handshake. ciphersuite: RC4
Server read successful
Server exiting
Server about to create socket
Server created socket
Server specified cert by nickname
client about to connect
Server about to accept
Client specified cert by nickname
client connected
org.mozilla.jss.ssl.SSLSocketException: ity/SignatureException: (-5974) Insufficient system resources.
at org.mozilla.jss.ssl.SSLServerSocket.socketAccept(Native Method)
at org.mozilla.jss.ssl.SSLServerSocket.accept(SSLServerSocket.java:198)
at org.mozilla.jss.tests.SSLClientAuth.run(SSLClientAuth.java:417)
at java.lang.Thread.run(Thread.java:595)
Server exiting
Exception in thread "main" org.mozilla.jss.ssl.SSLSocketException: SSL_ForceHandshake failed: (-5961) TCP connection reset by peer.
at org.mozilla.jss.ssl.SSLSocket.forceHandshake(Native Method)
at org.mozilla.jss.tests.SSLClientAuth.testConnection(SSLClientAuth.java:336)
at org.mozilla.jss.tests.SSLClientAuth.doIt(SSLClientAuth.java:196)
at org.mozilla.jss.tests.SSLClientAuth.main(SSLClientAuth.java:123)
JSSTEST_CASE 10 (SSLClientAuth bypass on): FAIL return value 1
From log it looks that we ran out of some system resources (sockets ??) on server side (socketAccept) and then also client failed. Not sure if this is system problem, or if there can be reason in our tests.
Reporter | ||
Comment 1•17 years ago
|
||
Build:
securitytip/20080707.1/charm~HP-UXB.11.11_OPT
Log:
============= SSLClientAuth FIPSMODE
/share/builds/components/jdk/1.5.0_06/HP-UX/jre/bin/java -cp /share/builds/mccrel3/security/securitytip/builds/20080707.1/hploan1_HPUX11i/mozilla/dist/release/no-policy/classes/org/../xpclass.jar org.mozilla.jss.tests.SSLClientAuth /share/builds/mccrel3/security/securitytip/builds/20080707.1/wozzeck_Solaris8/mozilla/tests_results/jss/charm.2 passwords 2903 bypassoff 150
***FilePasswordCallback returns m1oZilla
The NSS database is confirued in FIPSmode.
Enable ony FIPS ciphersuites.
Server about to create socket
Server created socket
Server specified cert directly
Server about to accept
client about to connect
Client specified cert directly
client connected
Server accepted
Server about to read
server got a completed handshake (security is ON)
client got a completed handshake (security is ON)
client forced handshake. ciphersuite: AES-256
Server read successful
Server exiting
Server about to create socket
Server created socket
Server specified cert by nickname
client about to connect
Server about to accept
Client specified cert by nickname
client connected
org.mozilla.jss.ssl.SSLSocketException: : (-5974) Insufficient system resources.
at org.mozilla.jss.ssl.SSLServerSocket.socketAccept(Native Method)
at org.mozilla.jss.ssl.SSLServerSocket.accept(SSLServerSocket.java:198)
at org.mozilla.jss.tests.SSLClientAuth.run(SSLClientAuth.java:417)
at java.lang.Thread.run(Thread.java:595)
Server exiting
Exception in thread "main" org.mozilla.jss.ssl.SSLSocketException: SSL_ForceHandshake failed: (-5961) TCP connection reset by peer.
at org.mozilla.jss.ssl.SSLSocket.forceHandshake(Native Method)
at org.mozilla.jss.tests.SSLClientAuth.testConnection(SSLClientAuth.java:336)
at org.mozilla.jss.tests.SSLClientAuth.doIt(SSLClientAuth.java:196)
at org.mozilla.jss.tests.SSLClientAuth.main(SSLClientAuth.java:123)
JSSTEST_CASE 29 (SSLClientAuth FIPSMODE): FAIL return value 1
Updated•15 years ago
|
Assignee: gbmozilla → nobody
Comment 2•3 years ago
|
||
JSS development has moved from the Mozilla community to the Dogtag PKI community. Please re-file this bug at https://github.com/dogtagpki/jss if it is still relevant. Thank you!
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•