Fixes are available
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
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
This is a problem with the mapping of the modules in the application to the IBM HTTP Server with a script. If you create an unmanaged node with an corresponding IBM HTTP Server first, then try to map the .war modules to the IBM HTTP Server, during this mapping you might get the CWSAD0055E error. However if you use the administrative console you can can map the same module to the IBM HTTP Server without any problems. The error messages that are logged as a result are these: [10/22/10 7:54:04:756 CEST] 00000028 ValidateAppTa 3 validation errors = [CWSAD0055E: Ejb jar and its HTTP router WAR module are not targeted to the same server. EJB JAR has the target of WebSphere:cell=myCell01,cluster=myCluster and HTTP router WAR module has the target of WebSphere:cell=myCell01,cluster=myCluster+WebSphere:cell=myCell0 1,node=myihs7Node,server=myihs7.] [10/22/10 7:54:04:756 CEST] 00000028 ValidateAppTa 1 performTask FFDC: sourceId=com.ibm.ws.management.application.task.ValidateAppTask. performTask, probeId=292 com.ibm.websphere.management.exception.AdminException: ADMA5055E: Errors in validating application target association for myApplication - CWSAD0055E: Ejb jar and its HTTP router WAR module are not targeted to the same server. EJB JAR has the target of WebSphere:cell=myCell01,cluster=myCluster and HTTP router WAR module has the target of WebSphere:cell=myCell01,cluster=myCluster+WebSphere:cell=myCell0 1,node=myihs7Node,server=myihs7. at java.lang.Throwable.<init>(Throwable.java:67) at com.ibm.ws.exception.WsException.<init>(WsException.java:80) at com.ibm.websphere.management.exception.AdminException. <init>(AdminException.java:35) at com.ibm.ws.management.application.task.ValidateAppTask. performTask(ValidateAppTask.java:132)
Local fix
Use the administrative console to do the mapping
Problem summary
**************************************************************** * USERS AFFECTED: All administrators of IBM WebSphere * * Application Server V7.0 * **************************************************************** * PROBLEM DESCRIPTION: Using a script to create a new server * * and map modules to it might result in * * an ADMA5055E exception. * **************************************************************** * RECOMMENDATION: Install an fix pack containing this APAR. * **************************************************************** This is a problem with the mapping of the modules in the application to the IBM HTTP Server with a script. If you create an unmanaged node with a corresponding IBM HTTP Server first, then try to map the .war modules to the IBM HTTP Server, during this mapping you might get the CWSAD0055E error. However if you use the administrative console you can can map the same module to the IBM HTTP Server without any problems. The error messages that are logged as a result are these: [10/22/10 7:54:04:756 CEST] 00000028 ValidateAppTa 3 validation errors = [CWSAD0055E: Ejb jar and its HTTP router WAR module are not targeted to the same server. EJB JAR has the target of WebSphere:cell=myCell01,cluster=myCluster and HTTP router WAR module has the target of WebSphere:cell=myCell01,cluster=myCluster+WebSphere:cell=myCell0 1,node=myihs7Node,server=myihs7.] [10/22/10 7:54:04:756 CEST] 00000028 ValidateAppTa 1 performTask FFDC: sourceId=com.ibm.ws.management.application.task.ValidateAppTask. performTask, probeId=292 com.ibm.websphere.management.exception.AdminException: ADMA5055E: Errors in validating application target association for myApplication - CWSAD0055E: Ejb jar and its HTTP router WAR module are not targeted to the same server. EJB JAR has the target of WebSphere:cell=myCell01,cluster=myCluster and HTTP router WAR module has the target of WebSphere:cell=myCell01,cluster=myCluster+WebSphere:cell=myCell0 1,node=myihs7Node,server=myihs7. at java.lang.Throwable.<init>(Throwable.java:67) at com.ibm.ws.exception.WsException.<init>(WsException.java:80) at com.ibm.websphere.management.exception.AdminException. <init>(AdminException.java:35) at com.ibm.ws.management.application.task.ValidateAppTask. performTask(ValidateAppTask.java:132) As an example, this might occur when trying to map WebSphere Service Registry and Repository ( WSRR ) using a script.
Problem conclusion
The problem occurred because the runtime was not recognizing the newly created server because it was not yet part of the saved configuration. The runtime has been updated to get information about the newly created server from the most recent configuration update, instead of from the saved configuration. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.19. 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
PM35471
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-03-23
Closed date
2011-04-15
Last modified date
2011-04-15
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
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R700 PSY
UP
Document Information
Modified date:
27 October 2021