Sorry for the delayed answer,

here is the screenshot:

In the logfile the tmpdir is set as

INFORMATION Command line argument: -Djava.io.tmpdir=/home/tomcat/temp/

There is no error message in the logs for the failed deployment.

/home/tomcat/temp is writeable for the user tomcat who runs ActiveVOS' tomcat, the directory activevos-reports-work is already written there.

Just today we had this error again at a Linux server with our Designer 9.2.4.1, which was not running as root

A 'sudo find -mtime 0 |grep upload' revealed,

that a directory

./java.io.tmpdir/upload_577dc761_1552f7b58e5__7ffe_00000001.tmp

was created, although environment variable java.io.tmpdir was set.

So it seems to be a bug, that ActiveVos creates and uses literally a directory /java.io.tmpdir/

We just had this problem again at a new installation of ActiveVOS Server Unix 9.2.4.3 at Tomcat on SUSE Linux Enterprise Server 12 SP3. Tomcat does not and should not run as root.

We might have found the reason for using /java.io.tmpdir, that's why this post after almost 3 years.

We have found that in

activevos/WEB-INF/classes/struts.xml

and

activevos/WEB-INF/classes/struts-bpeladmin.xml

is declared:

<constant name="struts.multipart.saveDir" value="java.io.tmpdir" />

We changed those to 

<constant name="struts.multipart.saveDir" value="${java.io.tmpdir}" />

and restarted tomcat.

After that the Upload of the BPR worked.