Controlling WebSphere 8.5.5.17 with MyEclipse 2020

  1. MyEclipse IDE > WebSphere Development

This topic contains 5 replies, has 4 voices, and was last updated by  Brian Fernandes 4 days, 22 hours ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #660526 Reply

    scott.sobotka
    Participant

    Hi, Genuitec!

    I just updated my local WebSphere Application Server installation from 8.5.5.16 to 8.5.5.16 and I haven’t been able to run or debug my WAS instance from within MyEclipse ever since. I receive the following error message when I attempt to Run or Debug the WAS instance from MyEclipse:

    runConfigActions script execution failed. Exit code: 1
    Exception caught while waiting for runConfigActions script to complete: C:\was85\profiles\AppSrv01\bin\runConfigActions.bat

    That said, I’m still able to:

    • Start the instance externally via startServer.bat from a command prompt. The instance starts just as expected and the MyEclipse console will detect that the WAS instance is running and display the SystemOut.log.
    • Publish local application changes from MyEclipse to the WAS instance without issue.
    • Stop the instance from MyEclipse using the Server view.

    This is a relatively minor inconvenience, but I would like to be able to debug our applications again on this local instance.

    With regard to my development environment, I’m running on Windows Server 2019 with the following versions of MyEclipse:
    Version: 2020.5.18
    Build id: 16.0.0-20200518

    Thanks,
    Scott Sobotka

    #660532 Reply

    support-swapna
    Moderator

    Scott,

    Sorry that you are seeing this issue. Thank you for the details.
    I could replicate the issue at my end with WAS 8.5.5.17 version. A bug report is filed for the dev team to investigate further.

    As a workaround, you can create a file named runConfigActions.disableAtServerStartup (empty file) under the [profile_root]/properties/service/ directory and try starting the server again from inside MyEclipse. The suggested workaround fixes the startup problem at my end.
    Please give it a try and let us know if you see any issues.

    Apologies for inconvenience caused. Thank you once again for reporting this issue.

    –Swapna
    Genuitec Support

    #660581 Reply

    scott.sobotka
    Participant

    Hi, Swapna.

    That worked perfectly! I’ll file that away if I ever run into other WAS startup issues.

    Thank you so much!

    –Scott Sobotka

    #660607 Reply

    support-swapna
    Moderator

    Scott,

    Glad that the workaround helps. Thank you for getting back to us.
    Please let us know if you see any other issues.

    –Swapna
    Genuitec Support

    #663354 Reply

    pgillis-meb
    Participant

    Hi,

    Are there any plans to fix this issue? The workaround worked for me but I need to confirm whether we need to incorporate this into out profile creation process. Thanks.

    Pete

    #663378 Reply

    Brian Fernandes
    Moderator

    Pete,

    Yes, we do intend to fix this issue, but have been unable to prioritize a fix for the release we have due this week. We’re going to take a look at this for our next release, though I’m unsure at this time if this will be something we will be able to address in MyEclipse (via an env variable or startup switch). We will keep this thread updated with the fix progress – apologies for the delay.

Viewing 6 posts - 1 through 6 (of 6 total)
Reply To: Controlling WebSphere 8.5.5.17 with MyEclipse 2020

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