Issue Details (XML | Word | Printable)

Key: GLASSFISH-15830
Type: Bug Bug
Status: Resolved Resolved
Resolution: Won't Fix
Priority: Minor Minor
Assignee: Jennifer Chou
Reporter: jclingan
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
glassfish

unzip -t unsyncbundle.zip gives warning

Created: 03/Feb/11 09:47 PM   Updated: 18/Feb/11 12:54 PM   Resolved: 18/Feb/11 12:54 PM
Component/s: admin
Affects Version/s: 3.1_b40
Fix Version/s: None

Time Tracking:
Not Specified

Environment:

mac os x 10.6.6


Tags:
Participants: jclingan, Jennifer Chou, Tim Quinn and Tom Mueller


 Description  « Hide

I ran export-sync-bundle on a relatively clean install (just one cluster created). Unzipping the bundle seems fine. For example, domain.xml looks as it should. However, running "unzip -t" gives a warning/error on all files (output below). Not sure if this is an issue, but it is worth bringing up.

Output of "unzip -t mybundle.zip"


testing: config/domain.xml bad extra-field entry:
EF block length (30056 bytes) exceeds remaining EF data (183 bytes)
testing: config/ bad extra-field entry:
EF block length (30056 bytes) exceeds remaining EF data (183 bytes)
testing: config/admin-keyfile bad extra-field entry:
EF block length (30056 bytes) exceeds remaining EF data (183 bytes)
testing: config/cacerts.jks bad extra-field entry:
EF block length (30056 bytes) exceeds remaining EF data (183 bytes)
testing: config/default-web.xml bad extra-field entry:
EF block length (30056 bytes) exceeds remaining EF data (183 bytes)
testing: config/domain-passwords bad extra-field entry:
EF block length (30056 bytes) exceeds remaining EF data (183 bytes)
testing: config/keyfile bad extra-field entry:
EF block length (30056 bytes) exceeds remaining EF data (183 bytes)
testing: config/keystore.jks bad extra-field entry:
EF block length (30056 bytes) exceeds remaining EF data (183 bytes)
testing: config/login.conf bad extra-field entry:
EF block length (30056 bytes) exceeds remaining EF data (183 bytes)
testing: config/server.policy bad extra-field entry:
EF block length (30056 bytes) exceeds remaining EF data (183 bytes)
testing: config/sun-acc.xml bad extra-field entry:
EF block length (30056 bytes) exceeds remaining EF data (183 bytes)
testing: config/wss-server-config-1.0.xml bad extra-field entry:
EF block length (30056 bytes) exceeds remaining EF data (183 bytes)
testing: config/wss-server-config-2.0.xml bad extra-field entry:
EF block length (30056 bytes) exceeds remaining EF data (183 bytes)
testing: docroot/index.html bad extra-field entry:
EF block length (30056 bytes) exceeds remaining EF data (183 bytes)
testing: config/cluster1-config/docroot/ bad extra-field entry:
EF block length (30056 bytes) exceeds remaining EF data (183 bytes)
testing: config/cluster1-config/lib/ bad extra-field entry:
EF block length (30056 bytes) exceeds remaining EF data (183 bytes)
testing: config/cluster1-config/logging.properties bad extra-field entry:
EF block length (30056 bytes) exceeds remaining EF data (183 bytes)



Tom Mueller added a comment - 04/Feb/11 08:00 AM

Just curious - why are you unzipping the output from export-sync-bundle. The output is supposed to be an opaque archive that is passed to import-sync-bundle.

The manual page for export-sync-bundle doesn't actually say that the archive uses ZIP format. The only indication that the output is a ZIP file is in the example which uses ".zip" as the suffix for the output file.

I would recommend resolving this as "won't fix", but will leave that decision to Jennifer.


Tim Quinn added a comment - 04/Feb/11 08:50 AM

Just a quick note.

If I recall correctly, the sync bundle is created using the Payload implementation. These classes use the (published and supported) "extra" data feature of zip files to store additional information for each zip entry. We use the published Java API on ZipEntry to store and retrieve that extra data as a byte[]. Perhaps zip -t does not like binary data there??


jclingan added a comment - 04/Feb/11 09:27 AM

As to why I ran unzip, I just wanted to see what was in the bundle (curiosity). I ran "diff" on domain.xml with the original and the bundled, and they were the same. I just wanted to bring this to engineering's attention "just in case".


Tom Mueller added a comment - 18/Feb/11 12:54 PM

Marking as "won't fix".