Siyaram Singh

Hi Shaurav,
Have you got the solution ?
If you have please share with us. I am also looking same sort things to generate the diffrent log files for diffrent applications, using same code base.

IS IT POSSIBLE TO DO IT AT CONFIG FILE LEVEL ONLY, INSTEAD OF DOING (CHANGING) ANYTHING IN CODE ???


Regards,
SS

Lars,
Thanks a lot !
1. If AsyncAppender is not used, then how log4J writes log event to the file ? It uses any default buffer or It writes one by one event message in log file, I mean one even message = one I/O ???

2 If we use AsyncAppender and setBufferSize(int size).
And Configure Buffer size in log4j.xml.
If set value in setBufferSize(int size) is less than Buffer size in log4j.xml ???
How both are related and what would be the optimum guidlines ???
(default buffer size is set to 128 events)

3. Also I would like to know the actual / practical way to diffrentiate the FATAL, ERROR,INFO.
Is realy FATAL should be used for Business related error ??

Regards,
Siyaram

Hi
From Architecture point of view what could be the best practices to use Log4J. What are diffrent norms we should follow to acheive architectural goal (Performance /scaling, etc), when using Log4J.

How Log4j (Appender)writes event messages to a log file ? It collects certain meessage in buffer and then write in one I/O ?? or For every even log it make one I/O ??

How we can minimise the I/O calls, during Logging??

Regards,
SS

The expiration date is too near ! By the way, what would be the cost ??

Thanks,
SS

We are evaluating our existing application 's logging approch.
Application use WAS 4.0.X , Log4J logging framework, and J2EE (without EJB).
I think log4J is meant only for java applications, not for Application Server, Network Failure and etc.

How we should proceed to evaluate /monitor application server logging approch and ETC.......

Thanks,
SS

Hi
When the user logs in store the userid as a context level varables .


Could you please give some API / method level hints / details how to store user id into Context and again check with incoming user log in, TO not allow the duplicate login oncurrently??

Regards,
SS

Hi Sharad,
Its realy good input points to decide one of the option.

1. Concurrency : If concurrency is too high then database option would be better, instead of putting more more info i servelet context.
But could you tell what could be the upper boundary for concurrency ??? where we should go to database aproach !

2. In case of user second login attempt, which approch would be better ? should Invalidate the first session ?? or
show a login error for the second attempt?
what are justifications for both attempt. I think - show a login error for the second attempt -- is better approach.

But when the user close his browser or Browser get crashed then User needs to wait for session timout. It won't allow before session time out.

What could be the session timeout? 10 minuts or less than this ??

Regards,
SS

In our J2EE application
(Without EJB, IBM HTTP Server 1.3.x, WAS 4.X, DB2-7.X, Struts 1.0, JDK 1.2)

We are using database table to store and maintaine User information. Currently, during the user athentication application allows duplicate user (Same time more than two users with same user ID). We don't want to allow (duplicate user at same time) more than one user with same ID
We want single session to be maintained for one User ID.

What could be the Best approach to deal with this problem.

Solution should be light, simple and less resource consumming.

Thanks in Advance,
SS

In our J2EE application (Without EJB), We are using database table to store and maintaine User information. But during the user athentication It allows the duplicate user (Same time more than two users with same user ID). We don't want to allow (duplicate multiple user same time) more than one user with same ID

What could be the Best approach to deal with this problem.

Solution should be light, simple and less resource consumming.

Thanks in Advance,
SS

But the extra layer of wrapping would impact the performance.
And application will be less performant as compare to directly place the bussiness logic in SLSB.

Regards,

As JDO has been developed using Java Connector Architecture to interact between App Server to Data Source.

If application required to access any Legacy system JDO will do the same job OR still we need Java Connector ??


Regards,
Siyaram

Hi
Is there any optins in WebSphere 5.0 to launch and manage the Deomon Threads like garbage collector, would be used by the application.
Our application needs Online batch job processing. Application would take the client request submission and put it into a FIFO Queue. The expected Deamon Thread will pick and process the request from the Queue, and marked it as processed.

Regards,
Siyaram

Thank U sir ! I will do the same.
Regards,
Siyaram

Hi Kyle,
Thanks a lot for reponse and precise advise ! But the mentioned book is not available in India. Could you please send the PDF or text format of this book.
Thanks & Regards,
Siyaram

Hi Kyle,
What is the concurrent client request limit on single instance in Web Sphere 5.x?
what is Concurrent excecutable threds limit in Websphere 5.0 ?
we are using Websphere 5.x, Linux 8.0, Oracle 9i database, 4 CPU Box, 2048 MB RAM . Application is not is not very very complex . It contains 15 transactional screen and 35 simple queries screen. we don't use distributed option means all data is provided by only local database server.
Our requiremnt is to address 1200 concurrent users !
How many vertical clones should be created for good response time ?
Thanks & Regards,
Siyaram