IBM Support

Zip file is unreadable. Cause: java.util.zip.ZipException: invalid entry size

Troubleshooting


Problem

A zip file is received to be routed and unzipped by the routing template in Sterling Filegateway(SFG) and it fails to route with: FG_0455 Zip file is unreadable. Cause: java.util.zip.ZipException: invalid entry size. This mainly happens with larger files (larger than 4GB) but it can also happen with smaller zip files if the file format is ZIP64. This could also occur when using the compression service in a business process.

Symptom

File is not routed and the following error is in filegateway.log

[2015-02-12 13:02:13.955] ERROR Arrived File Failed
[2015-02-12 13:02:13.955] ERROR [1423764133955] Zip file is unreadable. Cause: java.util.zip.ZipException: invalid entry size (expected 778774528 but got 5073741824 bytes).
[2015-02-12 13:02:13.955] ERRORDTL [1423764133955]com.sterlingcommerce.fg.exception.FileGatewayRouteException: Zip file is unreadable. Cause: java.util.zip.ZipException: invalid entry size (expected 778774528 but got 5073741824 bytes).
at com.sterlingcommerce.fg.exception.FileGatewayRouteException.newZipUnreadable(FileGatewayRouteException.java:51)
at com.sterlingcommerce.fg.router.RouteIdentifier.extractZipEntry(RouteIdentifier.java:665)
at com.sterlingcommerce.fg.router.RouteIdentifier.crackOpenZip(RouteIdentifier.java:630)
at com.sterlingcommerce.fg.router.RouteIdentifier.getZipTOC(RouteIdentifier.java:601)
at com.sterlingcommerce.fg.router.RouteIdentifier.getMatches(RouteIdentifier.java:512)
at com.sterlingcommerce.fg.router.RouteIdentifier.findRoutePlansForChannel(RouteIdentifier.java:227)
at com.sterlingcommerce.fg.router.RouteIdentifier.findRoutePlans(RouteIdentifier.java:163)
at com.sterlingcommerce.fg.router.ArrivedFile.determineRoutes(ArrivedFile.java:544)
at com.sterlingcommerce.fg.router.ArrivedFile.startRoute(ArrivedFile.java:211)
at com.sterlingcommerce.fg.router.FileGatewayRouter.processRoute(FileGatewayRouter.java:136)
at com.sterlingcommerce.fg.services.FileGatewayRouteService.primitiveProcessData(FileGatewayRouteService.java:76)
at com.sterlingcommerce.fg.services.TransformingRouterService.processData(TransformingRouterService.java:79)
at com.sterlingcommerce.woodstock.workflow.activity.engine.ActivityEngineHelper.invokeService(ActivityEngineHelper.java:1818)
at com.sterlingcommerce.woodstock.workflow.activity.engine.ActivityEngineHelper.nextMainLogic(ActivityEngineHelper.java:631)
at com.sterlingcommerce.woodstock.workflow.activity.engine.ActivityEngineHelper.next(ActivityEngineHelper.java:362)
at com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListener.doWork(WorkFlowQueueListener.java:442)
at com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListener.run(WorkFlowQueueListener.java:236)
at com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListener.onMessage(WorkFlowQueueListener.java:197)
at com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueListener.onMessage(WorkFlowQueueListener.java:184)
at com.sterlingcommerce.woodstock.workflow.queue.wfTransporter.run(wfTransporter.java:444)
at com.sterlingcommerce.woodstock.workflow.queue.BasicExecutor$Worker.run(BasicExecutor.java:508)
at java.lang.Thread.run(Thread.java:804)
Caused by: java.util.zip.ZipException: invalid entry size (expected 778774528 but got 5073741824 bytes)
at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:414)
at java.util.zip.ZipInputStream.read(ZipInputStream.java:206)
at java.io.FilterInputStream.read(FilterInputStream.java:118)
at com.sterlingcommerce.fg.router.RouteIdentifier.extractZipEntry(RouteIdentifier.java:656)
... 20 more

[{"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"--","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
14 November 2019

UID

swg21698692

Page Feedback