Hi Kiran,
The notion that an EJB should not spawn threads is a contentious issue
within the EJB community. While indeed the spec says don't do it, many
people would really like to. The justifications vary from quite reasonable
to wildly insane. Many EJB vendors don't strictly forbid it and for many
cases it does no harm.
The only muli-threaded log4j I've been tempted to use for EJBs is the
configureAndWatch feature of various configurators. The thread spawned in
this case is pretty innocuous. I think most EJB vendors are more concerned
with threads that try to exit or threaten their thread pooling.
And speaking of thread pooling, it can spoil the benefit provided by NDC.
I've seen thread pooled CORBA servers like IBM's Component Broker execute
on one thread, wait on a slow DB connection, and awake on a different
thread. So much for your NDC info.
Good luck,
- Paul
Paul Glezen
IT Specialist
WebSphere Engagement Team
Tel: 818 539 3321
[EMAIL PROTECTED]
Hi,
I have a question can log4j be used inside EJB's because EJB's do not
permit to spawn a thread inside container especially features like NDC and
asynchronus appender. It would be great if any one can give clarification
about these aspects
thanks
~Kiran
Kiran Lagisetty
Engineering Team
iSyndicate
[EMAIL PROTECTED]
tel:415-430-3620
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
