IBM Support

PM58222: Clicking on a resource reference in the EJB 2.x deployment descriptor editor may result in a java.lang.StackOverflowError

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Abstract:
    
    Attempts to click on certain types of Resource References (e.g.
    IMS connection factories) in the EJB 2.x Deployment descriptor
    Editor may result in a java.lang.StackOverflowError.
    
    Problem:
    
    The workspace .metadata/.log file will contain the following
    error:
    
    !ENTRY org.eclipse.ui 4 0 2012-02-08 19:00:21.551
    !MESSAGE Unhandled event loop exception
    !STACK 0
    java.lang.StackOverflowError
        at org.eclipse.emf.common.util.URI.equals(URI.java:1584)
        at java.util.HashMap.areEqualKeys(HashMap.java:880)
        at java.util.HashMap.findNonNullKeyEntry(HashMap.java:527)
        at java.util.HashMap.getEntry(HashMap.java:512)
        at java.util.HashMap.get(HashMap.java:498)
        at
    org.eclipse.jem.internal.util.emf.workbench.ProjectResourceSetIm
    pl.getResource(ProjectResourceSetImpl.java:1002)
        at
    com.ibm.ejs.models.base.bindings.commonbnd.AbstractTraversalHelp
    er.getBindingOrExtensionInExistingResource(AbstractTraversalHelp
    er.java:168)
        at
    com.ibm.ejs.models.base.bindings.commonbnd.AbstractTraversalHelp
    er.getBindingOrExtension(AbstractTraversalHelper.java:106)
        at
    com.ibm.ejs.models.base.bindings.commonbnd.CommonBindingsHelper.
    getBinding(CommonBindingsHelper.java:27)
        at
    com.ibm.ejs.models.base.bindings.ejbbnd.EJBBindingsHelper.getEJB
    JarBinding(EJBBindingsHelper.java:66)
        at
    com.ibm.ejs.models.base.bindings.ejbbnd.EJBBindingsHelper.getEjb
    Binding(EJBBindingsHelper.java:40)
        at
    com.ibm.etools.common.ui.ws.ext.JNDIBindingDetailSection.getEJBB
    indingForReferenceObject(JNDIBindingDetailSection.java:200)
        at
    com.ibm.etools.common.ui.ws.ext.ResourceRefBindingDetailControl.
    getResourceRefBinding(ResourceRefBindingDetailControl.java:694)
        at
    com.ibm.etools.common.ui.ws.ext.ResourceRefBindingDetailControl.
    getRefBindingObject(ResourceRefBindingDetailControl.java:659)
        at
    com.ibm.etools.common.ui.ws.ext.ResourceRefBindingDetailControl.
    addAdapterToResRefBinding(ResourceRefBindingDetailControl.java:2
    74)
        at
    com.ibm.etools.common.ui.ws.ext.ResourceRefBindingDetailControl.
    createResourceRefBinding(ResourceRefBindingDetailControl.java:74
    4)
    ...
    
    Once a workspace is corrupted it appears that it can not be
    fixed.
    
    Local fix:
    
    The work-around is to move the source folder containing the
    deployment descriptors to be the first listed folder in the
    project meta-data file:
    .settings/org.eclipse.wst.common.component. In this example the
    /src/main/resources folder has the EJB deployment descriptors.
    
    Broken configuration:
    
    ??xml version='1.0' encoding='UTF-8'??
    ?project-modules id='moduleCoreId' project-version='1.5.0'?
        ?wb-module deploy-name='MyEJB'?
            ?wb-resource deploy-path='/'
    source-path='/src/main/java'/?
            ?wb-resource deploy-path='/'
    source-path='/src/main/resources' tag='defaultRootSource'/?
            ?property name='java-output-path'
    value='/MyEJB/target/classes'/?
        ?/wb-module?
    ?/project-modules?
    
    
    Fixed configuration:
    
    ??xml version='1.0' encoding='UTF-8'??
    ?project-modules id='moduleCoreId' project-version='1.5.0'?
      ?wb-module deploy-name='MyEJB'?
            ?wb-resource deploy-path='/'
    source-path='/src/main/resources' tag='defaultRootSource'/?
            ?wb-resource deploy-path='/'
    source-path='/src/main/java'/?
            ?property name='java-output-path'
    value='/MyEJB/target/classes'/?
      ?/wb-module?
    ?/project-modules?
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This occurs if you have multiple non-standard deploy-path
    source folders and the first folder listed in the project
    meta-data file (.settings/org.eclipse.wst.common.component)
    is not the one containing the deployment descriptors files.
    This multiple source folder structure is typical of a Maven
    project.
    

Problem conclusion

  • This issue is fixed in Rational Application Developer
    v8.0.4.1.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM58222

  • Reported component name

    RATL APP DEV WI

  • Reported component ID

    5724J1901

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-02-14

  • Closed date

    2012-05-15

  • Last modified date

    2012-05-15

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    RATL APP DEV WI

  • Fixed component ID

    5724J1901

Applicable component levels

  • R801 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSRTLW","label":"Rational Application Developer for WebSphere Software"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 May 2012