IBM Support

IV38983: SERVERSOCKETCHANNEL.CLOSE() DOES NOT CLOSE SOCKET AFTER APPLYING JAVA 7 SR2

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Error Message: N/A.
.
Stack Trace: N/A
.
java.nio.channels.ServerSocketChannel.close() call does not
close the socket. Even after the call to
ServerSocketChannel.close(), the network trace shows that the
native fd is still open.

Local fix

  • No work around

Problem summary

  • The socket channel close path is bypassed on certain conditions.

Problem conclusion

  • This defect will be fixed in:
7.0.0 SR5
.
The JDK has been updated to ensure the socket channel close on
all the conditions.

Temporary fix

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    IV38983
    • 

  • Reported component name
    JAVA CLASS LIBS
    • 

  • Reported component ID
    620700130
    • 

  • Reported release
    700
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt
    • 

  • Submitted date
    2013-03-29
    • 

  • Closed date
    2013-05-15
    • 

  • Last modified date
    2013-07-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
    JAVA CLASS LIBS
    • 

  • Fixed component ID
    620700130
    • 



Applicable component levels


    

  • R700  PSY
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            21 February 2022
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback