- This topic has 8 replies, 3 voices, and was last updated 8 years, 6 months ago by
.
-
Posts
-
Getting the following error trying to access REST service. CWRPC0001E: The service with name ” ” is not found. IBM site indicates that CWRPC0001E error means “Verify that you have defined a service with the specified name in the RpcAdapterConfig.xml file”. The service is defined in the file correctly. This application runs fine with same code base using MyEclipse 10 & WAS Server 8.5.5.9. No other info from IBM sites or Genuitec
Greg,
Thank you for trying MyEclipse 2016 CI 2.I have escalated the issue to the dev team and they will get back to you soon.
–Swapna
MyEclipse SupportGreg,
Before getting into this issue, I presume that the WAS state is being correctly reported with 2016 CI 2?
Are there any errors that you see during deployment of the application in the console view?
What deployment mode are you using, if you are using the in-workspace mode, could you switch to the other mode of deployment, or vice-versa and see if that makes a difference?
Finally, what is the composition of your application? e.g. is it an EAR with a Web project, are the service and the consumer defined in the same module, etc.?
1. Using 2016 CI2
2. No deployment error with in-workspace mode
3. Changed to classis, now get following deploy error:
Caused by: com.ibm.ws.webcontainer.exception.WebAppNotLoadedException: Failed to load webapp: Context root /emp/* is already bound. Cannot start application tibempServiceWeb
at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:134)
at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:901)
4. This is an ear with Web projectGreg,
Thank you for the details.
Can you please check if the suggestions in these threads discussing similar issue help fix your problem?
http://stackoverflow.com/questions/20839866/application-is-not-starting-in-websphere-8-5-5-but-works-fine-in-tomcat
https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000013941586
http://www.coderanch.com/t/78516/Websphere/Error-publishing-Test-Environment-serverLet us know how it works for you.
–Swapna
MyEclipse Support1. Appears to deploy.. no visible errors.
2. When hitting the service URL, comes back to CWRPC0001E errorGreg,
1. To rule out issues with missing jars/files, please check if all the required jars/files are deployed. You can manage the deployment from the Deployment Assembly page of the project. Right click on the project > Properties > MyEclipse > Deployment Assembly.
Here is the tutorial for MyEclipse Deployment Assembly for your reference : https://www.genuitec.com/products/myeclipse/learning-center/basics/myeclipse-deployment-assembly/
2. Can you please clarify if the project works as expected when deployed in In-Workspace mode? Is it only with Classic deployment mode, that you are seeing the Service URL error?
3. Can you please check if the issue persists when deploying the EAR directly to WAS 8.5 outside of MyEclipse ?
4. We might need your project to help us replicate the issue at our end as this looks like an application specific issue. Can you please send your project privately (using Private Message available in your profile page ) to help us investigate further?
Thank you for your patience.
–Swapna
MyEclipse Support1. Jar files are accounted for. As stated previously, this same ear / war project deploys / runs correctly in MyEclipse 10.7 and WAS 8.5.5.9
2. The same error exists whether deployed in Classic or in-workspace
3. I did deploy straight from WAS, same issue
4. Have to check on that oneGreg,
I’m sorry I missed your reply. One way of figuring out what is going wrong is to export an EAR and deploy that with the admin console manually – either MyEclipse 2016 is creating the wrong EAR and/or it is deploying it incorrectly. To test this you would:
1) Export an EAR of your project with MyEclipse 10 (File > Export > Java EE > EAR file (MyEclipse))
2) Export an EAR of the project with MyEclipse 2016 (File > Export > MyEclipse JEE > EAR file)
3)
a) Try to deploy this EAR directly with the WebSphere admin console (not through MyEclipse). Does your application now work? If it does, then there would likely be a problem with how it’s being deployed. If it does not work, please see the next step:
b) Compare the EAR generated by MyEclipse 10 with the EAR generated by 2016. To do this, you could extract both EARs into separate directories and then use a directory comparison tool to compare the two directories. You might also need to expand the WARs within, if they are compressed.Do let us know if we can help in any way or if you need further clarifications.
