I see that this is caused by a connection reset. Is PostgreSQL logging
anything interesting around the time that this happens?
Remember that the DSpace connection limit should be a bit *lower* than the
Pg connection limit, because Pg reserves a few connections for
administration.
I found
ht
Thanks, Mark:
This hibernate stuff is a mystery to me, but I will continue digging to try
and fix my problem.
George Kozak
Cornell University
On Mon, Jan 7, 2019 at 12:07 PM Mark H. Wood wrote:
> I see that this is caused by a connection reset. Is PostgreSQL logging
> anything interesting aroun
Dear list,
Another data point in this mystery: I have just built a clean version of
DSpace 6.3 from the dspace-6.3 tag and I see the same behavior regarding
the lack of the `dspace.current.user.id` session cookie in XMLUI when
running under Tomcat 8.5.37. So it seems like it's a Tomcat configurati
Hi Alan,
I googled around for "Tomcat 8.5" and "Session Cookie" and found this:
http://tomcat.10.x6.nabble.com/cookie-related-regression-in-Tomcat-8-5-td5054371.html
At least someone else has encountered differences between how cookies are
handled in Tomcat 8.0 and 8.5. Maybe this problem is si
Hi, Mark:
In the postgres log file, I am seeing "The postmaster has commanded this
server process to roll back the current transaction and exit, because
another server process exited abnormally and possibly corrupted shared
memory." whenever this fails. I am suspecting maybe an out of memory
condi
