Discussion of DB Connections in DSpace 6 (Hibernate) vs DSpace 5. (More=
notes at DSpace Da=
tabase Access)=20
In DSpace 5, each "Context" established a new DB connection. Context th=
en committed or aborted the connection after it was done (based on results =
of that request). Context could also be shared between methods if a s=
ingle transaction needed to perform actions across multiple methods.
In DSpace 6, Hibernate manages the DB connection pool. Each =
thread grabs a Connection from the pool. This means two Co=
ntext objects could use the same Connection (if they are in the same thread=
). In other words, code can no longer assume each new Context() is treated as a new database transaction.=20
This is what we saw in DS-3659, two separate Context objects used the s=
ame connection, and one accidentally rolled back the changes of a previous =
Context (because they were in the same thread).
High Priority (Blocker, Critical or Major) and flagged for release=
p>
key
summary
type
created
updated
assignee
reporter
priority
status
fixversions
Unable to locate J=
ira server for this macro. It may be due to Application Link configuration.=
Need Code Review, Flagged for Release
key
summary
type
created
updated
assignee
reporter
priority
status
fixversions
Unable to locate J=
ira server for this macro. It may be due to Application Link configuration.=
DSpace + Spring: Slack Discussion on whether DSpace codebase s=
hould move more towards the Spring way of doing things (e.g. Dependency Inj=
ection via beans) or the traditional DSpace patterns (e.g. classloaders wit=
h little DI).
DS-3372 and DS-3587: discussion required, should we add more SQL dialect support? MySQL, MS S=
QL? Are we ready to support, test and maintain these dialects in the future=
?=20