- This topic has 3 replies, 3 voices, and was last updated 13 years, 10 months ago by
.
-
Posts
-
Hi,
we are currently working on a proof of concept in order to migrate our applications from RAD 7.5 to MyEclipseBlue 8.6.In our first application to deploy, we have MDBs, REST services.
The application deploys and runs successfully with RAD, however while trying to deploy on websphere 7 using myEclipse, I keep on getting the following error in the wsadmin.traceout file :
[07/01/11 15:57:40:718 EST] 00000000 ManagerAdmin I TRAS0017I: The startup trace state is *=info. [07/01/11 15:57:41:295 EST] 00000000 AbstractShell A WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode. [07/01/11 15:57:41:295 EST] 00000000 AbstractShell A WASX7326I: Loaded properties file "/C:/Program%20Files/IBM/WebSphere/AppServer/profiles/ProfilSNE-MEB/properties/wsadmin.properties" [07/01/11 15:57:41:311 EST] 00000000 AdminControlC W WASX7072E: The control service is not available. [07/01/11 15:57:41:358 EST] 00000000 ModelMgr I WSVR0801I: Initializing all server configuration models [07/01/11 15:57:43:060 EST] 00000000 WorkSpaceMana A WKSP0500I: Workspace configuration consistency check is disabled. [07/01/11 15:57:43:107 EST] 00000000 AdminConfigCl A WASX7208I: Validation settings in effect now: Level=HIGHEST, Cross-validation=true, Output file=C:/Program Files/IBM/WebSphere/AppServer/profiles/ProfilSNE-MEB/logs/wsadmin.valout [07/01/11 15:57:43:138 EST] 00000000 AdminAppClien W WASX7072E: The control service is not available. [07/01/11 15:57:45:746 EST] 00000000 AbstractShell A WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "[C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\ProfilSNE-MEB\\installableApps\\SNEEAR.ear, WXP-2291Node03Cell, WXP-2291Node03, server1, SNEEAR, {{"SNEWeb.war" "SNEWeb.war,WEB-INF/web.xml" default_host}}, {{.* .* AppDeploymentOption.Yes 1}}, false, true, true, C:/Program Files/Genuitec/MyEclipse-Blue-Edition-8.6/configuration/org.eclipse.osgi/bundles/12/1/.cp/scriptutil/scriptutil.jar, C:/Program Files/IBM/WebSphere/AppServer/profiles/ProfilSNE-MEB/installedApps/WXP-2291Node03Cell/SNEEAR.ear/SNEEJB.jar, 5.0]" [07/01/11 15:57:45:746 EST] 00000000 AbstractShell A WASX7091I: Executing script: "C:\Program Files\Genuitec\Common\plugins\com.genuitec.eclipse.blue.websphere7_8.6.0.me201007292038\installEAR_EJB3.jacl" [07/01/11 15:58:08:778 EST] 00000000 wtp E org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ModuleFileImpl processNoSuchClassException Annotations scanning of archive [ SNEWeb.war ] completed with errors. [b]Could not find class [ org.apache.commons.digester.BeanPropertySetterRule ]. [07/01/11 15:58:09:262 EST] 00000000 AbstractShell E WASX7120E: Diagnostic information from exception with text "com.ibm.ws.scripting.ScriptingException: WASX7109E: Insufficient data for install task "BindJndiForEJBMessageBinding[/b] ADMA0099E: A validation error occurred in task Binding enterprise beans to listener port names or activation specification JNDI names. The listener port name or Java Naming and Directory Interface (JNDI) name is not specified for enterprise bean NotificateurMDB in module SNEEJB.jar." " follows: com.ibm.ws.scripting.ScriptingException: WASX7109E: Insufficient data for install task "BindJndiForEJBMessageBinding ADMA0099E: A validation error occurred in task Binding enterprise beans to listener port names or activation specification JNDI names. The listener port name or Java Naming and Directory Interface (JNDI) name is not specified for enterprise bean NotificateurMDB in module SNEEJB.jar." at com.ibm.ws.scripting.AbstractShell.setAndThrowScriptingException(AbstractShell.java:1813) at com.ibm.ws.scripting.AdminAppClient.prepare(AdminAppClient.java:3095) at com.ibm.ws.scripting.AdminAppClient.commonPrepare(AdminAppClient.java:3008) at com.ibm.ws.scripting.AdminAppClient.doInstall(AdminAppClient.java:2127) at com.ibm.ws.scripting.AdminAppClient.doInstall(AdminAppClient.java:2038) at com.ibm.ws.scripting.AdminAppClient.install(AdminAppClient.java:1362) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at tcl.lang.reflect.PkgInvoker.invokeMethod(PkgInvoker.java:125) at tcl.lang.JavaInvoke.call(JavaInvoke.java:263) at tcl.lang.JavaInvoke.callMethod(JavaInvoke.java:121) at tcl.lang.ReflectObject.cmdProc(ReflectObject.java:914) at tcl.lang.Parser.evalObjv(Parser.java:818) at tcl.lang.Parser.eval2(Parser.java:1221) at tcl.lang.Interp.eval(Interp.java:2222) at tcl.lang.Interp.eval(Interp.java:2276) at com.ibm.bsf.engines.jacl.JaclEngine.eval(Unknown Source) at com.ibm.bsf.util.BSFEngineImpl.exec(Unknown Source) at com.ibm.bsf.BSFManager$6.run(Unknown Source) at java.security.AccessController.doPrivileged(AccessController.java:251) at com.ibm.bsf.BSFManager.exec(Unknown Source) at com.ibm.ws.scripting.AbstractShell.executeScript(AbstractShell.java:1162) at com.ibm.ws.scripting.AbstractShell.run(AbstractShell.java:2166) at com.ibm.ws.scripting.WasxShell.main(WasxShell.java:1010) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:213) at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:93) at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:74) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340) at org.eclipse.core.launcher.Main.basicRun(Main.java:282) at org.eclipse.core.launcher.Main.run(Main.java:981) at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:330) at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:108) [07/01/11 15:58:09:262 EST] 00000000 AbstractShell A WASX7093I: Issuing message: "WASX7017E: Exception received while running file "C:\Program Files\Genuitec\Common\plugins\com.genuitec.eclipse.blue.websphere7_8.6.0.me201007292038\installEAR_EJB3.jacl"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7109E: Insufficient data for install task "BindJndiForEJBMessageBinding ADMA0099E: A validation error occurred in task Binding enterprise beans to listener port names or activation specification JNDI names. The listener port name or Java Naming and Directory Interface (JNDI) name is not specified for enterprise bean NotificateurMDB in module SNEEJB.jar." "PatrickBlais,
The application deploys and runs successfully with RAD,
Can you clarify if you are using the same version of Websphere for both RAD and MyEclipse?
Currently migration of projects within the same WAS version is supported, please refer to the following link for further reference –
https://www.genuitec.com/forums/topic/problem-when-trying-to-deploy-a-project/#post-308930Here is a tutorial on project migration from RAD to MyEclipse. Please have a look.
http://www.myeclipseide.com/documentation/quickstarts/blueedition/project_migration/As the tutorial is based on previous versions of ME, you will now have an option ‘Enhance RAD project to work with MyEclipse’ instead of ‘Migrate Project’ mentioned in the tutorial.
Let us know how it works for you.
Hi,
I’ve tried using the migration wizard and seems to have corrected the problem.I have a workspace that is compatible with RAD and MyEclipseBlue which is something nice because our build & deploy system relies on RAD config files. (It ain’t nice).
I would like to know if the option “clean” for the server is available somewhere? I seem to have something not working when deploying and would like to start the server in “clean” mode.
[10/01/11 13:39:16:336 EST] 00000017 wtp E org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ModuleFileImpl processNoSuchClassException Annotations scanning of archive [ SNEWeb.war ] completed with errors. Could not find class [ javax.servlet.annotation.HandlesTypes ]. [10/01/11 13:39:16:336 EST] 00000017 wtp E org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ModuleFileImpl processNoSuchClassException Annotations scanning of archive [ SNEWeb.war ] completed with errors. Could not find class [ javax.servlet.annotation.HandlesTypes ]. [10/01/11 13:39:16:336 EST] 00000017 wtp E org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ModuleFileImpl processNoSuchClassException Annotations scanning of archive [ SNEWeb.war ] completed with errors. Could not find class [ javax.servlet.annotation.HandlesTypes ]. [10/01/11 13:39:16:336 EST] 00000017 wtp E org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ModuleFileImpl processNoSuchClassException Annotations scanning of archive [ SNEWeb.war ] completed with errors. Could not find class [ javax.servlet.annotation.HandlesTypes ]. [10/01/11 13:39:16:336 EST] 00000017 wtp E org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ModuleFileImpl processNoSuchClassException Annotations scanning of archive [ SNEWeb.war ] completed with errors. Could not find class [ javax.servlet.annotation.HandlesTypes ]. [10/01/11 13:41:01:910 EST] 00000013 wtp E org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ModuleFileImpl processNoSuchClassException Annotations scanning of archive [ SNEWeb.war ] completed with errors. Could not find class [ javax.servlet.annotation.HandlesTypes ]. [10/01/11 13:41:01:910 EST] 00000013 wtp E org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ModuleFileImpl processNoSuchClassException Annotations scanning of archive [ SNEWeb.war ] completed with errors. Could not find class [ javax.servlet.annotation.HandlesTypes ]. [10/01/11 13:41:01:910 EST] 00000013 wtp E org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ModuleFileImpl processNoSuchClassException Annotations scanning of archive [ SNEWeb.war ] completed with errors. Could not find class [ javax.servlet.annotation.HandlesTypes ]. [10/01/11 13:41:01:910 EST] 00000013 wtp E org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ModuleFileImpl processNoSuchClassException Annotations scanning of archive [ SNEWeb.war ] completed with errors. Could not find class [ javax.servlet.annotation.HandlesTypes ]. [10/01/11 13:41:01:910 EST] 00000013 wtp E org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ModuleFileImpl processNoSuchClassException Annotations scanning of archive [ SNEWeb.war ] completed with errors. Could not find class [ javax.servlet.annotation.HandlesTypes ].@support-swapna wrote:
PatrickBlais,
The application deploys and runs successfully with RAD,
Can you clarify if you are using the same version of Websphere for both RAD and MyEclipse?
Currently migration of projects within the same WAS version is supported, please refer to the following link for further reference –
https://www.genuitec.com/forums/topic/problem-when-trying-to-deploy-a-project/#post-308930Here is a tutorial on project migration from RAD to MyEclipse. Please have a look.
http://www.myeclipseide.com/documentation/quickstarts/blueedition/project_migration/As the tutorial is based on previous versions of ME, you will now have an option ‘Enhance RAD project to work with MyEclipse’ instead of ‘Migrate Project’ mentioned in the tutorial.
Let us know how it works for you.
we are getting class not found exception while deploying EJB part of a EAR which is dependant on the other jar files which is in the root folder of the ear project. but the 2 of the jar files have the name in lower case not as per the project name declared in the eclipse org.eclipse.wst.common.component config file <wb-module deploy-name=”AppCommon”> instead of AppCommon.jar. it was appcommon.jar.
Does anyone knows what will be the issue?
