PM22862: FILETRANSFER SERVLET DOES NOT HANDLE "JAVA.IO.IOEXCEPTION: SRVE0080E: INVALID CONTENT LENGTH" CONDITION WELL.

Fixes are available

APAR status

Closed as program error.

Error description

Addnode process hangs during the federation . Looking at dmgr
SystemOut.log file following error was seen :

[9/14/10 20:20:21:916 CDT] 0000001b AdminOperatio A   ADMN1101I:
Beginning attempt to federate a node with WebSphere version
6.1.0.29 to a cell controlled by dmgr at version 6.1.0.29.

[9/14/10 20:32:01:535 CDT] 0000002a ServletWrappe E   SRVE0068E:
Uncaught exception thrown in one of the service methods of the
servlet: transfer. Exception thrown : java.io.IOException:
SRVE0080E: Invalid content length

Local fix

```
no work-around
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V6.1 and 7.0.                        *
****************************************************************
* PROBLEM DESCRIPTION: The system filetransfer application     *
*                      may fail to respond to the client       *
*                      after an error occurs during upload.    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In the filetransfer servlet, if an error is encountered when
the input or output stream is closed after an upload, the
servlet terminates the current operation and does not respond
to the filetransfer client. This can cause an operation such
as addNode to hang.

For example, a stack trace like following might be seen in the
logs, where an exception is thrown from the
FileTransferServlet.doPut() method:

[8/4/10 12:33:15:672 CDT] 00000041 ServletWrappe E SRVE0068E:
Uncaught exception thrown in one of the service methods of the
servlet: transfer. Exception thrown :
java.io.IOException: SRVE0080E: Invalid content length
at
com.ibm.ws.webcontainer.srt.http.HttpInputStream.finish(HttpInpu
tStream.java:166)
at
com.ibm.ws.webcontainer.srt.http.HttpInputStream.close(HttpInput
Stream.java:499)
at
java.util.zip.InflaterInputStream.close(InflaterInputStream.java
:228)
at java.util.zip.GZIPInputStream.close(GZIPInputStream.java:129)
at
com.ibm.ws.management.filetransfer.servlet.FileTransferServlet.d
oPut(FileTransferServlet.java:544)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:766)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr
apper.java:1152)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser
vletWrapper.java:593)
at
com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(S
ervletWrapper.java:534)
at
com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleReques
t(CacheServletWrapper.java:90)
at
com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.
java:751)
at
com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContaine
r.java:1478)
...

This stack trace points to two problems in the filetransfer
servlet code:

First, the exception is thrown from a place in the code (a
finally block) where it could be masking another exception that
was thrown earlier.

Second, an error while closing an input stream is causing the
FileTransferServlet.doPut() method to completely fail, even
though such an error may not be serious enough to prevent the
operation from continuing.

Problem conclusion

The filetransfer application code was modified to prevent
exceptions from masking other exceptions. Also, code was
modified so that exceptions thrown when input streams are
closed are logged in FFDC but do not cause the operation to
fail.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.37 and 7.0.0.17.  Please refer to the
Recommended Updatespage for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM22862
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-09-20
Closed date
2010-12-15
Last modified date
2010-12-15

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PM22862: FILETRANSFER SERVLET DOES NOT HANDLE "JAVA.IO.IOEXCEPTION: SRVE0080E: INVALID CONTENT LENGTH" CONDITION WELL.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?