PQ51988: AAT 20 WON'T VALIDATE PREVIOUSLY VALID EJBS

APAR status
Closed as fixed if next.

Error description
When exporting the EJB's using the option Export->EJB 1.1 JAR.
and then validate in the AAT, this is the message received:
BBO94061I Begin validating EJB JAR GeoAreaEJB within appl. CRA.
  The input line is too long.
The syntax of the command is incorrect.
BBO90145E Run time error occurred, stack trace follows:
com.ibm.etools.ejbdeploy.EJBDeploymentException: Error executing
EJBDeploy
at com.ibm.etools.ejbdeploy.EJBDeploy.execute(EJBDeploy.java:158
at
  com.ibm.cb390sm.aat.SMAATEjbDeployToolBridge.verify(SMAATEjb
      DeployToolBridge.verify(SMAATEjbDeployToolBridge.java:387)
at
com.ibm.cb390sm.aat.SMAATEjbJar.validateApplication(SMAATEjbJar.
      java:504)
at com.ibm.cb390sm.aat.SMAATRequest.runValidate(SMAATRequest.jav
      a:622)
at com.ibm.cb390sm.aat.SMAATRequest.run(SMAATRequest.java:362)
at java.lang.Thread.run(Thread.java:498)
BBO94058E EJB JAR GeoAreaEJB within application CRA cannot be
    deployed.
But this bean is known to be valid since it already was
deployed and run this same system (via previous version of AAT).
Local fix
Export a deployed jar from VAJ and then in AAT choose "Options"
and there 'deselect' the "Enable Ejb deploy" option.  This
should circumvent the AAT problem.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0 for z/OS and OS/390.                    *
****************************************************************
* PROBLEM DESCRIPTION: When using the latest version of the    *
*                      Application Assembly Tool               *
*                      (AAT 4.00.020), it fails to validate    *
*                      EJB's that have already been deployed   *
*                      successfully with previous versions of  *
*                      the AAT.                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When using validate/deploy functionality in the AAT, this is the
message that is displayed:

BBO94061I Begin validating EJB JAR *** within application ***.

        The input line is too long.

        The syntax of the command is incorrect.

      BBO90145E Run time error occurred, stack trace follows:
      com.ibm.etools.ejbdeploy.EJBDeploymentException: Error
      executing EJBDeploy
       at com.ibm.etools.ejbdeploy.EJBDeploy.execute
       (EJBDeploy.java:158)
       at com.ibm.cb390sm.aat.SMAATEjbDeployToolBridge.verify
       (SMAATEjbDeployToolBridge.java:387)
       at com.ibm.cb390sm.aat.SMAATEjbJar.validateApplication
       (SMAATEjbJar.java:504)
       at com.ibm.cb390sm.aat.SMAATRequest.runValidate
       (SMAATRequest.java:622)
       at com.ibm.cb390sm.aat.SMAATRequest.run
       (SMAATRequest.java:362)
       at java.lang.Thread.run(Thread.java:498)

BBO94058E EJB JAR *** within application *** cannot be deployed.

This message appears even though this bean is valid and already
running on an existing system. The EJBDeploy tool running within
AAT currently has a limitation on the length of the classpath
being used internally for each application. Certain
applications, those which have many jar files included within
its application EAR file, may face this problem during the
validate/deploy step within AAT.

The AAT tool needs to be modified such that the EJBDeploy tool
it uses does not have the limitation on the length of the
classpath.

As a workaround to this problem, if you are using an existing
EAR file, with properly generated deployed EjbJar files,
the user can use the AAT's 'Options' pull down, and 'de-select'
the 'Enable Ejb deploy' option to disable EJBDeploy tool usage
during the validate/deploy process. These actions will allow the
user to bypass the regeneration of the deployed code for EJBs.
Problem conclusion Temporary fix Comments
This APAR is being closed FIN with concurrence from the
submitting customer. A solution to this problem will be
delivered in a WebSphere Application Server for z/OS
and OS/390 release within the next 18 months.
.
A fix for the problem reported by this APAR has been
provided in the Application Assembly Tool (AAT) for
z/OS and OS/390 Driver 27 and later. The AAT drivers
can be obtained from the WebSphere Application Server
for z/OS and OS/390 download Web site:

http://www.ibm.com/software/webservers/appserv/download_v4z.html
APAR information
APAR number PQ51988
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 400
Status CLOSED FIN
PE NoPE
HIPER NoHIPER
Submitted date 2001-08-30
Closed date 2001-09-18
Last modified date 2002-07-24

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information

Applicable component levels
R400 PSN    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ51988
IBM Group: Software Group
Modified date: Jul 24, 2002