Http Status Line Parse Error
FIPS UPDATE. Fixes are available 8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4 8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1 8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5 8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2 8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6 8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7 8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8 8.0.0.9: WebSphere Application https://www.ibm.com/support/knowledgecenter/SSZLC2_7.0.0/com.ibm.commerce.install.doc/refs/rigwsadminscript.htm Server V8.0 Fix Pack 9 8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10 8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11 8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12 Subscribe You can track all active APARs for this component. APAR status Closed as program error. Error description With additional FIPS options avaiable http://www.ibm.com/support/docview.wss?uid=swg1PM64146 in the V8 security configuration it is more likely that customers could miss updating ssl.client.props and see this error when running syncNode. ADMU0113E: Program exiting with error: com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host localhost at port 8881., resulting from: [SOAPException: faultCode=SOAP-ENV:Client; msg=Error parsing HTTP status line "??? ??": java.util.NoSuchElementException; targetException=java.lang.IllegalArgumentException: Error parsing HTTP status line "??? ??": java.util.NoSuchElementException] ADMU4123E: Ensure that the Deployment Manager is running on the specified host and port. Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server v8.0 and V8.5 Network Deployment * * edition. * **************************************************************** * PROBLEM DESCRIPTION: When the security configuration at * * the deployment manager is modified to * * enable or modify FIPS, it is required * * for the administrator to make also * * update to the ssl.client.props file * * at all nodes in the cell
() OCCLUST03EVS1 ! ugd ! att ! com [Download message RAW] Thanks a lot for your responses- It seems that I am getting NoSuchElementException when the https://marc.info/?l=soap-dev&m=111024319725863 read timeout expires using \ HTTPS. If I use http to send https://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html the request to the host, I get the proper Read time out \ exception: EXCEPTION CAUGHT---> Read timed out [SOAPException: faultCode=SOAP-ENV:Client; msg=Read timed out; \ targetException=java.io.InterruptedIOException: Read timed out] Vivian Ching AT&T MT A2-2E04 200 S Laurel Avenue Middletown, NJ 07748 732.420.2452 -----Original Message----- From: Aleksander Slominski [mailto:aslom@cs.indiana.edu] Sent: Monday, http status March 07, 2005 2:35 PM To: soap-dev@ws.apache.org Subject: Re: NoSuchElementException - Error parsing HTTP status line"" hi, my limited experience with SOAPHTTPConnection would suggest it is HTTPUtils and \ problem is in broken response from server that is not HTTP (for exampel SSL?) or is \ oen line off (broken content length) as it seems status line is empty ("" == \ "") http status line throw new SOAPException(Constants.FAULT_CODE_CLIENT, "Error parsing HTTP status line \"" + \ StringUtils.getStringISO8859_1(linebuf, 0, count, cbuf) + "\": " + e, e); http://cvs.apache.org/viewcvs.cgi/ws-soap/java/src/org/apache/soap/util/net/HTTPUtils. \ java?rev=1.46
Section 4.5 | response-header ; Section 6.2 | entity-header ) CRLF) ; Section 7.1 CRLF [ message-body ] ; Section 7.2 6.1 Status-Line The first line of a Response message is the Status-Line, consisting of the protocol version followed by a numeric status code and its associated textual phrase, with each element separated by SP characters. No CR or LF is allowed except in the final CRLF sequence. Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF 6.1.1 Status Code and Reason Phrase The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. These codes are fully defined in section 10. The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use by automata and the Reason-Phrase is intended for the human user. The client is not required to examine or display the Reason- Phrase. The first digit of the Status-Code defines the class of response. The last two digits do not have any categorization role. There are 5 values for the first digit: - 1xx: Informational - Request received, continuing process - 2xx: Success - The action was successfully received, understood, and accepted - 3xx: Redirection - Further action must be taken in order to complete the request - 4xx: Client Error - The request contains bad syntax or cannot be fulfilled - 5xx: Server Error - The server failed to fulfill an apparently valid request The individual values of the numeric status codes defined for HTTP/1.1, and an example set of corresponding Reason-Phrase's, are presented below. The reason phrases listed here are only recommendations -- they MAY be replaced by local equivalents without affecting the protocol. Status-Code = "100" ; Section 10.1.1: Continue | "101" ; Section 10.1.2: Switching Protocols | "200" ; Section 10.2.1: OK | "201