axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William Walsh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AXIS2-5110) Compatibility with WebSphere Application Server on z/OS
Date Thu, 04 Aug 2011 19:10:27 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-5110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079535#comment-13079535
] 

William Walsh commented on AXIS2-5110:
--------------------------------------

I'm following up on the workarounds suggested in AXIS2-4263 and am wondering exactly what
"remove the scripting module" entails.  I've turned off hotdeployment in axis2.xml; but how
do I remove scripting:
* I don't have anything like scripting listed in modules.list.
* I've searched all the jars we use for the classes in axis2-1.5.1-src\modules\scripting\src\org\apache\axis2\scripting
and don't find them.
So, can you please clarify.

(Thanks for correcting me on the APAR versioning.)



> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message