- This topic has 3 replies, 2 voices, and was last updated 11 years, 1 month ago by support-swapna.
-
AuthorPosts
-
David FaheyMemberI am running MyEclipse Blue 10.7 on Windows 7 64 bit, deploying to WAS 7.0. I’ve been running fine until updating my workspace with some EJB interface changes. When I run EJB Deploy, I get an error message with 800 lines about various bundles that could not be started. Here are the first few lines. The section from “Cannot start” to the end of my snippet appears to repeat for 400 or so other bundles. What has happened to my workspace to kill EJB deploy?
EJB deploy failed
EJBdeploy framework creation failed
Cannot start bridge bundle
The bundle “com.genuitec.eclipse.blue.ejbdeploy.was7_1.0.0 [2]” could not be resolved. Reason: Missing Constraint: Require-Bundle: org.eclipse.core.runtime; bundle-version=”0.0.0″
Cannot start com.genuitec.eclipse.blue.ejbdeploy.was7: The bundle “com.genuitec.eclipse.blue.ejbdeploy.was7_1.0.0 [2]” could not be resolved. Reason: Missing Constraint: Require-Bundle: org.eclipse.core.runtime; bundle-version=”0.0.0″
The bundle “com.genuitec.eclipse.blue.ejbdeploy.was7_1.0.0 [2]” could not be resolved. Reason: Missing Constraint: Require-Bundle: org.eclipse.core.runtime; bundle-version=”0.0.0″Attachments:
You must be logged in to view attached files.
support-swapnaModeratordmfahey,
Sorry that you are seeing this issue.
The error messages about missing bundles mean that the EJB Deploy installation has been corrupted. I am not sure what exactly would have triggered this issue, but certainly not the updation of EJB interfaces.
Can you please go to [websphere-installation-dir]/deploytool/itp/plugins and see if the plugins are present?
If the plugins are missing, please either reinstall the EJB Deploy feature of the WAS installation or reinstall the WAS installation to fix the issue with missing bundles.Let us know how it works for you.
David FaheyMemberI see the plugins in the WebSphere directory, and I can successfully run ejb deploy from another workspace. Is there some metadata in the bad workspace that might not be pointing to the right WebSphere installation directory?
support-swapnaModeratordmfahey,
The server connector might be incorrectly defined.
Can you please ‘Restore Defaults’ on the Websphere server connector and try reconfiguring the WAS to see if it fixes the issue?Let us know how it works for you.
-
AuthorPosts