Wednesday, June 11, 2014

Deployment from com.ibm.ast.ws.deployer.WSDeployer had errors:

I got below error while publishing MyProject code to WAS

Error: application is configured for application profiling, but the Application Profiling service is disabled

Publishing failed
  deploySuccess
    Deploying MyProjectAdditionWSEJB
      Deployment from com.ibm.ast.ws.deployer.WSDeployer had errors:

      Deployment from com.ibm.ast.ws.deployer.WSDeployer had errors:

      Deployment from com.ibm.ast.ws.deployer.WSDeployer had errors:

      Deployment from com.ibm.ast.ws.deployer.WSDeployer had errors:

      Deployment from com.ibm.ast.ws.deployer.WSDeployer had errors:

      Deployment from com.ibm.ast.ws.deployer.WSDeployer had errors:

      Deployment from com.ibm.ast.ws.deployer.WSDeployer had errors:

      Deployment from com.ibm.ast.ws.deployer.WSDeployer had errors:

     
       
            Warning messages were issued.
              WSWS3440W: Warning: The WSDL2Java emitter does not understand qname CustProdBObj specified in field xml-element-name of construct variable-mapping in the mapping file: platform:/resource/MyProjectAdditionWSEJB/ejbModule/META-INF/MyProjectAdditionService_mapping.xml. The construct is found in the mapping file but not in the wsdl file..  The information in the mapping file corresponding to this qname will be ignored.
              WSWS3440W: Warning: The WSDL2Java emitter does not understand qname CustStatusBObj specified in field xml-element-name of construct variable-mapping in the mapping file: platform:/resource/MyProjectAdditionWSEJB/ejbModule/META-INF/MyProjectAdditionService_mapping.xml. The construct is found in the mapping file but not in the wsdl file..  The information in the mapping file corresponding to this qname will be ignored.
              WSWS3440W: Warning: The WSDL2Java emitter does not understand qname CustomerValuesBObj specified in field xml-element-name of construct variable-mapping in the mapping file: platform:/resource/MyProjectAdditionWSEJB/ejbModule/META-INF/MyProjectAdditionService_mapping.xml. The construct is found in the mapping file but not in the wsdl file..  The information in the mapping file corresponding to this qname will be ignored.
              WSWS3440W: Warning: The WSDL2Java emitter does not understand qname CustomRelationshipBObj specified in field xml-element-name of construct variable-mapping in the mapping file: platform:/resource/MyProjectAdditionWSEJB/ejbModule/META-INF/MyProjectAdditionService_mapping.xml. The construct is found in the mapping file but not in the wsdl file..  The information in the mapping file corresponding to this qname will be ignored.
              WSWS3440W: Warning: The WSDL2Java emitter does not understand qname SecondaryCardBObj specified in field xml-element-name of construct variable-mapping in the mapping file: platform:/resource/MyProjectAdditionWSEJB/ejbModule/META-INF/MyProjectAdditionService_mapping.xml. The construct is found in the mapping file but not in the wsdl file..  The information in the mapping file corresponding to this qname will be ignored.
  The publish encountered some problems and the application may not have been installed or it may have been successfully installed but was unable to start.
 
    ======== MyProject ========
 
    Application Failed to Start.  MyProject
    com.ibm.ws.exception.RuntimeWarning: The MyProject application is configured for application profiling, but the Application Profiling service is disabled
    com.ibm.ws.appprofile.ApplicationMetaDataHelper.metaDataCreated(ApplicationMetaDataHelper.java:122)
    com.ibm.ws.runtime.component.MetaDataMgrImpl.fireMetaDataCreated(MetaDataMgrImpl.java:189)
    com.ibm.ws.runtime.component.MetaDataMgrImpl.createMetaData(MetaDataMgrImpl.java:342)
    com.ibm.ws.runtime.component.MetaDataMgrImpl.createMetaDataFromFactories(MetaDataMgrImpl.java:173)
    com.ibm.ws.runtime.component.MetaDataMgrImpl.createMetaData(MetaDataMgrImpl.java:307)
    com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:922)
    com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:740)
    com.ibm.ws.runtime.component.ApplicationMgrImpl$1.run(ApplicationMgrImpl.java:1312)
    com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:4189)
    com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:4367)
    com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:255)
    com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplicationDynamically(ApplicationMgrImpl.java:1317)
    com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2089)
    com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:437)
    com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:122)
    com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:380)
    com.ibm.ws.runtime.component.CompositionUnitMgrImpl.startCompositionUnit(CompositionUnitMgrImpl.java:644)
    com.ibm.ws.runtime.component.CompositionUnitMgrImpl.startCompositionUnit(CompositionUnitMgrImpl.java:613)
    com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:1215)
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    java.lang.reflect.Method.invoke(Method.java:599)
    sun.reflect.misc.Trampoline.invoke(MethodUtil.java:36)
    sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    java.lang.reflect.Method.invoke(Method.java:599)
    sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:243)
    javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1085)
    javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:966)
    com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:848)
    com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:773)
    com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1313)
    com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
    com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:1206)
    com.ibm.ws.management.remote.AdminServiceForwarder.invoke(AdminServiceForwarder.java:334)
    javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1437)
    javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:83)
    javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1275)
    javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1370)
    javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:799)
    javax.management.remote.rmi._RMIConnectionImpl_Tie.invoke(_RMIConnectionImpl_Tie.java:749)
    javax.management.remote.rmi._RMIConnectionImpl_Tie._invoke(_RMIConnectionImpl_Tie.java:157)
    com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:622)
    com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:475)
    com.ibm.rmi.iiop.ORB.process(ORB.java:504)
    com.ibm.CORBA.iiop.ORB.process(ORB.java:1571)
    com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2771)
    com.ibm.rmi.iiop.Connection.doWork(Connection.java:2640)
    com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)
    com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)
    com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1527)
  The publish encountered some problems and the application may not have been installed or it may have been successfully installed but was unable to start. View the Details to display the exceptions and server logs that occurred during the publish.
 
    ======== MDM ========
 
    Failed to update application
    Failed to update application
    Please see server logs for more details.
    [6/4/14 12:07:35:986 IST] 00000013 FfdcProvider  I com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\logs\ffdc\server1_1d2a1d2a_14.06.04_12.07.35.78317500.txt com.ibm.ws.runtime.component.ApplicationMgrImpl 1449
    [6/4/14 12:07:36:002 IST] 00000013 CompositionUn E   WSVR0194E: Composition unit WebSphere:cuname=MyProject in BLA WebSphere:blaname=MyProject failed to start.
    [6/4/14 12:07:36:142 IST] 00000013 FfdcProvider  I com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\logs\ffdc\server1_1d2a1d2a_14.06.04_12.07.36.01717501.txt com.ibm.ws.management.AdminServiceImpl.invoke 679
    [6/4/14 12:26:34:038 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\BusinessServicesWS.jar cannot be deleted.
    [6/4/14 12:26:34:053 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\BusinessServicesWSEJB.jar cannot be deleted.
    [6/4/14 12:26:34:241 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\CrossDomainServicesWS.jar cannot be deleted.
    [6/4/14 12:26:34:256 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\CrossDomainServicesWSEJB.jar cannot be deleted.
    [6/4/14 12:26:34:334 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\DWLAdminServicesWS.jar cannot be deleted.
    [6/4/14 12:26:34:350 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\DWLAdminServicesWSEJB.jar cannot be deleted.
    [6/4/14 12:26:34:381 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\DWLBusinessServicesWS.jar cannot be deleted.
    [6/4/14 12:26:34:428 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\DWLCommonServicesEJB.jar cannot be deleted.
    [6/4/14 12:26:34:428 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\DWLCommonServicesWS.jar cannot be deleted.
    [6/4/14 12:26:34:521 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\EventManagerEJB.jar cannot be deleted.
    [6/4/14 12:26:34:553 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\FinancialServicesEJB.jar cannot be deleted.
    [6/4/14 12:26:34:568 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\FinancialServicesWS.jar cannot be deleted.
    [6/4/14 12:26:34:646 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\MyProjectAdditionWS.jar cannot be deleted.
    [6/4/14 12:26:34:662 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\MyProjectAdditionWSEJB.jar cannot be deleted.
    [6/4/14 12:26:34:724 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\MyProjectCompositeBPWS.jar cannot be deleted.
    [6/4/14 12:26:34:740 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\MyProjectCompositeBPWSEJB.jar cannot be deleted.
    [6/4/14 12:26:34:849 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\MDMQSWS_client.jar cannot be deleted.
    [6/4/14 12:26:35:021 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\PartyEJB.jar cannot be deleted.
    [6/4/14 12:26:35:021 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\PartyWS.jar cannot be deleted.
    [6/4/14 12:26:35:099 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\ProductServicesWS.jar cannot be deleted.
    [6/4/14 12:26:35:114 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650\ProductWS.jar cannot be deleted.
    [6/4/14 12:26:35:208 IST] 00000024 AppUtils      W   ADMA0078W: The file: C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\wstemp\temp\ServiceIndexServerTask\MDM_146659df650 cannot be deleted.
    [6/4/14 12:31:44:843 IST] 00000024 FfdcProvider  I com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\logs\ffdc\server1_1f4b1f4b_14.06.04_12.31.44.82717517.txt com.ibm.ws.webservices.admin.deploy.VerifyEJBandItsRoutersTaskImpl.verifyPartialUpdate 559
    [6/4/14 12:31:44:999 IST] 00000024 FfdcProvider  I com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\logs\ffdc\server1_1f4b1f4b_14.06.04_12.31.44.85817518.txt com.ibm.ws.webservices.admin.deploy.VerifyEJBandItsRoutersTask.performTask 177
    [6/4/14 12:31:47:011 IST] 00000024 FfdcProvider  I com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\MyProjectUpgrade\logs\ffdc\server1_1f4b1f4b_14.06.04_12.31.46.37117519.txt com.ibm.ws.management.application.SchedulerImpl.run 297
    [6/4/14 12:31:47:027 IST] 00000024 SystemErr     R com.ibm.websphere.management.exception.AdminException: CWSAD0077E: The value of serverStringOfDeployedRouterMoudule is null.
    [6/4/14 12:31:47:027 IST] 00000024 SystemErr     R         at


Solution to enabling the application profiling service
-----------------------------------------------------------------------------------------------
Procedure
1. Log in to the Integrated Solutions Console:
a. Open a browser and navigate to the following URL: https://host_name:port/ibm/console.
Where:
? host_name is the fully qualified host name of the server where the application or the network deployment manager is deployed.
? port is the secured port used to access the console. The default port is 9043.
Note: The default unsecured port is 9060. If you use 9060, you must have "http" instead of "https" in the URL.
b. Enter an administrator user ID and password. (Omit the password if security is not enabled.)
c. Click Log in.
2. Click Servers > Server Types > WebSphere application servers.
3. Click the name of the server where you plan to deploy the WebSphere IMS Connector application.
4. Expand Container Services and click Application profiling service.
5. Select the Enable service at server startup check box.
6. Click OK and to save your changes.
7. Repeat these steps for each server where you plan to deploy the WebSphere IMS Connector application.


OR
try prepare for deployment  of the WS projects in the above error.



No comments:

Post a Comment