Skip navigation
Currently Being Moderated

Saving a big file withouth check-in takes a long time

Oct 19, 2011 6:41 AM

A customer who uses our custom connector noticed that when saving a big file (+250MB) to a folder on a virtual  Drive without checking it in, it still takes a long time for the operation to complete.

Since this behavior is consistently reproducible, I requested the log file to find out what is going on exactly during this delay.

I would not expect our connector handlers to be active at this point since no check-in is taking place and the file is presumably only saved to the local Drive cache.

The log file seems to confirm that no custom connector code is executed during the delay, since there appears to be no logging at all while we are waiting for the save operation to complete.

 

I have included the relevant part of the log below. I have three questions about this log:

 

1. What is happening between 11:46:24 and 11:53:05 and why does no logging occur? What might be causing this delay while saving the file to the local cache?

2. There appear to be two different sources logging (IFSConnection-1 and JobHandler-3). What is the cause of this? Is this normal behavior or should I be worried about this?

3. Should I be worried about the exception that occurs after the delay at 11:53:05?

 

Many thanks in advance.

 

2011/10/19 11:46:24,156 [IFSConnection-1] DEBUG OpenHandler - IN

2011/10/19 11:46:24,172 [IFSConnection-1] TRACE OpenHandler - (assetId:f1d03182-6458-4631-bbb8-e704aaf076e7@ffbd978e-c723-46b2-b537 -2ed9dd154a8d | assetPath:/Cluster 2/Estafette nieuw/Handleiding/M6/Binnenwerk/Links/-rr-20060622-0002.jpg | versionNumber:1)

2011/10/19 11:46:24,203 [IFSConnection-1] DEBUG OpenHandler - OUT

2011/10/19 11:46:24,203 [IFSConnection-1] DEBUG CloseHandler - IN

2011/10/19 11:46:24,203 [IFSConnection-1] DEBUG CloseHandler - OUT

2011/10/19 11:46:24,219 [IFSConnection-1] DEBUG OpenHandler - IN

2011/10/19 11:46:24,234 [IFSConnection-1] TRACE OpenHandler - (assetId:f1d03182-6458-4631-bbb8-e704aaf076e7@ffbd978e-c723-46b2-b537 -2ed9dd154a8d | assetPath:/Cluster 2/Estafette nieuw/Handleiding/M6/Binnenwerk/Links/-rr-20060622-0002.jpg | versionNumber:1)

2011/10/19 11:46:24,266 [IFSConnection-1] DEBUG OpenHandler - OUT

2011/10/19 11:46:24,266 [IFSConnection-1] DEBUG CloseHandler - IN

2011/10/19 11:46:24,266 [IFSConnection-1] DEBUG CloseHandler - OUT

2011/10/19 11:46:24,281 [IFSConnection-1] DEBUG OpenHandler - IN

2011/10/19 11:46:24,297 [IFSConnection-1] TRACE OpenHandler - (assetId:f1d03182-6458-4631-bbb8-e704aaf076e7@ffbd978e-c723-46b2-b537 -2ed9dd154a8d | assetPath:/Cluster 2/Estafette nieuw/Handleiding/M6/Binnenwerk/Links/-rr-20060622-0002.jpg | versionNumber:1)

2011/10/19 11:46:24,312 [IFSConnection-1] DEBUG OpenHandler - OUT

2011/10/19 11:46:24,344 [IFSConnection-1] DEBUG CloseHandler - IN

2011/10/19 11:46:24,344 [IFSConnection-1] DEBUG CloseHandler - OUT

2011/10/19 11:53:05,813 [JobHandler-3] ERROR GetAssetById - Caught exception

  1. com.adobe.drive.data.model.DriveException: com.adobe.drive.data.model.asset.ModelObjectNotFoundException: Cannot find class com.adobe.drive.data.internal.model.Asset with id='60.871'

            at com.adobe.drive.data.model.asset.DeprecatedAssetFactory.findAssetById (DeprecatedAssetFactory.java:42)

            at com.adobe.drive.internal.data.manager.DataManager.getCachedAsset(Data Manager.java:1232)

            at com.adobe.drive.internal.biz.versioncue.service.call.GetAssetById.exe cuteItem(GetAssetById.java:59)

            at com.adobe.drive.internal.biz.versioncue.service.call.GetAssetById.exe cuteItem(GetAssetById.java:1)

            at com.adobe.drive.internal.biz.versioncue.service.call.VersionCueCall$1 .run(VersionCueCall.java:125)

            at com.adobe.drive.internal.biz.versioncue.service.call.VersionCueCall$1 .run(VersionCueCall.java:1)

            at com.adobe.drive.data.internal.persistence.PersistenceRunner.run(Persi stenceRunner.java:119)

            at com.adobe.drive.internal.biz.versioncue.service.call.VersionCueCall.e xecute(VersionCueCall.java:137)

            at com.adobe.drive.internal.biz.versioncue.service.VersionCueService.get Asset(VersionCueService.java:207)

            at com.adobe.drive.ncomm.versioncue.GetAssetById.handle(GetAssetById.jav a:54)

            at com.adobe.drive.ncomm.versioncue.VersionCueRequestHandler$1.run(Versi onCueRequestHandler.java:185)

            at com.adobe.drive.core.internal.jobs.JobHandler$JobWrapper.run(JobHandl er.java:270)

            at com.adobe.drive.core.internal.jobs.JobHandler$JobWrapper.run(JobHandl er.java:286)

            at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

            at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

            at java.lang.Thread.run(Unknown Source)

Caused by: com.adobe.drive.data.model.asset.ModelObjectNotFoundException: Cannot find class com.adobe.drive.data.internal.model.Asset with id='60.871'

            at com.adobe.drive.data.persistence.factories.AssetFactory.findAssetById (AssetFactory.java:244)

            at com.adobe.drive.data.model.asset.AssetFactory.findAssetById(AssetFact ory.java:69)

            at com.adobe.drive.data.model.asset.DeprecatedAssetFactory.findAssetById (DeprecatedAssetFactory.java:38)

            ... 15 more

2011/10/19 11:53:06,422 [JobHandler-1] DEBUG GetChildrenHandler - IN

2011/10/19 11:53:06,438 [JobHandler-1] TRACE GetChildrenHandler - (assetId:09c6e3a8-d865-4813-a6b4-0bec4828e19b | assetPath:/Cluster 2/Estafette nieuw/Handleiding/M6/Binnenwerk)

2011/10/19 11:53:06,469 [JobHandler-1] TRACE HandlerFactory - Path /Cluster 2/Estafette nieuw/Handleiding/M6/Binnenwerk/Links represents classification ffbd978e-c723-46b2-b537-2ed9dd154a8d.

2011/10/19 11:53:06,469 [JobHandler-1] TRACE HandlerFactory - Path /Cluster 2/Estafette nieuw/Handleiding/M6/Binnenwerk/Links represents classification ffbd978e-c723-46b2-b537-2ed9dd154a8d.

2011/10/19 11:53:06,516 [JobHandler-1] DEBUG GetChildrenHandler - OUT

 
Replies
  • Currently Being Moderated
    Oct 27, 2011 2:04 AM   in reply to hverlinde

    Hi,

     

    Sorry for late response since we are currently focusing on some high priority things.

     

    Regarding this issue, I can just give you some simple comments, 

     

    1) Can you clearly points out what occupied most of CPU time after using some profiling tool?

     

    2) IFSConnection-1 is a thread for processing the request from Finder/Explorer, JobHandler-x is the thread fro processing the request form Creative applications or Bridge.so I think the user must have openned one of them during saving the big file on the virtual drive.

     

    3) you dont't have to worry about the exception, it's just normal when saving a new file on the folder since AD doesn't cache it before. 

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points