, Edward [mailto:[EMAIL PROTECTED]
Sent: Friday, May 12, 2006 1:55 PM
To: Log4J Users List
Subject: RE: CustomSQLDBReceiver not working correctly. Where can I find
the code for it?
After getting the source and putting in debug statements I found the
problem. The code is not trimming the
h
"log4jid" and claiming it was not a match. When I removed the space
everything worked fine.
-Original Message-
From: Mostrom, Edward [mailto:[EMAIL PROTECTED]
Sent: Friday, May 12, 2006 2:08 PM
To: Log4J Users List
Subject: RE: CustomSQLDBReceiver not working correctly. Where c
PM
To: Log4J Users List
Subject: RE: CustomSQLDBReceiver not working correctly. Where can I find
the code for it?
The SVN repository was down for a couple of days. Here's a link to the
latest revision of CustomSQLDBReceiver. As always, patches are always
appreciated!
http://svn.apache.org/v
The SVN repository was down for a couple of days. Here's a link to the
latest revision of CustomSQLDBReceiver. As always, patches are always
appreciated!
http://svn.apache.org/viewcvs.cgi/logging/log4j/trunk/src/java/org/apach
e/log4j/db/CustomSQLDBReceiver.java?view=markup
Scott
-Original
Please feel free to contribute a patch resolving your issue.
-Original Message-
From: Tan Kah Siong [mailto:[EMAIL PROTECTED]
Sent: Fri 6/24/2005 4:41 PM
To: Log4J Users List
Cc:
Subject:RE: CustomSQLDBreceiver MDC
Changing delimiters is not the resolution to the
Changing delimiters is not the resolution to the
problem. Since there could be a chance that any
delimiters can be in a retrieved string.
--- Scott Deboy <[EMAIL PROTECTED]> wrote:
> Access the source from CVS and modify the receiver
> to use a different delimiter.
>
>
> -Original Message
Access the source from CVS and modify the receiver to use a different delimiter.
-Original Message-
From: Tan Kah Siong [mailto:[EMAIL PROTECTED]
Sent: Fri 6/24/2005 2:34 AM
To: [email protected]
Cc:
Subject:CustomSQLDBreceiver MDC
Hi,
The current implem
We should do another 1.3 alpha release around the same time we release
1.2.11.
-Mark
> -Original Message-
> From: Scott Deboy [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 14, 2005 6:34 PM
> To: Log4J Users List
> Subject: RE: CustomSQLDBReceiver
>
> CustomSQLDB
Scott
> >
> > -Original Message-----
> > From: Tan Kah Siong [mailto:[EMAIL PROTECTED]
> > Sent: Tue 6/14/2005 8:46 PM
> > To: Log4J Users List
> > Cc:
> > Subject:RE: CustomSQLDBReceiver
> > Hi,
> >
> > i
xml, then re-run the db target.
>
> Scott
>
> -Original Message-
> From: Tan Kah Siong [mailto:[EMAIL PROTECTED]
> Sent: Tue 6/14/2005 8:46 PM
> To: Log4J Users List
> Cc:
> Subject: RE: CustomSQLDBReceiver
> Hi,
>
> i recompiled a log4j-db (ant
the log4j 1.3alpha6 tar.gz with this new build.xml, then re-run the db target.
Scott
-Original Message-
From: Tan Kah Siong [mailto:[EMAIL PROTECTED]
Sent: Tue 6/14/2005 8:46 PM
To: Log4J Users List
Cc:
Subject: RE: CustomSQLDBReceiver
Hi,
i recompiled a log4j-db
t; Sent: Tue 6/14/2005 6:00 PM
> To: Log4J Users List
> Cc:
> Subject: RE: CustomSQLDBReceiver
> I had followed the instructions to loading the
> config
> file. I had the error encountered attached.
> It seems that the SQLreceiver class cannot be found.
>
> Th
00 PM
To: Log4J Users List
Cc:
Subject: RE: CustomSQLDBReceiver
I had followed the instructions to loading the config
file. I had the error encountered attached.
It seems that the SQLreceiver class cannot be found.
The program was run using the provided chainsaw.bat.
Thanks
---
I had followed the instructions to loading the config
file. I had the error encountered attached.
It seems that the SQLreceiver class cannot be found.
The program was run using the provided chainsaw.bat.
Thanks
--- Scott Deboy <[EMAIL PROTECTED]> wrote:
> 1. The file-load menu items are provide
1. The file-load menu items are provided as a way to process a log file created
by a file appender configured to use XMLLayout.
Instead, configure Chainsaw this way:
Open Chainsaw
Select the view-show application wide preferences menu
In the 'automatic configuration url' field at the bottom, sp
EMAIL PROTECTED]
Sent: Sat 12/18/2004 4:13 PM
To: Log4J Users List
Cc:
Subject: RE: CustomSQLDBReceiver in Chainsaw
At 02:50 PM 12/18/2004, Scott Deboy wrote:
>A couple of things:
>
>Are you running Chainsaw through webStart?
>
>Your db driver jar must be in the classp
At 02:50 PM 12/18/2004, Scott Deboy wrote:
A couple of things:
Are you running Chainsaw through webStart?
Your db driver jar must be in the classpath - jre/lib/ext if using WebStart.
The JavaDoc describe some restrictions that are in place to use
CustomSQLDBReceiver:
- You must have an identity c
At 02:50 PM 12/18/2004, Scott Deboy wrote:
A couple of things:
Are you running Chainsaw through webStart?
no
Your db driver jar must be in the classpath - jre/lib/ext if using WebStart.
I added it to the batch file that runs chainsaw, but jre/lib/ext may work
better...
The JavaDoc describe some r
A couple of things:
Are you running Chainsaw through webStart?
Your db driver jar must be in the classpath - jre/lib/ext if using WebStart.
The JavaDoc describe some restrictions that are in place to use
CustomSQLDBReceiver:
- You must have an identity column and specify that field as the IDFi
19 matches
Mail list logo