Fixes are available
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
JAXRS applications that specify a rest servlet such as com.ibm.websphere.jaxrs.server.IBMRestServlet in the web.xml must specify an application <init-param> will fail on application startup. Currently the messaging is insufficient to allow the customer to determine that the <init-param> is missing.
Local fix
In our particular case the following worked: The reason for specifying the IBMRestServlet in the web.xml is to associate it with an Application subclass - in this case, the sample.ApplicationConfig class. The JAX-RS implementation should be able to scan the WAR file and find appropriate Application subclases - so long as they are annotated with @ApplicationPath. But if the user specifies the IBMRestServlet, then the JAXRS implementation in WAS will need to associate it with an application. Without the init-param that indicates the application class, it won't know which application class is associated with which servlet (and more importantly, which servlet URI path). The customer should include the init-param element as such: <servlet> <servlet-name>JAX-RS Servlet</servlet-name> <servlet-class>com.ibm.websphere.jaxrs.server.IBMRestServlet</se rvlet-c lass> <init-param> <param-name>javax.ws.rs.Application</param-name> <param-value>sample.ApplicationConfig</param-value> </init-param> <load-on-startup>1</load-on-startup> </servlet> We tested this addition to the web.xml and were able to start the server and web app without exception.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server who use the JAXRS 2.0 feature * * function. * **************************************************************** * PROBLEM DESCRIPTION: No message exists to warn users that * * specifying a rest servlet in the * * web.xml requires an application * * <init-param>. * **************************************************************** * RECOMMENDATION: * **************************************************************** When JAXRS applications specify a rest servlet, such as com.ibm.websphere.jaxrs.server.IBMRestServlet in the web.xml, then must also specify an application <init-param> or the application will fail to start. Currently there is no messages to indicate clearly that this problems exists and explain what to do.
Problem conclusion
The following messages have been added to resolve this issue: CWWKW0101W (warn.servlet.specified.without.application) CWWKW0102W (warn.servlet.specified.with.invalid.application) The fix for this APAR is currently targeted for inclusion in fix pack 9.0.0.6. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI82162
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-05-25
Closed date
2017-08-10
Last modified date
2017-08-10
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R900 PSY
UP
Document Information
Modified date:
03 May 2022