IBM Support

PI27366: NEED TO THROW NAMENOTFOUNDEXCEPTION FOR INVALID NAMES FOR PARITY WITH FULL PROFILE

Fixes are available

8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • APAR PM70014 revealed that the Liberty profile had a different
behavior than full profile when performing lookups of JNDI names
that were not in the valid java:<namespace> namespaces. In full
profile,  a NameNotFoundException was thrown, while in Liberty
profile an InvalidNameException was thrown.
.
Under PM70014 the code was updated to resolve the reported
problem for a lookup of "java:/jdbc/name" to throw a
NameNotFoundException instead of an InvalidNameException.
.
However, to make the minimum necessary change an additional
problem of a really invalid name being looked up was not
resolved under that APAR.
.
If you lookup "java:/\"jbdc/name" in full profile you get a
NameNotFoundException, if you lookup the same in the Liberty
profile you get an InvalidNameException. Instead, the Liberty
profile ought to wrap the InvalidNameException and throw a
NameNotFoundException.

Local fix

  • 



Problem summary


    

  • ****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty Profile who also use Full    *
*                  Profile                                     *
****************************************************************
* PROBLEM DESCRIPTION: Need to throw NameNotFoundException for *
*                      invalid names not InvalidNameException  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
APAR PM70014 revealed that the Liberty profile had different
behavior than full profile  when performing lookups of JNDI
names that were not in the valid java:<namespace> namespaces. In
full profile  a NameNotFoundException was thrown, while in
Liberty profile an InvalidNameException was thrown.

Under
PM70014 the code was updated to resolve the reported problem for
a lookup of "java:/jdbc/name" to throw a NameNotFoundException
instead of an InvalidNameException.

However, to make the
minimum necessary change an additional problem of a really
invalid name being looked up was not resolved under that
APAR.

If you lookup "java:/\"jbdc/name" in full profile you get
a NameNotFoundException, if you lookup the same in the Liberty
profile you get an InvalidNameException. Instead, the Liberty
profile ought to wrap the InvalidNameException and throw a
NameNotFoundException.

    



Problem conclusion


    

  • The fix for this APAR correctly throws the NameNotFoundException
with a wrapped InvalidNameException where appropriate.  The
behavior now matches the behavior in WebSphere Application
Server Full Profile.

The fix for this APAR is currently
targeted for inclusion in fix pack 8.5.5.4.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

    



Temporary fix


    

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    PI27366
    • 

  • Reported component name
    WAS LIBERTY COR
    • 

  • Reported component ID
    5725L2900
    • 

  • Reported release
    855
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2014-10-10
    • 

  • Closed date
    2014-10-17
    • 

  • Last modified date
    2014-11-11
    • 





    

  • 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
    WAS LIBERTY COR
    • 

  • Fixed component ID
    5725L2900
    • 



Applicable component levels


    

  • R855  PSY
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB45","label":"Automation"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            28 April 2022
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback