I haven't been able to figure out how to print out the headers to see whether there are too many. There really isn't much before the method: 

BEGIN {
use Log::Log4perl qw(:easy);

Log::Log4perl->easy_init(
        {
        file  => ">> /tmp/uiv2_logfile.txt",
        level => $INFO,
        },
  );

 $SIG{__DIE__} = sub {
        if($^S) {
            # We're in an eval {} and don't want to log
            # this message but catch it later
            return;
        }
        $Log::Log4perl::caller_depth++;
        LOGDIE @_;
    };
}


use strict;
use warnings;
use diagnostics;
use CGI;
use CGI::Carp 'fatalsToBrowser';
use Frontier::RPC2;
use Frontier::Responder;
use DBI;


$ENV{ORACLE_HOME} = '/vol/ora_client/product/10.2.0.2';
my $Schema = "lv";
my $conn_data="/path/to/connection_information";

open (CONNECTION_DATA, $conn_data)
        or die "Failed to open connection data file\n";
my $DBHOST = <CONNECTION_DATA>;
my $DBUSER = <CONNECTION_DATA>;
my $DBPASS = <CONNECTION_DATA>;

close (CONNECTION_DATA);

chomp ($DBHOST); 
chomp ($DBUSER);   
chomp ($DBPASS);

my $res = Frontier::Responder->new(
         methods => {
                  Get_Login =>               \&Get_Login,
                  Get_Last_Name =>           \&Get_Last_Name,
                  Get_First_Name =>          \&Get_First_Name,
                  Get_Dept_No   =>           \&Get_Dept_No,
                  Get_AltEmpNo =>            \&Get_AltEmpNo,
                  Get_Supervisor_Emp_No =>   \&Get_Supervisor_Emp_No,
                  Get_Job_Class =>           \&Get_Job_Class,
                  GetAllByLastName =>        \&GetAllByLastName,
                  GetAllByFirstName =>       \&GetAllByFirstName,
                  GetAllByFirstOrLastName => \&GetAllByFirstOrLastName
+,
                  GetAllByLogin =>           \&GetAllByLogin,
                  GetAllByDept =>            \&GetAllByDept,
                  GetAllByEmpNo =>           \&GetAllByEmpNo,
                  GetAllByDeptExtRoom =>     \&GetAllByDeptExtRoom,
                  GetAllBySupervisor =>      \&GetAllBySupervisor,
                  GetUnixContractorInfo =>   \&GetUnixContractorInfo,
                  GetManagerList     =>      \&GetManagerList,
                  GetPeopleReportingTo =>    \&GetPeopleReportingTo,
                  Get_LoginByEmpNo =>   \&Get_LoginByEmpNo
                 }
        );

print $res->answer;

[download]
: followed by each of the methods. : Any setting of headers is being done inside Frontier. And, as I said, I've tests for each of the methods, and most are working fine. For that matter, if I pass this method a different department number, it works okay. I have 2 departments in my test data - one department has 2 people in it, and the other has 27 people in it. In the live system, there's going to be departments with a couple hundred people in it! I don't see anything obvious in the method that should impact the headers. But I don't know what code is generating the headers, so I can't tell if there's something weird in the CGI environment that's influcing the code in this one case.

In reply to Re^2: Help sought determining why Frontier::Client reporting too many header lines by lvirden
in thread Help sought determining why Frontier::Client reporting too many header lines by lvirden

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.