Topic
  • 11 replies
  • Latest Post - ‏2013-04-04T14:59:41Z by adbdkb
adbdkb
adbdkb
46 Posts

Pinned topic Error in importing an EAR file in RAD 8 - The selected runtime does not sup

‏2013-03-28T23:36:05Z |
We have an EAR file which is deployed in production and is running under websphere 7. This EAR also includes source.

We need to go back to the version of code to the time of the EAR creation, so we tried to import it as an EAR in RAD.

Initially, we get this error - The selected runtime does not support the version of the archive. It is a dropdown showing websphere 7 and none. If we select None and somehow get the EAR imported and compiled / built, when trying to run it on server, we are getting Server does not support version 3.0 of the J2EE module Specification.

How can we resolve it? I have been unable to find what causes the initial error about server runtime and version of archive. How / where can I check, so if I can correctly bring in the EAR in RAD, i may not get the error about module specification version.

Thank you for any help
Updated on 2013-04-04T14:59:41Z at 2013-04-04T14:59:41Z by adbdkb
  • ivyho
    ivyho
    67 Posts

    Re: Error in importing an EAR file in RAD 8 - The selected runtime does not sup

    ‏2013-03-29T03:05:06Z  
    If your EAR is running on Websphere Application server 7, the highest web module version it will support is 2.5

    Only starting Websphere Application server 8, web module version 3.0 is supported.

    When you import the EAR into the RAD workspace, you will need to target a runtime time, so <None> is not a correct selection.

    You should target the WAS 7 runtime, after it is imported to the workspace , you can go to your Project->Properties
    Under Project Facets - Dynamic Web Module
    You should be able to see what versions your projects are .

    But you have to find out what web module your
    project used before and was it created from previous version of RAD?

    Hope this help
  • adbdkb
    adbdkb
    46 Posts

    Re: Error in importing an EAR file in RAD 8 - The selected runtime does not sup

    ‏2013-03-29T12:10:17Z  
    • ivyho
    • ‏2013-03-29T03:05:06Z
    If your EAR is running on Websphere Application server 7, the highest web module version it will support is 2.5

    Only starting Websphere Application server 8, web module version 3.0 is supported.

    When you import the EAR into the RAD workspace, you will need to target a runtime time, so <None> is not a correct selection.

    You should target the WAS 7 runtime, after it is imported to the workspace , you can go to your Project->Properties
    Under Project Facets - Dynamic Web Module
    You should be able to see what versions your projects are .

    But you have to find out what web module your
    project used before and was it created from previous version of RAD?

    Hope this help
    Unfortunately, I have no way to find out how the EAR was created. I have been asked to help with bringing it in.

    The application.xml in the EAR shows the version is 1.4

    <application id="Application_ID" version="1.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd">
    I agree, that None is not a correct selection, but Websphere 7 selection gives an error - The selected runtime does not support the version of the archive

    So, initially, I selected None and tried to change Facets and exported the Project Interchange.

    I actually do not know, where the error for Server does not support version 3.0 of the J2EE module Specification - is coming from. The web.xml shows the version to be 2.5

    <web-app id="WebApp_ID" version="2.5"
    xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
    But the weird part is Project Facets -> Dynamic Web Module shows 3.0 and if I try to change that to 2.5. it says, Caanot change the version of project facet Dynamic Web Module to 2.5.

    I am really confused :(
    Any pointers?

    Thanks a lot
  • SystemAdmin
    SystemAdmin
    14225 Posts

    Re: Error in importing an EAR file in RAD 8 - The selected runtime does not sup

    ‏2013-04-02T10:22:57Z  
    • adbdkb
    • ‏2013-03-29T12:10:17Z
    Unfortunately, I have no way to find out how the EAR was created. I have been asked to help with bringing it in.

    The application.xml in the EAR shows the version is 1.4

    <application id="Application_ID" version="1.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd">
    I agree, that None is not a correct selection, but Websphere 7 selection gives an error - The selected runtime does not support the version of the archive

    So, initially, I selected None and tried to change Facets and exported the Project Interchange.

    I actually do not know, where the error for Server does not support version 3.0 of the J2EE module Specification - is coming from. The web.xml shows the version to be 2.5

    <web-app id="WebApp_ID" version="2.5"
    xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
    But the weird part is Project Facets -> Dynamic Web Module shows 3.0 and if I try to change that to 2.5. it says, Caanot change the version of project facet Dynamic Web Module to 2.5.

    I am really confused :(
    Any pointers?

    Thanks a lot
    As a wild guess: it might be that somehow the web.xml is not being found during the import. Since projects without web.xml are allowed starting from web module v3.0, it could be that importer algorithm then assumes that this is a web 3.0 product.
    If you cannot figure out why the web.xml is not being picked up, I recommend opening a support case and supplying that ear file for investigation.

    https://www-947.ibm.com/support/servicerequest/Home.action
  • SystemAdmin
    SystemAdmin
    14225 Posts

    Re: Error in importing an EAR file in RAD 8 - The selected runtime does not sup

    ‏2013-04-02T15:43:53Z  
    • adbdkb
    • ‏2013-03-29T12:10:17Z
    Unfortunately, I have no way to find out how the EAR was created. I have been asked to help with bringing it in.

    The application.xml in the EAR shows the version is 1.4

    <application id="Application_ID" version="1.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd">
    I agree, that None is not a correct selection, but Websphere 7 selection gives an error - The selected runtime does not support the version of the archive

    So, initially, I selected None and tried to change Facets and exported the Project Interchange.

    I actually do not know, where the error for Server does not support version 3.0 of the J2EE module Specification - is coming from. The web.xml shows the version to be 2.5

    <web-app id="WebApp_ID" version="2.5"
    xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
    But the weird part is Project Facets -> Dynamic Web Module shows 3.0 and if I try to change that to 2.5. it says, Caanot change the version of project facet Dynamic Web Module to 2.5.

    I am really confused :(
    Any pointers?

    Thanks a lot
    Hello,

    What version of RAD are you using? Does the EAR have only web modules? or other modules like EJB? Do all your modules have deployment descriptors? If yes, what's their versions?

    At what point do you see the error? at the third page of the wizard, which says "EAR Module and Utility JAR projects? If you have multiple modules, have yo tried unchecking modules to find which module is the one that is not supported by the target runtime?

    When a target runtime is selected, the EAR import wizard verifies that the target runtime supports the version of all modules in the EAR (including the EAR) specified in the deployment descriptor. If a module does not have deployment descriptor, then the project is imported with the highest facet supported by the target runtime.

    Also, I suggest to verify the EAR does not contain metadata that should not be there. For example, should not contain a .settings folder in any of the modules.

    And as Lara suggested, you could also open a support case.
  • adbdkb
    adbdkb
    46 Posts

    Re: Error in importing an EAR file in RAD 8 - The selected runtime does not sup

    ‏2013-04-02T16:29:46Z  
    Hello,

    What version of RAD are you using? Does the EAR have only web modules? or other modules like EJB? Do all your modules have deployment descriptors? If yes, what's their versions?

    At what point do you see the error? at the third page of the wizard, which says "EAR Module and Utility JAR projects? If you have multiple modules, have yo tried unchecking modules to find which module is the one that is not supported by the target runtime?

    When a target runtime is selected, the EAR import wizard verifies that the target runtime supports the version of all modules in the EAR (including the EAR) specified in the deployment descriptor. If a module does not have deployment descriptor, then the project is imported with the highest facet supported by the target runtime.

    Also, I suggest to verify the EAR does not contain metadata that should not be there. For example, should not contain a .settings folder in any of the modules.

    And as Lara suggested, you could also open a support case.
    RAD 8.0.4.2 ( ifix1 ). It has only web modules ( just a single one ) and all modules have deployment descriptors - application.xml and web.xml - respectively.

    I see the error right at the first step, when I select the EAR file to import - it auto selects the websphere 7 runtime and gives the error.

    It doesn't even reach the EAR Module and Utility Jar projects part. And I verified that there is no .settings folder anywhere

    Opening a support case may be an option - sometimes, it takes long to get that resolved than getting answers on the forums from knowledgeable people - so I have left it as a last one.
  • adbdkb
    adbdkb
    46 Posts

    Re: Error in importing an EAR file in RAD 8 - The selected runtime does not sup

    ‏2013-04-02T16:29:50Z  
    Hello,

    What version of RAD are you using? Does the EAR have only web modules? or other modules like EJB? Do all your modules have deployment descriptors? If yes, what's their versions?

    At what point do you see the error? at the third page of the wizard, which says "EAR Module and Utility JAR projects? If you have multiple modules, have yo tried unchecking modules to find which module is the one that is not supported by the target runtime?

    When a target runtime is selected, the EAR import wizard verifies that the target runtime supports the version of all modules in the EAR (including the EAR) specified in the deployment descriptor. If a module does not have deployment descriptor, then the project is imported with the highest facet supported by the target runtime.

    Also, I suggest to verify the EAR does not contain metadata that should not be there. For example, should not contain a .settings folder in any of the modules.

    And as Lara suggested, you could also open a support case.
    RAD 8.0.4.2 ( ifix1 ). It has only web modules ( just a single one ) and all modules have deployment descriptors - application.xml and web.xml - respectively.

    I see the error right at the first step, when I select the EAR file to import - it auto selects the websphere 7 runtime and gives the error.

    It doesn't even reach the EAR Module and Utility Jar projects part. And I verified that there is no .settings folder anywhere

    Opening a support case may be an option - sometimes, it takes long to get that resolved than getting answers on the forums from knowledgeable people - so I have left it as a last one.
  • adbdkb
    adbdkb
    46 Posts

    Re: Error in importing an EAR file in RAD 8 - The selected runtime does not sup

    ‏2013-04-02T16:48:19Z  
    • adbdkb
    • ‏2013-04-02T16:29:46Z
    RAD 8.0.4.2 ( ifix1 ). It has only web modules ( just a single one ) and all modules have deployment descriptors - application.xml and web.xml - respectively.

    I see the error right at the first step, when I select the EAR file to import - it auto selects the websphere 7 runtime and gives the error.

    It doesn't even reach the EAR Module and Utility Jar projects part. And I verified that there is no .settings folder anywhere

    Opening a support case may be an option - sometimes, it takes long to get that resolved than getting answers on the forums from knowledgeable people - so I have left it as a last one.
    I have attached the image of the initial error
  • SystemAdmin
    SystemAdmin
    14225 Posts

    Re: Error in importing an EAR file in RAD 8 - The selected runtime does not sup

    ‏2013-04-02T18:06:22Z  
    • adbdkb
    • ‏2013-04-02T16:48:19Z
    I have attached the image of the initial error
    I'm running out of ideas. I tried this scenario (import an EAR 1.4 with a web 2.5) and I did not get any error...Do you see exceptions in the log?

    I have one more thing to try, in case you need to have the code loaded ASAP, your EAR has only one web module, and your EAR does not have too many files other than the deployment descriptor
    1. Create an EAR 1.4 project using RAD, target it to WAS 7
    2. Using a zip utility, extract the war from the EAR
    3. Import the war file using RAD, target it to WAS 7
    4. Add the web project to the EAR using the deployment assembly page
    5. Add to the deployment descriptor of the new EAR the contents of the original EAR's deployment descriptor.

    This is just a work around, but I still suggest to call support.

    Hope this helps
  • adbdkb
    adbdkb
    46 Posts

    Re: Error in importing an EAR file in RAD 8 - The selected runtime does not sup

    ‏2013-04-03T21:25:20Z  
    I'm running out of ideas. I tried this scenario (import an EAR 1.4 with a web 2.5) and I did not get any error...Do you see exceptions in the log?

    I have one more thing to try, in case you need to have the code loaded ASAP, your EAR has only one web module, and your EAR does not have too many files other than the deployment descriptor
    1. Create an EAR 1.4 project using RAD, target it to WAS 7
    2. Using a zip utility, extract the war from the EAR
    3. Import the war file using RAD, target it to WAS 7
    4. Add the web project to the EAR using the deployment assembly page
    5. Add to the deployment descriptor of the new EAR the contents of the original EAR's deployment descriptor.

    This is just a work around, but I still suggest to call support.

    Hope this helps
    Found out another interesting thing today. Below is what I received from the person who originally asked me to help with this issue

    
    After some investigation, we discovered that the problems importing the EAR were related to the version difference between her RAD installation, and the version I have on my desktop.   The version that she has installed is 8.0.  The version that I have installed in 8.0.4.  We found there is a difference in behavior when you create a 
    
    new workspace related to the target runtime.   I have version 8.0 installed on my virtual Windows 7 machine, so I loaded up the EAR there w/o any problems (I’m talking the EAR, not the PI that you produced of the ear).  I was able to run it too.   The problem immediately below was that WAS 7 does not support web module 3.0… it had to be 2.5 or lower, but RAD 8.0.4 won’t let me change that facet… BTW, many of the other facets were also different from when you export/
    
    import the EAR from/to 8.0.   What 
    
    do you think could be happening?
    


    Any insights into differences between 8.0 and 8.0.4 or 8.0.4.2 and why it would regress - works in earlier version but not in the latest?

    Thank you
  • SystemAdmin
    SystemAdmin
    14225 Posts

    Re: Error in importing an EAR file in RAD 8 - The selected runtime does not sup

    ‏2013-04-04T14:44:23Z  
    • adbdkb
    • ‏2013-04-03T21:25:20Z
    Found out another interesting thing today. Below is what I received from the person who originally asked me to help with this issue

    <pre class="jive-pre"> After some investigation, we discovered that the problems importing the EAR were related to the version difference between her RAD installation, and the version I have on my desktop. The version that she has installed is 8.0. The version that I have installed in 8.0.4. We found there is a difference in behavior when you create a new workspace related to the target runtime. I have version 8.0 installed on my virtual Windows 7 machine, so I loaded up the EAR there w/o any problems (I’m talking the EAR, not the PI that you produced of the ear). I was able to run it too. The problem immediately below was that WAS 7 does not support web module 3.0… it had to be 2.5 or lower, but RAD 8.0.4 won’t let me change that facet… BTW, many of the other facets were also different from when you export/ import the EAR from/to 8.0. What do you think could be happening? </pre>

    Any insights into differences between 8.0 and 8.0.4 or 8.0.4.2 and why it would regress - works in earlier version but not in the latest?

    Thank you
    Are you using WTE 7 in both RAD 8.0 and 8.0.4? What version of WAS are you using? Could be a problem with the target runtime.
  • adbdkb
    adbdkb
    46 Posts

    Re: Error in importing an EAR file in RAD 8 - The selected runtime does not sup

    ‏2013-04-04T14:59:41Z  
    Are you using WTE 7 in both RAD 8.0 and 8.0.4? What version of WAS are you using? Could be a problem with the target runtime.
    I myself do not have RAD 8.0 but from the statement from the colleague who mentioned that they could pull it in I presume, theirs is WTE 7.

    In my 8.0.4.2 iFix1, as you can see from my attachment a few replies back, when I try to bring in the same EAR in my RAD, it auto selectes the WAS 7 and on the top gives the error.

    I am creating a brand new workspace before importing the EAR, and from what I understand, the target runtime is associated with or defined in the EAR I bring in ( Isn't that why it is auto selecting WAS 7 ) and RAD 8.0 doesn't have the problem.

    I am now really confused :(

    Thanks for any pointers or suggestions