Read Error in Expat.pm at Line 464

HI,

I have a script (ipl file) which is trying to make use of Expat.pm and when I execute the script (ipl file) its exists with an error message saying "read error at

\iw-home\iw-perl\site\lib/XML/Parser/Expat.pm line 464."

When I went under

\iw-home\iw-perl\site\lib\XML\Parser\Expat.pm file exists. On line 464, it reads
$result = ParseStream($parser, $ioref, $delim);

and no where in the Perl Module the function ParseStream exists.

I need to check and clarify from your end where does this ParseStream funtion exists? Or is the Expat.pm is corrupted and from where can I find the new PM from ?

Thanks & Regards
Sunil

Interwoven TeamSite Consultant

Find more posts tagged with

Comments

Johnny

I could be wrong but I am pretty sure the expat module uses compile C code for libraries. That would mean, you wouldnt be able to easily find the reference to that routine if its implemented in those compiled libraries.

John Cuiuli

Adam Stoller

It would probably help if you posted (as an attachment) the script you are trying to run *and* the file you are trying to parse -- if possible (if not already the case) simplify both to something small that demonstrates the problem (rather than a real large script and a huge XML file).

Chances are though, that the problem is in the data you are trying to read - some illegal [to-XML] text within the file. One of the things to check for is that the XML file is not riddled with DOS ^M's

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

sunil_j

Hi Fish,

Please find attached the iwcreatefilelist.ipl which I was trying to execute. Its has a Lgging mechanism which logs the execution of the script. The log it generates shows that the script executed till Line 186 and then it stops any further Logs. At the command prompt its shows the error message "read error at

\iw-home\iw-perl\site\lib/XML/Parser/Expat.pm line 464".

Regards
Sunil

Interwoven TeamSite Consultant

Adam Stoller

I hope that isn't the actual script. It contains all sorts of msftedit formatting garbage in it.

Once you remove that cruft - why aren't you using TeamSite::Config::iwgethome() to get the path to IWHOME ?
You should also be able to use $ENV{IWODHOME} to get the pat to OpenDeploy's installation directory - rather than hard-coding both of them.

There are probably a whole bunch of other comments I could make regarding your code - but the crux of it is that I have to guess you're problem is with IWXML.pm's parsing of the in-memory logs - but without seeing what's happening it's difficult to do any further diagnosis.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

fiquebem

Hey Sunil, were you able to find out what it was?

I tried to add bad characters to a file name in the hopes of reproducing a similar error message we're getting ("read error at /usr/interwoven/iw-home/iw-perl/lib/perl5/site_perl/5.005/aix/XML/Parser/Expat.pm line 438, <LOG_FILE_NAME> chunk 56676"), but all I was able to obtain was someting like:

not well-formed at line 11, column 224, byte 2330

Here's the script I was using to test:

use lib "/interwoven/OpenDeployNG/solutions/perl";
use IWXML;
my($xml) = IWXML::GetLogDataFromFile("/tmp/testLog.mf");
my(@f_success) = $xml->GetSucceededFiles();
print "All ready\n";

Then I would manually edit /tmp/testLog.mf, adding "strange" characters to it.

Is the "read error at /usr/interwoven/iw-home/iw-perl/lib/perl5/site_perl/5.005/aix/XML/Parser/Expat.pm" due to lack or memory or what? It's happening once in a blue moon during one of our deployments. We're on OD Version 5.6.0.1.0 Build 26834 Interwoven 20031027 (and TS 5.5.2).

Thanks,

S.

Adam Stoller

If you find it happens again - with a particular deployment - and you're script is intended to read/parse the manifest file (as shown in your example) - make a copy of that manifest file and see if the problem is repeatable just with that file.

If so - it should be significantly easier to debug then.
If not - then it does sound like it might be a memory (or other transient resource) issue of some sort.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com