Hey all,
I am getting a weird error when I start/restart my catalyst server. The error
does not seem to be stopping anything from working from what I can tell.
This is the error:
Tried to write to the catalyst_component_name accessor - is your component
broken or just mad? (Write ignored -
On Tue, Sep 7, 2010 at 10:42 AM, Mesdaq, Ali ames...@websense.com wrote:
Hey all,
I am getting a weird error when I start/restart my catalyst server. The
error does not seem to be stopping anything from working from what I can
tell.
This is the error:
Tried to write to the
Hi,
I am running 3 separate Catalyst (version '5.80022) apps that use a common
(Oracle 11g) database. Each app has a model class which wraps around a
common DBIC schema class, like so.
-
package App1::Model::DB;
use strict;
use base 'Catalyst::Model::DBIC::Schema';
package web::View::JSON;
use strict;
use warnings;
use parent 'Catalyst::View::JSON';
1;
Thanks,
--
Ali Mesdaq (CISSP, GIAC-GREM)
Sr. Security Researcher
Websense Security Labs
http://www.WebsenseSecurityLabs.comhttp://www.websensesecuritylabs.com/
On Tue, Sep 7, 2010 at 12:10 PM, Mesdaq, Ali ames...@websense.com wrote:
package web::View::JSON;
use strict;
use warnings;
use parent 'Catalyst::View::JSON';
1;
Thanks,
--
Ali Mesdaq (CISSP, GIAC-GREM)
Sr. Security Researcher
Hi Simon,
Reducing the number of connections to the database from three to one
will reduce the responsiveness and will definitely hurt when trying to
debug issues (performance, etc). My recommendation is that each
application have at least one unique connection to the database.
jason
On
I'm with Tom on this one. Unless you've narrowed all optimization efforts
and this is all you have left - it could be worth a try.. but as Jason
points out, you may not gain a thing. I'd recommend profiling your code and
tracking down performance issues from that base level. Please post your
