Topic
  • 7 replies
  • Latest Post - ‏2012-05-14T15:22:38Z by SystemAdmin
Venkat@stepupyourlife
1 Post

Pinned topic Existing module failed to publish to WESB server

‏2011-04-20T13:04:40Z |
The ESB module that has been deployed and working good is now causing issues in publishing it to WESB. I dont have any issue in publishing all other modules and thus ruling out the corruption of ESB profile.

The issue has started just after I had to kill the ESB process by force. Here is the exception I am encountering when tried to publish RentalMediationModule. Please help in identifying the solution.

Publishing failed
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.

======== RentalMediationModuleApp ========

Application Failed to Install. RentalMediationModuleApp
4/20/11 8:44:54:071 EDT 00000043 ModuleEJBUtil W CWLIN1502W: The target mapping for the RentalMediationModuleWeb.war default Web module cannot be found. Therefore, the target mapping for the RentalMediationModuleEJB.jar generated Enterprise JavaBeans (EJB) module cannot be set.
Updated on 2012-05-14T15:22:38Z at 2012-05-14T15:22:38Z by SystemAdmin
  • Ronn78
    Ronn78
    12 Posts

    Re: Existing module failed to publish to WESB server

    ‏2011-04-20T22:08:12Z  
    Try couple of things.

    1. Goto to JAVA EE perspective from WID-- delete App and Web files related to your module then clean your project and deploy to server.
    2. If it doesn't work goto installed app folder(eg. C:\\IBM\WID7_WTE\runtimes\bi_v7\profiles\qwps\installedApps\qcell), delete the specific module you are interested(RentalMediationModule) and follow step one.

    Hope it helps.
    Thanks
    Ronnie
  • SystemAdmin
    SystemAdmin
    289 Posts

    Re: Existing module failed to publish to WESB server

    ‏2011-04-26T12:27:04Z  
    I had the same issue, in addition to Ronnie's steps I had also to delete directories named after the application from the "cus" and "blas" folders (C:\\IBM\WID7_WTE\runtimes\bi_v7\profiles\qwps\config\cells\qcellcus)

    In addition, the WID 7.0.0.3-IFix-20101103 version seems to generate the "App" project with an incorrect project facet that defines it as a JEE 1.4 version Ear, which causes problems if you have EJB 3.0 projects in your ear. Don't know if this had an effect on my issue, but I had to set this right as well to make it work again.

    cheers,
    Ben
  • SystemAdmin
    SystemAdmin
    289 Posts

    Re: Existing module failed to publish to WESB server

    ‏2011-06-28T16:17:47Z  
    I had the same issue, in addition to Ronnie's steps I had also to delete directories named after the application from the "cus" and "blas" folders (C:\\IBM\WID7_WTE\runtimes\bi_v7\profiles\qwps\config\cells\qcellcus)

    In addition, the WID 7.0.0.3-IFix-20101103 version seems to generate the "App" project with an incorrect project facet that defines it as a JEE 1.4 version Ear, which causes problems if you have EJB 3.0 projects in your ear. Don't know if this had an effect on my issue, but I had to set this right as well to make it work again.

    cheers,
    Ben
    Hi Ben,

    I had similar issue like you. I tried the 2 steps deleting the app and web projects and cleaned and try to install it, but it is failing with same error. As this is my first time i am trying deploy into server so i didn't see anything in the installapps folder. You are talking some thing else to set the facet stuff. Can you please explain in detail more what are the things should be done to fix my issue. Below is your previous explanation.

    "In addition, the WID 7.0.0.3-IFix-20101103 version seems to generate the "App" project with an incorrect project facet that defines it as a JEE 1.4 version Ear, which causes problems if you have EJB 3.0 projects in your ear. Don't know if this had an effect on my issue, but I had to set this right as well to make it work again."
    My Error Message

    <<<<<<<<<<<<<<<<<<<
    6/28/11 12:03:24:361 EDT 000004ac ModuleEJBUtil W CWLIN1502W: The target mapping for the AccountMediationModuleWeb.war default Web module cannot be found. Therefore, the target mapping for the AccountMediationModuleEJB.jar generated Enterprise JavaBeans (EJB) module cannot be set.
    6/28/11 12:03:37:068 EDT 000004ac SystemErr R org.eclipse.emf.common.util.BasicEList$BasicIndexOutOfBoundsException: index=0, size=0
    6/28/11 12:03:37:069 EDT 000004ac SystemErr R at org.eclipse.emf.common.util.BasicEList.get(BasicEList.java:512)
    6/28/11 12:03:37:069 EDT 000004ac SystemErr R at com.ibm.ws.sca.internal.deployment.jaxrpc.JaxRpcRuntimeInstaller.execute(JaxRpcRuntimeInstaller.java:100)
    6/28/11 12:03:37:069 EDT 000004ac SystemErr R at com.ibm.ws.bpm.cmdfrmwrk.task.WBILazyInstantiationTask.invokeTask(WBILazyInstantiationTask.java:326)
    6/28/11 12:03:37:070 EDT 000004ac SystemErr R at com.ibm.ws.bpm.cmdfrmwrk.task.WBILazyInstantiationTask.execute(WBILazyInstantiationTask.java:255)
    6/28/11 12:03:37:071 EDT 000004ac SystemErr R at com.ibm.ws.bpm.cmdfrmwrk.task.WBIInstallFrameworkTask.executeTasks(WBIInstallFrameworkTask.java:92)
    6/28/11 12:03:37:071 EDT 000004ac SystemErr R at com.ibm.ws.bpm.cmdfrmwrk.task.WBIInstallFrameworkTask.performTask(WBIInstallFrameworkTask.java:55)
    6/28/11 12:03:37:072 EDT 000004ac SystemErr R at com.ibm.ws.bpm.deploy.delegator.DelegatingTaskProvider.delegatePerformTask(DelegatingTaskProvider.java:458)
    6/28/11 12:03:37:073 EDT 000004ac SystemErr R at com.ibm.ws.bpm.deploy.delegator.DelegatingTaskProvider.performTask(DelegatingTaskProvider.java:424)
    6/28/11 12:03:37:073 EDT 000004ac SystemErr R at com.ibm.ws.bpm.deploy.BPMTaskProvider.performTask(BPMTaskProvider.java:100)
    6/28/11 12:03:37:073 EDT 000004ac SystemErr R at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:285)
    6/28/11 12:03:37:074 EDT 000004ac SystemErr R at java.lang.Thread.run(Thread.java:736)

    >>>>>>>>>>>>>>>>>

    Thanks
    Ray
  • SystemAdmin
    SystemAdmin
    289 Posts

    Re: Existing module failed to publish to WESB server

    ‏2011-08-11T13:28:02Z  
    Hi Ben,

    I had similar issue like you. I tried the 2 steps deleting the app and web projects and cleaned and try to install it, but it is failing with same error. As this is my first time i am trying deploy into server so i didn't see anything in the installapps folder. You are talking some thing else to set the facet stuff. Can you please explain in detail more what are the things should be done to fix my issue. Below is your previous explanation.

    "In addition, the WID 7.0.0.3-IFix-20101103 version seems to generate the "App" project with an incorrect project facet that defines it as a JEE 1.4 version Ear, which causes problems if you have EJB 3.0 projects in your ear. Don't know if this had an effect on my issue, but I had to set this right as well to make it work again."
    My Error Message

    <<<<<<<<<<<<<<<<<<<
    6/28/11 12:03:24:361 EDT 000004ac ModuleEJBUtil W CWLIN1502W: The target mapping for the AccountMediationModuleWeb.war default Web module cannot be found. Therefore, the target mapping for the AccountMediationModuleEJB.jar generated Enterprise JavaBeans (EJB) module cannot be set.
    6/28/11 12:03:37:068 EDT 000004ac SystemErr R org.eclipse.emf.common.util.BasicEList$BasicIndexOutOfBoundsException: index=0, size=0
    6/28/11 12:03:37:069 EDT 000004ac SystemErr R at org.eclipse.emf.common.util.BasicEList.get(BasicEList.java:512)
    6/28/11 12:03:37:069 EDT 000004ac SystemErr R at com.ibm.ws.sca.internal.deployment.jaxrpc.JaxRpcRuntimeInstaller.execute(JaxRpcRuntimeInstaller.java:100)
    6/28/11 12:03:37:069 EDT 000004ac SystemErr R at com.ibm.ws.bpm.cmdfrmwrk.task.WBILazyInstantiationTask.invokeTask(WBILazyInstantiationTask.java:326)
    6/28/11 12:03:37:070 EDT 000004ac SystemErr R at com.ibm.ws.bpm.cmdfrmwrk.task.WBILazyInstantiationTask.execute(WBILazyInstantiationTask.java:255)
    6/28/11 12:03:37:071 EDT 000004ac SystemErr R at com.ibm.ws.bpm.cmdfrmwrk.task.WBIInstallFrameworkTask.executeTasks(WBIInstallFrameworkTask.java:92)
    6/28/11 12:03:37:071 EDT 000004ac SystemErr R at com.ibm.ws.bpm.cmdfrmwrk.task.WBIInstallFrameworkTask.performTask(WBIInstallFrameworkTask.java:55)
    6/28/11 12:03:37:072 EDT 000004ac SystemErr R at com.ibm.ws.bpm.deploy.delegator.DelegatingTaskProvider.delegatePerformTask(DelegatingTaskProvider.java:458)
    6/28/11 12:03:37:073 EDT 000004ac SystemErr R at com.ibm.ws.bpm.deploy.delegator.DelegatingTaskProvider.performTask(DelegatingTaskProvider.java:424)
    6/28/11 12:03:37:073 EDT 000004ac SystemErr R at com.ibm.ws.bpm.deploy.BPMTaskProvider.performTask(BPMTaskProvider.java:100)
    6/28/11 12:03:37:073 EDT 000004ac SystemErr R at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:285)
    6/28/11 12:03:37:074 EDT 000004ac SystemErr R at java.lang.Thread.run(Thread.java:736)

    >>>>>>>>>>>>>>>>>

    Thanks
    Ray
    Did you find a solution for this? The tips posted here does not work for me either.

    IBM's info center says this:
    "CWLIN1502W: The target mapping for the {0} default Web module cannot be found. Therefore, the target mapping for the {1} generated Enterprise JavaBeans (EJB) module cannot be set.
    Explanation: The target mapping is not valid. If the target mapping of the generated EJB module is not set, the application might not start properly.
    User Action: Specify a valid target for the default Web module, and repeat the installation."

    I don't know what they mean by specify a valid target for the web module. Has anyone solved this?
    Br,
    Mats
  • SystemAdmin
    SystemAdmin
    289 Posts

    Re: Existing module failed to publish to WESB server

    ‏2011-08-11T13:42:00Z  
    Did you find a solution for this? The tips posted here does not work for me either.

    IBM's info center says this:
    "CWLIN1502W: The target mapping for the {0} default Web module cannot be found. Therefore, the target mapping for the {1} generated Enterprise JavaBeans (EJB) module cannot be set.
    Explanation: The target mapping is not valid. If the target mapping of the generated EJB module is not set, the application might not start properly.
    User Action: Specify a valid target for the default Web module, and repeat the installation."

    I don't know what they mean by specify a valid target for the web module. Has anyone solved this?
    Br,
    Mats
    Hi Mats,

    I am able to resolve the issue by following below the 2 steps.

    1) I serached for cus and blas folders seperatelyt in IBM installed directory and deleted the directories the folders.

    Search for cus in the below folder and delete them and then search for blas in the same folder and then delete them
    Eg: C:\ibm\WID7\

    2 Then i deleted the installed projects manually inside the installed app.

    After doing above 2 spteps i am able to fix the issue.

    Please let me know if you are able to fix the issue after doing above steps.

    Thanks
    Ray
  • SystemAdmin
    SystemAdmin
    289 Posts

    Re: Existing module failed to publish to WESB server

    ‏2012-04-16T09:32:05Z  
    Hi Mats,

    I am able to resolve the issue by following below the 2 steps.

    1) I serached for cus and blas folders seperatelyt in IBM installed directory and deleted the directories the folders.

    Search for cus in the below folder and delete them and then search for blas in the same folder and then delete them
    Eg: C:\ibm\WID7\

    2 Then i deleted the installed projects manually inside the installed app.

    After doing above 2 spteps i am able to fix the issue.

    Please let me know if you are able to fix the issue after doing above steps.

    Thanks
    Ray
    I was also getting the same error. But the issue was related to a dependent library, which was not imported properly.
  • SystemAdmin
    SystemAdmin
    289 Posts

    Re: Existing module failed to publish to WESB server

    ‏2012-05-14T15:22:38Z  
    I was also getting the same error. But the issue was related to a dependent library, which was not imported properly.
    Can I know what is the issue with the dependent library ?