Publish Failed During Serialisation Due To Invalid Character
(Doc ID 1539074.1)
Last updated on APRIL 03, 2024
Applies to:
Oracle WebCenter Sites - Version 11.1.1.6.1 and laterInformation in this document applies to any platform.
Symptoms
Publish failed during serialisation phase with the following errors:
Packager (LOCAL): 26%. Last known action: EXCEPTION: com.fatwire.cs.core.realtime.DataException: Exception serializing item ASSET:Media_C:1230987654321
at com.fatwire.realtime.DefaultSerializerImpl.execute(DefaultSerializerImpl.java:300)
at com.fatwire.realtime.PubDataPackager.execute(PubDataPackager.java:80)
at com.fatwire.realtime.PubMain._standardPublish(PubMain.java:322)
at com.fatwire.realtime.PubMain.execute(PubMain.java:107)
at org.apache.jsp.jsp.cs_005fdeployed.OpenMarket.Xcelerate.PrologActions.Publish.AdvPub.PublishApprovedAssets_jsp._jspService(PublishApprovedAssets_jsp.java:98)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
[...]
Caused by: java.lang.NullPointerException
at com.fatwire.realtime.BinaryAssetSerializerImpl._serialize(BinaryAssetSerializerImpl.java:63)
at com.fatwire.realtime.BinaryAssetSerializerImpl.execute(BinaryAssetSerializerImpl.java:44)
at com.fatwire.realtime.DefaultSerializerImpl.execute(DefaultSerializerImpl.java:296)
... 92 more
and
2013-03-05 16:44:24.443 [-] [-] Publish failed for approved assets (error number: -508). Data is corrupt: Blob attribute '1239876543210' has empty value for row '1238765432109' in MungoBlobs table.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |