Fixes are available
APAR status
Closed as program error.
Error description
Calls to the SIP servlet fail with NullPointerException at com.ibm.ws.webcontainer.filter. WebAppFilterChain.doFilter(WebAppFilterChain.java:140). Problem is due to the web.xml file created when the SIP Converged project is created is missing the required servlet tag. For example: <servlet> <servlet-name>ExampleSipServlet</servlet-name> <display-name>ExampleSipServlet</display-name> <description/> <servlet-class>com.ibm.sample.ExampleSipServlet </servlet-class> <load-on-startup/> </servlet> <servlet-mapping> <servlet-name>ExampleSipServlet</servlet-name> <url-pattern>/ExampleSipServlet</url-pattern> </servlet-mapping>
Local fix
As a work-around, the customer can export the SIP converged project as aSAR file which can be directly deployed to the server. If the project needs to be included in part of the file, then the customer will need to manually add the necessary servlet information into the web.xml file.
Problem summary
**************************************************************** * USERS AFFECTED: All WebSphere Application Server Toolkit * * users of the SIP functionality * **************************************************************** * PROBLEM DESCRIPTION: SIP applications developed in * * WebSphere Application Server Toolkit * * fail to run successfully on a * * WebSphere Application Server runtime. * **************************************************************** * RECOMMENDATION: * **************************************************************** SIP projects (including converged projects) are packaged as Servlet Archive (SAR) files. SAR is not a supported J2EE module and therefore not recognized in EAR files. Therefore, the AST 6.1 SIP toolkit did not allow for adding SIP projects to EAR projects. Converged projects can be packaged as WAR files and WAR files are valid J2EE modules. Therefore, Converged projects should be allowed to be included in an EAR project. However, WebSphere Application Server version 6.1 will not recognize the WAR file as being a SIP/HTTP project unless the web.xml has been modified. In fact, when a SAR file is deployed to Application Server it preprocesses the file through a sartowar tool, which actually converts the SAR file to WAR file with a modified web.xml. This is done under the covers so users never know about it. But if a WAR file with SIP content is included in an EAR file and the WAR file has not been processed through the sartowar tool, then Application Server will not recognize the SIP content. Therefore, in order to avoid that problem, we disabled adding Converged projects to EAR projects in the AST 6.1 release.
Problem conclusion
We have updated the SIP tools for AST 6.1.1 which will now do the same processing that sartowar does to sip.xml and web.xml to allow the SIP pplications to deploy in an EAR file and run/debug on WAS 6.1. So whenever changes are made to the sip.xml, the user is prompted to update the web.xml. Since the web.xml is required by WAS, now all the projects are converged projects. And now it will allow for the projects to be packaged in EAR files and run on server. The fix for this APAR is currently targeted for inclusion in WebSphere Application Server Toolkit refresh pack 6.1.1. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PK27698
Reported component name
WEBAPP SERVER A
Reported component ID
5724J0820
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2006-07-06
Closed date
2006-09-20
Last modified date
2006-12-19
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
SIP
Fix information
Fixed component name
WEBAPP SERVER A
Fixed component ID
5724J0820
Applicable component levels
R610 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
19 October 2021