- This topic is empty.
-
Posts
-
Jim,
So, just to be clear. You, yourself, are not having any of the problems on the machine you cleared up and the disabled Finish button is only a problem when you are trying to deploy (in this case an EAR project) to a profile that already has a partial deploy (due to the previous unending deploy), and the project causing the problem is one created with WebSphere Development Studio Client for iSeries? Is that right?
Your colleague is now trying to create a clean Websphere profile with the database connection set up properly for the deploy and you’ll let us know if that works. Is that right?
Thanks for your patience and sorry you and your colleague are seeing these problems.
I am Jim’s colleague from his previous post.
I migrated my application to a new Workspace, created a new WAS 6.1 profile (server loaded on same PC), and restarted Blue with -clean in the ini settings. The deployment started and appeared to hang at the same point in the log as in Jim’s first post. I left work with it running. When I returned, the deployment had completed…11 hours later… with no intervening activity. I tested the application and it is running successfully, but would like to know what might have caused the long deployment.
I returned to my original workspace, and tried the deployment there, and again it has taken over 1 hour so far and is not completed.
The deployment time is too long to be practical. Can you tell us how to troubleshoot this problem?
mnovak5528,
Jim had previously said that a deployment from the admin console also takes a long time. Can you try that also? Export to an EAR or a WAR and try to deploy from the WAS admin console. MyEclipse is basically using the tools WebSphere provides, so the deployment time should be very similar. If deploying outside of MyEclipse is not as slow then the problem is with MyEclipse and I’ll get a developer to look at it, but it’s hard to track down without a means to replicate the problem, like a project that always takes a long time to deploy on any machine.
Following Tony’s advice, we ran the deploy from the admin console and got the same long delay. We then checked IBM’s support web site and determined there are a lot of long deployment issues with older subversions of WAS 6.1. So I upgraded the server from 6.1.0.29 to 6.1.0.39 (current version), and the long deployment problem has gone away. Initial deployments are now taking a more typical time < 10 minutes.
