tomcat/temp folder

[marco_altieri]

Hi,

on a live environment running Alfresco 3.4.6, everytime Alfresco restarts a lot of temporary files are created in tomcat/temp.
I don't know why they are created. Linux recognizes them as "PostScript document text":

file "+~JF3284278016701430061.tmp"
+~JF3284278016701430061.tmp: PostScript document text
‍‍‍‍

The text below is the content of one of these files:

%!FontType1-1.0 AHGMFP+LobsterTwo-BoldItalic null
10 dict begin
/FontInfo 10 dict dup begin
/version (null) readonly def
/Notice (Copyright © 2011 by Pablo Impallari. www.impallari.com. All rights reserved.) readonly def
/FullName (null) readonly def
/FamilyName (null) readonly def
/Weight (Bold) readonly def
/ItalicAngle 0 def
/isFixedPitch false def
/UnderlinePosition -100 def
/UnderlineThickness 50 def
end readonly def
/FontName /AHGMFP+LobsterTwo-BoldItalic def
/PaintType 0 def
/FontType 1 def
/FontMatrix [0.001 0 0 0.001 0 0] readonly def
/FontBBox [0 -17 696 750] readonly def
/StrokeWidth 0 def
/Encoding 256 array
0 1 255 {1 index exch /.notdef put} for
dup 30 /uni001e put
dup 31 /uni001f put
dup 32 /uni0020 put
dup 68 /uni0044 put
dup 97 /uni0061 put
dup 105 /uni0069 put
dup 108 /uni006c put
dup 118 /uni0076 put
dup 256 /uni0042 put
readonly def
currentdict end
currentfile eexec
D9D66F633B846A989B9974B0179FC6CC445BC2C03103C68570A7B354A4A280AE6FBF7F98
88E039AB60FCAF852EB4CE3AFEB979D5EA70FDE44A2AE5C8C0166C27BF9665EEA11C7D23
29C1A211DD26BB372BE5822F5EA70D99EB578C7BEFD44CDF045A363056E5E1CC51525EA6
FC061DCEBB337208EFF729802376A2801424F6700E7E6397B28F15BC10B40012B0A3EAEB
2693E8F7F627C4C9C7C6C5BFF105C1E41B2B9E8F09253B61177E95EA219474796072D4FC
D7E9AD6E4FCBCFC12A63BA842BE388946621ADA1C6BA12238C6919D4ECBF8C2B09767C44
AD639ACEDF4836B6CBEE757E489F9A93D5217B4251B96B01D1FA063D17CBED94BA2B1814
5E5021BF090E3D396A0480F80FD823DD836834852E1ECA48E550D63F17D50D376FED456A
956DD04536268232346714CD7B2B9E2242765738F744281179FF059DA521FF094DA1AC33
254A6A98CC02A11276444A5609BDA13C188B41D9376B75B55A594499D8B1513A764CA894
BFE0079CDFAC566ADAB8AD25C8E40F01D544EECCF5CDB960954CAC19CC09AABD5B9F80BC
ECD6F827CB1E06DE3EC01DBBD3E1F758CB0DC22D62D9494AA315C21646243B70B07A7F9E
0672F163FBC6F70E20FB7292670F2C9B802C54E2E0599CCB202C169FE1993FAA16DE77A3
090E8DA05D5C23A7CF75800B3C7F10E775F25C127C1B8FD4EC72AA5945BFD987AE54DAE4
5C1AD2BFCAD67D7B01BCBBB9B720B45B8ABFAE6C4DD2EE42723547FE6E617BC12B0F2FA5
FE64D0FDF38478397FA9552267BE223213239965B90ED0FB96C65079C0E5C243C858F60F
353E92BC3E6E291EA03732D6EEA08AD08BF3AB8F24F59C9C576321D6F7D2865B397C048A
533D4A34CF551809976CF08977637B990B9E459399980CCA27E6658CB553FD86CC7B8A61
300F30C7EB00C34E0B7234ECED88FFA5ED0C2AEF1F13713F8451B18566B57F06F3E22F00
848F98B3FD21D1FE47D795D0D738B367EFD2859A6529FB852E2855324CEFB341C5B83A27
4304480332F9B7023ED76535B78F3708A19A4464BFC3EB79367D811D463AC895C2AB13B2
124FA4E6B3ABF14E533EAE13FD477716A29E9A4F945CA1804A1AD414F86BBF97F6E727D8
5CEBB20133DF6525BF646D22214A9DF97617E29B10E44F21B55A64F598A34A7DEC313749
E436516518D489C3134F771BF99A3B67FA8E6C9BAE0187B8F964F2079798BEE4E77BAD3E
7596723518923F12BC8487901AEC58442BB8B21E289679AA6B72F920E45D010438D9E050
C6BD0D47BD1B7FB957658D13B5752E488C07C1B1DCA37343997489CBA33F588C4D983B1D
684F5E83760943258090E1643C8C2E76DB4D6A36AF7F8CC2C7EEB202790231E7A9E02B0D
6E614771358133833A505F05F518A9CD7970DF833D2B54CBB48A1CC9C3282C1F45A82CBD
36EFF062BB24145F060717B53E00B647191107C44F0374E5CD389C2084024056E678F58D
9CA03DF2C55987988051653A4D564EACA766DC8F6BAC2C2AECCD587CBAF9255590ACE1A1
DFDD5116FBB0DE2CD37451428C30FE94687B5B38750696CA08F57EFA9B5DDC238B70CB42
5CF049CC80CB18829043E644D7B31D2B626190731F0EA952060B0ACEE22EB3973B5E9CB6
0FBFB99A216000BD9565D9D14D3BF6BC80E06408D8606D86BCA83D1A3105A75701BB16F6
08B91478EC47F0ADBD37B3E697E89A867735C7BA9BB0D3F95260DE29FAF8C3B633687424
548556F7903A890978995018ED2C0D53B40CC80635C391C64BD1358100DA2150F878DC68
56267C6E35A581FF938C9A014B214E593E9AABF4028047F577FADD95F098807C1364C60D
2211547B492EAB682F55D46314BE428E2F1A832B63FD7164E9CB1AD3E694CB7E78BF9C27
C9F338288B7970A4E9E415AEDCEF279FC4AA3A8D71E2949B996E15A953607926B6A053CD
40F59299DC7CB886B2D23B87472705679B31B9BB0581D7A2CE870F7CBB698396931CA065
5AAB18F9FE7DC77CD7F97C72685DA6D1634902241E6F52D40692B4DD25B849800D772026
0172590BE24EB071E92845CA5B5DC0CCA52B18FE74EA96181841FBFFEDAE3BBB1F4DE0A0
D8649F653A1936A8AE1E4AAD6C406D13EC45AFF1F5DBBEBD1D6C62169A7E0B2FAA056471
114D686C385D588A265A7C19F559EF36F5251BF7C3E963DF69314F6E256EF4A9A114F827
F31B238BE61EBA7C2C4EF676722816BFED52
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
cleartomark
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

The creation of these files takes about 20 minutes. During this period the CPU usage is high and the site is slower than usual.

Has anybody seen the same problem?

Regards,
Marco

[mrogers]

The temp location is used to store temporary files.     Although Alfresco tends to use TOMCAT/temp/Alfresco.

It sounds like something is being transformed and is using a temporary file.      The use of the temporary file is a symptom of something else and is not a problem in itself.

[cegesin]

Hi, I've got a similar issue with Community 3.4d…

During a bulk process with GB's of documents, my tomcat/temp/Alfresco/ dir was full of temporary files under a ./<year>/<month>/<day>/<hour>/<minute>/ directory structure. Seems like temporary metadata info about the documents that bulk is processing. The question is… How can I predict the amount of space i'll need under /tomcat/temp/Alfresco?

The space is liberated after an hour aprox. but the filesystem was full until then… Any problem with this?

I suspect that it depends from a lot of variables, like number, type and size of documents but it's needed for a good storage dimension. Somebody knows any formula for estimating this need?

Greets

[mrogers]

The space used will be proportional to the amount of data you are uploading and the number of transformations used.
And it should only exist for a minimum of time but in very worst cases could be 24 hours (for big bulk imports and transfers).

Unfortunately last time I looked into this there is a windows/java incompatibility/design error that means it can be difficult to clean certain types of files as quickly as you would expect.     There may also be places in the code which do not clean up correctly, but these are bugs. 

The old rule of thumb was keep your disk at least 20% empty.  That's probably still good advice.

[marco_altieri]

The temp location is used to store temporary files.     Although Alfresco tends to use TOMCAT/temp/Alfresco.

It sounds like something is being transformed and is using a temporary file.      The use of the temporary file is a symptom of something else and is not a problem in itself.

Thank you for your reply.
This happens every time I restart alfresco and it doesn't depend on new uploaded documents.
I don't know what transformation involves this type of files: they are not pdf… In our repository most of the nodes are quickstart articles, images and pdfs.

Regards,
Marco