- This topic is empty.
-
Posts
-
I have ported our RAD project successfully to My Eclipse Blue. It was difficult but we have released to production. Now I have a new machine and am deploying the project. I had noticed this before but I have to ask, sometimes when I am deploying the app to WebSphere 6.1.0.29, the deployment gets stuck. My Deployment log has not changed in about 15 minutes.
MyEclipse: deployment START exploded project: SupplierNetReleaseEar server: websphere61Server#AppSrv04 time: Tue Sep 13 13:39:25 EDT 2011
—————————————————————————————————————————————–
WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: “[D:\\Program Files\\IBM\\SDP70\\runtimes\\base_v61\\profiles\\AppSrv04\\installableApps\\SupplierNetReleaseEar.ear, CNWIN168QXNode03Cell, CNWIN168QXNode03, server1, SupplierNetReleaseEar, {{“SupplierNetRelease.war” “SupplierNetRelease.war,WEB-INF/web.xml” default_host}}, {{“null” “SupplierNetRelease.war,WEB-INF/ibm-web-ext.xmi”AppDeploymentOption.Yes 1}}, false, false, true, D:/Program Files/MyEclipse Blue Edition/MyEclipse Blue Edition 9/configuration/org.eclipse.osgi/bundles/16/1/.cp/scriptutil/scriptutil.jar, true]”
D:\Program Files\IBM\SDP70\runtimes\base_v61\profiles\AppSrv04\installableApps\SupplierNetReleaseEar.ear
CNWIN168QXNode03Cell
CNWIN168QXNode03
server1
SupplierNetReleaseEar
{“SupplierNetRelease.war” “SupplierNetRelease.war,WEB-INF/web.xml” default_host}
{“null” “SupplierNetRelease.war,WEB-INF/ibm-web-ext.xmi”AppDeploymentOption.Yes 1}
-nopreCompileJSPs -distributeApp -server “server1” -useMetaDataFromBinary -nodeployejb -appname “SupplierNetReleaseEar” -createMBeansForResources -reloadEnabled -reloadInterval 1 -deployws -validateinstall off -processEmbeddedConfig -filepermission .*.dll=755#.*.so=755#.*.a=755#.*.sl=755 -buildVersion Unknown -noallowDispatchRemoteInclude -noallowServiceRemoteInclude -MapWebModToVH {{“SupplierNetRelease.war” “SupplierNetRelease.war,WEB-INF/web.xml” default_host}} -JSPReloadForWebMod {{“null” “SupplierNetRelease.war,WEB-INF/ibm-web-ext.xmi”AppDeploymentOption.Yes 1}}
false
false
true
D:/Program Files/MyEclipse Blue Edition/MyEclipse Blue Edition 9/configuration/org.eclipse.osgi/bundles/16/1/.cp/scriptutil/scriptutil.jar
true
-nodeployejb
-processEmbeddedConfig
ADMA5016I: Installation of SupplierNetReleaseEar started.
ADMA5058I: Application and module versions are validated with versions of deployment targets.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
WSWS0039W: Warning from Web services deploy tool: Warning messages were issued.
ADMA5005I: The application SupplierNetReleaseEar is configured in the WebSphere Application Server repository.
ADMA5053I: The library references for the installed optional package are created.
ADMA5005I: The application SupplierNetReleaseEar is configured in the WebSphere Application Server repository.
ADMA5001I: The application binaries are saved in D:\Program Files\IBM\SDP70\runtimes\base_v61\profiles\AppSrv04\wstemp\Script13263df4d34\workspace\cells\CNWIN168QXNode03Cell\applications\SupplierNetReleaseEar.ear\SupplierNetReleaseEar.ear
ADMA5005I: The application SupplierNetReleaseEar is configured in the WebSphere Application Server repository.
SECJ0400I: Successfuly updated the application SupplierNetReleaseEar with the appContextIDForSecurity information.SInce I have noticed this before, and I was warned before hand to configure the deployment connection in classic mode as enhanced deployment goes on forever, I wanted to ask if this is a bug anyone is working on. Steps to replicate – get a hefty Enterprise Java Web with a WEB – tier and an EAR FILE. Reuse the IBM WEBSphere installation runtimes base_v61. Try to deploy. Good luck.
jamestthomas ,
Sorry that you are seeing this issue with MyEclipse.
Can you give us some more information for us to investigate further ?
1) Is this issue intermittent ?
2) Do you see the issue with both Classic and Enhanced modes?
3) Did you try the new in-workspace deployment ? If no then can you please try it and let us know if you see any issues ?
4) Also can you check if there are any errors of interest logged in the .log file which is located at <workspace dir>/.metadata/.log when the issue happens? If yes then paste them here for us.
1. The issue is steady – cannot get server to accept deployed project – deployment never stops.
2. When things were working Enhanced Mode was still something we avoided as it always took too long.
3. In workspace deployment was not tried because no deployment was working – I will try that but I do not expect any change.Attached is the log
Jim,
Just to be clear, on your first post, you said:
sometimes when I am deploying the app to WebSphere 6.1.0.29, the deployment gets stuck
Yet in your latest post, you said it wasn’t an intermittent problem (i.e. happens on every deployment). Could you confirm that you cannot deploy because of this error?
The log file you posted is quite large, covering many sessions. Could you please delete the log, recreate the problem and then post the resulting log. This will help narrow down any logged problems that relate to your issue.
However, firstly, it might be helpful to run MyEclipse Blue with the clean flag (see https://www.genuitec.com/forums/topic/troubleshoot-using-the-clean-command-line-argument/) and also try with a fresh workspace (see this FAQ for some help with that). These actions will help make sure that there aren’t any corrupted files hanging around that could cause the error you’re seeing.
Do you have any colleagues who also have the same problem? We sometimes see problems reported that aren’t seen by other developers at the same site and it often comes down to a different setup, in some way.
The new in-workspace mode of deployment uses a different technique, so it may give different results and, if it works for you, might be a much nicer way of developing.
The reference to sometimes the deployment get stuck is based on the fact that I have in the past deployed successfully. I first put MEB on a test machine, loaded our project and eventually deployed it not only locally but to our test server. That’s why we bought 6 licenses. For some reason the server stopped opening properly on the test machine last week. I can deploy to that machine but the site will not work. Starting the server gives me the following glitch when it gets to our app:
[9/19/11 16:20:05:131 EDT] 00000015 WSServerImpl E WSWS1002E: An error occurred while processing the Web services deployment descriptor for module: SupplierNetRelease.war with error: com.ibm.ws.webservices.engine.deployment.wsdd.WSDDException: java.lang.ClassCastException: com.ibm.ws.webservices.engine.encoding.ser.BeanSerializerFactory incompatible with com.ibm.ws.webservices.engine.encoding.SerializerFactory
java.lang.ClassCastException: com.ibm.ws.webservices.engine.encoding.ser.BeanSerializerFactory incompatible with com.ibm.ws.webservices.engine.encoding.SerializerFactory
at com.ibm.ws.webservices.engine.encoding.ser.BaseSerializerFactory$CreateFactoryPRIThat is one problem. I have tried to see if I have conflicting versions of files but have not found them yet.
Second issue: On my regular machine which has IBM development studio on it I installed MEB and attempted to use the already installed WebSphere 6.1.0.29 – just as we use in test and production. On that machine deployment has just run for an hour and a half and I had to close the tool. The attached log is a reduced copy containing one days attempted deploy. In workspace mode so far has not cured either problem. If I could get one to work for now, I could go on. Any thoughts on the test machine class issue? Any ideas from the log from my regular machine.
James,
You didn’t say whether you’d tried the clean flag and/or a clean workspace.
If neither of the above work, please try performing the deployment and startup outside of MyEclipse. This might help us determine whether the problem is outside of MyEclipse.
Did the test machine problem occur after a deployment from MyEclipse or did it occur with a deployment that had previously started OK? It seems like something changed in the WebSphere set-up that you might not be aware of.
I’m not familiar with IBM development studio but on your regular machine, have you never succeeded with a deployment? Again, I’d suggest the clean flag and fresh workspace, plus trying deployment outside of MyEclipse (you can export your project as a WAR or an EAR, and use the WebSphere admin console to deploy.
Let me know how this goes so we can, hopefully, get more useful information on this.
I have attached a document with screen prints and comments. I did try -clean to no avail. In workspace deployment I tried on my test machine – but the site does not come up. Please see my attachment.
James,
Thanks for the screen shots but I’m not clear on any of my other questions or which suggestions have been tried.
Have you tried a new workspace? Import your project(s) into that new workspace, configure the serve and try a deploy.
Have you tried deploying outside of MyEclipse? Export the project to an EAR or WAR and then use the WAS admin console to deploy from that file. Does that work OK?
For your colleagues’ slow deployments, how does the deploy time compare with deploying from the WAS admin console? MyEclipse uses WAS deployment tools, so there shouldn’t be much difference in timing. However, as your colleagues can deploy successfully, this suggests some difference between their setups and your setup. Could you look into that?
Reinstalling MyEclipse Blue Edition can also sometimes help, if the -clean flag and fresh workspace doesn’t.
If you still have the problem, can you clear the log, recreate the problem and then attach the log, so that there are only messages that might be related to the deployment problem.
I’m not sure why the Finish button doesn’t enable but sometimes fiddling with the dialog controls helps with this sort of thing (like selecting something else from the drop-down box then selecting the project you want, or clicking on the radio buttons).
I was hoping what I showed you might relate to something you have seen before. As far as what options have been tried, today I am going to start with a new work space.
>Have you tried a new workspace? Import your project(s) into that new workspace, >configure the serve and try a deploy.
I am trying a new workspace today. I have set up workspaces from scratch and wrote the directions we follow here. The workspace I was working on was new last week.
>Have you tried deploying outside of MyEclipse? Export the project to an EAR or WAR >and then use the WAS admin console to deploy from that file. Does that work OK?
I did try that and got the application to come up but it had some problems. Plus the development environment would be unusable for me. It had failed deploys still showing in the server screen and stopping and restarting the server was problematic.
>For your colleagues’ slow deployments, how does the deploy time compare with >deploying from the WAS admin console? MyEclipse uses WAS deployment tools, so >there shouldn’t be much difference in timing. However, as your colleagues can deploy >successfully, this suggests some difference between their setups and your setup. >Could you look into that?
Deployment from the admin console still took a long time on my machine. Everything you are saying are the things I basically try. I am working with a co-worker who has the set up I want. Oddly, created with my instructions. Something got off. I can say it can be a fragile situation …. this is the most stuck I have been in years on anything… very frustrating.
>Reinstalling MyEclipse Blue Edition can also sometimes help, if the -clean flag and fresh >workspace doesn’t.
>If you still have the problem, can you clear the log, recreate the problem and then attach >the log, so that there are only messages that might be related to the deployment problem.
Yep that’s the next step.
>I’m not sure why the Finish button doesn’t enable but sometimes fiddling with the dialog >controls helps with this sort of thing (like selecting something else from the drop-down >box then selecting the project you want, or clicking on the radio buttons).
That looks like a bug to me, the fooling around to get the finish button to enable should not be necessary. It should be consistent. I have to solve this today so I’ll post the solution tomorrow.
I started from scratch. New workspace – everything exactly as set up on my friends machine. Deployment actually finished. When trying to run the site I got a virtual host not defined. Then when I tried to stop the server I got:
ADMU0116I: Tool information is being logged in file D:\Program
Files\IBM\SDP70\runtimes\base_v61\profiles\AppSrv03\logs\server1\stopServer.log
ADMU0128I: Starting tool with the AppSrv03 profile
ADMU3100I: Reading configuration for server: server1
ADMU0111E: Program exiting with error: javax.management.JMRuntimeException:
ADMN0022E: Access is denied for the stop operation on Server MBean
because of insufficient or empty credentials.
ADMU4113E: Verify that username and password information is correct. If
running tool from the command line, pass in the correct -username
and -password. Alternatively, update the <conntype>.client.props
file.
ADMU1211I: To obtain a full trace of the failure, use the -trace option.
ADMU0211I: Error details may be seen in the file: D:\Program
Files\IBM\SDP70\runtimes\base_v61\profiles\AppSrv03\logs\server1\stopServer.logDoes the above give us a clue here? Thank you. James
James,
It looks like some progress has been made as you can now deploy from MyEclipse.
Do you have administrative security enabled on the WebSphere profile that you are using from MyEclipse? That’s the only reason I can think of for the message you got when you tried to stop the server. It is recommended that you don’t enable administrative security for a development system.
I think you’ve seen that deployment is slow from the WAS admin console and we can’t speed that up with MyEclipse. However, once deployed, the deployment should be kept in sync with changes you make in the IDE.
For the Finish button not being enabled, you’re right that you shouldn’t need to fiddle with the dialog controls to get it to enable but did it work, and are you still seeing the same problem following your setup changes? If you are still seeing the problem, I’ll raise a bug report against it.
Hi Tony, I eventually got my test machine to work and I have left my regular machine for later. The problem with the test machine was the project somehow was no longer being recognized as an Enterprise Java Application. I created a new workspace and after that things fell into place. My comrade who was working fine has uninstalled his WebSphere Development Studio Client for iSeries (this is what I have on my regular machine – as the development environment we are replacing). That means he has to install WebSphere on his machine. At one point he started a deploy and it never stopped… what I complained about. He had to shut down My Eclipse Blue and reboot. (I suggested you could also open task manager and kill java). Any way he made adjustments to the server through admin console which he should have done first actually. However when he went to deploy again – the partial deploy leaves My Eclipse Blue in a bad state. It does not recognize a partial deploy. We got the same window I stated to you I though was a bug. You said do send it in if we got it again. look at the attached. See how Finish is not enabled regardless of what you pick. As developers we have a good sense this is a bug you may want to look into.
Jim,
A partial deploy won’t be recognized as other than something has been deployed where MyEclipse Blue wants to deploy a project. However, the disabling of the Finish button is a puzzle and not something I can replicate here. I presume you’re not now having that problem?
Can your colleague try a new workspace, as you did, as a way to get everything working again?
What type of project is it? A Web project or an Enterprise Application Project? Is it a RAD migrated project? I’d like to file a problem report for the disabled Finish button but will need information about the project that causes it and the conditions under which it occurs.
Our projects were originally developed on WebSphere Development Studio Client for iSeries. I explained how some deployments never stop. This can only be stopped by shutting down Eclipse, going into task manager and killing java, then reopen. My colleague was originally working with a profile from his wdsc server supplied server which is WebSphere 6.1. He eventually wanted to clear all wdsc off his machine. He did that, installed WebSphere available from IBM – and successfully applied Service Pak 29 and the package for web services you have in your tutorial. All went well. He created a profile. He pulled our application into his workspace. We cleared errors. By mistake, my friend began to deploy the Enterprise Application Ear file. However, we first should go into the admin council to set up the server for database connections and yada yada yada. He forgot to do that so got an endless deploy. Again the deployment configuration file last entry began with a mis-spelled succesfully. I told him to stop Eclipse – you also have to check task manager for java still running and kill it. Then he went into admin council, adjusted his server as needed. Attempts to redeploy produced the screen I sent you. We are now deleting profiles using the manageprofiles.bat file. He is trying to get a clean profile and hope deploy succeeds. The screen print must be a flaw because it does not function correctly.
