Posts tagged "Fixpack"

LiveCycle ES2: errors after updating to WebSphere 6.1 Fixpack 35 (6.1.0.35)

Issue

 If you are running LiveCycle ES2 on WebSphere and you update to WAS FP35 (6.1.0.35) you may notice some random errors in the server logs such as:

com.adobe.livecycle.docconverter.client.ValidationException: ALC-CVT-S00-003: Error while validating PDF/A conformance of a document: docConverter.pdf
 at com.adobe.livecycle.docconverter.DocConverterServiceImpl.isPDFA(DocConverterServiceImpl.java:463)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:618)
...
Caused by: com.adobe.internal.pdfm.pdfa.PDFAServiceException: PDFM_I27002: PDF/A Validation was unable to release document 
"{SharedPDFMDocHandle name=docConverter.pdf ID=270667810 getStore={SharedStore name=docConverter.pdf ID=637281788 (faux clone of 1810918384) 
idp=<document state="passive" senderVersion="3" persistent="false" senderPersistent="false" passivated="true" senderPassivated="false" deserialized="true" 
senderHostId="127.0.0.1/4.241.117.208/4.241.117.207/4.241.117.214/4.241.117.234/4.241.117.233/4.241.117.232/4.241.117.236/4.241.117.227/4.241.117.226/
4.241.117.210/4.241.117.216/4.241.117.209/4.241.117.215/4.241.117.218/172.16.252.148/4.239.195.28/4.100.183.28" callbackId="0" senderCallbackId="16" 
callbackRef="com.adobe.idp._IDocumentCallbackStub:IOR:00bdbdbd0000002849444c3a636f6d2f61646f62652f6964702f49446f63756d656e7443616c6c6261636b3a312e30000000000
100000000000000c4000102bd000000194431303041455539313535382e443130302e696e7465726e00bd24550000002c4a4d42490000001071960b49000000000000000000000000000000000000
002400000008000000120000000000000007000000010000001400bdbdbd0501000100000000000101000000000049424d0a0000000800bd00011500000200000026000000020002bdbd49424d040
00000050005020102bdbdbd0000001f0000000400bd0003000000200000000400bd0001000000250000000400bd0003" isLocalizable="true" isTransactionBound="false" 
defaultDisposalTimeout="600" disposalTimeout="600" maxInlineSize="65536" defaultMaxInlineSize="65536" inlineSize="0" contentType="null" length="95543">
<cacheId/><localBackendId><DocumentFileID fileName="/usd/as91558a/work/was-v61/apps/jvmdms.a.1/temp/AdobeDocumentStorage/local/docm1302791768337/1925ec208e7deba285534660215ae481"/>
<localBackendId/><globalBackendId><DocumentFileID fileName="/usd/as91558a/work/was-v61/apps/jvmdms.a.1/native/adobe/jvmdms.a.1.as91558.1/DocumentStorage/docm1302792793931/d570dc3cf31fc6f368d4ee043ede67d5"/>
<globalBackendId/><senderLocalBackendId/><senderGlobalBackendId/><inline/><senderPullServantJndiName>adobe/idp/DocumentPullServant/adobews__957269328</senderPullServantJndiName>
<attributes/></document> pdfDoc=null sharedData=null} getPdfDoc=null getCounted=null refCount=0}".
    at com.adobe.internal.pdfm.pdfa.PDFAService.isPDFA(PDFAService.java:273)
    at com.adobe.internal.pdfm.pdfa.PDFAService.isPDFA(PDFAService.java:193)
    at com.adobe.livecycle.docconverter.DocConverterServiceImpl.isPDFA(DocConverterServiceImpl.java:461)
... 71 more
Caused by: com.adobe.internal.pdfm.NotAPDFException: PDFM_S00025: Document docConverter.pdf of type application/octet-stream is not a PDF.
    at com.adobe.livecycle.assembler.SharedPDFMDocHandle.open(SharedPDFMDocHandle.java:232)
    at com.adobe.internal.pdfm.PDFMDocHandle.acquire(PDFMDocHandle.java:608)
    at com.adobe.internal.pdfm.PDFMDocHandle.acquirePDF(PDFMDocHandle.java:662)
    at com.adobe.internal.pdfm.pdfa.PDFAService.isPDFA(PDFAService.java:217)
... 73 more

The errors that occur depend on what kind of processes and activities you are running in the LiveCycle server, so they could be very different to the above.  The cause of these errors is the WebSphere version and changes that were made to the JDK used by WebSphere.  With WAS FP35 (and probably FP33 and 37) the default behaviour of IgnoreMalformedInput has been set to false, resulting in this change in behaviour for the String constructor in the JDK, causing these issues in LiveCycle.

Solution

 Contact IBM to ensure you have the latest fixes which should contain the solution to this problem as outlined below.  The latest fixes should reset the default behaviour of IgnoreMalformedInput=true.

As an immediate workaround you can manually set the JVM parameter “-Dcom.ibm.IgnoreMalformedInput=true” in your WebSphere administration console.

Additional information

 Information from IBM related to the changes that cause this behaviour and the relevant workaround and fixes:

String constructor does not operate correctly with UTF-16 in Java SR12 FP1

This is a known issue and we had to make changes because of the behavior difference between IBM and OracleJVMs.  The change was to enable conformity with the Oracle JDK for malformed URLs.  To revert back to the original behavior you must add the following  parameter to the “Generic JVM Args” section in the WAS Admin console (instructions in the link below):

-Dcom.ibm.IgnoreMalformedInput=true

Where to set generic JVM arguments in WebSphere Application Server: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21417365

For more details  on the issue please refer to the APAR- IZ80870  (link below).

IZ80870: REPLACING THE ILLEGAL UTF8 BYTE SEQUENCES WITH \UFFFD: http://www-01.ibm.com/support/docview.wss?uid=swg1IZ80870

Please note, this change went into SR 12 FP1, which is why the same behavior does not occur in the previous SDK releases.  Here is the SDK fix list confirming the above APAR went into SR 12 FP1:

http://www.ibm.com/developerworks/java/jdk/aix/j532/fixes.html#SR12FP1

reference: (182181050/2838202)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 9.0/10 (1 vote cast)