PK83749: VISUALAGE GENERATOR APPLICATION GENERATED IN JAVA DOES NOT CLOSE DB2 CONNECTIONS PROPERLY

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • Customer generated an Java application, and when running it
    using WebSphere Application Server and VisualAge Generator
    runtime.
    She is able to monitor db2 connections using list applications
    command and sees that after EZECOMIT and EZECLOS the connections
    to db2 remains active.
    Here we have a sample.
    
    1) before app execution>
    db2admin@serv0997linux:~> db2 list applications
    SQL1611W  No data was returned by Database System Monitor.
    SQLSTATE=00000
    
    2) after app execution>
    db2admin@serv0997linux:~> db2 list applications
    
    Auth Id  Application    Appl.      Application Id
    DB
    # of
             Name           Handle
    Name
    Agents
    -------- -------------- ----------
    ------------------------------
    -------- -----
    PRUSRLJ  java           1016       *LOCAL.db2admin.090309210122
    LOJA
    1
    PRUSRLJ  java           1026       *LOCAL.db2admin.090309210106
    LOJA
    1
    PRUSRLJ  java           1018       *LOCAL.db2admin.090309210052
    LOJA
    1
    

Local fix

Problem summary

  • Customer generated an Java application, and when running it
    using WebSphere Application Server and VisualAge Generator
    runtime.
    She is able to monitor db2 connections using list applications
    command and sees that after EZECOMIT and EZECLOS the connections
    to db2 remains active.
    Here we have a sample.
    1) before app execution>
    db2admin@serv0997linux: > db2 list applications
    SQL1611W  No data was returned by Database System Monitor.
    SQLSTATE=00000
    
    2) after app execution>
    db2admin@serv0997linux: > db2 list applications
    
    Auth Id  Application    Appl.      Application Id
    DB
    # of
             Name           Handle
    Name
    Agents
    PRUSRLJ  java           1016       *LOCAL.db2admin.090309210122
    LOJA
    1
    PRUSRLJ  java           1026       *LOCAL.db2admin.090309210106
    LOJA
    1
    

Problem conclusion

Temporary fix

  • It was determined that the Java source code in Vagen that
    handles closing DB2 connections was not functioning
    properly. A change was made to correct the closing
    functionality, then testing performed to show the problem
    had been resolved.
    The JAR file was rebuilt and sent to the customer for
    testing.
    The JAR file is available on request to resolve this
    problem if other customers report it.
    

Comments

APAR Information

  • APAR number

    PK83749

  • Reported component name

    VA GEN DEVELOPE

  • Reported component ID

    5697G9806

  • Reported release

    450

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-03-31

  • Closed date

    2009-06-16

  • Last modified date

    2009-06-16

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

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

Fix information

Applicable component levels

  • R450 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

VisualAge Generator

Software version:

4.5

Reference #:

PK83749

Modified date:

2009-06-16

Translate my page

Machine Translation

Content navigation