Fixes are available
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. [Root exception is java.lang.IllegalStateException: Local interface not defined] It runs fine on earlier fixpacks and works fine on WAS 7 with fixpack 19 , 23, 25 , 27 appears to be introduced by FP 29 . Issue was able to be recreated . Root cause: Failure is due to a change in behavior related to the processing of <local-home /> in an <ejb-local-ref> in web.xml. Although a local-home value is not specified, the presence of the element in web.xml is confusing the EJB container, causing it to attempt to inject a home interface, rather than the configured business local interface. The target EJB does not have a local home interface, thus the "Local interface not defined" is reported.
Local fix
The problem may be worked around by deleting the empty <local-home /> element.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 with EJB 3.0 applications * **************************************************************** * PROBLEM DESCRIPTION: IllegalStateException: Local * * interface not defined when empty * * <local-home/> present in ejb-jar.xml * * or web.xml * **************************************************************** * RECOMMENDATION: * **************************************************************** When ejb-jar.xml or web.xml contains an empty local-home element of an ejb-local-ref stanza, such as <local-home />, an IllegalStateException will occur at runtime with the message "Local interface not defined".
Problem conclusion
The EJB container will be updated to properly handle empty local-home elements in ejb-jar.xml or web.xml. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.31. 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
PM95086
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-08-14
Closed date
2013-10-08
Last modified date
2013-10-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PM96574
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
Document Information
Modified date:
02 November 2021