1 Reply Latest reply on Dec 22, 2009 8:33 PM by Adam Bowen

    BL App Server Log Warnings: User session did not properly release a database connection

    S Crawford

      We recently migrated our core database SAN storage to a newer subsystem, which was a seamless process.  However, when this happened, these warning messages starting populating the ConfigAppServer logs on one of our 2 app servers:

       

      [22 Dec 2009 20:52:08,233] [Client-Connections-Thread-2] [WARN] [Client] User session did not properly release a database connection.
      [22 Dec 2009 20:52:08,323] [Client-Connections-Thread-14] [WARN] [Client] User session did not properly release a database connection.
      [22 Dec 2009 20:52:13,215] [Client-Connections-Thread-17] [WARN] [Client] User session did not properly release a database connection.
      [22 Dec 2009 20:52:13,357] [Client-Connections-Thread-36] [WARN] [Client] User session did not properly release a database connection.
      [22 Dec 2009 20:52:17,431] [Client-Connections-Thread-45] [WARN] [Client] User session did not properly release a database connection.
      [22 Dec 2009 20:52:18,288] [Client-Connections-Thread-8] [WARN] [Client] User session did not properly release a database connection.

      They only went away once the app server was recycled.  Are these warnings typical when the app server temporarily loses connection with the DB?  Trying to determine if the SAN migration caused this to happen or not.  What are the risks of not dealing with these warning msgs?