[MAGNOLIA-5331] Force closing of connection upon finishing activation Created: 24/Sep/13  Updated: 25/Oct/13  Resolved: 22/Oct/13

Status: Closed
Project: Magnolia
Component/s: activation
Affects Version/s: 4.5
Fix Version/s: 4.5.13

Type: Bug Priority: Neutral
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Solaris


Issue Links:
Cloners
is cloned by MGNLACTIVATION-41 CLONE - Force closing of connection u... Closed
Relates
relates to MGNLXAA-72 Force closing of connection after fin... Closed
causality
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: Support
Sprint: 5.1 - Final, 4.5.13

 Description   

While under normal circumstances connection is managed and released fast enough by server/jvm, certain JVM implementations (Oracle JVM 7 for Solaris) doesn't do so. To help ensure proper release of resources Magnolia should for releasing the connection.

Performed tests on OSX, CentOS and Ubuntu didn't confirm this issue in other platforms.



 Comments   
Comment by Jan Haderka [ 22/Oct/13 ]

check fix on magnolia-4.5.x-MAGNOLIA-5331-2 branch pls.

Generated at Mon Feb 12 04:04:08 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.