Hi,
There is my 2 cents:
1. Using Database for logging will raise performance issue.
2. Using persistent JMS
with (persistent store == database) will raise performance issue
with (persistent store == file) has no advantage on file
logging
3. Using non-persistent JMS has no advantages on file logging(FL), but
still have a performance issue comparing with FL.
So use file logging and enjoy :-).
<IMHO>
The usage of a database makes sense if the information is
important for your customers and you plan to to show the data to
customers.
For daily development needs file logging + perl/sed/vim is enough,
even on cluster environment.
</IMHO>
Tuesday, September 30, 2003, 3:37:53 PM, you wrote:
VRRC> I have already made it clear accessing a JMS Queue for
VRRC> logging purposes is not advisable..
VRRC> -----Original Message-----
VRRC> From: Igor Cunko [mailto:icunko@(protected)]
VRRC> Sent: Tuesday, September 30, 2003 4:39 PM
VRRC> To: J2EEPATTERNS-INTEREST@(protected)
VRRC> Subject: Re: How does ejbs do logging?
VRRC> If that is your concern make JMS to use persistent store. That way you will
VRRC> not lose any messages.
VRRC> Igor
>> -----Original Message-----
>> From: Vadlamudi, Ranga Rao (Cognizant)
>> [mailto:VRanga@(protected)]
>> Sent: Tuesday, September 30, 2003 1:39 AM
>> To: J2EEPATTERNS-INTEREST@(protected)
>> Subject: Re: How does ejbs do logging?
>>
>> But still there is a risk as we are holding the messages in memory before
>> writing to file for sometime if the server crashes or down then we will
>> loose the messages.
>>
>> -----Original Message-----
>> From: Dhiren Mehta [mailto:dhirenm@(protected)]
>> Sent: Tuesday, September 30, 2003 10:39 AM
>> To: J2EEPATTERNS-INTEREST@(protected)
>> Subject: Re: How does ejbs do logging?
>>
>>
>> Hi,
>>
>> You can use Log4J Async Appender. This appends the log (text) file in
>> async. mode and does not block the caller, which drastically improves the
>> performance.
>>
>>
>>
>> -----Original Message-----
>> From: Vadlamudi, Ranga Rao (Cognizant)
>> [mailto:VRanga@(protected)
>> ent: Monday, September 29, 2003 5:44 PM
>> To: J2EEPATTERNS-INTEREST@(protected)
>> Subject: Re: How does ejbs do logging?
>>
>> << File: InterScan_Disclaimer.txt >> Accessing JMS Queue for logging will
>> also create performance problems better to write a memory Queue instead of
>> JMS Queue
>>
>> -----Original Message-----
>> From: BOWMAN, James [mailto:James.Bowman@(protected)]
>> Sent: Monday, September 29, 2003 4:53 PM
>> To: J2EEPATTERNS-INTEREST@(protected)
>> Subject: Re: How does ejbs do logging?
>>
>>
>> Use log4j by all means. However, you may not use the log4j file appender
>> as
>> this writes to the file system which is not allowed within the EJB
>> container. As an alternative, I am suggesting that you use the log4j JMS
>> appender to write to a JMS queue. You can then have a simple logging
>> server
>> that simply takes messages from the JMS queue and then writes them to the
>> log using either the log4j database or file appender depending upon where
>> you wish to store your log.
>>
>> -----Original Message-----
>> From: Senthil Kumar M [mailto:senthilkumar.ma@(protected)]
>> Sent: 29 September 2003 12:07
>> To: J2EEPATTERNS-INTEREST@(protected)
>> Subject: Re: [J2EEPAT-INT] How does ejbs do logging?
>>
>>
>>
>> If there's something better available like log4j then why do we have to
>> Build a server to replicate the functionalities of an existing one.
>> - senthil
>>
>>
>>
>>
>> "BOWMAN, James"
>> <James.Bowman@(protected):
>> J2EEPATTERNS-INTEREST@(protected)
>> .SLB.COM> cc: (bcc:
>> senthilkumar.ma/Polaris)
>> Sent by: An interest list Subject: Re: How
>> does ejbs do logging?
>> for Sun Java Center J2EE
>> Pattern Catalog
>> <J2EEPATTERNS-INTEREST@(protected)
>> VA.SUN.COM>
>>
>>
>> 09/29/2003 04:24 PM
>> Please respond to An
>> interest list for Sun
>> Java Center J2EE Pattern
>> Catalog
>>
>>
>>
>>
>>
>>
>>
>> Build a logging server that actually performs the database write. This
>> server can then sit on a JMS queue to which your application can send
>> messages to. That way your database writes are performed asynchronously.
>>
>> -----Original Message-----
>> From: Vadlamudi, Ranga Rao (Cognizant)
>> [mailto:VRanga@(protected)]
>> Sent: 29 September 2003 11:54
>> To: J2EEPATTERNS-INTEREST@(protected)
>> Subject: Re: [J2EEPAT-INT] How does ejbs do logging?
>>
>>
>> If we start logging to database then iam sure it will become a performance
>> issue for a high transaction application..
>>
>> -----Original Message-----
>> From: BOWMAN, James [mailto:James.Bowman@(protected)]
>> Sent: Monday, September 29, 2003 3:44 PM
>> To: J2EEPATTERNS-INTEREST@(protected)
>> Subject: Re: How does ejbs do logging?
>>
>>
>> Log to the database. Accessing the file system is not allowed within the
>> EJB container. If you really wish to have a log file, the code that
>> writes
>> to the file must run outside of the container. EJBs can then make calls
>> to
>> this "logging server" using RMI, sockets or JMS.
>>
>> -----Original Message-----
>> From: peng wang [mailto:wp0@(protected)]
>> Sent: 26 September 2003 15:56
>> To: J2EEPATTERNS-INTEREST@(protected)
>> Subject: [J2EEPAT-INT] How does ejbs do logging?
>>
>>
>> Hi,
>>
>> I heard of the ejbs cannot access local file system,
>> is it true? if true, I wonder how ejbs do logging
>> into files such as printing debug info.
>>
>> In addition, if there are two session beans which are
>> packed in two different jar files, the two jar files
>> are deployed within one same ejb container. Can one
>> session call the other by using local interface?(The
>> local interface has been implemented.)
>>
>> Thanks for help!
>>
>> __________________________________
>> Do you Yahoo!?
>> The New Yahoo! Shopping - with improved product search
>> http://shopping.yahoo.com
>>
>> ====================================================================
>> Companion Site: http://www.corej2eepatterns.com
>> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
>> List Archive:
>> http://archives.java.sun.com/archives/j2eepatterns-interest.html
>> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
>> listserv@(protected)
>>
>> ---
>> Incoming mail is certified Virus Free.
>> Checked by AVG anti-virus system (http://www.grisoft.com).
>> Version: 6.0.518 / Virus Database: 316 - Release Date: 11/09/2003
>>
>> ====================================================================
>> Companion Site: http://www.corej2eepatterns.com
>> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
>> List Archive:
>> http://archives.java.sun.com/archives/j2eepatterns-interest.html
>> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
>> listserv@(protected)
>>
>> ====================================================================
>> Companion Site: http://www.corej2eepatterns.com
>> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
>> List Archive:
>> http://archives.java.sun.com/archives/j2eepatterns-interest.html
>> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
>> listserv@(protected)
>>
>> ---
>> Incoming mail is certified Virus Free.
>> Checked by AVG anti-virus system (http://www.grisoft.com).
>> Version: 6.0.518 / Virus Database: 316 - Release Date: 11/09/2003
>>
>> ====================================================================
>> Companion Site: http://www.corej2eepatterns.com
>> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
>> List Archive:
>> http://archives.java.sun.com/archives/j2eepatterns-interest.html
>> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
>> listserv@(protected)
>>
>>
>>
>>
>>
>>
>> ====================================================================
>> Companion Site: http://www.corej2eepatterns.com
>> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
>> List Archive:
>> http://archives.java.sun.com/archives/j2eepatterns-interest.html
>> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
>> listserv@(protected)
>>
>> ---
>> Incoming mail is certified Virus Free.
>> Checked by AVG anti-virus system (http://www.grisoft.com).
>> Version: 6.0.518 / Virus Database: 316 - Release Date: 11/09/2003
>>
>> ====================================================================
>> Companion Site: http://www.corej2eepatterns.com
>> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
>> List Archive: http://archives.java.sun.com/archives/j2eepatterns-
>> interest.html
>> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
>> listserv@(protected)
>>
>> ====================================================================
>> Companion Site: http://www.corej2eepatterns.com
>> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
>> List Archive: http://archives.java.sun.com/archives/j2eepatterns-
>> interest.html
>> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
>> listserv@(protected)
>>
>>
>>
>>
>> MASTEK
>> "Making a valuable difference"
>> Mastek in NASSCOM's 'India Top 20' Software Service Exporters List.
>> In the US, we're called MAJESCO
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Opinions expressed in this e-mail are those of the individual and not that
>> of Mastek Limited, unless specifically indicated to that effect. Mastek
>> Limited does not accept any responsibility or liability for it. This e-
>> mail and attachments (if any) transmitted with it are confidential and/or
>> privileged and solely for the use of the intended person or entity to
>> which it is addressed. Any review, re-transmission, dissemination or other
>> use of or taking of any action in reliance upon this information by
>> persons or entities other than the intended recipient is prohibited. This
>> e-mail and its attachments have been scanned for the presence of computer
>> viruses. It is the responsibility of the recipient to run the virus check
>> on e-mails and attachments before opening them. If you have received this
>> e-mail in error, kindly delete this e-mail from all computers.
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> ====================================================================
>> Companion Site: http://www.corej2eepatterns.com
>> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
>> List Archive: http://archives.java.sun.com/archives/j2eepatterns-
>> interest.html
>> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
>> listserv@(protected)
>>
>> ====================================================================
>> Companion Site: http://www.corej2eepatterns.com
>> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
>> List Archive: http://archives.java.sun.com/archives/j2eepatterns-
>> interest.html
>> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
>> listserv@(protected)
VRRC> ====================================================================
VRRC> Companion Site: http://www.corej2eepatterns.com
VRRC> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
VRRC> List Archive:
VRRC> http://archives.java.sun.com/archives/j2eepatterns-interest.html
VRRC> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
VRRC> ====================================================================
VRRC> Companion Site: http://www.corej2eepatterns.com
VRRC> J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
VRRC> List Archive:
VRRC> http://archives.java.sun.com/archives/j2eepatterns-interest.html
VRRC> Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
--
Best regards,
Anton mailto:achistyakov@(protected)
...Avoid reality at all costs.
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
