Hello Friends
have u configured tomcat with log4j concept
Could you include the contents of your log4j.properties file.
2) Are you 100% sure that the trio
- LogManager.shutdown();
- java.beans.Introspector.flushCaches();
- LogFactory.releaseAll();java.beans.Introspector.flushCaches()
real
Hi,
I am using axis too and am able to deploy it to a
Tomcat5.0.29 with minimal issue. I noticed you have a
META-INF/services/org.apache.axis.EngineConfigurationFactory
which does not exist on the axis 1.1 I am using.
Isnt it this META-INF/services something to do with
EJB? I dont think Tom
Thank you for the reply. I tried your method with a little twist. I
cannot call LogManager.shutdown() because "shutdown()" was not there.
So I called LogManager.getInstance().reset() instead. However, doing
all the steps you listed without the shutdown did not help. Please note
that I actu
Hi,
I am using Axis 1.2. I am not sure how that thing get there. It's
probably something to do with the log4j thing. I use Tomcat 5.5.4.
Please look at my reply to deepak shripat mane's message for more
information.
Thanks,
vh.
sven morales wrote:
Hi,
I am using axis too and am able to
This is really strange. With standalone version, and identical webapp
(and same log4j's property file) to the embedded version. Mostly the
same preloaded libraries. For the webapp's libraries, they're the
same. It's a copy and pasted over. However, the standalone can stop
and start the app
I have some luck out of this. The problem happens with the Admin
Servlet, not AxisServlet. So, what I did was disabled this
AdminServlet, and I am back to business for now.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
ist
>Subject: Re: Unnable to redeploy an axis web app
>
>
>I have some luck out of this. The problem happens with the Admin
>Servlet, not AxisServlet. So, what I did was disabled this
>AdminServlet, and I am back to business for now.
>
>-
