facebook

Moving from WebSphere 6.1 to 8.5 – deploy gets stuck again

  1. MyEclipse IDE
  2.  > 
  3. WebSphere Development
Viewing 15 posts - 1 through 15 (of 24 total)
  • Author
    Posts
  • #329639 Reply

    jamestthomas
    Member

    We love the tool but the weak link seems to be constant deployment issues. Generally, once we get them to work we are fine. However, I am attempting to update our enterprise web/ear project to use WS 8.5. I got the server installed and connected to our database. However deploy always stops at the same point. When I his cancel the deploy – it will not stop (potential bug). I have to close MyEclipse Blue to stop it. Attached is where it hangs up (and frankly where it always hung up in the past). Are there tips for upgrading from WS6.1 to WS8.5 as far as MyEclipse Blue is concerned?

    Attachments:
    You must be logged in to view attached files.
    #329675 Reply

    support-joy
    Member

    James,

    Sorry to hear you are running into this issue. Please answer below queries –
    1. Open MyEclipse Blue IDE, from menu options click on MyEclipse > Installation Summary > Installation Details > [Copy to Clipboard] and paste the same here
    2. From MyEclipse Blue IDE menu options click on Help > About MyEclipse Blue Edition and attach a screenshot or copy and paste the Build id and version details here.
    3. Attach a screenshot of Window > Preferences > MyEclipse > Servers > Websphere – Blue Connector > WebSphere 7.0. Select the Server Instance > Edit. This will open Edit Instance Wizard. Please attach screenshot of Edit Instance Wizard.
    3. Attach your .log file located at [your workspace dir]/.metadata/.log

    Could you try the following –
    1. From menu options click on Window > Preferences > MyEclipse > Servers > WebSphere – Blue Connector > WebSphere 7.0. Edit the server instance and change the deployment connection to Classic / Enhanced / In-Workspace Mode and check if this helps?
    2. Right click on your Project > MyEclipse > Add/Remove Project Deployments and click on [Add]. Check with the deploy type – Exploded archive and next Packaged Archive and check if that helps
    3. In case this does not help, I would recommend you do the following. Right click on your project > Export and export as WAR or EAR depending on your project
    4. Next open WAS 8.5 Administrative console and deploy your project(using the above exported war/ear file and check if there is any issue with your project?

    Let me know how this works for you.

    #329699 Reply

    jamestthomas
    Member

    Thank you for the answer. I think I need to reload WS at this point for several reasons. When I get back to this point I will report on my progress.

    #329868 Reply

    jamestthomas
    Member

    Sorry for my delay. I had ID problems at work and some of those may have confused things in the logs you requested. The ID is resolved and I am back trying to deploy. Enhanced mode did not work for me. Packaged got stuff in that said it needed to be redeployed – which would never work. Installing from admin has not worked yet – it just sits there. Now I am back in the state where I am told there are no projects to deploy – even when I delete the directories they were deployed to. I have kept the project at Java 1.5 for now, not wanting to change to much at once – I think the facet represents 1.5. Any further adivce is welcome.

    Attachments:
    You must be logged in to view attached files.
    #329873 Reply

    jamestthomas
    Member

    Attached is a screen print of where the deployment always stops when in classic mode if it is not going to work. Classic mode is the only mode we have ever gotten to work however so that is our preferred approach.

    Regards, Jim

    Attachments:
    You must be logged in to view attached files.
    #329900 Reply

    support-joy
    Member

    Jim

    Thank you for the attachments. The screenshots and installation details look good. Could you please verify the following –
    1. Please check if your exported EAR contains all the relevant files and libs.
    2. Next, can you check if you are able to deploy other projects to WAS? You could also use any of the EODs and check if you are able to deploy and run the same. To do this, from menu options click on MyEclipse > Examples on Demand. This will open Examples on Demand browser and you can click on [Install Project] to check-out any of the projects to your package explorer.

    #329907 Reply

    jamestthomas
    Member

    Joy, I went to deploy one of the EOD as you suggested. I would not accept the installation so I use the manageProfiles.bat file and eliminated my first Profile and recreated it. This time the deploy stopped with an out of memory error. You know it is really obvious to us that the only weak link in the tool is deployment woes. Anyway, I’ll adjust the heap and try again – perhaps it was working. The Ear had all the libraries needed as far as I can tell. Here is the recent deployment failure:

    —————————————————————————————————————————————–
    MyEclipse: deployment START exploded project: SupplierNetReleaseEAR server: websphere85Server#AppSrv01 time: Thu Sep 06 12:24:33 EDT 2012
    —————————————————————————————————————————————–
    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\\WebSphere\\AppServer\\profiles\\AppSrv01\\installableApps\\SupplierNetReleaseEAR.ear, CNWIN168QXNode01Cell, CNWIN168QXNode01, server1, SupplierNetReleaseEAR, {{“SupplierNetRelease.war” “SupplierNetRelease.war,WEB-INF/web.xml” default_host}}, {{.* .* AppDeploymentOption.Yes 1}}, false, false, true, D:/Program Files/MyEclipse Blue Edition/MyEclipse Blue Edition 10/configuration/org.eclipse.osgi/bundles/20/1/.cp/scriptutil/scriptutil.jar, none, 1.4, true, none]”
    D:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\installableApps\SupplierNetReleaseEAR.ear
    CNWIN168QXNode01Cell
    CNWIN168QXNode01
    server1
    SupplierNetReleaseEAR
    {“SupplierNetRelease.war” “SupplierNetRelease.war,WEB-INF/web.xml” default_host}
    {.* .* 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 {{.* .* AppDeploymentOption.Yes 1}}
    false
    false
    true
    D:/Program Files/MyEclipse Blue Edition/MyEclipse Blue Edition 10/configuration/org.eclipse.osgi/bundles/20/1/.cp/scriptutil/scriptutil.jar

    -nodeployejb
    1.4
    -processEmbeddedConfig
    JVMDUMP039I Processing dump event “systhrow”, detail “java/lang/OutOfMemoryError” at 2012/09/06 12:26:38 – please wait.
    JVMDUMP032I JVM requested System dump using ‘D:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\core.20120906.122638.12284.0001.dmp’ in response to an event
    JVMDUMP010I System dump written to D:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\core.20120906.122638.12284.0001.dmp
    JVMDUMP032I JVM requested Heap dump using ‘D:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\heapdump.20120906.122638.12284.0002.phd’ in response to an event
    JVMDUMP010I Heap dump written to D:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\heapdump.20120906.122638.12284.0002.phd
    JVMDUMP032I JVM requested Java dump using ‘D:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\javacore.20120906.122638.12284.0003.txt’ in response to an event
    JVMDUMP010I Java dump written to D:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\javacore.20120906.122638.12284.0003.txt
    JVMDUMP032I JVM requested Snap dump using ‘D:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\Snap.20120906.122638.12284.0004.trc’ in response to an event
    JVMDUMP010I Snap dump written to D:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\Snap.20120906.122638.12284.0004.trc
    JVMDUMP013I Processed dump event “systhrow”, detail “java/lang/OutOfMemoryError”.
    JVMDUMP039I Processing dump event “systhrow”, detail “java/lang/OutOfMemoryError” at 2012/09/06 12:27:13 – please wait.
    JVMDUMP032I JVM requested Heap dump using ‘D:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\heapdump.20120906.122713.12284.0005.phd’ in response to an event
    JVMDUMP010I Heap dump written to D:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\heapdump.20120906.122713.12284.0005.phd
    JVMDUMP032I JVM requested Java dump using ‘D:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\javacore.20120906.122713.12284.0006.txt’ in response to an event
    JVMDUMP010I Java dump written to D:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\javacore.20120906.122713.12284.0006.txt
    JVMDUMP032I JVM requested Snap dump using ‘D:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\Snap.20120906.122713.12284.0007.trc’ in response to an event
    JVMDUMP010I Snap dump written to D:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\Snap.20120906.122713.12284.0007.trc
    JVMDUMP013I Processed dump event “systhrow”, detail “java/lang/OutOfMemoryError”.
    WASX7017E: Exception received while running file “D:\Program Files\MyEclipse Blue Edition\Common\plugins\com.genuitec.eclipse.blue.websphere85_9.0.0.me201205210617\installEAR.jacl”; exception information: com.ibm.websphere.management.application.client.AppDeploymentException: com.ibm.websphere.management.application.client.AppDeploymentException: [Root exception is java.lang.OutOfMemoryError: Java heap space]
    java.lang.OutOfMemoryError: java.lang.OutOfMemoryError: Java heap space

    ——————————————————————————————————————————
    MyEclipse: deployment END project: SupplierNetReleaseEAR server: websphere85Server#AppSrv01 time: Thu Sep 06 12:27:25 EDT 2012
    ——————————————————————————————————————————

    #329908 Reply

    jamestthomas
    Member

    After deployment the application said Redeploy – when I did everything turned to normal as shown on attached file. However, when I go to start the server there is no mention of the application at all?? The tool is telling me it is deployed but does not start the application. I verified the files had been deployed. I bet dollars to donuts that when I go back into admin it will not list SupplierNet as an installed Enterprise application. Does 10.6 address any of these types of issues?

    Attachments:
    You must be logged in to view attached files.
    #329909 Reply

    jamestthomas
    Member

    After deployment the application said Redeploy – when I did everything turned to normal as shown on attached file. However, when I go to start the server there is no mention of the application at all?? The tool is telling me it is deployed but does not start the application. I verified the files had been deployed. I bet dollars to donuts that when I go back into admin it will not list SupplierNet as an installed Enterprise application. We are on 10.6

    #329911 Reply

    jamestthomas
    Member

    Joy, I seem to be closer. At least now there is an attempt to start the app. Please see attached log from the latest start.

    Attachments:
    You must be logged in to view attached files.
    #329946 Reply

    support-joy
    Member

    Jim,

    Is cnwin168qx.dom3.ad.sys your localhost? Could you change the weblink to http://localhost:9080/SupplierNetRelease or relevant and check if it works?

    Please confirm if you were able to run any existing EOD on WAS?

    #329950 Reply

    jamestthomas
    Member

    Hi Joy, Yes – that is localhost – the app starts with a Login page, no context – we don’t want to change the URL to the app. I’ll try what you said when I get back to a pseudo running state.

    I cannot install the eod’s – it says retrieving or some such thing then stops saying installation failed. I am considering moving the project to 1.6. I’m back to can’t deploy and even when I get the projects out there they are not recognized anymore. Should I be able to move an Enterprise application for Java 1.5 to WebSphere 8.5? Are there any gotcha’s? are you planning a tutorial on this? I have to get this going and will be trying things over again. Why would an app be in the installed app directory – fully – and when you start the server it is not started? Maybe answers to those simple questions will shed some light for me. Thank you.

    Regards, James Thomas

    #329969 Reply

    jamestthomas
    Member

    Joy, I brought in a new version of the workspace, got a clean compile then again attempted a deploy. Again it got stuck where it always does and eventually I have to close the entire application. With an Admin console install I have more luck as our application shows up in the Enterprise Applications and also the BLA which I think is new to WebSphere as we are coming from 6.1. When deployment within admin is complete, the application there but not started. When I start the app I get system out errors at times, very befuddling. I note that a connection to the database fails right off and certain classes within the app are not found . When in admin I established the JDBC data source to Oracle and the test was successful – so why when running the app it fails I do not know. Any thoughts on how to re- go about this. Should I have used a migration tool? thank you as always.

    #330008 Reply

    support-tony
    Keymaster

    James,

    I’m sorry you’re continuing to have this problem.

    As you seem to be having trouble installing EOD examples, could you please try a simple test, if you haven’t already done so. Just create an enterprise application project and create a web project to go with it. No need to add any code as the web project will just display a simple message via a JSP. See if you can deploy and run this simple enterprise project.

    Looking at the deployment log, the output looks strange about the point you say it hangs. In deploying a simple app (such as the one I mentioned above) myself, I see the following lines in the deployment log:

    .../scriptutil.jar
    1.4
    -nodeployejb
    true
    -processEmbeddedConfig
    

    Yet yours appears to be out of order:

    .../scriptutil.jar
    
    -nodeployejb
    1.4
    -processEmbeddedConfig
    

    At this point, I’m not quite sure if these differences are significant but if you get the simple application deployed, it might be instructive to check the differences in the deployment log with your failed deployment. Hopefully, testing with a simple app will give us more information to track this down.

    The answers to a couple of additional questions may be of help also. Does the exploded EAR reach the installableApps folder of the WAS profile during deployment? Can you still deploy the application to WAS 6.1?

    So far as migration between WAS releases is concerned, we don’t have any special educational materials for that, though IBM may provide some.

    #330018 Reply

    jamestthomas
    Member

    Thank you Tony, I was able to create a new Enterprise application with a web module and deploy it successfully to my server – I used the same profile in fact. It installed and ran fine. So I believe the basic installation of WebSphere is good. Here is the deployment log.

    MyEclipse: deployment START exploded project: TestProject server: websphere85Server#AppSrv01 time: Mon Sep 10 11:27:24 EDT 2012
    ——————————————————————————————————————————-
    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\\WebSphere\\AppServer\\profiles\\AppSrv01\\installableApps\\TestProject.ear, CNWIN168QXNode01Cell, CNWIN168QXNode01, server1, TestProject, {{“TestProjectWeb.war” “TestProjectWeb.war,WEB-INF/web.xml” default_host}}, {{.* .* AppDeploymentOption.Yes 1}}, false, false, true, D:/Program Files/MyEclipse Blue Edition/MyEclipse Blue Edition 10/configuration/org.eclipse.osgi/bundles/20/1/.cp/scriptutil/scriptutil.jar, none, 1.4, true, none]”
    D:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\installableApps\TestProject.ear
    CNWIN168QXNode01Cell
    CNWIN168QXNode01
    server1
    TestProject
    {“TestProjectWeb.war” “TestProjectWeb.war,WEB-INF/web.xml” default_host}
    {.* .* AppDeploymentOption.Yes 1}
    -nopreCompileJSPs -distributeApp -server “server1” -useMetaDataFromBinary -nodeployejb -appname “TestProject” -createMBeansForResources -reloadEnabled -reloadInterval 1 -deployws -validateinstall off -processEmbeddedConfig -filepermission .*.dll=755#.*.so=755#.*.a=755#.*.sl=755 -buildVersion Unknown -noallowDispatchRemoteInclude -noallowServiceRemoteInclude -MapWebModToVH {{“TestProjectWeb.war” “TestProjectWeb.war,WEB-INF/web.xml” default_host}} -JSPReloadForWebMod {{.* .* AppDeploymentOption.Yes 1}}
    false
    false
    true
    D:/Program Files/MyEclipse Blue Edition/MyEclipse Blue Edition 10/configuration/org.eclipse.osgi/bundles/20/1/.cp/scriptutil/scriptutil.jar

    -nodeployejb
    1.4
    -processEmbeddedConfig
    ADMA5016I: Installation of TestProject started.
    ADMA5058I: Application and module versions are validated with versions of deployment targets.
    WSWS0041I: Web services deploy task completed successfully.
    ADMA5005I: The application TestProject is configured in the WebSphere Application Server repository.
    ADMA5005I: The application TestProject is configured in the WebSphere Application Server repository.
    ADMA5081I: The bootstrap address for client module is configured in the WebSphere Application Server repository.
    ADMA5053I: The library references for the installed optional package are created.
    ADMA5005I: The application TestProject is configured in the WebSphere Application Server repository.
    ADMA5001I: The application binaries are saved in D:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\wstemp\Script139b0cae506\workspace\cells\CNWIN168QXNode01Cell\applications\TestProject.ear\TestProject.ear
    ADMA5005I: The application TestProject is configured in the WebSphere Application Server repository.
    SECJ0400I: Successfully updated the application TestProject with the appContextIDForSecurity information.
    ADMA5005I: The application TestProject is configured in the WebSphere Application Server repository.
    ADMA5005I: The application TestProject is configured in the WebSphere Application Server repository.
    ADMA5113I: Activation plan created successfully.
    ADMA5011I: The cleanup of the temp directory for application TestProject is complete.
    ADMA5013I: Application TestProject installed successfully.

    ———————————————————————————————————-
    In trying to bring over our 6.1 project I essentially copied the workspace, deleted all previous server references, compiled and replaced a few references. I am thinking now perhaps I should recreate the project in the tool instead of working off an old workspace. I do not have both WebSphere 6.1 and 8.5 installed on the machine I am trying this on so I can’t attempt to redeploy back to 6.1 on this machine. In comparing the deployment descriptor and application.XML files, I see no difference.
    New Ones
    #Web XML

    <?xml version=”1.0″ encoding=”UTF-8″?>
    <web-app version=”2.5″
    xmlns=”http://java.sun.com/xml/ns/javaee&#8221;
    xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance&#8221;
    xsi:schemaLocation=”http://java.sun.com/xml/ns/javaee
    http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd”&gt;
    <display-name></display-name>
    <welcome-file-list>
    <welcome-file>index.jsp</welcome-file>
    </welcome-file-list>
    </web-app>

    #Application.xml

    <?xml version=”1.0″ encoding=”UTF-8″?>
    <application xmlns=”http://java.sun.com/xml/ns/javaee&#8221; xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance&#8221; version=”5″
    xsi:schemaLocation=”http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd”><description></description&gt;
    <display-name>TestProject</display-name>
    <icon></icon><module id=”myeclipse.1347290516079″>
    <web>
    <web-uri>TestProjectWeb.war</web-uri>
    <context-root>/TestProjectWeb</context-root>
    </web>
    </module>
    </application>

    Top of my project descriptor
    <?xml version=”1.0″ encoding=”UTF-8″?>
    <web-app version=”2.5″
    xmlns=”http://java.sun.com/xml/ns/javaee&#8221;
    xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance&#8221;
    xsi:schemaLocation=”http://java.sun.com/xml/ns/javaee
    http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd”&gt;
    <display-name>SupplierNetRelease</display-name>

    I am afraid a few jars I had to bring in may be incompatible so will be trying to recreate the workspace from scratch. Does that sound reasonable?

Viewing 15 posts - 1 through 15 (of 24 total)
Reply To: Moving from WebSphere 6.1 to 8.5 – deploy gets stuck again

You must be logged in to post in the forum log in