axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William Walsh (JIRA)" <>
Subject [jira] [Commented] (AXIS2-5110) Compatibility with WebSphere Application Server on z/OS
Date Mon, 15 Aug 2011 16:55:27 GMT


William Walsh commented on AXIS2-5110:

Andreas,  Sorry for my confusion on this. Addressing this from the standpoint of more correctly
managing the threads makes sense.  But, since I had compared execution of Axis2 on distributed
vs. z/OS and saw it equivalent in its thread processing I had taken the information IBM had
provided me and chose to pursue a solution in my environment that addresses this based on
those platform differences.

It's not that I'm refusing to do an upgrade, I just don't have time budgeted in the project
to do one right now; we will get to that eventually (this is a non-trivial activity for us).
Since I don't see anything in AXIS2-4263 that looked like it was making specific changes in
this area it would be hard for us to justify taking on a new Axis2 version for this one issue.

Perhaps we should close this JIRA, we can use our temporary fix for the time being, and then
investigate this area further when we take on a later Axis2 version.  How does that sound?

Thanks for your feedback and time on this.

> Compatibility with WebSphere Application Server on z/OS
> -------------------------------------------------------
>                 Key: AXIS2-5110
>                 URL:
>             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/
> /org/apache/axis2/util/threadpool/
> /org/apache/axis2/transport/http/server/
> I would propose adding conditional code to force daemon threads when running on z/OS:
>   if (System.getProperty("").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:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message