Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Newbie Perl CGI Help

Status
Not open for further replies.

rcampbel

Programmer
Mar 7, 2008
3
US
I have been thrown into using perl at work recently, and while doing so I have come across a glitch that I can't seems to figure out how to fix.

I'm working on a cgi that query's a database and returns the information in the form of an HTML Table. The script works fine from the command line but when it is ran over the Apache Web Server is freezes on the 260th row of the HTML Table, where there is supposed to be 344 rows in the table.

Would this possibly be caused by limitation set in the apache config for perl?

Any suggestions would be nice since the solution has be eluding me for a couple of weeks now.
 
Possibly a time out ? How long does it run for?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[noevil]
Travis - Those who say it cannot be done are usually interrupted by someone else doing it; Give the wrong symptoms, get the wrong solutions;
 
It will run till you kill the perl process for it.
 
How is your program put together?
Gather data into an array/hash, then output, or build the output after each DB fetch?

Have you tried a few debug messages to a logfile or to screen?

Paul
------------------------------------
Spend an hour a week on CPAN, helps cure all known programming ailments ;-)
 
It is built after each db fetch. and i have tried both methods for debugging. With printing more information to the screen, less of the original non-error checking information showed up(
example: original:
the blue bird flew far.
this is not the end of the
with test text:
the blue bird flew far. Test 1
this is not the
). And with the log file there are no errors that i could find when i log all the sql calls and their returned status since that was my first place i looked when this started.

rcampbel
 
Had a similar problem which turned out to be a stray speech mark in the data and Perl objected to it at display time.
Does it always die on row 260?
Try stopping it at row 259 and see if it complains.
Try ignoring row 260 and see if it complains.
Have you tried returning plain text instead of HTML?

Keith
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top