On 7/5/07, Todd Finney <[EMAIL PROTECTED]> wrote:
With due respect, Perrin, I disagree with the (common, unfortunately) belief that a lack of an active release cycle indicates that a package is somehow unsuitable. Sometimes, that just means that it's done.
Sure, but the real problem is that no one else is using it anymore, so it's hard to get help with it.
If I comment out the line '$rate_request->submit() or die $rate_request->user_error();', I get the hello world output as expected. If I do not comment out that line, I get no output, and my logs say this: [Thu Jul 5 15:38:06 2007] [notice] Apache/1.3.37 (Unix) PHP/4.4.7 mod_perl/1.30 configured -- resuming normal operations [Thu Jul 5 15:38:06 2007] [notice] Accept mutex: sysvsem (Default: sysvsem) [Thu Jul 5 15:38:13 2007] [notice] child pid 1013 exit signal Segmentation fault (11)
If you can get a stacktrace, someone may be able to help you find where the problem is. My shot in the dark is that you either upgraded perl and didn't recompile something, or mod_perl is not using the same perl that ePerl is. It seems to be a problem between Business::Shipping and the perl that mod_perl is using. It may actually be an issue with an SSL socket library that Business::Shipping uses. - Perrin
