Group
Subject: Re: [Archivesspace_Users_Group] Java error -
Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3
Many thanks Megan for the lead. I just poked around and found a few things out.
It turns out to be interesting in at least three bad ways.
1. User records are updated every t
s_group-boun...@lyralists.lyrasis.org>> on behalf
> of Tom Hanstra mailto:hans...@nd.edu>>
> Sent: Monday, March 15, 2021 9:10 AM
> To: Archivesspace Users Group
> <mailto:archivesspace_users_group@lyralists.lyrasis.org>>
> Subject: Re: [Archivesspace_Users_Gro
ubject: Re: [Archivesspace_Users_Group] Java error -
Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3
Oh gee, I’ve seen that horror. And, yes, it is caused by records having times
in that non-existent hour. From memory the only fix I could find was to delete
the offending rows, or update their times.
asis.org <
> archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of Tom
> Hanstra
> *Sent:* Monday, March 15, 2021 9:10 AM
> *To:* Archivesspace Users Group <
> archivesspace_users_group@lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Gro
up
Subject: Re: [Archivesspace_Users_Group] Java error -
Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3
Any suggestion on what ArchivesSpace might have changed? I had the server
running but indexing was complete. What might it have been changing and in what
database table would I lo
yralists.lyrasis.org> on behalf of
> James Bullen
> *Sent:* Sunday, March 14, 2021 11:04 PM
> *To:* Archivesspace Users Group <
> archivesspace_users_group@lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] Java error -
> Java::JavaSql::SQLException: HOU
Oh gee, I’ve seen that horror. And, yes, it is caused by records having times
in that non-existent hour. From memory the only fix I could find was to delete
the offending rows, or update their times.
Cheers,
James
> On Mar 15, 2021, at 1:59 PM, Tom Hanstra wrote:
>
> I don't seem to be
I don't seem to be able to win with ArchivesSpace.
After having indexing again finally give up because of another Java heap
error, I restarted archivesspace again with some different java settings. I
believe it actually got through the indexing, at least of the first
repository.
But tonight,
