PI93596: SNAPSHOTS CLEANUP FAILS WITH CORRESPONDING HIBERNATE WARNINGS INDEPLOYSERVER.OUT

APAR status

• Closed as program error.

Error description

• Snapshot cleanup will fail silently with no exceptions noted in
  deployerserver.out or cleanup.log.
  
  The cleanup thread is exiting in the middle of cleanup, and at
  that time the following hibernate warnings are noted in
  deployserver.out:
  
  AEDT WARN  AsynEventService-7
  org.hibernate.engine.loading.LoadContexts - fail-safe cleanup
  (collections) :
  org.hibernate.engine.loading.CollectionLoadContext@1bbdd73e<rs=c
  om.mchange.v2.c3p0.impl.NewProxyResultSet@7f1904e3>
  WARN  AsynEventService-7
  org.hibernate.engine.loading.LoadContexts - fail-safe cleanup
  (collections) :
  org.hibernate.engine.loading.CollectionLoadContext@1bbdd73e<rs=c
  om.mchange.v2.c3p0.impl.NewProxyResultSet@7f1904e3>
  WARN  AsynEventService-7
  org.hibernate.engine.loading.CollectionLoadContext - On
  CollectionLoadContext#cleanup, localLoadingCollectionKeys
  contained [1] entries
  
  If snapshot cleanup fails artifact cleanup will not start since
  the cleanup thread has terminated
  

Local fix

• Disable snapshot cleanup to ensure artifact cleanup still occurs
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All end users on all supported browsers.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Snapshot cleanup will fail silently with no exceptions noted *
  * in                                                           *
  * deployerserver.out or cleanup.log.                           *
  *                                                              *
  * The cleanup thread is exiting in the middle of cleanup, and  *
  * at                                                           *
  * that time the following hibernate warnings are noted in      *
  * deployserver.out:                                            *
  *                                                              *
  * AEDT WARN  AsynEventService-7                                *
  * org.hibernate.engine.loading.LoadContexts - fail-safe        *
  * cleanup                                                      *
  * (collections) :                                              *
  * org.hibernate.engine.loading.CollectionLoadContext@1bbdd73e< *
  * rs=c                                                         *
  * om.mchange.v2.c3p0.impl.NewProxyResultSet@7f1904e3>          *
  * WARN  AsynEventService-7                                     *
  * org.hibernate.engine.loading.LoadContexts - fail-safe        *
  * cleanup                                                      *
  * (collections) :                                              *
  * org.hibernate.engine.loading.CollectionLoadContext@1bbdd73e< *
  * rs=c                                                         *
  * om.mchange.v2.c3p0.impl.NewProxyResultSet@7f1904e3>          *
  * WARN  AsynEventService-7                                     *
  * org.hibernate.engine.loading.CollectionLoadContext - On      *
  * CollectionLoadContext#cleanup, localLoadingCollectionKeys    *
  * contained [1] entries                                        *
  *                                                              *
  * If snapshot cleanup fails artifact cleanup will not start    *
  * since                                                        *
  * the cleanup thread has terminated                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Fixed in version 6.2.7.2                                     *
  ****************************************************************
  

Problem conclusion

• Fix is provided in IBM UrbanCode Deploy 6.2.7.2
  

Temporary fix

Comments

APAR Information

• 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

  UC DEPLOY

• Fixed component ID

  5725M5400

Applicable component levels