|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
DFDL Serializer Test Exception |
View previous topic :: View next topic |
Author |
Message
|
goffinf |
Posted: Wed Jun 12, 2013 6:41 am Post subject: DFDL Serializer Test Exception |
|
|
Chevalier
Joined: 05 Nov 2005 Posts: 401
|
version: 8.0.0.2
I was running the CSV Sample. Did a 'DFDL Test Parse' and everything was fine. Then did a 'DFDL Test Serialize' and *boom* it throws up the 'Problem Occurred' dialogue allowing you to send an error report to IBM (which I did).
In this case (the CSV Sample) I used both the CSV_2.csv input file and tried using the generated logical instance. The error reported was the same in both cases, although when using the actual CSV_2.csv file the 'Content is not allowed in prolog.' error was reported as well (see below).
Has anyone else experienced this (I 'DFDL Test Serialize' on some other DFDL schemas I had been working on and the same thing occurred even though they parsed successfully also) ?
The reported error(s) were :-
Quote: |
An internal error occurred during: "Running DFDL Serializer".
Serializer state error. Cannot call 'removeServiceTraceListener(IDFDLServiceTraceListener)' while a serialize is in progress.
Content is not allowed in prolog.
Detailed :-
java.lang.IllegalStateException: Serializer state error. Cannot call 'removeServiceTraceListener(IDFDLServiceTraceListener)' while a serialize is in progress.
at com.ibm.dfdl.internal.processor.impl.DFDLUnparser.removeServiceTraceListener(Unknown Source)
at com.ibm.dfdl.internal.ui.parser.SerializerInterface.setupSerializer(Unknown Source)
at com.ibm.dfdl.internal.ui.parser.ParserControl.setupSerializer(Unknown Source)
at com.ibm.dfdl.internal.ui.actions.RunDFDLSerializerAction.internalRun(Unknown Source)
at com.ibm.dfdl.internal.ui.actions.AbstractRunDFDLAction$1.runInWorkspace(Unknown Source)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)
org.xml.sax.SAXParseException: Content is not allowed in prolog.
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at com.ibm.dfdl.internal.ui.utils.XMLUtils.getRootElementFromXMLFile(Unknown Source)
at com.ibm.dfdl.internal.ui.actions.RunDFDLSerializerAction.internalRun(Unknown Source)
at com.ibm.dfdl.internal.ui.actions.AbstractRunDFDLAction$1.runInWorkspace(Unknown Source)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)
eclipse.buildId=unknown
java.fullversion=JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-20110218_76011 (JIT enabled, AOT enabled)
J9VM - 20110218_076011
JIT - r9_20101028_17488ifx3
GC - 20101027_AA
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB
Framework arguments: -showlocation -product com.ibm.etools.msgbroker.tooling.ide
Command-line arguments: -os win32 -ws win32 -arch x86 -showlocation -product com.ibm.etools.msgbroker.tooling.ide -data E:\wbimbv8\migration
|
|
|
Back to top |
|
 |
MrSmith |
Posted: Tue Dec 09, 2014 3:14 am Post subject: |
|
|
 Master
Joined: 20 Mar 2008 Posts: 215
|
I get same dialogue box would be interested to know what the procedure is to fix
Quote: |
Cannot call 'removeServiceTraceListener(IDFDLServiceTraceListener)' while a serialize is in progress. |
_________________ -------- *
“Outside of a dog, a book is man's best friend. Inside of a dog it's too dark to read.” |
|
Back to top |
|
 |
kimbert |
Posted: Tue Dec 09, 2014 5:03 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
MrSmith: which version of the toolkit are you using? _________________ Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
Back to top |
|
 |
shanson |
Posted: Tue Dec 09, 2014 9:21 am Post subject: |
|
|
 Partisan
Joined: 17 Oct 2003 Posts: 344 Location: IBM Hursley
|
One of the posts says 8.0.0.2. I know this has been fixed in the IBM DFDL code base, as I raised the original defect and tested the fix. I am pretty sure that the fix is in the latest 8.0.0.x so please try upgrading. |
|
Back to top |
|
 |
|
|
  |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|