[
https://issues.apache.org/jira/browse/AXIS2-5110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078890#comment-13078890
]
Andreas Veithen commented on AXIS2-5110:
----------------------------------------
The statement in the document from IBM is actually correct, in the sense that
it correctly identifies the root cause of the failure to stop the app server.
However, that doesn't mean that the proper solution is to always use daemon
threads/timers. The proper solution is to make sure that the application
destroys these threads/timers when it is stopped. In your case, as per
AXIS2-4263 it is probably enough to remove the scripting module (unless you use
scripting of course).
PS: Note that the version in APAR IZ94326 actually refers to the JDK version,
not the WebSphere version. The version of the JDK that contained this bug was
actually shipped with WAS 7.0.0.15 and we had a couple of servers that went
down because of this issue. But again, z/OS is a different story...
> Compatibility with WebSphere Application Server on z/OS
> -------------------------------------------------------
>
> Key: AXIS2-5110
> URL: https://issues.apache.org/jira/browse/AXIS2-5110
> Project: Axis2
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 1.5.1
> Environment: WebSphere on z/OS V7
> Reporter: William Walsh
> Priority: Minor
>
> In using Axis2 with WebSphere across multiple platforms we have found that
> once we invoked a web service against Axis2 on WebSphere for z/OS that the
> application server would not shutdown properly. (The architecture on z/OS is
> very different than other platforms - it uses a number of address spaces to
> host WebSphere and the control and servant address spaces would not
> terminate.) We asked IBM about this and it has to do with differences in how
> the JVM is implemented and started by WebSphere on z/OS. The long and the
> short of this is that Timer threads must be defined as daemon to allow
> WebSphere to terminate properly on z/OS.
> I'd like to propose a patch for this and would like to know/confirm:
> Are these classes where I saw non-daemon threads created the appropriate
> places for change?
> /org/apache/axis2/util/threadpool/ThreadPool.java
> /org/apache/axis2/util/threadpool/DefaultThreadFactory.java
> /org/apache/axis2/transport/http/server/DefaultThreadFactory.java
> I would propose adding conditional code to force daemon threads when running
> on z/OS:
> if (System.getProperty("os.name").equals("z/OS")
> Would this be appropriate, or do you feel the check needs to be more
> explicit; also checking for WebSphere?
--
This message is automatically generated by JIRA.
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]
