APAR status
Closed as program error.
Error description
The customer is running a predeploy.xml file to package
their ear files with new binding information. In their ear
file, they have a web module (a war) that needs to reference
EJBs in another ear file and the xml file is throwing
warning:
"■wsDefaultBindings WARNING: BNDE0007W: EJB reference could
not be resolved: com.highmark.negative.DoNothingHome".
The jndiName in the EJB references are also being changed to
null. The EJB references are in the web module's
ibm-web-bnd.xmi file. (TSTWEBafterPredploy.ear ->
TSTWEBWeb.war ->WEB-INF ->ibm-web-bnd.xmi).
<ejbRefBindings xmi:id="EjbRefBinding_1077896439935"
jndiName="ejb/com/highmark/negative/DoNothingHome">
<bindingEjbRef href="WEB-INF/web.xml#EjbRef_96439935"/>
</ejbRefBindings>
After running the XML the references in the file are being
removed from the ejbRefBindings entry.
<ejbRefBindings xmi:id="EjbRefBinding_1077896439935">
<bindingEjbRef href="WEB-INF/web.xml#EjbRef_96439935"/>
</ejbRefBindings>
-
We were able to recreate this problem just be creating a
bind.bat file
@setlocal
@echo off
@REM Bootstrap values ...
call "%~dp0setupCmdLine.bat"
SET CONSOLE_ENCODING=-Dws.output.encoding=console
SET PATH=%WAS_PATH%
"%JAVA_HOME%\bin\java" "-classpath"
"C:\WebSphere\AppServer\lib\wjmxapp.jar"
com.ibm.ws.management.application.dfltbndngs.BindEar
-ear c:\downloads\82499\TSTWEB.ear
-output c:\downloads\82499\TSTOUT1.ear
-forceBindings true
@endlocal
Local fix
KEYWORDS: ANT XML EAR WAR EJB PREDEPLOY BIND BINDING WEBSPHERE
Problem summary
****************************************************************
* USERS AFFECTED: Websphere Application Server users *
* using Bindear command for an application *
* that has Ejb references pointing to EJBs *
* external to the ear. *
****************************************************************
* PROBLEM DESCRIPTION: The Ejb references are not being *
* found if the War has Ejb references *
* that are pointing to EJBs external *
* to the ear. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When using a Bindear command where the War has Ejb references
that are pointing to EJBs external to the ear, the Ejb
references are not being found. This is causing the JNDI
reference to be null.
Problem conclusion
Code has been corrected to properyl handle it if the ear has
external EJB references. We are no longer getting JNDI name as
null.
Temporary fix
The problem was locally reproducible. Confirmed the fix and
targeted for next service pack.
Comments
APAR information |
APAR number |
PQ87202 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00S |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-04-06 |
Closed date |
2004-06-14 |
Last modified date |
2004-06-28 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|