- This topic has 6 replies, 3 voices, and was last updated 13 years, 3 months ago by gbibens.
-
AuthorPosts
-
gbibensMemberHi,
I have an issue while deploying an application on Websphere 7.0 via MEB. Indeed, when I deploy the application, everythning is going well to the phase where MEB wants to start the application. There, if my undertsanding is correct, startApplication.jacl is called and it seems that server parameter passed is a wrong one. My server is named “serveur” and the server passed to startApplication.jacl is named “server1”.
The server configures on my profile is well named (ie “serveur”). The deployement script (in my case installEAR_EJB3.jacl) is getting the good server name.
I have try to comment the last line of installEAR_EJB3.jacl (# $AdminControl invoke $appManager stopApplication $appName) and it seems that this way application is deployed and started. I can access it. However there still is an error in MEB server view saying that deployement has failed. The log still gives an error about startApplication.jacl :
————————————————————————————————————————–
MyEclipse: deployment START packaged project: SNEEAR server: websphere7Server#ProfilSNE time: Tue Oct 18 13:24:21 EDT 2011
————————————————————————————————————————–
WASX7209I: Connect, au processus “serveur” sur le noeud noeud en utilisant le connecteur SOAP. Le type de processus est : UnManagedProcess
WASX7303I: Les options suivantes sont transmises … l’environnement de scriptage et sont disponibles sous forme d’arguments stock,s dans la variable argv : “[server1, SNEEAR]”
server1
SNEEAR
Starting application SNEEAR
WASX7017E: Exception re‡ue lors de l’ex,cution du fichier “C:\Program Files\MyEclipse Blue Edition\Common\plugins\com.genuitec.eclipse.blue.websphere7_9.0.0.me201103140131\startApplication.jacl” ; informations sur l’exception : com.ibm.ws.scripting.ScriptingException: WASX7025E: Erreur d,tect,e dans la chaÅ’ne “” ; impossible de cr,er ObjectName.—————————————————————————————————————
MyEclipse: deployment END project: SNEEAR server: websphere7Server#ProfilSNE time: Tue Oct 18 13:24:29 EDT 2011
—————————————————————————————————————Is there any one that kmow from where the server1 value is retrieved so that I check that it is well filled there?
Thanks,
Regards,
Guillaume
support-tonyKeymasterGuillaume,
I can’t reproduce your error. Go to the server configuration in MyEclipse, click on your profile. Does the server name show server1 or serveur? This can be edited by clinking the Edit button then clicking on Next. However, the dialog will show an error if you try to change the name from the name in the WebSphere profile. You can reload from the profile by clicking the button at the bottom.
I’ve tried a deployment on MyEclipse Blue 9.1. Are you using a different release of Blue?
gbibensMemberHello Tony,
I am actually running :
MyEclipse Blue Edition
Version: 9.0 Blue
Build id: 9.0-Blue-20110318When I go to server configuration server is shown as serveur. When application is deployed “serveur” name is well retrieved as shown in the following log :
————————————————————————————————————————–
MyEclipse: deployment START packaged project: SNEEAR server: websphere7Server#ProfilSNE time: Tue Oct 18 12:57:17 EDT 2011
————————————————————————————————————————–
WASX7209I: Connect, au processus “serveur” sur le noeud noeud en utilisant le connecteur SOAP. Le type de processus est : UnManagedProcess
WASX7303I: Les options suivantes sont transmises … l’environnement de scriptage et sont disponibles sous forme d’arguments stock,s dans la variable argv : “[C:\Program Files\IBM\WebSphere\AppServer\profiles\ProfilSNE\installableApps\SNEEAR.ear, cellule, noeud, serveur, SNEEAR, {{“SNEWeb.war” “SNEWeb.war,WEB-INF/web.xml” default_host}}, {{.* .* AppDeploymentOption.Yes 1}}, true, true, false, C:/Program Files/MyEclipse Blue Edition/MyEclipse Blue Edition 9/configuration/org.eclipse.osgi/bundles/15/1/.cp/scriptutil/scriptutil.jar, C:/Program Files/IBM/WebSphere/AppServer/profiles/ProfilSNE/installableApps/SNEEAR.ear/SNEEJB.jar, 6.0, true]”
C:\Program Files\IBM\WebSphere\AppServer\profiles\ProfilSNE\installableApps\SNEEAR.ear
cellule
noeud
serveur…
But when starting it, it seems to take value from anywhere else or a default one, like shown in previously posted log.
We have tried with several application, we actually have the issue with all application running with an EJB 3.0 project. It works fine if we have an EJB 2.0 project or if we have no EJB project.Thanks for your help,
Regards,Guillaume
support-tonyKeymasterGuillaume,
I can’t replicate the problem, here.
I’ve asked someone else to take a look at this.
However, it’s not clear that the problem is consistent. At first you said that the deployment didn’t work properly because the correct server name wasn’t being passed to the deployment tool (and the log messages showed that). But your last post seemed to show that the correct server name is now being passed in. The problem now seems to be when running your application. Is that right? If so what are the symptoms and are there any log messages related to the problem? Did you change anything to get the deployment to pass the correct server name in?
If the problem is now in running the application, can you try to remove the deployment and then deploy again to see if that cleans things up?
Another thing to try is to export the application to an EAR file and then use the WebSphere admin console to deploy the application. This would be a check of whether the problem is in the MyEclipse environment or the WebSphere environment.
Which log file contains the deployment messages that you’re posting, or is that just a copy and paste of the console messages?
gbibensMemberHello Tony,
In fact the behaviour is the same from the beginning, I will try to explain in a better way.
When launching deployment, two steps are presents into logs :
– First one is real deployment, it seems to work fine. No errors shown, at the end server is started correctly then stopped. This behaviour seems to be in accordance with what I have seen in installEAR_EJB30.jacl.
– Then, MEB try to start application, using startApplication.jacl. This step is not working because server passed to the script is server1 and not serveur.
These two steps are run automatically when I deploy the application. Result is an error shown in the server view for the global deployment (statut = redeploy).
Besides, I have try to comment the line in first step that stop the server, it still try to start it afterwards so that I still get the error. However, the server and the application are deployed correctly into WS and are accessible. This way application is functionnal but not detected as by MEB. I still have a deployment error onto ther server view.
I have also tried to install the application and to start it from WS admin console and it works fine.
Hope this is more understandable,
Thanks for your help,Best regards,
Guillaume
Brian FernandesModeratorGuillaume,
I’m sorry I missed this bug in my support pass. This issue was very categorically fixed in MyEclipse 9.1 and I see you are using 9.0. If you update to 9.1, you should not have to do anything manually and everything should work just fine. We had a hardcoded “server1” server name which was later made more intelligent.
Short of upgrading to 9.1, I’m afraid I cannot offer any other suggestions, it would be rather difficult and cumbersome to work around this problem.
Hope this helps and sorry for the delay.
gbibensMemberHello,
Thanks for the answer, we will look forward upgrading MEB version if possible,
Regards,
Guillaume -
AuthorPosts