PK75441: FILETRANSFER FAILURE CAUSES CELL SYNC FAILURE

Fixes are available

APAR status

Closed as program error.

Error description

Filetransfer will randomly fail, and it causes the cell to
be unable to sync properly until the cell is restarted

Symptom:

[10/16/08 16:01:07:049 EDT] 0000003d FileDocument  E
ADMR0105E: The system is unable to write document cells/myCell
/xdcatalognodes.config:
java.io.FileNotFoundException: File download failed:
java.io.IOException: File download failed [404].Message:
404 Not Found for http;//mycorp.com:9060/FileTransfer/transfer/
download%2Fcells%2FmyCell%2Fxdcatalognodes.config1687.tmp?
compress=true&deleteOnCompletion=true.
 at com.ibm.websphere.management.filetransfer.client.
FileDownloadInputStream.getStream(FileDownloadInputStream.java
:226)
 at com.ibm.websphere.management.repository.RepositoryInputStr
 eam.read(RepositoryInputStream.java:133)
 at java.security.DigestInputStream.read(DigestInputStream.jav
 a:161)
 at java.io.FilterInputStream.read(FilterInputStream.java:113)
 at com.ibm.ws.management.repository.FileDocument.copyDocument
 (FileDocument.java:445)
 at com.ibm.ws.management.repository.FileDocument.write(FileDo
 cument.java:288)
 at com.ibm.ws.management.repository.FileRepository.modifyInte
 rnal(FileRepository.java:1154)
 at com.ibm.ws.management.repository.FileRepository.updateInte
 rnal(FileRepository.java:1354)
 at com.ibm.ws.management.repository.FileRepository.update(Fil
 eRepository.java:1286)
 at com.ibm.ws.management.repository.FileRepository.modify(Fil
 eRepository.java:1073)
 at com.ibm.ws.management.repository.FileRepository.modify(Fil
 eRepository.java:1065)
 at com.ibm.ws.management.sync.NodeSyncTask.processFolderSyncU
 pdate(NodeSyncTask.java:465)
 at com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTas
 k.java:296)
 at com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.j
 ava:181)
 at java.lang.Thread.run(Thread.java:810)

Here is a trace snippet showing the root cause:

[10/30/08 10:11:12:648 EDT] 00000093 FileTransferS 3
sendFile: Method = GET
[10/30/08 10:11:12:648 EDT] 00000094 FileTransferS 3
sendFile: Method = GET
[10/30/08 10:11:12:648 EDT] 00000095 FileTransferS 3
sendFile: Method = GET
[10/30/08 10:11:12:648 EDT] 00000095 FileTransferS 3
The repository root=[/opt/WAS61/profiles/dmgr/config/temp]
[10/30/08 10:11:12:648 EDT] 00000093 FileTransferS 3
The repository root=[/opt/WAS61/profiles/dmgr/config/temp]
[10/30/08 10:11:12:648 EDT] 00000094 FileTransferS 3
The repository root=[/opt/WAS61/profiles/dmgr/config/tem]
[10/30/08 10:11:12:648 EDT] 00000095 FileTransferS >  sendFile
 Entry /download/cells/myCell/xdcatalognodes.config5734.tmp
[10/30/08 10:11:12:648 EDT] 00000093 FileTransferS >  sendFile
 Entry /download/cells/myCell/xdcatalognodes.config5740.tmp
[10/30/08 10:11:12:648 EDT] 00000094 FileTransferS >  sendFile
 Entry /download/cells/myCell/xdcatalognodes.config5735.tmp

Note the three strings "The repository root = ". The 'p' gets
stripped off in the final one due to the thread concurrently
updating the servlet instance variable.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V6.0.2, V6.1 and V7.0                *
****************************************************************
* PROBLEM DESCRIPTION: Filetransfer can fail randomly,         *
*                      causing a cell to be unable to          *
*                      synchronize properly until the cell     *
*                      is restarted.                           *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Under certain conditions, the repository root value in
FileTransferServlet can become corrupted.

Here is a sample log from an IBM WebSphere Extended Deployment
system that shows one symptom of the problem:

[10/16/08 16:01:07:049 EDT] 0000003d FileDocument EADMR0105E:
The system is unable to write document
cells/myCell/xdcatalognodes.config:
java.io.FileNotFoundException: File download failed:
java.io.IOException: File download failed [404].Message: 404
Not Found for
'http://xdblade.mycompany.com:9060/FileTransfer/transfer/downloa
d'
%2Fcells%2FmyCell%2Fxdcatalognodes.config1687.tmp?compress=true&
delete
OnCompletion=true.
at
com.ibm.websphere.management.filetransfer.client.FileDownloadInp
utStream.getStream(FileDownloadInputStream.java:226)
at
com.ibm.websphere.management.repository.RepositoryInputStream.re
ad
(RepositoryInputStream.java:133)
at
java.security.DigestInputStream.read(DigestInputStream.java:161)
at java.io.FilterInputStream.read(FilterInputStream.java:113)
at
com.ibm.ws.management.repository.FileDocument.copyDocument(File
Document.java:445)
at
com.ibm.ws.management.repository.FileDocument.write(FileDocument
.
java:288)
at
com.ibm.ws.management.repository.FileRepository.modifyInternal(F
ile
Repository.java:1154)
at
com.ibm.ws.management.repository.FileRepository.updateInternal(F
ile
Repository.java:1354)
at
com.ibm.ws.management.repository.FileRepository.update(FileRepos
itory.
java:1286)
at
com.ibm.ws.management.repository.FileRepository.modify(FileRepos
itory.
java:1073)
at
com.ibm.ws.management.repository.FileRepository.modify(FileRepos
itory.
java:1065)
at
com.ibm.ws.management.sync.NodeSyncTask.processFolderSyncUpdate
(NodeSyncTask.java:465)
at
com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTask.java
:296)
at
com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.java:18
1)
at java.lang.Thread.run(Thread.java:810)

The root cause is illustrated by the trace below (with trace
spec com.ibm.ws.management.filetransfer.servlet.*=all):

[10/30/08 10:11:12:648 EDT] 00000093 FileTransferS 3 sendFile:
Method = GET
[10/30/08 10:11:12:648 EDT] 00000094 FileTransferS 3 sendFile:
Method = GET
[10/30/08 10:11:12:648 EDT] 00000095 FileTransferS 3 sendFile:
Method = GET
[10/30/08 10:11:12:648 EDT] 00000095 FileTransferS 3 The
repository root=[/opt/WAS61/profiles/dmgr/config/temp]
[10/30/08 10:11:12:648 EDT] 00000093 FileTransferS 3 The
repository root=[/opt/WAS61/profiles/dmgr/config/temp]
[10/30/08 10:11:12:648 EDT] 00000094 FileTransferS 3 The
repository root=[/opt/WAS61/profiles/dmgr/config/tem]
[10/30/08 10:11:12:648 EDT] 00000095 FileTransferS > sendFile
Entry
/download/cells/myCell/xdcatalognodes.config5734.tmp
[10/30/08 10:11:12:648 EDT] 00000093 FileTransferS > sendFile
Entry
/download/cells/myCell/xdcatalognodes.config5740.tmp
[10/30/08 10:11:12:648 EDT] 00000094 FileTransferS > sendFile
Entry

/download/cells/myCell/xdcatalognodes.config5735.tmp

Notice that the third repository root value is truncated,
because a single field is being updated by multiple threads at
the same time.

Problem conclusion

The code was fixed by modifying the method that sets the value
of repository root to be thread safe.

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

Temporary fix

Comments

APAR Information

APAR number
PK75441
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-11-11
Closed date
2009-04-09
Last modified date
2009-04-10

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
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":"BU059","label":"IBM Software w\/o TPS"},"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:
28 December 2021

Tips

PK75441: FILETRANSFER FAILURE CAUSES CELL SYNC FAILURE

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

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?