Locks Held, Threads Continue to Run, Memory is Leaked After Application Undeploy in Weblogic
Last updated on DECEMBER 22, 2016
Applies to:Oracle Commerce Platform - Version 220.127.116.11 and later
Information in this document applies to any platform.
The following thread types remain running in the Application Container's JVM after undeploying the application's EAR file.
You may also notice that ServerLockManager's lock table still shows write locks owned by the instance whose application was undeployed
The undeployed application's JVM will leak memory, file descriptors and network ports every time the application EAR is undeployed/redeployed.
After Undeploying an Oracle Commerce Application's EAR file in WebLogic you see various symptoms described above.
You may be using WebLogic Hot Deployment.
You may be using Side-by-Side Deployment.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms