There is a DTD for core elements but alternate elements can be added (like rewritepolicy)...you won't find rewritepolicy in the DTD.
Can you add -Dlog4j.debug=true to your appender-side java command, and paste the output? Thanks Scott On Thu, Sep 15, 2011 at 10:38 AM, Konduru, Geetha <[email protected]>wrote: > Where can I find XMLschema file for log4j XML configuration file???? > > > Thank U, > VGSS > > -----Original Message----- > From: Scott Deboy [mailto:[email protected]] > Sent: Wednesday, September 14, 2011 4:51 PM > To: Log4J Users List > Subject: Re: log4j----Edit the event received > > Missed the end param on the nested properties param...not sure about > case of > RewritePolicy node name..may be rewritePolicy. > > <appender name="rewrite" > class="org.apache.log4j.rewrite.RewriteAppender"> > <appender name="socket" class="org.apache.log4j.net.SocketAppender"> > <param name="Port" value="12346"/> > <param name="RemoteHost" value="localhost"/> > <param name="Application" value="app1"/> > <param name="ReconnectionDelay" value="60000"/> > <param name="Threshold" value="ALL"/> > </appender> > <RewritePolicy name="propertyPolicy" > class="org.apache.log4j.rewrite.PropertyRewritePolicy"> > <param name="properties" > value="somepropertyname1=somepropertyvalue1,somepropertyname2=someproper > tyvalue2"/> > </RewritePolicy> > </appender> > > > On Wed, Sep 14, 2011 at 1:48 PM, Konduru, Geetha > <[email protected]>wrote: > > > Thank U... > > > > -----Original Message----- > > From: Scott Deboy [mailto:[email protected]] > > Sent: Wednesday, September 14, 2011 4:31 PM > > To: Log4J Users List > > Subject: Re: log4j----Edit the event received > > > > remoteSourceInfo contains the connected port: > > > > hostName = socket.getInetAddress().getHostName(); > > remoteInfo = hostName + ":" + socket.getPort(); > > > > On Wed, Sep 14, 2011 at 1:23 PM, Konduru, Geetha > > <[email protected]>wrote: > > > > > yes, I got them > > > > > > how are "hostname" and " log4j.remoteSourceInfo" different from > each > > > other.... > > > > > > thank U > > > VGSS > > > > > > > > > -----Original Message----- > > > From: Scott Deboy [mailto:[email protected]] > > > Sent: Wednesday, September 14, 2011 4:15 PM > > > To: Log4J Users List > > > Subject: Re: log4j----Edit the event received > > > > > > The SocketReceiver adds two properties to each event: > > > hostname > > > log4j.remoteSourceInfo > > > > > > With the developer snapshot of Chainsaw you should see those as > > > individual > > > columns in the table. If they aren't displayed by default you can > > > enable > > > them via the tab preferences menu (select Columns). > > > > > > Scott > > > > > > On Wed, Sep 14, 2011 at 12:38 PM, Konduru, Geetha > > > <[email protected]>wrote: > > > > > > > Hi, > > > > > > > > > > > > > > > > What I am looking for is, every event received by SocketAppender, > > > even > > > > before it send to remote machine, it must append to the event(on > > > which > > > > log4j is running). > > > > > > > > > > > > > > > > Can any one please tell me a solution for this. > > > > > > > > > > > > > > > > Example: if application(running on machine HOSTNAME) logs message > "I > > > am > > > > a Logging event", than SOCKET APPENDER must send following to > REMOTE > > > > machine(or SOCKET RECEIVER on Remote machine should receive > > following > > > as > > > > log message). > > > > > > > > > > > > > > > > "HOSTNAME:I am a Logging event" > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thank U, > > > > > > > > VGSS > > > > > > > > > > ********************************************************************** > > > > This e-mail message and any attachments contain confidential > > > information > > > > from Medco. If you are not the intended recipient, you are hereby > > > notified > > > > that disclosure, printing, copying, distribution, or the taking of > > any > > > > action in reliance on the contents of this electronic information > is > > > > strictly prohibited. If you have received this e-mail message in > > > error, > > > > please immediately notify the sender by reply message and then > > delete > > > the > > > > electronic message and any attachments. > > > > > > > > > > > ********************************************************************** > > > This e-mail message and any attachments contain confidential > > information > > > from Medco. If you are not the intended recipient, you are hereby > > notified > > > that disclosure, printing, copying, distribution, or the taking of > any > > > action in reliance on the contents of this electronic information is > > > strictly prohibited. If you have received this e-mail message in > > error, > > > please immediately notify the sender by reply message and then > delete > > the > > > electronic message and any attachments. > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > > ********************************************************************** > > This e-mail message and any attachments contain confidential > information > > from Medco. If you are not the intended recipient, you are hereby > notified > > that disclosure, printing, copying, distribution, or the taking of any > > action in reliance on the contents of this electronic information is > > strictly prohibited. If you have received this e-mail message in > error, > > please immediately notify the sender by reply message and then delete > the > > electronic message and any attachments. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > ********************************************************************** > This e-mail message and any attachments contain confidential information > from Medco. If you are not the intended recipient, you are hereby notified > that disclosure, printing, copying, distribution, or the taking of any > action in reliance on the contents of this electronic information is > strictly prohibited. If you have received this e-mail message in error, > please immediately notify the sender by reply message and then delete the > electronic message and any attachments. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
