[JOB] Junior Mod_Perl Developer - New York City
(Note: Address to send resumes to is at bottom of this description; any resumes sent to my personal address will be ignored per company policy) TheMuniCenter is seeking an Apache/mod_perl developer to work on its next generation bond trading system. We are seeking an intelligent, dynamic candidate capable of thinking outside of the box, working under stress and meeting deadlines. The ideal candidate should have demonstrable project experience working with Apache/mod_perl. TheMuniCenter is NOT ANOTHER DOT COM! We have an established, award winning bond trading system backed by some of the biggest players in the Financial Industry. We are looking for another developer to help bring us to the next level! We are seeking someone with all or most of the following: - In depth knowledge of Perl programming, with recent experience using 5.6 or higher in projects - A reasonable understanding of regular expressions and their usage. - Solid knowledge of Apache and its configuration and usage. - Reasonable knowledge of mod_perl. This includes the API, pitfalls and benefits. - Good programming skills. These include logic, reasoning, problem solving and proper application design. - Web application development experience. This includes a fair knowledge of HTML (recent versions [4.x) and JavaScript, as well as good UI design. - Knowledge of SQL. - Knowledge of Perl's DBI libraries for Database access. In addition, we are always seeking candidates who also have the following skills on top of those listed above: - Java (Applets, servlets, JSP) - J2EE (EJB) - Weblogic 6 - Fixed Income Experience (Municipal Corporate bonds, especially!) - Database Experience - Sybase Oracle. Do you have what it takes to join one of the most dynamic development teams on Wall Street? Send resumes, with cover letter to [EMAIL PROTECTED] Serious applicants ONLY!
RE: [JOB] Junior Mod_Perl Developer - New York City
No, I believe I said 'outside of the box' =) -Original Message- From: Levon Barker [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 03, 2002 1:58 PM To: [EMAIL PROTECTED] Subject: RE: [JOB] Junior Mod_Perl Developer - New York City Did he say out of the box ? -Original Message- From: Brendan W. McAdams [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 03, 2002 1:50 PM To: [EMAIL PROTECTED] Subject: [JOB] Junior Mod_Perl Developer - New York City (Note: Address to send resumes to is at bottom of this description; any resumes sent to my personal address will be ignored per company policy) TheMuniCenter is seeking an Apache/mod_perl developer to work on its next generation bond trading system. We are seeking an intelligent, dynamic candidate capable of thinking outside of the box, working under stress and meeting deadlines. The ideal candidate should have demonstrable project experience working with Apache/mod_perl. TheMuniCenter is NOT ANOTHER DOT COM! We have an established, award winning bond trading system backed by some of the biggest players in the Financial Industry. We are looking for another developer to help bring us to the next level! We are seeking someone with all or most of the following: - In depth knowledge of Perl programming, with recent experience using 5.6 or higher in projects - A reasonable understanding of regular expressions and their usage. - Solid knowledge of Apache and its configuration and usage. - Reasonable knowledge of mod_perl. This includes the API, pitfalls and benefits. - Good programming skills. These include logic, reasoning, problem solving and proper application design. - Web application development experience. This includes a fair knowledge of HTML (recent versions [4.x) and JavaScript, as well as good UI design. - Knowledge of SQL. - Knowledge of Perl's DBI libraries for Database access. In addition, we are always seeking candidates who also have the following skills on top of those listed above: - Java (Applets, servlets, JSP) - J2EE (EJB) - Weblogic 6 - Fixed Income Experience (Municipal Corporate bonds, especially!) - Database Experience - Sybase Oracle. Do you have what it takes to join one of the most dynamic development teams on Wall Street? Send resumes, with cover letter to [EMAIL PROTECTED] Serious applicants ONLY!
Re: Apache::DBI startup failure
I've seen similar behavior with DBD::Sybase; if your SYBASE env variable
is not set or points at an invalid directory Apache starts up but begins
segging every child process over and over again.
I'm not familiar with Postgres but this might point you in the right
direction.
On Thu, 2002-03-14 at 18:09, Doug Silver wrote:
I can't seem to get Apache::DBI to start up properly.
Here's my startup.pl:
#!/usr/bin/perl -w
use strict;
use Apache ();
use Apache::Status ();
use Apache::DBI (); # This *must* come before all other DBI modules!
use Apache::Registry;
use CGI ();
CGI-compile(':all');
use CGI::Carp ();
$Apache::DBI::DEBUG = 2;
Apache::DBI-connect_on_init
(DBI:Pg:dbname=demo;host=localhost, demo, ,
{
PrintError = 1, # warn() on errors
RaiseError = 0, # don't die on error
AutoCommit = 0, # require transactions
}
)
or die Cannot connect to database: $DBI::errstr;
1;
And here's what happens:
[Thu Mar 14 14:28:35 2002] [notice] Apache/1.3.22 (Unix) mod_perl/1.26 PHP/4.1.0
mod_ssl/2.8.5 OpenSSL/0.9.6a configured -- resuming normal operations
13336 Apache::DBI PerlChildInitHandler
13337 Apache::DBI PerlChildInitHandler
13338 Apache::DBI PerlChildInitHandler
13339 Apache::DBI PerlChildInitHandler
13340 Apache::DBI PerlChildInitHandler
[Thu Mar 14 14:28:35 2002] [notice] Accept mutex: flock (Default: flock)
[Thu Mar 14 14:28:35 2002] [notice] child pid 13338 exit signal Segmentation fault
(11)
[Thu Mar 14 14:28:35 2002] [notice] child pid 13339 exit signal Segmentation fault
(11)
[Thu Mar 14 14:28:35 2002] [notice] child pid 13337 exit signal Segmentation fault
(11)
[Thu Mar 14 14:28:35 2002] [notice] child pid 13336 exit signal Segmentation fault
(11)
[Thu Mar 14 14:28:36 2002] [notice] child pid 13340 exit signal Segmentation fault
(11)
If I don't use the connect_on_init stuff, I can run a test script fine with those
exact db parameters.
Any suggestions?
Thanks!
--
~
Doug Silver
Network Manager
Quantified Systems, Inc
~
--
Brendan W. McAdams | [EMAIL PROTECTED]
Senior Applications Developer | (646) 375-1140
TheMuniCenter, LLC | www.themunicenter.com
Always listen to experts. They'll tell you what can't be done, and why.
Then do it.
- Robert A. Heinlein
signature.asc
Description: This is a digitally signed message part
[Fwd: Re: Apache::DBI startup failure]
Weird, although I bet if you had straced the apache processes you would
have seen the File not found.
For some reason I recall DBD Drivers being case sensitive.
On Thu, 2002-03-14 at 20:06, Doug Silver wrote:
Ok, I found it, but this has got to be some kind of bug.
This works:
Apache::DBI-connect_on_init(dbi:pg:demo,demo);
This doesn't:
Apache::DBI-connect_on_init(dbi:Pg:demo,demo);
That's right, putting 'dbi:pg' in lowercase made it work. I looked through
some old newsgroup stuff and saw someone using Postgres had it similar to
that.
Here's some further debugging information for the developers:
perl -v = v5.6.1 on i386-freebsd (FreeBSD 4.4)
# pkg_info |egrep -i dbi|postgres
p5-Apache-DBI-0.88 DBI persistent connection, authentication and authorization
p5-DBD-Pg-1.01 Provides access to PostgreSQL databases through the DBI
p5-DBI-1.20 The perl5 Database Interface. Required for DBD::* modules
postgresql-7.1.3A robust, next generation, object-relational DBMS
-doug
On 14 Mar 2002, Brendan W. McAdams wrote:
I've seen similar behavior with DBD::Sybase; if your SYBASE env variable
is not set or points at an invalid directory Apache starts up but begins
segging every child process over and over again.
I'm not familiar with Postgres but this might point you in the right
direction.
On Thu, 2002-03-14 at 18:09, Doug Silver wrote:
I can't seem to get Apache::DBI to start up properly.
Here's my startup.pl:
#!/usr/bin/perl -w
use strict;
use Apache ();
use Apache::Status ();
use Apache::DBI (); # This *must* come before all other DBI
modules!
use Apache::Registry;
use CGI ();
CGI-compile(':all');
use CGI::Carp ();
$Apache::DBI::DEBUG = 2;
Apache::DBI-connect_on_init
(DBI:Pg:dbname=demo;host=localhost, demo, ,
{
PrintError = 1, # warn() on errors
RaiseError = 0, # don't die on error
AutoCommit = 0, # require transactions
}
)
or die Cannot connect to database: $DBI::errstr;
1;
--
Brendan W. McAdams | [EMAIL PROTECTED]
Senior Applications Developer | (646) 375-1140
TheMuniCenter, LLC | www.themunicenter.com
Always listen to experts. They'll tell you what can't be done, and why.
Then do it.
- Robert A. Heinlein
--
Brendan W. McAdams | [EMAIL PROTECTED]
Senior Applications Developer | (646) 375-1140
TheMuniCenter, LLC | www.themunicenter.com
Always listen to experts. They'll tell you what can't be done, and why.
Then do it.
- Robert A. Heinlein
signature.asc
Description: This is a digitally signed message part
RE: About Apache::DBI
Once you use Apache::DBI; all calls to DBI should transparently use it. You should not have to change any of your other code (connect statements, etc) -Original Message- From: Axel Andersson [mailto:[EMAIL PROTECTED]] Sent: Friday, March 08, 2002 8:51 PM To: modperl Subject: About Apache::DBI Hi Okay, so I read up on Apache::DBI, but I still have a question or two. Specifically, am I supposed to keep my use DBI, DBI-connect(), and everything DBI related and not change a single thing in my source after I've added Apache::DBI-connect_on_init() in startup.pl? Right, I guess that's all. Thanks in advance, Axel Andersson -- [EMAIL PROTECTED] http://www.animanga.nu/morris/ 1. Radiant one, this experience may dawn between two breaths. After breath comes in and just before turning up--the benefience.
Re: Hi
This is a virus. A warning to all who use windoze, dont open the attachment =) On Tue, 2001-12-04 at 16:40, Christopher Rivera wrote: How are you ? When I saw this screen saver, I immediately thought about you I am in a harry, I promise you will love it! -- Brendan W. McAdams | [EMAIL PROTECTED] Senior Applications Developer | (212) 208-9116 TheMuniCenter, LLC | www.themunicenter.com Always listen to experts. They'll tell you what can't be done, and why. Then do it. - Robert A. Heinlein rm -rf /bin/laden; chmod a+rwx /bin/freedom
Re: PerlChildInitHandler
Yup.
(I knew i did since i compiled with EVERYTHING=1).
All handlers lists as Enabled when this script is run.
So ... whats the next step in debugging here?
-brendan
-
Brendan W. McAdams| email: [EMAIL PROTECTED]
Programmer/Systems Administrator | office: (305)377-2880
Plexus InterActive| pager: (305)277-4879
http://www.plexmedia.com | cell phone: (305)401-7313
"Always listen to the experts - they'll tell you what can't be done and why.
Then do it."
-Robert A. Heinlein
- Original Message -
From: "Sean Chittenden" [EMAIL PROTECTED]
To: "Brendan W. McAdams" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, February 14, 2000 12:17 PM
Subject: Re: PerlChildInitHandler
Check to make sure that you compiled in the Init and Exit handlers
into mod_perl.
If you include the following code in a script, you should be able
to figure this out really quick:
require mod_perl;
require mod_perl_hooks;
my @retval = qw(table);
my @list = mod_perl::hooks();
for my $hook (sort @list) {
my $on_off =
mod_perl::hook($hook) ? "bEnabled/b" : "iDisabled/i";
push @retval, "trtd$hook/tdtd$on_off/td/tr\n";
}
push @retval, qw(/table);
print @retval;
Credit goes to Doug MacEachern on the code. Stick that chunket of
code in a script and it should let you know what you have available and
what you don't. ;) --SC
On Mon, 14 Feb 2000, Brendan W. McAdams wrote:
Date: Mon, 14 Feb 2000 12:02:45 -0500
From: Brendan W. McAdams [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: PerlChildInitHandler
I'm having trouble getting apache to even recognise the existance of
PerlChildInitHandler ( and childexithandler it seems as well) .
I've tried declaring my PerlChildInitHandler inside a VirtualHost, in the
main body of the config, and as a push_handler in my startup file [which
is,
i know for a fact, being execed].
no matter what I try, apache is compeltely ignoring this directive.
I've put write to log when initialised traps in the modules that are being
handled on init and they never trip.
I've tried this with both Apache 1.39/modperl1.19 and Apache
1.311/modperl1.21 and no luck
Any assistance would be greatly appreciated.
Brendan
-
Brendan W. McAdams| email: [EMAIL PROTECTED]
Programmer/Systems Administrator | office: (305)377-2880
Plexus InterActive| pager: (305)277-4879
http://www.plexmedia.com | cell phone: (305)401-7313
"Always listen to the experts - they'll tell you what can't be done and
why.
Then do it."
-Robert A. Heinlein
--
Sean Chittenden
[EMAIL PROTECTED]
(408)530-0001
Re: PerlChildInitHandler
Nope.
I'm not seeing it initialised.
nothing in my logs...
I _COULD_ do it in startup but it would defeat purpose.
I'm building persistant database connections with mySQL and Apache::DBI
from everything I've read and deduced, optimally EACH CHILD should be
opening a localised persistant database connection (and leaving any scripts
run under the child to have access to $dbh database handler)
To do this I need the $DBH to be opened, or at the least, initialised, when
the Child starts up.
Consequently, I really need to get the ChildInitHandlers working =)
-brendan
-
Brendan W. McAdams| email: [EMAIL PROTECTED]
Programmer/Systems Administrator | office: (305)377-2880
Plexus InterActive| pager: (305)277-4879
http://www.plexmedia.com | cell phone: (305)401-7313
"Always listen to the experts - they'll tell you what can't be done and why.
Then do it."
-Robert A. Heinlein
- Original Message -
From: "Sean Chittenden" [EMAIL PROTECTED]
To: "Brendan W. McAdams" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, February 14, 2000 12:33 PM
Subject: Re: PerlChildInitHandler
It's a bit harsh, but I'd try something like this just for kicks
to make sure I can get access to the requested Handler.
# In httpd.conf
PerlModule DieOnInit
# In DieOnInit package
package DieOnInit;
sub handler {
warn "Child $$ is going to die in 20 seconds";
sleep(20); # Prevents children from constantly dying and filling up the
# error logs
die "Child dead: $$";
}
1;
#-- End package
I have a variation of this module lying around someplace that
provides me with a sanity check with regards to programming. If the child
dies, then the code is executed and I can plop in my ___ number of lines
of code that weren't being executed earlier. This kind of approach is
pretty top-down, but works when setting apache up... I've had a few
instances where the child _wasn't_ dying because of a config problem
farther up in the conf file.
At any rate, let me know if the handler isn't being executed... and
what you're trying to execute for that matter. Could you use a
PerlRequire directive and place your init stuff in there? --SC
On Mon, 14 Feb 2000, Brendan W. McAdams wrote:
Date: Mon, 14 Feb 2000 12:25:30 -0500
From: Brendan W. McAdams [EMAIL PROTECTED]
To: Sean Chittenden [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: PerlChildInitHandler
Yup.
(I knew i did since i compiled with EVERYTHING=1).
All handlers lists as Enabled when this script is run.
So ... whats the next step in debugging here?
-brendan
-
Brendan W. McAdams| email: [EMAIL PROTECTED]
Programmer/Systems Administrator | office: (305)377-2880
Plexus InterActive| pager: (305)277-4879
http://www.plexmedia.com | cell phone: (305)401-7313
"Always listen to the experts - they'll tell you what can't be done and
why.
Then do it."
-Robert A. Heinlein
- Original Message -----
From: "Sean Chittenden" [EMAIL PROTECTED]
To: "Brendan W. McAdams" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, February 14, 2000 12:17 PM
Subject: Re: PerlChildInitHandler
Check to make sure that you compiled in the Init and Exit handlers
into mod_perl.
If you include the following code in a script, you should be able
to figure this out really quick:
require mod_perl;
require mod_perl_hooks;
my @retval = qw(table);
my @list = mod_perl::hooks();
for my $hook (sort @list) {
my $on_off =
mod_perl::hook($hook) ? "bEnabled/b" : "iDisabled/i";
push @retval, "trtd$hook/tdtd$on_off/td/tr\n";
}
push @retval, qw(/table);
print @retval;
Credit goes to Doug MacEachern on the code. Stick that chunket of
code in a script and it should let you know what you have available and
what you don't. ;) --SC
On Mon, 14 Feb 2000, Brendan W. McAdams wrote:
Date: Mon, 14 Feb 2000 12:02:45 -0500
From: Brendan W. McAdams [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: PerlChildInitHandler
I'm having trouble getting apache to even recognise the existance of
PerlChildInitHandler ( and childexithandler it seems as well) .
I've tried declaring my PerlChildInitHandler inside a VirtualHost, in
the
main body of the config, and as a push_handler in my startup file [which
is,
i know for a fact, being execed].
no matter what I try, apache is compeltely ignoring this directive.
I've put write to log when initialised traps in the modules that are
being
handled on init and they never trip.
I've tried this with both Apache 1.39/modperl1.19 and Apache
1.311/modperl1.21 and no luck
Any assistance would be greatly appreciated.
Brendan
-
Brendan W. McAdams
