myService5.init(sc) and myService5.destroy(sc) not called on a
http://alpha1:8080/manager/html/start?path=/axis2 -> start /stop-click in
scope=application
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Key: AXIS2-1990
URL: https://issues.apache.org/jira/browse/AXIS2-1990
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Components: samples, build,site
Affects Versions: 1.1
Environment: Any tomcat platform and version and axis2-1.1.x in
scope=application
Reporter: Josef Stadelmann
Hi Team,
I am running myService5 in application scope! axis2-1.1
Can somone from the axis development team explain what shall happen
when one goes to http://alpha1:8080/manager/html/start?path=/axis2
looks-out for axis2, (just one of a web applications) clicks stop to it,
waits until stop is confirmed in the message window, clicks start and
waits long enougth until confirmation is given in the message window?
a) what shall be seen in the tomact stdout_20070116.log of stop ?
b) what shall be seen in the tomcat stdout_20070116.log on start ?
c) what do you suggest to turn on, to configure to see what happens?
(there are so many loggs)
NORMAL:
myService5.init() is called when the application is deployed in
scope="application" at tomcat start.
I have a log statement in myService5.init(), so init() was called
and this was logged to stdout_20070116.log (well done)
BUT NOTHING was logged in stdout_20070116.log on a stop click in tomcat?
I would expect that myService5.destroy() gets called, just as a way
to safely close down all open user sessions and log em off from legacy
systems, as well as keeping users informed about the break in service.
AND:
I did it while a client was repeadtedly comunicating with a service,
clicking stop and the client got informed about that by an exception
with the soap message indicating that the service is not available.
Well done?!?!?
after the second start from the tomcat gui, I was able to launch the
client and continue!
BUT NOTHING was logged in the tomcat stdout_20070116.log on (re)start ?
I would expect that myservice5.init() is called again and logged.
then I stop again, wait for confirmation, start again, wait for confirmation
and the only service which did make it after a long time was the Library
service from the axis2 examples
all other previously deployed service where no longer available.
Only after a tomcat restart all services where available again.
What is the intention of the tomcat managment interface, tomcat
beeing one of a servlet engine?
Does axis2 support/intercept certain events from the tomcat managment gui?
How robust is axis2 in concert with tomcat managemenet interactions?
Are there any documents to read about that in deep?
Josef.Stadelmann
@winterthur.ch
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
