SWORD Empty Zip Error

[Florian Wille]

Hey There,
I am getting this Error Message for SWORDv1 pushes from SWORD Packages
that I pushed before and at that time had no trouble with them:

2021-09-13 12:56:42,169 ERROR org.dspace.sword.SWORDMETSIngester @
caught exception:
java.util.zip.ZipException: zip file is empty
at java.util.zip.ZipFile.open(Native Method)

This is for a DSpace 6.3 XMLUI on a Tomcat fronted by Apache over AJP.

I recently switched from Tomcat 8 to Tomcat 9 and had all sorts of
trouble with it. I suspect my AJP Connector which is configured like this:

<Connector protocol="AJP/1.3"
address="::1"
port="8009"
redirectPort="8443"
secretRequired=""
allowedRequestAttributesPattern=".*"
packetSize="65536" />

Maybe its not the AJP, I just suspect it...

Anyone a hint?

Regards Florian

[Mark H. Wood]

On Mon, Sep 13, 2021 at 01:32:43PM +0200, Florian Wille wrote:
> Hey There,
> I am getting this Error Message for SWORDv1 pushes from SWORD Packages
> that I pushed before and at that time had no trouble with them:
>
> 2021-09-13 12:56:42,169 ERROR org.dspace.sword.SWORDMETSIngester @
> caught exception:
> java.util.zip.ZipException: zip file is empty
> at java.util.zip.ZipFile.open(Native Method)
>
> This is for a DSpace 6.3 XMLUI on a Tomcat fronted by Apache over AJP.

You might try setting:

sword-server.keep-package-on-fail = true
sword-server.failed-package.dir = ${dspace.dir}/upload

so that you can check whether the file actually *is* empty. See the
comments in 'config/modules/sword-server.cfg'.

Are there any prior log records that might be relevant? Do the Tomcat
logs show anything unusual at the time of the submission?

> I recently switched from Tomcat 8 to Tomcat 9 and had all sorts of
> trouble with it. I suspect my AJP Connector which is configured like this:
>
> <Connector protocol="AJP/1.3"
> address="::1"
> port="8009"
> redirectPort="8443"
> secretRequired=""
> allowedRequestAttributesPattern=".*"
> packetSize="65536" />

This connector looks right to me. I've never used
'allowedRequestAttributesPattern', though.

--
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu

[Florian Wille]

Am 13.09.21 um 14:23 schrieb Mark H. Wood:

> On Mon, Sep 13, 2021 at 01:32:43PM +0200, Florian Wille wrote:
>> Hey There,
>> I am getting this Error Message for SWORDv1 pushes from SWORD Packages
>> that I pushed before and at that time had no trouble with them:
>>
>> 2021-09-13 12:56:42,169 ERROR org.dspace.sword.SWORDMETSIngester @
>> caught exception:
>> java.util.zip.ZipException: zip file is empty
>> at java.util.zip.ZipFile.open(Native Method)
>>
>> This is for a DSpace 6.3 XMLUI on a Tomcat fronted by Apache over AJP.
>
> You might try setting:
>
> sword-server.keep-package-on-fail = true
> sword-server.failed-package.dir = ${dspace.dir}/upload
>
> so that you can check whether the file actually *is* empty. See the
> comments in 'config/modules/sword-server.cfg'.
>

Did so and the failed file is empty. The file I send is not empty.
So I guess my problem is system-side not dspace-side, since the zip does
not reach dspace in the first place.

> Are there any prior log records that might be relevant? Do the Tomcat
> logs show anything unusual at the time of the submission?
>

In the dspace log there ist just the succesfull AUTH conversation
between SWORD Client and Server.
Neitther the Apache nor the Tomcat logs show me any errors, just access.

>> I recently switched from Tomcat 8 to Tomcat 9 and had all sorts of
>> trouble with it. I suspect my AJP Connector which is configured like this:
>>
>> <Connector protocol="AJP/1.3"
>> address="::1"
>> port="8009"
>> redirectPort="8443"
>> secretRequired=""
>> allowedRequestAttributesPattern=".*"
>> packetSize="65536" />
>
> This connector looks right to me. I've never used
> 'allowedRequestAttributesPattern', though.
>

That allows the shibd Daemon to pass Variables to Tomcat for Shibboleth
Authetication