Bug 1012872 - Repository shutdown doesn't complete if unregistering from JNDI fails
Summary: Repository shutdown doesn't complete if unregistering from JNDI fails
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: ModeShape
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: ---
Assignee: Horia Chiorean
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-27 10:01 UTC by Horia Chiorean
Modified: 2016-02-10 08:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-10 08:55:24 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker MODE-2058 0 Major Closed Repository shutdown doesn't complete if unregistering from JNDI fails 2014-02-18 12:46:25 UTC

Description Horia Chiorean 2013-09-27 10:01:30 UTC
Comment 1 JBoss JIRA Server 2013-09-27 14:43:12 UTC 
Horia Chiorean <hchiorea> made a comment on jira MODE-2058

Fixed repository#shutdown so that when the JNDI context is read-only, the shutdown doesn't fail. Also, made Connectors & Query engine shutdown more fault-tolerant and refactored the Sequencers dependencies.
Comment 2 JBoss JIRA Server 2013-09-27 16:26:06 UTC 
Randall Hauch <rhauch> made a comment on jira MODE-2058

Rebased and merged into the 'master' branch. Leaving this issue open until the fix can be cherry-picked onto the '3.3.x-prod-ip6.0' branch.
Comment 3 Horia Chiorean 2013-10-01 08:18:24 UTC 
https://github.com/jboss-integration/modeshape/commit/b553ded5c203d357b9a5e91ebfe53e574cf8678b
Comment 8 JBoss JIRA Server 2013-10-24 09:19:00 UTC 
Randall Hauch <rhauch> updated the status of jira MODE-2058 to Closed
Comment 9 belong 2013-11-19 23:20:58 UTC 
Fixed before GA - setting to requires_doc_text- accordingly
Note You need to log in before you can comment on or make changes to this bug.