Title: Message Title
|
|
|
|
The context is being stored in a private STATIC member variable in the ItemsResource class (and probably the others too - I haven't checked).
This means that it will create it once, and never let it go.
Even removing the STATIC probably won't help - it's being wired through Spring, which typically only creates a single instance of the object when processing the configuration. Which puts it in the same class as webapp servlets - also, only a single instance is ever constructed for those too.
These objects/methods really should be re-entrant. So no member variables - apart from static instances to loggers and other things that you deliberately know need to persist over multiple calls. Everything should be passed as parameters.
This is particularly true for contexts / transactions that demarcate units of work. Apart from rare circumstances, these should always be passed in to method calls.
|
|
|
|
|
|
|
REST API (Jersey), grabs a context, and never frees/returns/releases it. I don't know exactly what is going on, but it causes the REST API to not be able to reflect real-time updates to content.
To repeat. Load a DSpace-REST result for some endpoint. Edit the title/name of the first object returned in that result. Reload the REST endpoint. For me, the...
|
|
|
|
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
