[MAGNOLIA-2714] Installation fails when java.io.tmpdir is not present or is not writable Created: 05/May/09  Updated: 12/Mar/12  Resolved: 31/Oct/11

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.0.1, 3.6.5
Fix Version/s: 4.5

Type: Bug Priority: Critical
Reporter: vychtrle Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Slackware 12.2, java version "1.6.0_13", Tomcat 6.0.18


Attachments: Text File MAGNOLIA-2714.patch     File StackTrace     File StackTrace_4.0.1    
Issue Links:
duplicate
is duplicated by MAGNOLIA-3874 Ensure system temp directory is writa... Closed
Template:
Patch included:
Yes
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

If the system temp dir does not exist, or is not writable by the Java process, the installation process fails with Error importing dms.openwfe: error while processing property value.
See stacktraces in attachment.



 Comments   
Comment by vychtrle [ 05/May/09 ]

Well, now I tried magnolia-bundled-webapp-4.0.1.war and it is the same bug as in the case of magnolia-bundled-webapp-3.6.5.

Comment by Magnolia International [ 06/May/09 ]

Did this really block / stop the installation, or is just logged and then ignored ?

ps: could you please move the stacktraces to attachments for readability? thanks.

Comment by vychtrle [ 06/May/09 ]

Yes, the installation stopped.
In the case of 3.6.5. with the General messages: Could not perform installation: Error importing dms.openwfe: error while processing property value

In the case of 4.0.1 with the Genralal messages like the above + Magnolia DNS module (version 1.3.0) : * Error while installing or updating dms module. (Error importing dms.openwfe: error while processing property value)

Comment by Wolfgang Habicht [ 25/Jun/09 ]

I encountered the same problem.
I solved it (at least for me) as follow (to see the solution read from bottom up; however I think my procedure helps to understand
1. disable dms (delete the module) --> installation continous, new error while loading my samle pages
2. disable magnolia.bootstrap.samples (in magnolia.properties) --> installation ok
3. manually import websites (import xml) --> exception
--> there is a general problem loading/importing nodes

Solution:

  • add a temp directory to your tomcat installation (mkdir tomcat/temp) (same level as webapps). It's a Jackrabbit "problem".
    (- switch changes 1-3 back (new clean installation)

now I could do the installation/startup without error

Comment by Philipp Bärfuss [ 26/Jun/09 ]

Jackrabbit uses temp files to import binaries. Unfortunately JR code swallows in that case the root cause. The problematic point is that empty temp folder sometimes don't survive the zip/unzip process.

Is the tomcat you have used the one we deliver in the bundle or a custom installation?

Comment by Magnolia International [ 12/Oct/11 ]

In all recent Tomcat releases, there is a safeToDelete.tmp file in the temp folder
to circumvent that. Why Tomcat does not recreate the directory is beyond me.

I guess it might happen that people (accidentally?) delete this directory; should we play it safe and ensure the system temp directory exists and is writable by the current process ?

Generated at Mon Feb 12 03:39:23 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.