facebook

WebSphere deployment not working with Windows 10 update 20H2

  1. MyEclipse IDE > WebSphere Development
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #674489 Reply

    Boeing-107
    Participant

    I have been running my application through MyEclipse and WebSphere for many years, with the deployments and refreshes working fairly well, occasional redeploy required, but typically functioning well. I had not updated WAS or MyEclipse in a while, I was running My Eclipse 2017 and WebSphere 8.5.5 in my local dev environment without issues. I recently had the Windows 10 update 20H2 pushed to my machine and after this I have not been able to successfully deploy. I cannot guarantee that the windows update was the cause, but it seems to be the timing of when it stopped working.
    I first saw this in my development branch, I have switched to my stable released branch and I am still seeing the same issues

    Now when I do a deployment and start the application I receive a message “Enterprise JavaBeans (EJB) module does not have any enterprise beans configured” and it shuts down the application. The deployment itself reports that it is successful. In the WAS installedApps folder (using classic deploy) there is a folder vector-ejb.jar_extract, where in a successful deploy I see it without the _extract extension.
    I have since updated my local environment, WAS 9.x and the current MyEclipse 2021.5.24
    Unfortunately after a full rebuild of the environment I am still seeing the same behavior.

    With the 2021 update of MyEclipse I am now seeing a bit more logging from the deployment, this seems to be the implementation of the EJB

    [6/15/21 11:01:10:885 EDT] 000000d9 DeployEJBTask I ADMA0158I: [EJBDeploy] Deploying jar vector-ejb
    [6/15/21 11:01:11:389 EDT] 000000d9 DeployEJBTask I ADMA0158I: [EJBDeploy] Generating deployment code
    [6/15/21 11:01:11:402 EDT] 000000d9 DeployEJBTask I ADMA0158I: [EJBDeploy] Refreshing ‘/vector-ejb/ejbModule’.
    [6/15/21 11:01:13:184 EDT] 000000d9 DeployEJBTask I ADMA0158I: [EJBDeploy] Invoking ‘Java Builder’ on ‘/vector-ejb’.
    [6/15/21 11:01:13:193 EDT] 000000d9 DeployEJBTask I ADMA0158I: [EJBDeploy] Preparing to build vector-ejb
    [6/15/21 11:01:13:270 EDT] 000000d9 DeployEJBTask I ADMA0158I: [EJBDeploy] Cleaning output folder for vector-ejb
    [6/15/21 11:01:13:272 EDT] 000000d9 DeployEJBTask I ADMA0158I: [EJBDeploy] Copying resources to the output folder
    [6/15/21 11:01:13:370 EDT] 000000d9 DeployEJBTask I ADMA0158I: [EJBDeploy] Analyzing sources
    [6/15/21 11:01:13:434 EDT] 000000d9 DeployEJBTask I ADMA0158I: [EJBDeploy] Build done
    [6/15/21 11:01:13:436 EDT] 000000d9 DeployEJBTask I ADMA0158I: [EJBDeploy] Invoking ‘Faceted Project Validation Builder’ on ‘/vector-ejb’.
    [6/15/21 11:01:13:448 EDT] 000000d9 DeployEJBTask I ADMA0158I: [EJBDeploy] Invoking ‘Validation’ on ‘/vector-ejb’.
    [6/15/21 11:01:13:449 EDT] 000000d9 DeployEJBTask I ADMA0158I: [EJBDeploy] Invoking ‘Faceted Project Validation Builder’ on ‘/vector-core.ear’.
    [6/15/21 11:01:13:450 EDT] 000000d9 DeployEJBTask I ADMA0158I: [EJBDeploy] Invoking ‘Validation’ on ‘/vector-core.ear’.
    [6/15/21 11:01:13:554 EDT] 000000d9 DeployEJBTask I ADMA0158I: [EJBDeploy] Invoking RMIC.
    [6/15/21 11:01:13:561 EDT] 000000d8 DeployEJBTask I ADMA0158I: [EJBDeploy] Jun 15, 2021 11:01:13 AM com.ibm.etools.ejbdeploy.logging.Logger logInfo
    [6/15/21 11:01:13:562 EDT] 000000d8 DeployEJBTask I ADMA0158I: [EJBDeploy] INFO: 0 class files
    [6/15/21 11:01:13:588 EDT] 000000d9 DeployEJBTask I ADMA0158I: [EJBDeploy] Writing output file
    [6/15/21 11:01:13:688 EDT] 000000d9 DeployEJBTask I ADMA0158I: [EJBDeploy] Exporting archive ‘dpl_vector-core.ear’. Refreshing ‘/vector-core.ear’.
    [6/15/21 11:01:13:707 EDT] 000000d9 DeployEJBTask I ADMA0158I: [EJBDeploy] Exporting archive ‘dpl_vector-core.ear’.
    [6/15/21 11:01:21:623 EDT] 000000d9 DeployEJBTask I ADMA0158I: [EJBDeploy] Shutting down workbench.
    [6/15/21 11:01:22:497 EDT] 000000d9 DeployEJBTask I ADMA0158I: [EJBDeploy] EJBDeploy complete.
    [6/15/21 11:01:22:498 EDT] 000000d9 DeployEJBTask I ADMA0158I: [EJBDeploy] 0 Errors, 0 Warnings, 0 Informational Messages

    I am not seeing any errors in here, but it is reporting 0 files, somewhere it seems an error is being swallowed, just not sure where it is failing.

    If I try and use the ‘In-workspace’ deployment mode I receive a classloading exception that I have never been able to work around, tried this route for a while with no success.

    Thanks
    -Scott

    #674500 Reply

    support-swapna
    Moderator

    Hi,

    Sorry that you are seeing this issue.

    1. Please share the .log file located at workspace dir/.metadata/.log to help us check for any errors logged.
    2. Are you working with EJB 2.x or 3.x?
    3. Can you check if you can manually extract the EJB jar in the WAS InstalledApps folder, to rule out any OS related issues with extraction?
    4. If possible, can you please export the EAR and deploy it to Websphere outside of MyEclipse to rule out any issues with the project/server itself?

    –Swapna
    Genuitec Support

    #674546 Reply

    Brian Fernandes
    Moderator

    Scott,

    Just checking in to see if you were able to make any progress on your deployment issues. Given the many changes you’ve made, getting a baseline export working would be a good step. This is what Swapna suggested in #4 – if you can export the EAR and use the WAS admin console to deploy it, does that work, does the application come up successfully?

    Do let us know how we can help.

    #674567 Reply

    Boeing-107
    Participant

    Yes, thank you. I do have it working. I was unaware of the log file that was referenced in 1
    That was the key to uncovering my problem. There was an error in there that was not being reported anywhere else, the error was relating to MyEclipse now trying to resolve a xsd with the name of one of the projects in it, this project had a space in the name and this caused everything to fail and not function. As soon as I removed the space from the name of the project, everything worked correctly.

    Removed the error text, as my post was blocked.

    Once I added a – to the middle of the project name it started working correctly. This name appears to be derived from the name element of the maven project file.

    #674568 Reply

    Boeing-107
    Participant

    Now separately trying to add the error message

    !ENTRY org.springframework.ide.eclipse.xml.namespaces 4 0 2021-06-09 13:28:32.232
    !MESSAGE Plugin.internal_error
    !STACK 0
    java.net.URISyntaxException: Illegal character in authority at index 16: project-aware://vector utilities/schemas/core.xsd
    at java.base/java.net.URI$Parser.fail(URI.java:2938)
    at java.base/java.net.URI$Parser.parseAuthority(URI.java:3272)
    at java.base/java.net.URI$Parser.parseHierarchical(URI.java:3183)
    at java.base/java.net.URI$Parser.parse(URI.java:3139)
    at java.base/java.net.URI.<init>(URI.java:623)
    at org.springframework.ide.eclipse.xml.namespaces.internal.ProjectClasspathUriResolver.getTargetNamespace(ProjectClasspathUriResolver.java:180)….

Viewing 5 posts - 1 through 5 (of 5 total)
Reply To: WebSphere deployment not working with Windows 10 update 20H2

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