• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

log4j design consideration

 
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All

I need your thoughts on the placement of log4j files

We have a remote architecture involving 2 enterprise servers. Each of these servers
will host different ejbs comprised of varied business logic.

I want to know for the above what sort of logging mechanism should we adopt.


Should we have a central file where all the logging would take place for
all the components on the 2 app servers.

In this case i would need to do a remote call everytime i need to do a log

or

should we keep a single logging file for each ejb app server so that all
business components in 1 particular app server will have one log file for them


Do post your thoughts on the trade off between the 2 approaches & which 1 will be
ideal for our situation


Thanks
 
Ranch Hand
Posts: 134
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
 
Mahesh Asrani
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Mehul

think you forgot to paste your reply

Bye
 
reply
    Bookmark Topic Watch Topic
  • New Topic