APAR status
Closed as program error.
Error description
First, we are getting the following exception when calling the
setModuleInfo() method:
com.ibm.websphere.management.exception.AdminException:
at com.ibm.ws.management.application.EditApplication.
setApplicationInfo(
EditApplication.java:332)
at com.ibm.ws.management.application.AppManagementImpl.
_setApplicationIn
fo(AppManagementImpl.java:401)
at com.ibm.ws.management.application.AppManagementImpl.
setModuleInfo(App
ManagementImpl.java:390)
---- Begin backtrace for nested exception
java.lang.NullPointerException
at com.ibm.ws.management.application.client.
DataSourceFor10EJBModulesHel
per.completeTask(DataSourceFor10EJBModulesHelper.java:200)
at com.ibm.websphere.management.application.client.
AppDeploymentControll
er.close(AppDeploymentController.java:558)
at com.ibm.ws.management.application.EditApplication.
setApplicationInfo(
EditApplication.java:311)
at com.ibm.ws.management.application.AppManagementImpl.
_setApplicationIn
fo(AppManagementImpl.java:401)
Here's the problem....
if (matchingTaskData.length > ((DataSourceFor10EJBModules)t).
jndiColumn) {
System.out.println("SMG >> in if");
System.out.println("SMG " +
ejbJarBinding.getDefaultDatasource());
//getDefaultDatasource returns null!!!
System.out.println("SMG t " + t );
System.out.println("SMG " + matchingTaskData
[((DataSourceFor10EJBModules)t).jndiColumn]);
ejbJarBinding.getDefaultDatasource().setJndiName(matchingTaskDat
a
[((DataSourceFor10EJBModules)t).jndiColumn]);
System.out.println("SMG done");
}
The problem is that the MBean API does not create bindings. It
expects a fully populated ear. Then when you edit such an app
since the bindings may not be in place you may see such a
problem.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: Websphere Application Server users who use *
* Mbean API to install enterprise applications *
****************************************************************
* PROBLEM DESCRIPTION: Removes requirement enterprise *
* application files must be *
* fully populated when using MBean API *
* to perform application installs. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Installing applications using Mbean
API will generate NullPointerException
when bindings are missing from
enterprise application file.
Problem conclusion
Creates default bindings when missing from EAR files.
Temporary fix
Fixes NullPointerException from missing bindings when using
MBean API to install or modify EAR
Comments
APAR information |
APAR number |
PQ78690 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2003-09-19 |
Closed date |
2003-11-14 |
Last modified date |
2003-11-14 |
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 |
|