Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332937 - JNDI lifecycles
Summary: JNDI lifecycles
Status: RESOLVED FIXED
Alias: None
Product: Jetty
Classification: RT
Component: server (show other bugs)
Version: 7.2.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 7.1.x   Edit
Assignee: Greg Wilkins CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-20 06:58 EST by Greg Wilkins CLA
Modified: 2011-01-10 07:38 EST (History)
1 user (show)

See Also:

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

Note You need to log in before you can comment on or make changes to this bug.
Description Greg Wilkins CLA 2010-12-20 06:58:57 EST 
We need to improve the lifecycle of JNDI resources, with respect to multiple start/stop cycles and or redeployment of contexts.

Currently JNDI entries in context.xml files are getting deployed multiple times and not necessarily cleaned up.

There is also manual code in the tests to stop Atomikos datasources.

Replace this with a generic Destroyable interface and cleanup associated JNDI lifecycles.
Comment 1 Greg Wilkins CLA 2011-01-10 07:38:41 EST 
Destroyable has been added.