chainsaw with CustomSQLDBReceiver

2006-09-13 Thread karen . e . greene
Hi. I was hoping someone may have gotten a chance to look at this error I am getting. I am using CustomSQLDBReceiver with chainsaw. When chainsaw is launched, I am getting a null pointer exception (the details of which are included below). Any thoughts on what the issue might be? I have in

RE: Chainsaw with CustomSQLDBReceiver fo oracle

2005-03-22 Thread Scott Deboy
ver config, change IDField to reference the ID column (unless it's really the msisdn column you're using as the unique id), and get rid of the 'application' and 'hostname' params (they're defined in the sql concat statement above) -Original Message-

RE: Chainsaw with CustomSQLDBReceiver fo oracle

2005-03-22 Thread Ghielli Patrick
CTED] Sent: Wed 3/16/2005 8:14 AM To: '[email protected]' Cc: Subject:Chainsaw with CustomSQLDBReceiver fo oracle Hi, I am trying to configure a CustomSQLDBReceiver for the Oracle DB I am using. After solving some problems mentionned in other postings on this mailing list

RE: Chainsaw with CustomSQLDBReceiver fo oracle

2005-03-22 Thread Ghielli Patrick
l. Regards, Patrick. -Original Message- From: Scott Deboy [mailto:[EMAIL PROTECTED] Sent: vrijdag 18 maart 2005 6:22 To: Log4J Users List Subject: RE: Chainsaw with CustomSQLDBReceiver fo oracle If you can post your table schema and what you have for an 'sql' parameter and we can fi

RE: Chainsaw with CustomSQLDBReceiver fo oracle

2005-03-17 Thread Scott Deboy
l tell you if your sql is executing, because lastID is the highest value of the identity field that the receiver was able to retrieve from the database. -Original Message- From: Ghielli Patrick [mailto:[EMAIL PROTECTED] Sent: Wed 3/16/2005 8:14 AM To: 'log4j-user

Chainsaw with CustomSQLDBReceiver fo oracle

2005-03-16 Thread Ghielli Patrick
Hi, I am trying to configure a CustomSQLDBReceiver for the Oracle DB I am using. After solving some problems mentionned in other postings on this mailing list, I now try set up a working sql statement. The statement I have now results in an error. The event in the chainsaw log describe it as an in