PK56080: BATCHEXTENSION NOT FOUND WHEN RUNNING EJBDEPLOY

Fixes are available

APAR status

Closed as program error.

Error description

When running ejbdeploy customer encounters the following error:
.

ADMA0115W: Resource assignment of name DB2I and type
javax.sql.DataSource, with JNDI name DB2I is not found within
scope
of module VPS_Systemdoc_web with URI VPS_Systemdoc_web.war,
WEB-INF/web.xml deployed to target
WebSphere:cell=soat,node=vps1,
server=wsoat.
.
ADMA5068I: The resource validation for application sysdok
completed
successfully, but warnings occured during validation.
.
ADMA5018I: The EJBDeploy command is running on enterprise
archive
(EAR) file
/was/soat/AppServer/profiles/default/wstemp/754256292/
upload/sysdok.ear.
.
Starting workbench.
.
framework search path:
/SWVPS1/usr/lpp/zWebSphere/V6R1/deploytool/itp/plugins
.
An unexpected exception was thrown. Halting execution.
Shutting down workbench.
 .
Error executing deployment:
org.eclipse.core.runtime.CoreException.
Error is Plug-in com.ibm.etools.ejbdeploy was unable to load
class
com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension..
.
org.eclipse.core.runtime.CoreException: Plug-in
com.ibm.etools.ejbdeploy was unable to load class
com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.
at
org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.
throwException(RegistryStrategyOSGI.java:165)
.
.
.

Local fix

To circumvent this problem you may follow these steps:
.
1. First you need to locate the EJB Deploy configuration
   directory. To do that run ejbdeploy.sh from the
   $WAS_HOME/bin directory with the -log command
   line option.  The format of this should be:
   ejbdeploy.sh <inputEAR> <workingDirectory> <outputEAR> -log
.
2. Delete all files/directories from the EJB Deploy
   configuration directory found in Step 1.  It is a good
   practice to backup this directory before performing the
   deletion.
   * Note: for v6.1 and above the config.ini file must exist
     in order for ejbdeploy to function.  For v6.0 however,
     the config.ini file is not required by ejbdeploy and will
     be created if needed.
.
3. Re-deploy the application.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of EJBDeploy on WebSphere         *
*                  Application Server V6.0.1                   *
****************************************************************
* PROBLEM DESCRIPTION: The WebSphere Application Server        *
*                      EJBDeploy OSGi caching directory is     *
*                      not cleaned after installing a new      *
*                      fix pack.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The WebSphere Application Server EJBDeploy OSGi caching
directory is not cleaned after installing a new fixpack. This
can cause errors when running EJBDeploy as it may fail to
locate plug-ins or extensions defined within the EJBDeploy
application.  See the following URL for more information and
work-arounds for this problem:

http://www.ibm.com/support/docview.wss?uid=swg21239141

This technote is applicable to all supported WebSphere
Application Server platforms.

Problem conclusion

For the WebSphere Application Server product on z/OS a
post install action has been introduced to ensure that the
default OSGi directories are purged.  For WebSphere Application
Server on other platforms a config action was introduced to
ensure that the default OSGi directories are purged
as part of fix pack installation.

APAR PK56080 is currently targeted for inclusion in Service
Level (Fix Pack) 6.0.2.31 of WebSphere Application Server V6.0.1
for z/OS.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

manually delete the $WAS_HOME/deploytool/itp/configuration/
and $USER_INSTALL_ROOT/ejbdeploy/configuration/ directory
contents except for the config.ini file.

Comments

APAR Information

APAR number
PK56080
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
601
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-11-06
Closed date
2008-08-15
Last modified date
2008-11-04

APAR is sysrouted FROM one or more of the following:

PK55319
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R601 PSY UK40557
UP08/10/17 P F810

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
19 October 2021

Tips

PK56080: BATCHEXTENSION NOT FOUND WHEN RUNNING EJBDEPLOY

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R601 PSY UK40557

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

Document Information

Share your feedback

Need support?