[MGNLXAA-72] Force closing of connection after finishing activation Created: 24/Sep/13  Updated: 25/Oct/13  Resolved: 23/Oct/13

Status: Closed
Project: Transactional Activation
Component/s: None
Affects Version/s: 1.3
Fix Version/s: 1.3.9, 2.0.1

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:
Relates
relates to MAGNOLIA-5331 Force closing of connection upon fini... Closed
relates to MGNLACTIVATION-41 CLONE - Force closing of connection u... Closed
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: 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 [ 23/Oct/13 ]

already merged on 1.3.x branch, but waiting with merge on master until after 5.1.1. release.

Generated at Mon Feb 12 11:06:47 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.